Breaking changes on Grafana Labs

Breaking changes in Grafana v11.0

Fri, 03 Apr 2026 12:35:46 -0500

Breaking changes in Grafana v11.0

Following are breaking changes that you should be aware of when upgrading to Grafana v11.0.

For our purposes, a breaking change is any change that requires users or operators to do something. This includes:

Changes in one part of the system that could cause other components to fail
Deprecations or removal of a feature
Changes to an API that could break automation
Changes that affect some plugins or functions of Grafana
Migrations that can’t be rolled back

For each change, the provided information:

Helps you determine if you’re affected
Describes the change or relevant background information
Guides you in how to mitigate for the change or migrate
Provides more learning resources

For release highlights and deprecations, refer to our v11.0 What’s new. For the specific steps we recommend when you upgrade to v11.0, check out our Upgrade guide.

Users and Operators

AngularJS support is turned off by default

Description

In Grafana v11, support for the deprecated AngularJS framework is turned off by default for all self-managed (on-premise) and Cloud instances of Grafana. This prevents any data source or panel visualization which relies on AngularJS from being loaded, and therefore has the potential to significantly disrupt your dashboards. Support will be fully removed in the next major release of Grafana.

Migration/mitigation

To avoid disruption, ensure all plugins are up to date and migrate from any remaining AngularJS plugins to a React-based alternative. If a plugin relies on AngularJS, a warning icon and message will be displayed in the plugins catalog in Grafana and any dashboard panel where it’s used. Additionally, a warning banner will appear in any impacted dashboards. A list of all impacted dashboards can also be generated using the detect-angular-dashboards tool.

Our documentation lists all known public plugins and provides migration advice when possible.

For self-managed users of Grafana and existing Grafana Cloud instances, you can temporarily re-enable support through the configuration parameter, angular_support_enabled=false. However, AngularJS-based plugins will not receive any further updates and we strongly recommend migration as soon as possible. This configuration parameter will also be removed in the next major release after Grafana v11.

New Grafana Cloud users will be unable to request that support be added to their instance.

Learn more

Refer to this blog post for more information.

Grafana Enterprise: Anonymous devices are billed as users

Description

Effective starting in Grafana v11, anonymous users are counted and charged as users in Grafana Enterprise. When you upgrade to v11, anonymous users will be automatically counted as active users against your Grafana Enterprise license.

Migration/mitigation

Turn off anonymous access, and consider using public dashboards to allow view-only access to publicly-accessible dashboards.

Learn more

Anonymous access documentation

Legacy alerting is entirely removed

Legacy alerting has reached its end-of-life. In Grafana v11 you can no longer enable legacy alerting, and Grafana will fail to start if the settings are not updated to run the new Grafana Alerting. This also means that starting in Grafana v11, it is no longer possible to migrate from legacy alerting to our new alerting. Grafana v10.4.x is the last version that offers migration, so make sure to migrate to the new Grafana Alerting system before upgrading to Grafana v11. Learn more about Grafana Alerting and the advantages of the new system in the legacy alerting deprecation documentation. Learn more about migration in the upgrade alerting documentation.

For more details on the code removal, review the following PRs:

Deprecated endpoints and fields in Reporting removed

Description

In Grafana v11, support for deprecated endpoints and fields in Reporting related to the old scheduling format, email, and dashboard is fully removed. This prevents any calls to deprecated endpoints and passing in values to deprecated fields. This feature only affects Cloud and Enterprise customers who use the API to generate reports.

Migration/mitigation

Ensure deprecated endpoints are updated to new corresponding endpoints and deprecated fields are removed and replaced with new corresponding fields.

Learn more

The Reporting API documentation lists all supported endpoints and fields.

Description

In Grafana v11, custom branding public dashboard footer behavior is changed to default to the Grafana logo if no footer logo or footer text is set. There is no option to hide the public dashboard footer anymore. This feature only affects Cloud Advanced and Enterprise customers.

Migration/mitigation

Ensure you have a public dashboard footer logo or footer text set if you don’t want to display the default Grafana footer.

Learn more

Configure custom branding documentation for public dashboards

Subfolders cause very rare issues with folders that have forward slashes in their names

Description and migration/mitigation

The upgrade to enable subfolders can cause some issues with alerts in certain cases. If you’ve previously set up a folder that uses a forward slash in its name, you have an alert rule in that folder, and the notification policy is set to match that folder’s name, notifications will be sent to the default receiver instead of the configured receiver.

In these cases, we recommend that you take these steps before the upgrade to enable subfolders:

Create a copy of the affected routes and rewrite the matchers for the new copy. For example, if the original matcher was grafana_folder=MyFolder/sub-folder, then the new route matcher will be grafana_folder=MyFolder\/sub-folder.
After enabling subfolders, you can delete the old routes.

Please note that if you use file provisioning, you can upgrade and update the routes at the same time.

Learn more

Subfolders announcement

Provisioning: Provision dashboards into subfolders PR

The Input data source is removed

The direct input data source plugin has been removed in Grafana v11. It has been in alpha for four years and is superseded by TestData, which ships with Grafana. This is a small deprecation.

Review this PR for details.

Data sources: Query filtering changes

The Disable query button in the query editor row has caused a lot of confusion among data source developers and end-users. Until now, it has been up to data source developers to filter out any hidden queries before or after they’re executed. Starting from Grafana v11, the tooltip of this button is changed from Disable query to Hide response/Show response. Responses that are associated with hidden queries will be removed by Grafana before they’re passed to the panel.

Users of data source plugins that didn’t previously remove hidden queries (before or after they were executed) will see a change of behavior as, previously, clicking the Disable query button had no impact on the query result. Starting from Grafana v11, responses associated with hidden queries are longer returned to the panel.

We’re also moving the call to the datasource.filterQuery method to the query runner. This means that frontend-only data sources (or any data source that doesn’t extend DataSourceWithBackend class) can implement this method. This streamlines data source plugin behavior, ensuring filtering works in the same way for all kinds of data source plugins.

Migration/mitigation

If data is missing in panels, make sure the query editor Hide response button is not clicked.

For data sources that extend DataSourceWithBackend, the filterQuery method is now called before the data source query method. If the filterQuery method assumes that some kind of query migration happens before this method is called, you now need to do the migration inside this method too.

Learn more

GitHub PR

Chore: Query oauth info from a new instance

We’ve added a validation between the response of the ID token HD parameter and the list of allowed domains as an extra layer of security. In the event that the HD parameter doesn’t match the list of allowed domains, we’re denying access to Grafana.

If you set Google OAuth configuration using api_url, you might be using the legacy implementation of OAuth, which doesn’t have the HD parameter describing the organization from which the approved token comes. This could break your login flow.

You can turn off this feature through the configuration toggle validate_hd . Anyone using the legacy Google OAuth configuration should turn off this validation if the ID Token response doesn’t have the HD parameter.

GitHub PR

Changes to how the panel view URL is generated for repeated panels

Description

With the introduction of the Scenes library to dashboards, the URL that’s generated when viewing an individual repeated panel has changed. We’ve changed how these panels are referenced and what used to be &viewPanel=panel-5 is now &viewPanel=panel-3-clone1.

This means that the previous URLs won’t work anymore and instead you’ll be redirected to the dashboard view and you’ll get a Panel not found error. From this point on, the dashboard will continue to work as expected.

Migration/mitigation

Reopen the panel in view mode and you’ll get the new URL.

Plugin developers

React Router is deprecated

Description

In Grafana v11 we’re marking react-router v5 as deprecated. App plugins should start migrating to use react-router v6.

Migration/mitigation

For a complete guide, please follow our migration docs on the developer portal.

Learn more

Grafana v9.x to v10.x migration guide
Official react-router v5 to v6 migration guide
Grafana community forum topic

The grafana/e2e testing tool is deprecated

Description

The Cypress based grafana/e2e end-to-end testing tool is now deprecated.

Migration/mitigation

We recommend all plugin authors to migrate their end-to-end tests to use the new Playwright-based grafana/plugin-e2e package instead. Find details on how to migrate from grafana/e2e to grafana/plugin-e2e in the migration guide.

Chore: Taint ArrayVector with `never` to further discourage

GitHub PR

The Vector interface that was deprecated in Grafana v10 is further deprecated. Using it now generates build-time Typescript errors, but it remains working at runtime. If you’re still using ArrayVector in your code, you should remove it immediately and replace it with plain arrays. Plugins that are compiled against older versions and depend on calling get/set will continue to work because the Array prototype still has a modified prototype. This will be removed in the future.

Chore: Remove React 17 peer deps

GitHub PR

We’ve removed React 17 as a peer dependency from our packages. Anyone using the new versions of these packages should ensure they’ve upgraded to React 18 following the upgrade steps.

Chore: Remove SystemJS from Grafana/Runtime

