|
|
@@ -12,6 +12,8 @@ weight = -6
|
|
|
|
|
|
# What's New in Grafana v5.0
|
|
|
|
|
|
+> Out in beta: [Download now!](https://grafana.com/grafana/download/5.0.0-beta1)
|
|
|
+
|
|
|
This is the most substantial update that Grafana has ever seen. This article will detail the major new features and enhancements.
|
|
|
|
|
|
- [New Dashboard Layout Engine]({{< relref "#new-dashboard-layout-engine" >}}) enables a much easier drag, drop and resize experience and new types of layouts.
|
|
|
@@ -22,10 +24,12 @@ This is the most substantial update that Grafana has ever seen. This article wil
|
|
|
- [Group users into teams]({{< relref "#teams" >}}) and use them in the new permission system.
|
|
|
- [Datasource provisioning]({{< relref "#data-sources" >}}) makes it possible to setup datasources via config files.
|
|
|
- [Dashboard provisioning]({{< relref "#dashboards" >}}) makes it possible to setup dashboards via config files.
|
|
|
+- [Persistent dashboard url's]({{< relref "#dashboard-model-persistent-url-s-and-api-changes" >}}) makes it possible to rename dashboards without breaking links.
|
|
|
+- [Graphite Tags & Integrated Function Docs]({{< relref "#graphite-tags-integrated-function-docs" >}}).
|
|
|
|
|
|
### Video showing new features
|
|
|
|
|
|
-<iframe height="215" src="https://www.youtube.com/embed/BC_YRNpqj5k?rel=0&showinfo=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
|
|
+<iframe width="450" height="270" src="https://www.youtube.com/embed/Izr0IBgoTZQ?rel=0&" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
|
|
<br />
|
|
|
|
|
|
## New Dashboard Layout Engine
|
|
|
@@ -36,7 +40,7 @@ The new dashboard layout engine allows for much easier movement and sizing of pa
|
|
|
a very intuitive way. Panels are sized independently, so rows are no longer necessary to create layouts. This opens
|
|
|
up many new types of layouts where panels of different heights can be aligned easily. Checkout the new grid in the video
|
|
|
above or on the [play site](http://play.grafana.org). All your existing dashboards will automatically migrate to the
|
|
|
-new position system and look close to identical. The new panel position makes dashboards saved in v5.0 not compatible
|
|
|
+new position system and look close to identical. The new panel position makes dashboards saved in v5.0 incompatible
|
|
|
with older versions of Grafana.
|
|
|
|
|
|
<div class="clearfix"></div>
|
|
|
@@ -49,7 +53,7 @@ Almost every page has seen significant UX improvements. All pages (except dashbo
|
|
|
|
|
|
<div class="clearfix"></div>
|
|
|
|
|
|
-### Dashboard Settings
|
|
|
+## Dashboard Settings
|
|
|
|
|
|
{{< docs-imagebox img="/img/docs/v50/dashboard_settings.png" max-width="1000px" class="docs-image--right" >}}
|
|
|
Dashboard pages have a new header toolbar where buttons and actions are now all moved to the right. All the dashboard
|
|
|
@@ -61,7 +65,7 @@ settings views have been combined with a side nav which allows you to easily mov
|
|
|
|
|
|
{{< docs-imagebox img="/img/docs/v50/new_white_theme.png" max-width="1000px" class="docs-image--right" >}}
|
|
|
|
|
|
-This theme has not seen a lot of love in recent years and we felt it was time to rework it and give it a major overhaul. We are very happy with the result.
|
|
|
+This theme has not seen a lot of love in recent years and we felt it was time to give it a major overhaul. We are very happy with the result.
|
|
|
|
|
|
<div class="clearfix"></div>
|
|
|
|
|
|
@@ -78,22 +82,26 @@ which is very useful if you have a lot of dashboards or multiple teams.
|
|
|
|
|
|
## Teams
|
|
|
|
|
|
-A team is a new concept in Grafana v5. They are simply a group of users that can be then be used in the new permission system for dashboards and folders. Only an admin can create teams.
|
|
|
+A team is a new concept in Grafana v5. They are simply a group of users that can be used in the new permission system for dashboards and folders. Only an admin can create teams.
|
|
|
We hope to do more with teams in future releases like integration with LDAP and a team landing page.
|
|
|
|
|
|
## Permissions
|
|
|
|
|
|
{{< docs-imagebox img="/img/docs/v50/folder_permissions.png" max-width="1000px" class="docs-image--right" >}}
|
|
|
|
|
|
-You can assign permissions to folders and dashboards. The default user role-based permissions can be removed and replaced with specific teams or users enabling more control over what a user can see and edit.
|
|
|
+You can assign permissions to folders and dashboards. The default user role-based permissions can be removed and
|
|
|
+replaced with specific teams or users enabling more control over what a user can see and edit.
|
|
|
+
|
|
|
+Dashboard permissions only limits what dashboards & folders a user can view & edit not which
|
|
|
+data sources a user can access nor what queries a user can issue.
|
|
|
|
|
|
<div class="clearfix"></div>
|
|
|
|
|
|
-# Provisioning from configuration
|
|
|
+## Provisioning from configuration
|
|
|
|
|
|
In previous versions of Grafana, you could only use the API for provisioning data sources and dashboards.
|
|
|
But that required the service to be running before you started creating dashboards and you also needed to
|
|
|
-set up credentials for the HTTP API. In 5.0 we decided to improve this experience by adding a new active
|
|
|
+set up credentials for the HTTP API. In v5.0 we decided to improve this experience by adding a new active
|
|
|
provisioning system that uses config files. This will make GitOps more natural as data sources and dashboards can
|
|
|
be defined via files that can be version controlled. We hope to extend this system to later add support for users, orgs
|
|
|
and alerts as well.
|
|
|
@@ -111,10 +119,36 @@ 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
|
|
|
|
|
|
-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.
|
|
|
+## Graphite Tags & Integrated Function Docs
|
|
|
+
|
|
|
+{{< docs-imagebox img="/img/docs/v50/graphite_tags.png" max-width="1000px" class="docs-image--right" >}}
|
|
|
+
|
|
|
+The Graphite query editor has been updated to support the latest Graphite version (v1.2) that adds
|
|
|
+many new functions and support for querying by tags. You can now also view function documentation right in the query editor!
|
|
|
+
|
|
|
+Read more on [Graphite Tag Support](http://graphite.readthedocs.io/en/latest/tags.html?highlight=tags).
|
|
|
+
|
|
|
+<div class="clearfix"></div>
|
|
|
+
|
|
|
+## Dashboard model, persistent url's and API changes
|
|
|
+
|
|
|
+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 persistent URL's for accessing dashboards, sharing them
|
|
|
+between instances and when using [dashboard provisioning](#dashboards). This means that dashboard can
|
|
|
+be renamed without breaking any links. We're changing the url format for dashboards
|
|
|
+from `/dashboard/db/:slug` to `/d/:uid/:slug`. We'll keep supporting the old slug-based url's for dashboards
|
|
|
+and redirects to the new one for backward compatibility. Please note that the old slug-based url's
|
|
|
+have been deprecated and will be removed in a future release.
|
|
|
+
|
|
|
+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.
|
|
|
+
|
|
|
+### API changes
|
|
|
+New uid-based routes in the dashboard API have been introduced to retrieve and delete dashboards.
|
|
|
+The corresponding slug-based routes have been deprecated and will be removed in a future release.
|
|
|
+
|
|
|
+
|