Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
N
nexpie-grafana-theme
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Registry
Registry
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kornkitt Poolsup
nexpie-grafana-theme
Commits
e86fe0b1
Commit
e86fe0b1
authored
Feb 05, 2018
by
Marcus Efraimsson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs: update dashboard model, new url structure and api changes in what's new in v5
parent
b2f62ae1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
6 deletions
+13
-6
docs/sources/guides/whats-new-in-v5.md
+13
-6
No files found.
docs/sources/guides/whats-new-in-v5.md
View file @
e86fe0b1
...
...
@@ -111,10 +111,17 @@ in sync with dashboards in Grafana's database. The dashboard provisioner has mul
which makes it possible to star them, use one as the home dashboard, set permissions and other features in Grafana that
expects the dashboards to exist in the database. More info in the
[
dashboard provisioning docs
](
/administration/provisioning/#dashboards
)
# Dashboard model
& API
# Dashboard model
, new url structure & API changes
We are introducing a new identifier (
`uid`
) in the dashboard JSON model. The new identifier will be a 9-12 character long unique id.
We are also changing the route for getting dashboards to use this
`uid`
instead of the slug that the current route and API are using.
We will keep supporting the old route for backward compatibility. This will make it possible to change the title on dashboards without breaking links.
Sharing dashboards between instances becomes much easier since the uid is unique (unique enough). This might seem like a small change,
but we are incredibly excited about it since it will make it much easier to manage, collaborate and navigate between dashboards.
We are introducing a new unique identifier (
`uid`
) in the dashboard JSON model. It's automatically
generated if not provided when creating a dashboard and will have a length of 9-12 characters.
The unique identifier allows having consistent URL's for accessing dashboards and sharing them
between instances. The new routes and API's for accessing dashboards will use the
`uid`
instead
of the
`slug`
. We'll keep supporting the old routes for accessing dashboards for backward
compatibility, but please note that we'll deprecate the old slug-based routes in the future.
This means that changing the title of dashboards will not break any bookmarked links.
Sharing dashboards between instances becomes much easier since the
`uid`
is unique (unique enough).
This might seem like a small change, but we are incredibly excited about it since it will make it
much easier to manage, collaborate and navigate between dashboards.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment