What's new from Grafana Labs

Creating browser tests is now faster and easier with the new experimental Agentic testing experience in Grafana Cloud.

Describe the user journey you want to test, such as signing in, completing checkout, or submitting a form, and Grafana Cloud helps turn that journey into a runnable browser test you can run, review, and iterate on without manually scripting every step.

In Grafana Cloud, the internal Grafana Alertmanager handles Grafana-managed alerts by default.

• New stacks use internal routing by default. Sending to an external Alertmanager isn’t enabled by default.
• Existing stacks move to internal routing by default, plan by plan. If your stack actively sends to an external Alertmanager, it keeps that configuration and continues to work.

Sending Grafana-managed alerts to an external Alertmanager is still supported. If you need it, contact Grafana Support.

Grafana Cloud Synthetic Monitoring now lets you organize your checks into Grafana Folders. As you create more checks or onboard new teams, a single flat list becomes hard to scan. With folders, you can group checks by team, service, or environment so the right checks are always easy to find and act on a whole group at once instead of one check at a time.

Want more control than our pattern-based recommendations, but not sure where to start?

Adaptive Logs now walks you through creating a drop rule tailored to your environment in three guided steps: pick one of your highest-volume services, choose a drop rate, and review a pre-filled rule before any logs are dropped. The flow targets debug logs, often the largest and least-queried part of your log volume, and you take it from there.

Starting with Grafana 13.1, Grafana Assistant comes pre-installed in Grafana Enterprise, with no plugin installation required. If you’re a Grafana Enterprise user, simply connect your Grafana Cloud account to start using Assistant right away. Get onboarded quicker, explore telemetry data, build dashboards, and get things done faster using natural language.

This builds on our vision of Assistant as an “anywhere agent” and our ongoing efforts to expand access to our purpose-built LLM, including to self-managed Grafana users.

You can now import a dashboard JSON straight into a Git Sync–provisioned folder. From the folder’s browse view, hit Import and Grafana will route you through a provisioned import flow: pick the file path, branch, commit message, and workflow, and the dashboard gets committed back to your repository as part of the import.

Git Sync now signs commits with your user’s signing key, so Git providers mark them as Verified. GPG, SSH, and S/MIME keys are all supported. Configure a signing key on the repository, and every commit Git Sync makes to your branch is signed automatically.

Git Sync provisioned folders now render their README.md inline below the dashboards list, out of the box. Add a README.md next to your dashboards in the repo and it shows up in Grafana: context, links, ownership notes, runbooks, whatever your team needs sitting alongside the dashboards.

Git Sync now supports syncing a repository to the top level of your Grafana instance, with no parent folder. Pick Sync at root level without a containing folder in the setup wizard and your provisioned dashboards land at the root, alongside everything else, instead of being scoped under a single folder.

Earlier this year, we introduced multi-property variables in public preview for Grafana OSS and Enterprise (and generally available in Grafana Cloud). Now, this feature is generally available in Grafana OSS and Enterprise.

PDC app v0.14.17 fixes an issue with token generation for older PDC networks created before 2024.

Dependencies have also been cleaned up, with an obsolete dependency removed that is no longer needed in modern browsers.

The revamped query editor experience is now in public preview. Since the initial private preview release, we’ve continued to refine the experience and added two new capabilities to help you work with complex panels even faster: multi-select with bulk actions and a stacked view.

Analyze metrics cardinality history directly in the Cost Management and Billing App

We’re excited to announce the general availability of Historical Cardinality!

When active series counts increase, it can be difficult to determine what changed and which metrics or labels are responsible. Historical Cardinality helps you investigate cardinality growth over time, identify the source of cardinality spikes, and uncover opportunities to reduce observability costs

You can now add static labels to Azure metrics credentials in Cloud Provider Observability. Static labels are custom key-value pairs that are attached to every metric collected from a credential, giving you a consistent, queryable dimension that Azure Monitor doesn’t provide on its own.

Find the trace you need, even when it was dropped. Adaptive Traces now keeps every dropped trace queryable by trace ID for 24 hours after ingest, so a trace ID from a log line, exemplar, or an upstream system always returns a result.