What's new from Grafana Labs

Kubernetes Monitoring offers CPU tabs with insightful panels on every detail page beyond the container page to provide you with quicker troubleshooting and better resource planning. You can gain deeper visibility from cluster to pod with utilization efficiency graphs and CPU distribution analysis.

CPU tabs available at every level beyond the container give you:

• An edge for finding issues
• Capacity sizing insights to optimize performance

You can now restrict Private Load Zones (PLZs) in Grafana Cloud k6 to be used by a limited set of projects.

This feature lets you assign projects to a PLZ so that only tests inside of that project can be run on a specific PLZ.

We’re excited to announce that Role-Based Access Control (RBAC) for Synthetic Monitoring is now generally available! This gives you the ability to fine-tune access and permissions within Synthetic Monitoring, offering greater control over who can access specific features.

With RBAC, you can assign different roles and permissions to users and teams, ensuring the right people have the right access. This makes managing your monitoring workflows more secure and flexible.

How it Works

Native TypeScript support is now available in the Grafana Cloud k6 Script Editor, allowing you to write type-safe code in the cloud without any additional setup.

TypeScript is a strongly typed language that extends JavaScript - all valid JavaScript code is also valid TypeScript. By adding static types, TypeScript helps you catch errors early in development, enabling you to identify bugs before your code runs.

You now have more flexibility to tailor Grafana IRM to your team’s specific incident response workflows with several new customization options:

• Custom incident statuses: Define additional phases, such as Investigating or Monitoring, to go beyond the default Active and Resolved statuses. Custom statuses help responders communicate progress more clearly and give stakeholders better visibility into the state of an incident.
• Custom metadata fields: Capture the information that matters most to your organization. Add custom fields, such as impacted services or involved teams, and even make them required to ensure consistent data collection across incidents.
• Private incidents: Limit visibility for sensitive incidents by declaring them privately. Private incidents automatically create a restricted Slack or Microsoft Teams channel and give you control over who has access throughout the incident.

To learn more, refer to the documentation on incident settings and private incidents.

Dynamic Alerting with our Forecasting and Outlier Detection features has been supporting role-based access control in Public Preview for the last months. We’re excited to announce that this feature is now generally available. This introduces the roles ML Editor, ML Viewer, Sift Editor and Sift Viewer to better manage access to our Dynamic Alerting features.

ML Editors can:

• Create/edit/delete forecasts and outlier detectors
• Create/edit/delete holidays

We’re excited to roll out three powerful enhancements to TraceQL, giving you more flexibility and performance when querying traces in Grafana Cloud with Tempo.

• Rank your metrics with new topk(n) and bottomk(n) functions to quickly get your highest and lowest ranking time series.
• Aggregate spans over time using sum_over_time() for built-in cumulative sums, such as total bytes, error counts.
• Fetch the latest traces first via the experimental most_recent=true query hint.

Ranking topk and bottomk functions for TraceQL metrics

When you’re looking at latency, error rates, or throughput across hundreds or thousands of services or endpoints, it’s easy to get lost in all the data. Previously, you’d have to pull back the full set of aggregates and then manually inspect or post‑process the results to find your worst offenders or best performers.

Segmentation allows customers to manage their Adaptive Metrics recommendations on a team, service, or system level, allowing for more granular management of Adaptive Metrics.

You can define label-based segments via a GUI, API, or Terraform. Each segment will then receive its own recommendations; rules and exemptions can then be managed per segment.

Logs Drilldown now contains a JSON viewer for structured log lines. With this new feature, users can more easily view, interact, and of course drill down into their JSON data. This table enables users to filter their JSON log lines so that they can view just the data they need in places like the Log Volume visualization.

To learn more, refer to the following video demo, as well as the Grafana Logs Drilldown documentation.

Upgrade your Grafana experience with a direct connection with GitHub.

Connect your instance to a GitHub repository, and manage your dashboards as code directly from the Grafana UI. By enabling Git Sync, you will be able to manage dashboards the same way you manage your code. Dashboards will be versioned in Git, and edited through a PR workflow, so that it’s always possible to track changes.

We’ve simplified the migration of data source-managed alert rules to Grafana-managed alert rules.

Using these tools and APIs, you can import data source-managed alert rules from Prometheus-compatible systems (Prometheus, Mimir, Loki) into Grafana as Grafana-managed alert rules. This simplifies migrating from data source alerts to Grafana Managed Alerts while preserving behavior of the rules. Alert rules can be imported from an easy-to-use UI tool or through API endpoints compatible with Mimirtool.

Flapping alerts can cause noise and obscure other issues. Now you can set the minimum amount of time that an alert remains firing after the breached threshold expression no longer returns any results. This sets an alert to a “Recovering” state for a duration of time so a re-triggered threshold incurred during this period won’t trigger a new alert.

Read the documentation for more information about how to set a “ Keep firing for” duration so you can use the Recovering state to eliminate unwanted noise.

You can now restore or permanently delete recently deleted Grafana-managed alert rules. Go to Alerts & IRM > Alerting > Recently deleted to see this function in action.

The table visualization panel just got a major performance boost. Load, sort, and filter large tables many times faster than before, now that the table visualization has been refactored to use the react-data-grid library.

Enhancements:

Performance: On a simulated large table of 41,400 rows and 17 columns, we see the following improvements:

If the feature flag for dynamic dashboards is enabled, once an existing dashboard is migrated to a dynamic dashboard and using schema v2, it can’t be migrated back. This issue will be solved in future versions of Grafana.

The issue only exists for self-managed users who want to roll back to a previous version of Grafana and users who provision dashboards as code. Grafana v12 has a mechanism to resolve both versions.