GitHub PR

SystemJS is no longer exported from @grafana/runtime. Plugin developers should instead rely on importing modules/packages using standard TS import syntax and npm/yarn for package installation.

Breaking changes in Grafana v10.3

Fri, 03 Apr 2026 12:35:46 -0500

Breaking changes in Grafana v10.3

Following are breaking changes that you should be aware of when upgrading to Grafana v10.3. Breaking changes that were introduced in release 10.2.3 are also included here and are marked with an asterisk.

For our purposes, a breaking change is any change that requires users or operators to do something. This includes:

Changes in one part of the system that could cause other components to fail
Deprecations or removal of a feature
Changes to an API that could break automation
Changes that affect some plugins or functions of Grafana
Migrations that can’t be rolled back

For each change, the provided information:

Helps you determine if you’re affected
Describes the change or relevant background information
Guides you in how to mitigate for the change or migrate
Provides more learning resources

For release highlights and deprecations, refer to our v10.3 What’s new. For the specific steps we recommend when you upgrade to v10.3, check out our Upgrade guide.

General breaking changes

Transformations*

In panels using the extract fields transformation, where one of the extracted names collides with one of the already existing fields, the extracted field will be renamed. Issue #77569.

If you use the Table visualization, you might see some inconsistencies in your panels. We have updated the table column naming. This will potentially affect field transformations and/or field overrides. To resolve this, either:

Update the transformation you are using
Update field override. Issue #76899.

Users who have transformations with the Time field might see their transformations are not working. Those panels that have broken transformations will fail to render. This is because we changed the field key. See related PR: #69865. To resolve this, either:

Remove the affected panel and re-create it
Select the Time field again
Edit the time field as Time for transformation in panel.json or dashboard.json. Issue #76641.

Data source permissions*

The following data source permission endpoints have been removed:

GET /datasources/:datasourceId/permissions
POST /api/datasources/:datasourceId/permissions
DELETE /datasources/:datasourceId/permissions
POST /datasources/:datasourceId/enable-permissions
POST /datasources/:datasourceId/disable-permissions

Please use the following endpoints instead:

GET /api/access-control/datasources/:uid for listing data source permissions
POST /api/access-control/datasources/:uid/users/:id, POST /api/access-control/datasources/:uid/teams/:id, and POST /api/access-control/datasources/:uid/buildInRoles/:id for adding or removing data source permissions

If you are using the Grafana provider for Terraform to manage data source permissions, you will need to upgrade your provider to version 2.6.0 or newer to ensure that data source permission provisioning keeps working. Issue #5880.

Breaking changes in Grafana v10.0

Fri, 03 Apr 2026 12:35:46 -0500

Breaking changes in Grafana v10.0

Following are breaking changes that you should be aware of when upgrading to Grafana v10.0.

For our purposes, a breaking change is any change that requires users or operators to do something. This includes:

Changes in one part of the system that could cause other components to fail
Deprecations or removal of a feature
Changes to an API that could break automation
Changes that affect some plugins or functions of Grafana
Migrations that can’t be rolled back

For each change, the provided information:

Helps you determine if you’re affected
Describes the change or relevant background information
Guides you in how to mitigate for the change or migrate
Provides more learning resources

For release highlights and deprecations, refer to our v10.0 What’s new. For the specific steps we recommend when you upgrade to v10.0, check out our Upgrade guide.

General breaking changes

Angular is deprecated and turned off by default for new Grafana Cloud stacks

You are affected if:

You create a new Grafana Cloud stack and intend to use any panel or data source plugins written using the Angular.js JavaScript framework. See the list of Angular plugins.

Background

AngularJS is an old frontend framework that stopped active development many years ago. Because of that, it’s a security risk. AngularJS also requires unsafe-eval in the CSP (Content Security Policy) settings, which also reduces the security level of how javascript is executed in the browser.

Angular plugin support in Grafana is deprecated, meaning it will be removed in a future release. There are still some community and private plugins built using Angular. Starting with v9.0, Grafana has a server configuration option, called angular_support_enabled, that controls whether Angular plugin support is available.

Change in Grafana v10

Angular is disabled by default for all new Grafana Cloud stacks. Existing stacks in Grafana Cloud, Grafana Enterprise on-premise instances, and Grafana OSS instances will not be automatically impacted.

How to mitigate

If you’re using Angular plugins in Grafana, try an alternative panel or data source that doesn’t use Angular. This list of detected Angular plugins offers alternatives where they exist.

