Menu
Documentationbreadcrumb arrow Grafana documentationbreadcrumb arrow Release notesbreadcrumb arrow Release notes for Grafana 8.5.4
Grafana Cloud Enterprise Open source

Release notes for Grafana 8.5.4

Features and enhancements

  • Alerting: Remove disabled flag for data source when migrating alerts. #48559, @yuri-tceretian
  • Alerting: Show notification tab of legacy alerting only to editor. #49624, @yuri-tceretian
  • Alerting: Update migration to migrate only alerts that belong to existing org\dashboard. #49192, @yuri-tceretian
  • AzureMonitor: Do not quote variables when a custom “All” variable option is used. #49428, @andresmgot
  • AzureMonitor: Update allowed namespaces. #48468, @jcolladokuri
  • CloudMonitor: Correctly encode default project response. #49510, @aangelisc
  • Cloudwatch: Add support for new AWS/RDS EBS* metrics. #48798, @szymonpk
  • InfluxDB: Use backend for influxDB by default via feature toggle. #48453, @yesoreyeram
  • Legend: Use correct unit for percent and count calculations. #49004, @dprokop
  • LokI: use millisecond steps in Grafana 8.5.x. #48630, @gabor
  • Plugins: Introduce HTTP 207 Multi Status response to api/ds/query. #48550, @wbrowne
  • Reporting: Improve PDF file size using grid layout. (Enterprise)
  • Transformations: Add an All Unique Values Reducer. #48653, @josiahg
  • Transformers: avoid error when the ExtractFields source field is missing. #49368, @wardbekker
  • [v8.5.x] Alerting: Update migration to migrate only alerts that belong to existing org\dashboard. #49199, @grafanabot
  • [v8.5.x] Reporting: Improve PDF file size using grid layout. (Enterprise)

Bug fixes

Breaking changes

For a data source query made via /api/ds/query :

  • If the DatasourceQueryMultiStatus feature is enabled and
    • The data source response has an error set as part of the DataResponse, the resulting HTTP status code is now 207 Multi Status instead of 400 Bad gateway
  • If the DatasourceQueryMultiStatus feature is not enabled and
    • The data source response has an error set as part of the DataResponse, the resulting HTTP status code is 400 Bad Request (no breaking change) –> Issue #48550