Data and AI releases

548 this month · 176 companies

Change in resource admin behavior

UpdateNot yet verified

In Grafana Cloud, we’re rolling out a change to what resource administrators can see on a resource’s permissions list. If you can view and manage the permissions on a folder or dashboard, you will soon see every user and team that has access to it. Today, Grafana filters that list.

SecurityBIDeveloper tools

Read on grafana.com

Also shipped Jun 12, 2026Grafana Labs in June 2026 →

What's new in Sigma

AI Build and interact with Sigma agents (Beta) Build agentic solutions natively in Sigma with Sigma agents . Agents provide AI capabilities to a dashboard or application based on a predefined context of the data elements in a workbook.

Beta
Source ↗

More from Grafana CloudEvery Grafana Cloud release →

Query dropped traces in Adaptive Traces

Find the trace you need, even when it was dropped. Adaptive Traces now keeps every dropped trace queryable by trace ID for 24 hours after ingest, so a trace ID from a log line, exemplar, or an upstream system always returns a result. These traces don’t appear in TraceQL search results, the service graph, or aggregations.

Update
Source ↗

Annotations clustering now generally available

Recently, we introduced several improvements to annotations to make them easier to explore, navigate, and manage at scale, including annotations clustering and indicator controls. These changes were introduced in public preview and now they are generally available. For more information about these changes, refer to the original announcement .

GA
Source ↗

Alerting: contact point logic update

Grafana Alerting’s provisioning endpoints now reject duplicate secret keys that differ in casing. Requests that include duplicate keys will now be treated as validation errors with a 4XX status code.

Update
Source ↗

Revamped Recommendations UI for Adaptive Metrics

Get started optimizing your Cloud Metrics quickly and more easily.! The Adaptive Metrics UI has been revamped to improve readability and instill confidence in our optimization recommendations. Here are a few of the highlights: Improved readability and clear calls to action.

Update
Source ↗

Suspect Commits in Frontend Observability

When an error appears in your app, you want to know which code change caused it , without digging through git log. Suspect Commits in Frontend Observability now pins the exact commit your app was built from at the top of the candidate list on the error summary page, so you can go straight from a stack trace to the change that introduced it.

Update
Source ↗