What's new from Grafana Labs

When debugging browser check failures like “timeout waiting for a selector”, you previously had to rely on text logs alone to understand what the browser rendered. Now, with screenshot thumbnails in the Timepoint Explorer and ad-hoc test panel, you can see exactly what the page looked like at the moment the check ran.

AI coding assistants and LLM workflows work best when they can pull in clean, structured context—but until now, getting Grafana documentation into your prompt meant scraping HTML and stripping out navigation, headers, and styling. No more.

Cloud Provider Observability now supports enhanced metrics, enabling you to monitor important service insights that aren’t available directly in CloudWatch. New derived metrics for such services as AWS Lambda, DynamoDB, RDS, and ElastiCache provide deeper visibility into resource capacity, usage, and limits—helping you build more informative dashboards and alerts.

The Cost Management and Billing app now supports Cost Attribution for Performance Testing!

You can break down Virtual User Hour (VUH) consumption using labels assigned to your k6 projects. This makes it easier to understand and allocate performance testing costs across teams, departments, environments, services, or any other dimension that matters to your organization.

The PDC agent now supports a native Go SSH mode, enabled with the -use-gossh flag. This replaces the agent’s reliance on an external OpenSSH process with a direct SSH implementation via Go’s golang.org/x/crypto/ssh library, and brings several improvements:

The table visualization’s nested rows feature has gotten some significant upgrades: a redesigned editor for the Group to nested tables transformation and the ability to apply field overrides to fields inside nested sub-tables.

When a time series panel renders a long list of series, finding the ones you care about often means editing the query or scanning a crowded legend. The new Series visibility filter in the time series visualization lets you narrow visible series interactively— by name, by label, or both— without touching the underlying query.

When an incident escalates, every minute matters, and you’re not always at your laptop. The Grafana IRM mobile app already keeps you on top of alerts, schedules, and shift swaps. Now it also notifies you the moment an incident you’re responding to changes.

When you have a role on an incident, you get a push notification when its severity changes (for example, Minor → Critical), its status changes (for example, Investigating → Resolved), or someone posts a status update. Tap the notification to open the incident in the IRM mobile app.

Diagnose slow queries faster with the new Grafana Assistant integration for Database Observability. Instead of manually correlating metrics, wait events, and execution plans, click a button to get a diagnosis grounded in your live Prometheus and Loki data — including specific fix recommendations like index changes or query rewrites tailored to your actual schema and database engine.

New Grafana Cloud stacks now use Grafana-Managed Alerting (GMA) by default — Datasource-Managed Alerting (DMA) is no longer provisioned in new stacks.

Scope: New stacks only. Existing stacks and existing DMA rules are unaffected. This is a provisioning-time change, not a migration.

You can now explore usage and cost data at both the organization and individual stack levels directly within the Cost Management and Billing app!

Key features include:

Grafana 13 tightens RBAC enforcement for custom roles, Terraform-managed roles, and role provisioning. Most users aren’t affected. If you maintain custom RBAC roles, especially roles with data source permissions scoped to specific UIDs, or roles using legacy annotation scopes, review your role definitions now to prevent errors.

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.

Adaptive Traces can now normalize span names to follow OpenTelemetry semantic conventions during ingestion, collapsing high-cardinality names like /api/users/7f3a into stable forms like GET /api/users/{id}. Span metrics aggregate under stable route names, dashboards show meaningful operations, and TraceQL queries match consistently across services regardless of how each team labeled its spans. The original name is preserved as grafana.original_span_name so you can still drill down to a specific request.

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.

Watch the following demo video to see the improved experience in action: