What's new from Grafana Labs

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:

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.

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:

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 your overall sampling rate while keeping coverage intact. Learn more in the docs →

We’ve added a Grafana Alloy component editor to Grafana Fleet Management! Now you can build and update Alloy configuration pipelines without writing a single line of Alloy syntax.

You can now define custom working hours so teammates can see when you’re available directly from on-call schedules.

We’ve added a Working hours tab to your IRM user settings, so you can customize each day to match your actual schedule. Toggle individual days on or off, set up to three time ranges per day, and copy one day’s configuration to all other active days in one click.

Once enabled, schedule hover cards show whether you’re currently inside or outside your working hours based on your configured availability.

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!

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!

Synthetic Monitoring checks are now linked to distributed traces they generate in Grafana Cloud Traces! When a Scripted check fails or looks slow, you can open the underlying trace with a single click from the check’s logs and see exactly which service, span, and downstream call caused the problem.

This helps to shrink the gap between a poor user experience and the underlying root cause.

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.