What's new from Grafana Labs

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.

Keep your team’s content all in one place, making it easier to find, organize, and manage access.

Team folders help you associate folders with teams so admins and team members can find the right dashboards, library panels, and alert rules faster. When you belong to a team that owns a folder, Grafana surfaces those folders at the top of the Dashboards page and in your team details, giving your team a clear home from day one.

Today, we announce that access to Assistant now extends to Grafana Enterprise and Grafana OSS users. This makes Grafana Assistant available in your self-managed environment to help you analyze telemetry data and code in real time, build dashboards, ask questions, and more. Self-managed Grafana users can create a Grafana Cloud account and connect it to their Grafana installation via a one-click setup.

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. Grafana uses the AWS Security Token Service (STS) to generate short-lived, scoped credentials at query time,  following AWS security best practices for least-privilege access.

Grafana is moving to /apis, an API layer that powers the App Platform and gives us a more consistent, scalable foundation going forward. With Grafana 13, we are officially deprecating the /api path in favor of the new /apis path. Deprecating /api marks our commitment to this new model.

Git Sync is now generally available for all Grafana Cloud and self-managed Grafana users.

Connect your Grafana instance to GitHub, GitLab, Bitbucket, or any git repository to manage dashboards as code. You can edit dashboards directly in Grafana and then save, commit, and open a pull request without leaving the UI.

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.

The new Graphviz panel plugin lets you define interactive diagrams in the Graphviz DOT language, and map live data to them from any data source.