What's next from Grafana Labs

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.

RSS
What's next from Grafana Labs
Loading...
Loading...

Deprecation notice for legacy dashboard star and unstar API endpoints

Deprecation notice
Open Source Enterprise Dashboards and visualizations
Announcement
2026-08-27
Planned rollout in Cloud
2026-09-24
Targeted self-managed release
grafana-v13.3.0

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.


Loki multi-store backends removed

Deprecation notice
Open Source Logs
Announcement
2026-08-24
Planned rollout in Cloud
Loki 4.0
Targeted self-managed release
Loki v4.0.0

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.


Loki table manager removed

Deprecation notice
Open Source Logs
Announcement
2026-08-24
Planned rollout in Cloud
Loki 4.0
Targeted self-managed release
Loki v4.0.0

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.


Loki SSD deployment no longer available

Deprecation notice
Open Source Logs
Announcement
2026-08-24
Planned rollout in Cloud
Loki 4.0
Targeted self-managed release
Loki v4.0.0

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.


CSV and JSON API data sources: support ends February 1, 2027

Deprecation notice
Open Source Enterprise Data sources Breaking change
Announcement
2026-08-21
Planned rollout in Cloud
2027-02-01
Targeted self-managed release
No self-managed release

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.


Parca data source: support ends January 2, 2027

Deprecation notice
Open Source Enterprise Data sources Breaking change Profiles
Announcement
2026-08-21
Planned rollout in Cloud
2027-01-02
Targeted self-managed release
No self-managed release

The Parca data source is deprecated. The plugin moves into a critical-security-updates-only phase: it keeps receiving critical security fixes, but no new features or non-security bug fixes. Support ends January 2, 2027.


Kubernetes Monitoring will give AI agents access to its queries

Behavior change
Kubernetes Monitoring AI
Announcement
2026-08-04
Planned rollout in Cloud
Kubernetes Monitoring, release to be confirmed
Targeted self-managed release
No self-managed release

Kubernetes Monitoring will let you give an AI agent access to the queries behind its own pages, such as the ones that count Nodes, total the CPU used by a namespace, and calculate cost. A new AI agent access tab in the Configuration page will hold a prompt you copy into your agent’s configuration.


gcx v1.0.0: command renames, config file format changes, opt-out usage statistics

Breaking change
Open Source Enterprise AI
Announcement
2026-07-28
Planned rollout in Cloud
2026-07-28
Targeted self-managed release
Grafana v13.0.0

If you upgrade gcx from v0.4.x or earlier, there are breaking changes to be aware of:

1. Commands are renamed across many providers, with no aliases. Old spellings fail as unknown commands. Behaviour, flags, positional arguments, output schemas, and exit codes are unchanged, only the names moved. The aim is to make a more predictable and understandable command surface. Here are all the changes:


The Team API now returns richer team context

Breaking change
Open Source Enterprise Authentication and authorization
Announcement
2026-07-07
Planned rollout in Cloud
2026-07-30
Targeted self-managed release
Grafana v13.2.0

The new Grafana Team API will return richer team context. When you query a team through the new API, the response will include the team’s members and its external group mappings as part of the Team resource itself, so a single call will give you a complete picture of the team.