What’s new in Grafana Cloud

Filter by Pod type on the Workloads list page to find static Pods and bare/unmanaged Pods.

Control the automatic refresh interval of the GUI as well as disable the auto refresh until you are ready to do so manually. This is particularly useful for very large Kubernetes fleets that display a lot of data.

Navigate to the Alert rules page from a list item on a Cluster, namespace, Node, Pod, or container list. To do so, click the underlined alert number for next to the list item.

Use the in-app Cardinality page to discover on a Cluster-by-Cluster basis where all your active series are coming from for:

• Troubleshooting after initial configuration
• Determining potential duplicate metrics
• Finding other potential cardinality issues

Explore Metrics is a query-less experience for browsing Prometheus-compatible metrics. Search for or filter to find a metric. Quickly find related metrics - all in just a few clicks. You do not need to learn PromQL! With Explore Metrics, you can:

• easily slice and dice metrics based on their labels, so you can see anomalies right away
• See the right visualization for your metric based on its type (e.g. gauge vs. counter) without building it yourself
• surface other metrics relevant to the current metric
• “explore in a drawer” - expand a drawer over a dashboard with more content, so you don’t lose your place
• view a history of user steps when navigating through metrics and their filters
• easily pivot to other related telemetry - IE, logs or traces

… all without writing any queries!

After you run a performance test in Grafana Cloud k6, the next step is to analyze the results and share any findings with your team. Sometimes, you don’t need your team members to view all the resulting metrics, or you might want to generate a PDF in an accessible, easy-to-read format to share with external stakeholders.

The new export summary functionality in Grafana Cloud k6 allows you to export your test results as a Grafana dashboard. This dashboard includes panels and charts with key metrics from your test, such as max throughput, HTTP failures, average response time, and more. You can then share it with other team members, edit it, or export it as a PDF.

Grafana 11 adds the ability to color full table rows using the Colored background cell type of the table visualization. When you configure fields in a table to use this cell type, an option to apply the color of the cell to the entire row becomes available.

This feature is useful for a wide variety of use cases including mapping status fields to colors (for example, info, debug, warning) and allowing rows to be colored based on threshold values. This is one of the first steps in making formatting tables more seamless, and allows for quick scanning of data using the table visualization.

Grafana Synthetics now supports longer durations for two options:

Timeout -> Increased maximum to 60 seconds.
Frequency -> Increased maximum to 60 minutes.

Plugin developers and users typically want their plugins to be compatible with a range of Grafana versions. However, ensuring this is true can be a challenge. The environment, APIs, and UI components may differ from one version to another. Manual testing is tedious and error-prone. End-to-End testing across multiple versions is prohibitively complicated given the version-to-version changes in Grafana itself - until now.

We would like to introduce @grafana/plugin-e2e - a new end-to-end testing library that is designed specifically for Grafana plugin developers. It extends @playwright/test capabilities with relevant fixtures, models, and expect matchers; enabling comprehensive end-to-end testing of Grafana plugins across multiple versions of Grafana. This package simplifies the testing process, ensuring your plugin is robust and compatible with various Grafana environments.

The Alerting Provisioning HTTP API has been updated to enforce Role-Based Access Control (RBAC).

• For Grafana OSS, users with the Editor role can now use the API.
• For Grafana Enterprise and Grafana Cloud, users with the role Rules Writer and Set Provisioning status can access the API and limit access to alert rules that use a particular data source.
• Other roles related to provisioning, for example Access to alert rules provisioning API still work.

From a Pod, Cluster, namespace, or workload view, you can begin an incident investigation by clicking Run Sift investigation.

Pause and resume alert rule evaluation directly from the Alert rules list and details view. This helps Improve visibility of when alert rules have been paused by displaying “Paused” as the alert rule state.

It is hard for teams to collaborate on dashboards because they have to use different datasources. Grafana instances become cluttered and confusing with 100s of datasources.

Team LBAC (Label Based Access Control) is our first step towards seamless management of Grafana Teams access for Loki logs. Each team views the same data source filtered by their team’s label permissions.

AWS Logs with Firehose is currently in public preview. Grafana Labs offers limited support, and breaking changes might occur prior to the feature being made generally available.

Logs with Firehose leverages Amazon Kinesis Data Firehose and a minimal infrastructure to deliver logs to the ingestion pipeline within Grafana Cloud.

Notification policies are evaluated from top to bottom, so it is key to be able to choose which notification policy receives alerts first. This feature enables you to add notification policies as siblings instead of always inserting a child policy as well as choose where to insert new notification policies by selecting insert above or below.