.changelog-archive/CHANGELOG.06.md
diff and percent_diff to not always be absolute. Something we introduced by mistake in 6.1.0. Alerting now support diff(), diff_abs(), percent_diff() and percent_diff_abs(). #21338In our mission to migrate away from AngularJS to React we have removed all AngularJS dependencies in the core data retrieval service backendSrv.
Removing the AngularJS dependencies in backendSrv has the unfortunate side effect of AngularJS digest no longer being triggered for any request made with backendSrv. Because of this, external plugins using backendSrv directly may suffer from strange behaviour in the UI.
To remedy this issue, as a plugin author you need to trigger the digest after a direct call to backendSrv.
Example:
backendSrv.get(‘http://your.url/api’).then(result => {
this.result = result;
this.$scope.$digest();
});
Another unfortunate outcome from this work in backendSrv is that the response format for .headers() changed from a function to an object.
To make your plugin work on 6.7.x as well as on previous versions you should add something like the following:
let responseHeaders = response.headers;
if (!responseHeaders) {
return null;
}
// Support pre 6.7 angular HTTP rather than fetch
if (typeof responseHeaders === 'function') {
responseHeaders = responseHeaders();
}
You can test your plugin with the master branch version of Grafana.
payload.custom_details field in PagerDuty notification to be a JSON object instead of a string.[security] setting cookie_samesite configured to none now renders cookies with SameSite=None attribute compared to before where no SameSite attribute was added to cookies. To get the old behavior, use value disabled instead of none. Refer to Upgrade Grafana for more information./**@ngInject*/. #20696, @hugohaggmarkCloudWatch: Pre Grafana 6.5.0, the CloudWatch datasource used the GetMetricStatistics API for all queries that did not have an ´id´ and did not have an ´expression´ defined in the query editor. The GetMetricStatistics API has a limit of 400 transactions per second. In this release, all queries use the GetMetricData API. The GetMetricData API has a limit of 50 transactions per second and 100 metrics per transaction. For API pricing information, please refer to the CloudWatch pricing page (https://aws.amazon.com/cloudwatch/pricing/).
CloudWatch: The GetMetricData API does not return metric unit, so unit auto detection in panels is no longer supported.
CloudWatch: The HighRes switch has been removed from the query editor. Read more about this in upgrading to 6.5.
CloudWatch: In previous versions of Grafana, there was partial support for using multi-valued template variables as dimension values. When a multi-valued template variable is being used for dimension values in Grafana 6.5, a search expression will be generated. In the GetMetricData API, expressions are limited to 1024 characters, so you might reach this limit if you are using a large number of values. Read our upgrading to 6.5 guide to see how you can use the * wildcard for this use case.
createdAt and updatedAt to api/users/lookup. #19496, @gotjoshCloudWatch: Pre Grafana 6.5.0, the CloudWatch datasource used the GetMetricStatistics API for all queries that did not have an ´id´ and did not have an ´expression´ defined in the query editor. The GetMetricStatistics API has a limit of 400 transactions per second. In this release, all queries use the GetMetricData API. The GetMetricData API has a limit of 50 transactions per second and 100 metrics per transaction. For API pricing information, please refer to the CloudWatch pricing page (https://aws.amazon.com/cloudwatch/pricing/).
CloudWatch: The GetMetricData API does not return metric unit, so unit auto detection in panels is no longer supported.
CloudWatch: The HighRes switch has been removed from the query editor. Read more about this in upgrading to 6.5.
CloudWatch: In previous versions of Grafana, there was partial support for using multi-valued template variables as dimension values. When a multi-valued template variable is being used for dimension values in Grafana 6.5, a search expression will be generated. In the GetMetricData API, expressions are limited to 1024 characters, so you might reach this limit if you are using a large number of values. Read our upgrading to 6.5 guide to see how you can use the * wildcard for this use case.
The MySQL data source connection string fix, #20192, that was part of this release also fixed a security vulnerability. Thanks Yuriy Dyachenko for discovering and notifying us about this.
There are some breaking changes in the annotations HTTP API for region annotations. Region annotations are now represented using a single event instead of two separate events. Check breaking changes in HTTP API below and HTTP API documentation for more details.
Grafana is now using Alpine 3.10 as docker base image.
GET /api/alert-notifications now requires at least editor access. New /api/alert-notifications/lookup returns less information than /api/alert-notifications and can be access by any authenticated user.GET /api/alert-notifiers now requires at least editor accessGET /api/org/users now requires org admin role. New /api/org/users/lookup returns less information than /api/org/users and can be access by users that are org admins, admin in any folder or admin of any team.GET /api/annotations no longer returns regionId property.POST /api/annotations no longer supports isRegion property.PUT /api/annotations/:id no longer supports isRegion property.PATCH /api/annotations/:id no longer supports isRegion property.DELETE /api/annotations/region/:id has been removed.PhantomJS, which is used for rendering images of dashboards and panels, is deprecated and will be removed in a future Grafana release. A deprecation warning will from now on be logged when Grafana starts up if PhantomJS is in use.
Please consider migrating from PhantomJS to the Grafana Image Renderer plugin.
grafana-cli within RPM/DEB packages and config/homepath are now global flags. #17695, @gotjosh--pluginsDir is not working.GF_INSTALL_PLUGINS environment variable. We have removed 6.2.3 tag from docker hub and latest tag now points to 6.2.2.More details in bug report: https://github.com/grafana/grafana/issues/17613
5 months ago we deprecated our old package cloud repository and replaced it with our own. We will remove the old depreciated repo on July 1st. Make sure you have switched to the new repo by then. The new repository has all our old releases so you are not required to upgrade just to switch package repository.
=. #16521, @DanCechms and s. #16455, @torkelod l toggles all Graph legends in a dashboard. #15770, @jsferreiMiddle bucket bound option #15683Reverse order option for changing order of buckets #15683resource_arns template variable query function #8207, thx @jeroenvollenbrocktz) clause #10322, thx @cykl$__from and $__to, #1909$__unixEpochNanoFilter, $__unixEpochNanoFrom, $__unixEpochNanoTo) #14711, thx @ander26Min width changed to Max per row for repeating panels. This lets you specify the maximum number of panels to show per row and by that repeated panels will always take up full width of row #12991, thx @pgiraudurl property in database settings #14709, thx @tpetrdisable_sanitize_html under the section [panels] in your Grafana ini file, or set env variable GF_PANELS_DISABLE_SANITIZE_HTML=true.minSpan replaced by maxPerRow. Dashboard migration will automatically migrate all dashboard panels using the minSpan property to the new maxPerRow property #12991For older release notes, refer to the CHANGELOG_ARCHIVE.md