The Time series to table transformation is now generally available. Convert time series query results into table rows containing a trend field, then display them as sparklines with the sparkline cell type, useful for building compact at-a-glance overviews across many series. This transformation has been available and enabled by default since Grafana 10.2.
k6 v1.7.1 is here 🎉! This release includes: Dependency updates for google.golang.org/grpc . Maintenance and internal improvements #5746 Updates google.golang.org/grpc which contains a fix for CVE-2026-33186 .
The Grafana Cloud app for Slack now supports a more complete incident response workflow, making it easier to declare, manage, and resolve incidents directly in Slack.
Keep every service represented in your traces, even when a few noisy ones produce most of your traffic. Volumetric sampling automatically distributes your sampling budget across services and request types, so low-volume services aren’t crowded out , and you can often lower sampling_percentage while keeping coverage intact. Learn more in the docs →
Access and analyze Grafana Cloud cost and usage data using the open FOCUS standard We’re excited to announce the general availability of FOCUS support in the Cost Management and Billing app! FOCUS (FinOps Open Cost and Usage Specification) is an open industry standard for cloud cost and usage data.
Detect unexpected spikes and drops in usage with intelligent anomaly detection We’re excited to announce the general availability of Anomaly Alerts in the Cost Management and Billing app!
A single bug can generate hundreds of unique error entries when messages contain variable data like memory addresses, line numbers, or request IDs. This fragments counts, skews prioritization, and floods on-call engineers with duplicate alerts.
We’re excited to announce AWS Grafana Assume Role support across Grafana’s AWS data sources, now generally available in Grafana Cloud. Instead of configuring long-lived AWS access keys and secrets in each data source, you can now authenticate using IAM role assumption.
Adaptive Logs Drop rules allow you precisely define noisy or wasteful logs to drop, and can be used in addition to our own optimization recommendations. Use cases for drop rules include filtering out debug logs, dropping health check log lines, or downsampling in non-production environments.
Writing a solid k6 performance test still means juggling URLs, VU counts, checks, thresholds, and how metrics will look in Grafana after the run. It is easy to get stuck on a blank script or to ship something that runs locally but does not match how your service actually behaves in production.
Data source APIs that referenced data sources using a numeric id were deprecated in Grafana v9.0 in favor of APIs that reference data sources using a uid instead. In Grafana v13.0, these deprecated APIs are disabled by default.
Add custom tabs in Frontend Observability that link directly to any Grafana dashboard, so your team can jump to the dashboards without losing context. Whether it’s a custom performance dashboard, a business metrics view, or a team-specific RUM report, custom tabs let you surface the right context exactly where you need it.
We’ve introduced a quality of life improvement when configuring Adaptive Metrics exemptions; now, you create prefix and suffix exemptions, to more easily exempt classes of metrics. Support is available for this in the UI, Terraform provider, and API.
Prometheus and Loki data source-managed alerts are being deprecated in Grafana Cloud and can no longer be created in new stacks. Although the pre-provisioned data sources are being depreciated, users can still add their own data sources and can create data source-managed alerts in those data sources.
Dynamic dashboards are now on by default for all Grafana Cloud users and self-managed Grafana instances. Every new and existing dashboard uses the new layout engine, editing experience, and dashboard structure automatically. Your existing dashboards are migrated to the new schema when you open them. No manual steps required.
The grafana.com/provenance annotation on alerting notification resources is now correctly read and enforced when writing using the Kubernetes-style API. Previously, provenance was hardcoded to none on all Kubernetes API writes, so the annotation was silently ignored. It is now respected.
Remote configuration, a key feature of Grafana Fleet Management, relies on collectors to poll the Fleet Management server at regular intervals for configuration changes. The problem with this automated approach is that it can be hard to tell when a collector has loaded the new remote configuration or if it experienced a configuration error.
We’ve redesigned the panel configuration experience to include the option to use a saved query. When you add a panel to a dashboard, you now have three starting points: an empty panel, a library panel, or a saved query. Select Use saved query to open the Saved queries dialog box and choose a query.
Database Observability brings your MySQL and PostgreSQL query performance data directly into Grafana Cloud, right alongside your metrics, logs, and traces. With Database Observability, you can identify slow and failing queries, understand wait events, analyze explain plans, and examine query samples all within Grafana.
We’ve redesigned the query editor to make complex panels easier to build and manage. The new experience provides a unified view of your entire data pipeline, queries, expressions, transformations, and related alerts, with clearer visual feedback and faster access to the settings that matter.
Releasesby Glyph