Project: Grafana (Observability and Analysis / Observability)
File: release-notes-9-0-0.md

aliases: [] hide_menu: true labels: products: cloud enterprise oss title: Release notes for Grafana 9.0.0 <!-- Auto generated by update changelog github action --> API: Add GET /api/annotations/:annotationId endpoint. , API: Add endpoint for updating a data source by its UID. , AccessControl: Add enterprise only setting for rbac permission cache. , AccessControl: Document basic roles changes and provisioning V2. , AccessControl: Enable RBAC by default. , AddDataSourceConfig: Remove deprecated checkHealth prop. , Alerting: Add Image URLs to Microsoft Teams notifier. , Alerting: Add RBAC actions and role for provisioning API routes. , Alerting: Add Screenshot URLs to Pagerduty Notifier. , Alerting: Add a "Reason" to Alert Instances to show underlying cause of state. , Alerting: Add a general screenshot service and alerting-specific image service. , Alerting: Add image url or file attachment to email notifications. , Alerting: Add image_urls to OpsGenie notification details. , Alerting: Add notification policy flow chart. , Alerting: Attach image URL to alerts in Webhook notifier format. , Alerting: Attach image URLs or upload files to Discord notifications. , Alerting: Attach image URLs to Google Chat notifications. , Alerting: Attach screenshot data to Unified Alerting notifications. , Alerting: Create folder for alerting when start from the scratch. , Alerting: Modify alertmanager endpoints for proxying using the datasource UID. , Alerting: Modify endpoint for testing a datasource rule using the UID. , Alerting: Modify prometheus endpoints for proxying using the datasource UID. , Alerting: State Manager takes screenshots. , Alerting: Use UID scope for folders authorization. , Alerting: modify ruler endpoints for proxying using the datasource UID. , Angular: Adds back two angular directives that are still used by remaining angular bits and plugins. , Azure Monitor: Add Resource Picker to Metrics Queries. , Azure Monitor: Add search feature to resource picker. , AzureMonitor: Add support for selecting multiple options when using the equals and not equals dimension filters. , AzureMonitor: Remove deprecated code. , Build: Change names to PascalCase to match. , Chore: Remove deprecated DataSourceAPI methods. , Chore: Upgrade typescript to 4.6.4. , Cloud Monitoring: Use new annotation API. , CloudMonitoring: Allow to set a custom value or disable graph_period. , CloudWatch: Add generic filter component to variable editor. , CloudWatch: Added missing AWS/AppRunner metrics. , CloudWatch: Enable support for dynamic labels with migrated alias patterns. , Cloudwatch: Pass label in deep link. , Cloudwatch: Use new annotation API. , Dashboard: Validate dashboards against schema on save. , DashboardPickerByID: Add option to exclude dashboards. , DashboardPickerById: Add optionLabel prop. , Dashboards: Display values of 0 with the configured decimal places. , Data: Remove deprecated types and functions from valueMappings. , Elasticsearch: Remove browser access mode. , Elasticsearch: Remove support for versions after their end of the life (<7.10.0). , Encryption: Add support for multiple data keys per day. , Encryption: Enable envelope encryption by default. , Explore: Remove support for legacy, compact format URLs. , Explore: Skip Angular error handling when Angular support is disabled. , Explore: simplify support for multiple query editors. , FeatureToggles: Support changing feature toggles with URL parameters. , FileUpload: Make component accessible by keyboard navigation. , Formatting: Make SI number formats more

