What's new from Grafana Labs
Grafana Labs products, projects, and features can go through multiple release stages before becoming generally available. These stages in the release life cycle can present varying degrees of stability and support. For more information, refer to release life cycle for Grafana Labs.
Loading...
Area of interest:
Cloud availability:
Cloud editions:
Self-managed availability:
Self-managed editions:
No results found. Please adjust your filters or search criteria.
There was an error with your request.
Filter by Pod type on the Workloads list page to find static Pods and bare/unmanaged Pods.

Control the automatic refresh interval of the GUI as well as disable the auto refresh until you are ready to do so manually. This is particularly useful for very large Kubernetes fleets that display a lot of data.

Navigate to the Alert rules page from a list item on a Cluster, namespace, Node, Pod, or container list. To do so, click the underlined alert number for next to the list item.

Use the in-app Cardinality page to discover on a Cluster-by-Cluster basis where all your active series are coming from for:
- Troubleshooting after initial configuration
- Determining potential duplicate metrics
- Finding other potential cardinality issues

Explore Metrics is a query-less experience for browsing Prometheus-compatible metrics. Search for or filter to find a metric. Quickly find related metrics - all in just a few clicks. You do not need to learn PromQL! With Explore Metrics, you can:
Explore Logs is a queryless experience for exploring Loki logs - no LogQL required! The primary interaction modes are point-and-click based on log volume, similar to Explore Metrics.
After you run a performance test in Grafana Cloud k6, the next step is to analyze the results and share any findings with your team. Sometimes, you don’t need your team members to view all the resulting metrics, or you might want to generate a PDF in an accessible, easy-to-read format to share with external stakeholders.

Grafana 11 adds the ability to color full table rows using the Colored background cell type of the table visualization. When you configure fields in a table to use this cell type, an option to apply the color of the cell to the entire row becomes available.

We are excited to announce our latest major release of Loki, version 3.0!
Key features:
- Query acceleration with Bloom filters (experimental): This is designed to speed up filter queries, with best results for queries that are looking for a specific text string like an error message or UUID. Docs: https://grafana.com/docs/loki/latest/operations/query-acceleration-blooms/
- Native OTel Support: A simplified ingestion pipeline (Loki Exporter no longer needed) and a more intuitive query experience for OTel logs. Docs: https://grafana.com/docs/loki/latest/send-data/otel/
- Docs improvements, including a new quickstart page to help new users get up and running with Loki faster.
- and more! Full docs: https://grafana.com/docs/loki/latest/
As always: To see a more comprehensive list of what is in Loki 3.0, please review our release notes. As this is a major version release: please review our upgrade guide before upgrading.
Grafana Synthetics now supports longer durations for two options:
Timeout -> Increased maximum to 60 seconds.
Frequency -> Increased maximum to 60 minutes.
Plugin developers and users typically want their plugins to be compatible with a range of Grafana versions. However, ensuring this is true can be a challenge. The environment, APIs, and UI components may differ from one version to another. Manual testing is tedious and error-prone. End-to-End testing across multiple versions is prohibitively complicated given the version-to-version changes in Grafana itself - until now.
The Alerting Provisioning HTTP API has been updated to enforce Role-Based Access Control (RBAC).
- For Grafana OSS, users with the Editor role can now use the API.
- For Grafana Enterprise and Grafana Cloud, users with the role Rules Writer and Set Provisioning status can access the API and limit access to alert rules that use a particular data source.
- Other roles related to provisioning, for example Access to alert rules provisioning API still work.
From a Pod, Cluster, namespace, or workload view, you can begin an incident investigation by clicking Run Sift investigation.

Pause and resume alert rule evaluation directly from the Alert rules list and details view. This helps Improve visibility of when alert rules have been paused by displaying “Paused” as the alert rule state.
It is hard for teams to collaborate on dashboards because they have to use different datasources. Grafana instances become cluttered and confusing with 100s of datasources.

