What's next from Grafana Labs
This page lists upcoming breaking changes, behavior changes, deprecations, and end of life for Grafana Labs products. The rollout date on each note indicates when the change is planned to take effect in Grafana Cloud. The targeted release indicates when the change is likely to take effect in the self-managed version. For information about upcoming features, refer to the Grafana ideas portal.
Loading...
Area of interest:
Change type:
No results found. Please adjust your filters or search criteria.
There was an error with your request.
Starting November 5th, 2026, edit mode for dashboards will no longer be available on a mobile phone. Dashboards will become view-only on a phone.
Editing on a tablet is not affected: tablets keep full dashboard edit mode, with the same feature set as desktop.
The self-service API that let Grafana Cloud users configure a limited number of Loki configuration settings has been deprecated. It has been replaced by the Database configuration app, which provides a user interface for making database configuration changes in Grafana Cloud.
What is changing
The Plugin Frontend Sandbox was a public preview feature which provided an additional layer of security by restricting what plugins could access and modify. Following the public preview period, we have decided not to progress this feature to general availability, and are deprecating it in Grafana v13.3 with the intent to fully remove it in Grafana v13.4. Grafana OSS and Enterprise users with the feature enabled will now see a deprecation warning in the server logs on startup.
The built-in MinIO subchart is deprecated in the Loki Community Helm chart, and will be removed on 2026-10-31. Setting minio.enabled=true without also setting ignoreMinioDeprecation: true causes chart rendering to fail with chart v17+. For production, configure an external object storage backend.
What is changing
Grafana is deprecating the [security] x_xss_protection setting. When the release containing this change reaches your self-managed instance, Grafana logs a deprecation warning on startup if the setting is enabled. Its default is true, so the warning can appear even if you have not set the option explicitly.
What is changing
On October 26, 2026, Agentic testing is being removed from Testing & synthetics. We’re taking this work into Grafana Assistant as a new experience. You won’t be able to view, edit, or re-run the tests it generated, and you can’t export those definitions. Recreate any journeys you still need before that date. Results from past runs stay in the Agentic Testing project until your retention window ends.
The legacy role-based access control (RBAC) HTTP API will let authorized role managers revoke access without holding the permissions being removed. This applies when you remove permissions from a role, delete an editable custom role, or remove role assignments from users or teams. Each operation will still require its management permissions.
If you delegate role management or use integrations with /api/access-control/ endpoints, review who should have this broader revocation authority. Otherwise, you don’t need to take action.
Custom labels in Grafana Cloud Synthetic Monitoring now attach directly to every check metric and log - not only the sm_check_info metric - and the label_ prefix is removed.
The dashboard-specific endpoints for starring and unstarring a dashboard are deprecated in favor of the generic Collections Stars API, which stars any kind of resource through one shared endpoint shape instead of a separate endpoint per resource kind.
The old endpoints still work, but are now marked deprecated:
POST /api/user/stars/dashboard/uid/{dashboard_uid}(star a dashboard)DELETE /api/user/stars/dashboard/uid/{dashboard_uid}(unstar a dashboard)
The replacement is:
PUT /apis/collections.grafana.app/v1alpha1/namespaces/{namespace}/stars/user-{your_user_uid}/update/dashboard.grafana.app/Dashboard/{dashboard_uid}(star)DELETE /apis/collections.grafana.app/v1alpha1/namespaces/{namespace}/stars/user-{user_uid}/update/dashboard.grafana.app/Dashboard/{dashboard_uid}(unstar)
No request body is needed; the star target is fully described by the URL path.
Grafana Loki deprecated several legacy multi-store backends in release 3.0 The following legacy storage backends have been removed in Loki 4.0:
- Apache Cassandra
- Amazon DynaomoDB
- BoltDB (for indexes)
- Google BigTable
- gRPC Store
Loki 4.0 will fail to start if a deprecated and removed storage backend is referenced in the schema or storage configuration.
The Loki release 3.4 introduce new object storage clients based on the Thanos Object Storage Client Go module. For several Loki releases this was opt-in and only took effect only when -use-thanos-objstore was set to true. In Loki 4.0 -use-thanos-objstore is set to `true` by default.
We deprecated mulit-storage backends in Loki 3.0 and they have been removed for Loki 4.0. Table manager is only needed if you are using a multi-store backend. Starting with Loki 4.0, the single store TSDB is the only supported Loki index. TSDB has been the recommended Loki index since Loki v2.8, and it does not need the table manager.
Simple Scalable Deployment mode is being deprecated and removed in Loki 4.0. The write, read, and backend targets, as well as the configuration option -legacy-read-mode will not be available any more and Loki will fail to start if used.
Users must migrate to monolithic mode, distributed mode, or the new HA Monolithic mode being introduced in Loki 4.0.
The CSV and JSON API data sources are deprecated. Both plugins move into a critical-security-updates-only phase: they keep receiving critical security fixes, but no new features or non-security bug fixes. Support for both data sources ends February 1, 2027.