, Graph: Deprecate Graph (old) and make it no longer a visualization option for new panels. , IconButton: IconButtons are now correctly aligned in Safari. , Logger: Enable new logging format by default. , Loki: Add more query patterns. , Loki: Enable new visual query builder by default. , Loki: use the same dataframe-format for both live and normal queries. , OAuth: Make allowed email domain case insensitive. , Panels: Use the No value option when showing the no data message. , Plugins: Remove plugin list panel. , Query History: Enable new query history by default. , QueryEditorRow: Show query errors next to query in a consistent way across Grafana. , SAML: Implement Name Templates for assertionattributename option. , Service accounts: Do not display service accounts assigned to team. , Settings: Use Grafana Azure SDK to pass Azure env vars for external plugins. , Shortcuts: Add shortcut to show shortcuts to the list of shortcuts. , Traces Panel: Add new Traces Panel visualization. , Traces: Filter by service/span name and operation in Tempo and Jaeger. , Transformations: Allow more complex regex expressions in `Rename by regex`. , grafana/ui: Add default type="button" to <Button>. , Alerting: Fix database unavailable removes rules from scheduler. , AzureMonitor: Fix auto-selection of time-grain for metrics. , DataSources: Fixes issue with expressions not being queried. , GraphNG: Fix thresholds by color not following data update. , Jaeger: Update operations dropdown. , Login: Fix mismatching label on auth_module in user list. , Playlists: Save button now correctly creates a new playlist. , RBAC: Fix migrations running in the wrong order causing inheritance problem in enterprise. , RBAC: Fix migrations running into the wrong order. (Enterprise) ServiceAccounts: Add identifiable token prefix to service account tokens. , Traces: Fix missing CopyButton on KeyValueTables and overlapping of panels. , The `@grafana/ui` package helper function `selectOptionInTest` used in frontend tests has been removed as it caused testing libraries to be bundled in the production code of Grafana. If you were using this helper function in your tests please update your code accordingly: ```js // before import { selectOptionInTest } from '@grafana/ui'; // ...test usage await selectOptionInTest(selectEl, 'Option 2'); // after import { select } from 'react-select-event'; // ...test usage await select(selectEl, 'Option 2', { container: document.body }); ``` Issue Removed deprecated `checkHealth` prop from the `@grafana/e2e` `addDataSource` config. Previously this value defaulted to `false`, and has not been used in end-to-end tests since Grafana 8.0.3. Issue Removes the deprecated `LegacyBaseMap`, `LegacyValueMapping`, `LegacyValueMap`, and `LegacyRangeMap` types, and `getMappedValue` function from grafana-data. Migration is as follows: | Old | New | | - | - | | `LegacyBaseMap` | `MappingType` | | `LegacyValueMapping` | `ValueMapping` | | `LegacyValueMap` | `ValueMap` | | `LegacyRangeMap` | `RangeMap` | | `getMappedValue` | `getValueMappingResult` | Issue This change fixes a bug in Grafana where intermittent failure of database, network between Grafana and the database, or error in querying the database would cause all alert rules to be unscheduled in Grafana. Following this change scheduled alert rules are not updated unless the query is successful. The `getalertrulesdurationseconds` metric has been renamed to `schedulequeryalertrulesduration_seconds`. Issue Any secret (data sources credential, alert manager credential, etc, etc) created or modified with Grafana

won't be decryptable from any previous version (by default) because the way encrypted secrets are stored into the database has changed. Although secrets created or modified with previous versions will still be decryptable by Grafana v9.0. If required, although generally discouraged, the `disableEnvelopeEncryption` feature toggle can be enabled to keep envelope encryption disabled once updating to Grafana v9.0. In case of need to rollback to an earlier version of Grafana (i.e. Grafana v8.x) for any reason, after being created or modified any secret with Grafana v9.0, the `envelopeEncryption` feature toggle will need to be enabled to keep backwards compatibility (only from `v8.3.x` a bit unstable, from `8.5.x` stable). As a final attempt to deal with issues related with the aforementioned situations, the `grafana-cli admin secrets-migration rollback` command has been designed to move back all the Grafana secrets encrypted with envelope encryption to legacy encryption. So, after running that command it should be safe to disable envelope encryption and/or roll back to a previous version of Grafana. Alternatively or complementarily to all the points above, backing up the Grafana database before updating could be a good idea to prevent disasters (although the risk of getting some secrets corrupted only applies to those updates/created with after updating to Grafana v9.0). Issue According to the dynamic labels documentation, you can use up to five dynamic values per label. Theres currently no such restriction in the alias pattern system, so if more than 5 patterns are being used the GetMetricData API will return an error. Dynamic labels only allow ${LABEL} to be used once per query. Theres no such restriction in the alias pattern system, so in case more than 1 is being used the GetMetricData API will return an error. When no alias is provided by the user, Grafana will no longer fallback with custom rules for naming the legend. In case a search expression is being used and no data is returned, Grafana will no longer expand dimension values, for instance when using a multi-valued template variable or star wildcard `*` in the dimension value field. Ref https://github.com/grafana/grafana/issues/20729 Time series might be displayed in a different order. Using for example the dynamic label `${PROP('MetricName')}`, might have the consequence that the time series are returned in a different order compared to when the alias pattern `{{metric}}` is used Issue In Elasticsearch, browser access mode was deprecated in grafana 7.4.0 and removed in 9.0.0. If you used this mode, please switch to server access mode on the datasource configuration page. Issue Environment variables passed from Grafana to external Azure plugins have been renamed: `AZURECLOUD` renamed to `GFAZPLAZURE_CLOUD` `AZUREMANAGEDIDENTITYENABLED` renamed to `GFAZPLMANAGEDIDENTITYENABLED` `AZUREMANAGEDIDENTITYCLIENTID` renamed to `GFAZPLMANAGEDIDENTITYCLIENTID` There are no known plugins which were relying on these variables. Moving forward plugins should read Azure settings only via Grafana Azure SDK which properly handles old and new environment variables. Issue Removes support for for ElasticSearch versions after their end-of-life, currently versions < 7.10.0. To continue to use ElasticSearch data source, upgrade ElasticSearch to version 7.10.0+. Issue Application Insights and Insight Analytics queries in Azure Monitor were deprecated in Grafana 8.0 and finally removed in 9.0. Deprecated queries will no longer be executed. Please refer to the for more information about this