If you’re a developer maintaining a plugin that uses Angular, we recommend you refactor or rewrite its frontend using React.js instead. The team at Grafana is ready to help and provide tools and guidance; you can reach us in Slack or on our Forum.

Learn more

Angular Support Deprecation documentation

Grafana legacy alerting is deprecated and no longer accepts internal or external contributions

You are affected if:

You use Grafana legacy alerting and have requested new features or changes to it.

Description

Grafana legacy alerting (dashboard alerts) has been deprecated since Grafana v9.0, in favor of the new, improved Grafana Alerting. In Grafana v10, the legacy alerting codebase—which depends on Angular—is still available, but we’ll no longer contribute to it or accept external contributions for it. We’ll continue to work on the migration path from legacy alerting to Grafana Alerting for our remaining users that need to migrate.

Migration path

The new Grafana Alerting was introduced in Grafana 8 and is a superset of legacy alerting. Learn how to migrate your alerts in the Upgrade Alerting documentation.

API keys are migrating to service accounts

You are affected if:

You use Grafana API keys and haven’t yet migrated to service accounts

Description

In Grafana v8.5, we introduced service accounts, which are a superset of API keys that support token rotation and role-based access control (RBAC). They were promoted to general availability (GA) in v9.1, with an option to manually migrate API keys to service accounts through the UI and API since then. When you upgrade to Grafana v10, Grafana will automatically migrate all API keys to service accounts and hide the API keys screen that was under the Admin section.

This is a “breaking” change because if users are used to seeing and interacting with API keys, they won’t see that page in navigation anymore and will need to navigate to the Service accounts page instead. However, your existing API tokens will remain fully functional and migrated to service accounts, so no automation will break. If you roll back to a previous version of Grafana, your API keys will remain intact.

Grafana’s HTTP API endpoints for generating and managing API Keys remain functional, but we recommend you begin using the Service account HTTP API to generate and manage machine authentication instead.

Migration path

While upgrading to Grafana v10, you don’t need to take any action; your API keys will be automatically migrated. To test or perform the migration from API keys to service accounts before upgrading to Grafana v10, follow our migration documentation.

Learn more

The experimental “dashboard previews” feature is removed

You are affected if:

You have the dashboardPreviews feature toggle switched on.

Description

We’re removing the experimental dashboard previews feature due to user permission and performance issues that prevented us from continuing its development. Dashboard previews have been behind a feature toggle since Grafana v9.0.

Migration path

The entire feature has been removed from Grafana. For users who enabled the dashboardPreviews feature flag, Grafana will continue to work as-is but without dashboard previews. We recommend you remove the dashboardPreviews feature flag from your Grafana configuration.

Learn more

Previous dashboard previews documentation

RBAC is on by default in Grafana Enterprise and cannot be disabled

You are affected if:

You have actively disabled RBAC in Grafana’s configuration.

Description

Starting from Grafana 9, RBAC has been enabled by default. An option to disable RBAC was introduced as an emergency mechanism and has only been used in rare cases. With Grafana v10 we removed the configuration option to disable RBAC. This ensures that Grafana works consistently across different features and decreases the risk of having issues with Grafana’s legacy access control. Additionally, access control for some of the Grafana v10 features only work with the RBAC, so disabling it is no longer an option.

Migration path

No action is needed—migration is automatic. Users’ current roles, permissions, SSO mapping, and other authorization functionality will continue to work as before.

Usernames are now case-insensitive by default

You are affected if:

You run Grafana with a Postgres or sqlite database, you import users from different SSO identity providers (like Google and Active Directory), and users who signed in from different providers were previously created twice because of case differences (for example “Myra@Grafana.com” vs “myra@grafana.com.”

Background

When someone signs up for a Grafana account, they can do it using an email or a login. The fields were case sensitive, which could lead to two or more accounts being created for the same user. Additionally, Grafana allows users to set up an authentication provider, and that provider might return an individual’s sign-up email with an uppercased domain name or some combination of uppercase and lowercase letters.

Having several accounts leads to split user permissions, confusion among signup flows, and unused “zombie” accounts in your database. Plus, multiple accounts can introduce issues when switching between authentication providers. We refer to these inconsistencies in user uniqueness as a user identity conflict.

Change in Grafana v10

Grafana will start matching users without regard for case. Conflicting users will not be able to sign in.

Migration path

We’ve built a CLI tool which users can use to resolve any potential conflicts beforehand. This breaking change was communicated already with Grafana v9.3.

Learn more

Blog post describing usage of the new CLI command

Grafana OAuth integrations do not work anymore with email lookups

You are affected if:

You have configured Grafana to use multiple identity providers, and you have users with the same email address in multiple identity providers.
You have configured Grafana to use Generic OAuth with an identity provider that does not support a unique ID field.

Background

Grafana used to validate identity provider accounts based on the email claim. On many identity providers, the email field is not unique, and this could open a possible account vector to perform an account takeover and authentication bypass in certain scenarios. This change also ensures that Grafana is protected against the CVE-2023-3128 vulnerability.

Change in Grafana v10

Grafana will not allow the affected users to sign in.

Migration path

In order to address any errors, we have provided an escape hatch that allows you to activate email lookup. You can use the following configuration in your Grafana instance to return the previous behavior.

[auth]
oauth_allow_insecure_email_lookup = true

We strongly recommend not doing this in case you are using Azure AD as an identity provider with a multi-tenant app.

Learn more

The “Alias” field in the CloudWatch data source is removed

You are affected if:

You’re using the “Alias” field in the CloudWatch data source, instead of using dynamic labels.

Description

Alias patterns in the CloudWatch query editor were replaced by Label (dynamic labels) behind a feature toggle. Starting from Grafana v9, Label has been enabled by default. With Grafana v10 we removed the option to disable Label and remove the Alias field entirely.

Migration path

Open and save each dashboard that uses the Alias field. Alias is migrated to Label automatically when you load the dashboard.

Learn more

Grafana CloudWatch documentation about the change

Athena data source plugin must be updated to version >=2.9.3

You are affected if:

You’ve installed and are using the Athena data source plugin.

Description

Grafana v10.0.0 ships with the new React 18 upgrade. In turn, changes in the batching of state updates in React 18 cause a bug in the query editor in Athena plugin versions <=2.9.2.

Migration path

Update the plugin to version 2.9.3 or higher in your Grafana instance management console. This will ensure your plugin query editor works as intended.

Redshift data source plugin must be updated to version >=1.8.3

You are affected if:

You’ve installed and are using the Redshift data source plugin.

Description

Grafana v10.0.0 ships with the new React 18 upgrade. In turn, changes in the batching of state updates in React 18 cause a bug in the query editor in Redshift plugin versions <=1.8.3.

Migration path

Update the plugin to version 1.8.3 or higher in your Grafana instance management console. This will ensure your plugin query editor works as intended.

DoiT International BigQuery plugin no longer supported

You are affected if:

You’ve installed and are using the DoiT International BigQuery data source plugin.

Description

In v10.0.0, Grafana no longer supports the use of the DoiT International BigQuery data source plugin, which was moved to a “retired” state in the latter half of 2022, and for which the GitHub repository was archived in December 2022. For BigQuery data sources to continue functioning, you’re required to migrate to the Official Grafana BigQuery data source plugin.

Migration path

For everyone using Grafana v8.5+, it’s possible to import queries created with the DoiT International BigQuery community plugin by simply changing the data source to Grafana BigQuery in the data source selector in the affected panel. Please note that queries will be imported as raw SQL queries.

Learn more

Information about importing DoiT International BigQuery queries.

For Plugin Developers

Upgrading to React 18

You are affected if:

You’ve developed a Grafana plugin that uses the React JS framework (this includes most app, panel, and data source plugins).

Description

Grafana has been upgraded to React 18 and now leverages the new React client rendering API. Plugin authors in particular should be aware, as there could be unintended side effects due to the changes around automatic batching of state updates and consistent useEffect timings.

Migration path

As a plugin developer: once a canary build has been released (post-9.5.0), test your plugin against one of the grafana-dev docker builds here (this one for example). Because of the extra optimisations made by React 18, some changes may be needed to maintain previous behavior.

Learn more

You are affected if:

You’re a plugin author and you use one of the following logs-related functions:

The interface type LogsParser in grafana-data
The following functions and classes related to logs in the grafana-ui package: 1LogLabels, LogMessageAnsi, LogRows, getLogRowStyles., getLogLevel, getLogLevelFromKey, addLogLevelToSeries, LogsParsers, calculateFieldStats, calculateLogsLabelStats, calculateStats, getParser, sortInAscendingOrder, sortInDescendingOrder, sortLogsResult, sortLogRows, checkLogsError, escapeUnescapedString.

Description

Certain rarely-used logs-related functions and variables have been moved from grafana-packages to the core grafana codebase. These items have been marked as deprecated previously, and a deprecation-notice was issued in the grafana changelog. Plugin authors who have relied on these functions and variables being available will have to adjust their codebase.

Migration path

If you’ve written a data source or panel plugin, make sure it doesn’t use the functions and variables that have been deprecated and removed.

Learn more

DataFrame: Use Array or Vector for field values

You are affected if:

You’re a plugin author and you’ve implemented your own version of Vector for data frames.

Description

Working with DataFrames was more complicated than it should have been because data was held in a Vector interface rather than a simple Array. In Grafana v10, the interface has been changed so developers can use simple arrays or Vectors.

Migration path

Any code using Vectors will continue to work without issue. If you’ve implemented your own version of Vector, it will need to be updated. The easiest approach is to refactor code so it extends MutableVector. This will work in both Grafana v9 and v10.

Learn more

https://github.com/grafana/grafana/issues/66480

grafana/toolkit CLI commands have been removed and migrated to the create-plugin package

You are affected if:

You develop plugins using @grafana/toolkit CLI commands.

Description

We announced the deprecation of the grafana/toolkit in v9.3 (November 2022) and have a new tool called create-plugin now available as a replacement. We encourage you to migrate and use our updated tooling. All grafana/toolkit commands except build are removed in Grafana v10.

Here are some of the benefits of create-plugin:

More flexible: With @grafana/create-plugin, you have more control over your plugins and their dependencies, and can more easily customize the tooling to fit your specific needs.
Faster development time: With its out-of-the-box development environment @grafana/create-plugin can significantly reduce development time compared to using @grafana/toolkit.
Improved testing capabilities: Testing plugins with @grafana/create-plugin is much easier with GitHub workflows that automate unit and e2e test runs whenever changes are pushed to GitHub.
Better documentation: The documentation for @grafana/create-plugin is more comprehensive and easier to discover than that of @grafana/toolkit.

Migration path

You may already be using the new tooling. If you have an existing plugin previously created using the @grafana/toolkit, you can use the following command to migrate it to the new build tooling:


# Run this command from the root of your plugin

cd ./my-plugin

npx @grafana/create-plugin@latest migrate

Learn more

Migration guide

Deprecations

Changing the folder UID through the API is deprecated. This functionality will be removed in a future release.

Breaking changes on Grafana Labs

Breaking changes in Grafana v11.0

Breaking changes in Grafana v11.0

Users and Operators

AngularJS support is turned off by default

Description

Migration/mitigation

Learn more

Grafana Enterprise: Anonymous devices are billed as users

Description

Migration/mitigation

Learn more

Legacy alerting is entirely removed

Deprecated endpoints and fields in Reporting removed

Description

Migration/mitigation

Learn more

Change custom branding public dashboard footer behavior

Description

Migration/mitigation

Learn more

Subfolders cause very rare issues with folders that have forward slashes in their names

Description and migration/mitigation

Learn more

The Input data source is removed

Data sources: Query filtering changes

Migration/mitigation

Learn more

Chore: Query oauth info from a new instance

Changes to how the panel view URL is generated for repeated panels

Description

Migration/mitigation

Plugin developers

React Router is deprecated

Description

Migration/mitigation

Learn more

The grafana/e2e testing tool is deprecated

Description

Migration/mitigation

Chore: Taint ArrayVector with never to further discourage

Chore: Remove React 17 peer deps

Chore: Remove SystemJS from Grafana/Runtime

Breaking changes in Grafana v10.3

Breaking changes in Grafana v10.3

General breaking changes

Transformations*

Data source permissions*

Breaking changes in Grafana v10.0

Breaking changes in Grafana v10.0

General breaking changes

Angular is deprecated and turned off by default for new Grafana Cloud stacks

You are affected if:

Background

Change in Grafana v10

How to mitigate

Learn more

Grafana legacy alerting is deprecated and no longer accepts internal or external contributions

You are affected if:

Description

Migration path

API keys are migrating to service accounts

You are affected if:

Description

Migration path

Learn more

The experimental “dashboard previews” feature is removed

You are affected if:

Description

Migration path

Learn more

RBAC is on by default in Grafana Enterprise and cannot be disabled

You are affected if:

Description

Migration path

Usernames are now case-insensitive by default

You are affected if:

Background

Change in Grafana v10

Migration path

Chore: Taint ArrayVector with `never` to further discourage