Issue grafana/ui: Button now specifies a default type="button" The `Button` component provided by @grafana/ui now specifies a default `type="button"` when no type is provided. In previous versions, if the attribute was not specified for buttons associated with a `<form>` the default value was `submit` per the You can preserve the old behavior by explicitly setting the type attribute: `<Button type="submit" />` . Issue The `Rename by regex` transformation has been improved to allow global patterns of the form `/<stringToReplace>/g`. Depending on the regex match used, this may cause some transformations to behave slightly differently. You can guarantee the same behaviour as before by wrapping the `match` string in forward slashes (`/`), e.g. `(.)` would become `/(.)/` Issue `<Select />` menus will now portal to the document body by default. This is to give more consistent behaviour when positioning and overlaying. If you were setting `menuShouldPortal={true}` before you can safely remove that prop and behaviour will be the same. If you weren't explicitly setting that prop, there should be no visible changes in behaviour but your tests may need updating. Please see the original PR (https://github.com/grafana/grafana/pull/36398) for migration guides. If you were setting `menuShouldPortal={false}` this will continue to prevent the menu from portalling. Issue Grafana alerting endpoint prefixed with `api/v1/rule/test` that tests a rule against a Corte/Loki data source now expects the data source UID as a path parameter instead of the data source numeric identifier. Issue Grafana alerting endpoints prefixed with `api/prometheus/` that proxy requests to a Cortex/Loki data source now expect the data source UID as a path parameter instead of the data source numeric identifier. Issue Grafana alerting endpoints prefixed with `api/ruler/` that proxy requests to a Cortex/Loki data source now expect the data source UID as a path parameter instead of the data source numeric identifier. Issue Grafana alerting endpoints prefixed with `api/alertmanager/` that proxy requests to an Alertmanager now expect the data source UID as a path parameter instead of the data source numeric identifier. Issue The format of log messages have been updated, `lvl` is now `level` and `eror`and `dbug` has been replaced with `error` and `debug`. The precision of timestamps has been increased. To smooth the transition, it is possible to opt-out of the new log format by enabling the feature toggle `oldlog`. This option will be removed in a future minor release. Issue In the Loki data source, the dataframe format used to represent Loki logs-data has been changed to a more efficient format. The query-result is represented by a single dataframe with a "labels" column, instead of the separate dataframes for every labels-value. When displaying such data in explore, or in a logs-panel in the dashboard will continue to work without changes, but if the data was loaded into a different dashboard-panel, or Transforms were used, adjustments may be necessary. For example, if you used the "labels to fields" transformation with the logs data, please switch to the "extract fields" transformation. Issue `setExploreQueryField`, `setExploreMetricsQueryField` and `setExploreLogsQueryField` are now deprecated and will be removed in a future release. If you need to set a different query editor for Explore, conditionally render based on `props.app` in your regular query editor. Please refer to https://grafana.com/developers/plugin-tools/create-a-plugin/extend-a-plugin/add-support-for-explore-queries for more information. Issue Chore: Remove react-testing-lib from bundles. , Select: Portal menu by default. ,