What’s new in Grafana Cloud

The SSO settings API has been updated to include support for SAML settings. The UI has also been updated to use the new API instead of the old Settings update at runtime API which is now deprecated and will be removed in a future version of Grafana. You can now manage SAML configurations as code from Terraform using the grafana_sso_settings resource.

Grafana Cloud k6 Cloud Insights is generally available! Cloud Insights can help you automatically identify potential issues in your system under test or k6 test script and get more accurate and insightful results from your performance tests. Cloud Insights analyzes telemetry data, such as metrics, logs, and traces generated during a test run, to identify issues and make recommendations on how to fix them. This can help you and your team save time when pinpointing the root cause of performance issues in your applications.

We are excited to release Explore Logs to most of our Cloud customers in public preview! Explore Logs helps developers quickly troubleshoot and gain insights from logs without needing to run a query. Notable highlights include: Quickly identify changes in behavior by looking at services in histograms Identify repeated log lines using the Patterns feature Easily remember and share state with teammates Progressively drill down to root cause using visual cues and point-and-click experiences to fine-tune scope For more information:

The Adobe Analytics data source plugin allows you to retrieve reports data from Adobe Analytics.

Standardized tooltips As a continuation of our efforts to standardize tooltips across visualizations, we’ve updated canvas visualization tooltips to be supported for all elements tied to data. Besides the element name and data, the tooltip now also displays the timestamp. This is a step forward from the previous implementation where tooltips were shown only if data links were configured. Data links improvements We’ve updated canvas visualizations so that you can add data links to canvas elements without using an override.

A new home page, Kubernetes Overview, gives you a snapshot of both healthy objects and potential issues. Additional user experience enhancements include: Overview and network tabs Deep links into Clusters More linking into root cause analysis Visual indicators for every Kubernetes object, including workload type, Pod, Cluster, and namespace For more enhanced ways to navigate, refer to Navigation tips.

For the past few months, we’ve been working on stabilizing the k6-browser module and its API, as well as improving the performance of Grafana Cloud k6 in handling browser tests with a high number of VUs. Today, we’re excited to announce that browser tests in Grafana Cloud k6 are generally available! You can now run browser tests with multiple VUs to better understand your application’s user experience and help you find and fix frontend performance issues.

You can now view a detailed timeline for a Grafana k6 browser test when executing it in Grafana Cloud k6, as well as any screenshots taken during that test run. The Grafana k6 browser module now uses OpenTelemetry to generate spans and traces that match a virtual user’s behavior and interactions with the browser as they execute the code in your test script. The results are streamed to Grafana Cloud k6 and displayed in the Browser Timeline section of the test results page.

To be more aligned with the OpenTelementry specification, Grafana Cloud Traces will return RetryInfo to correctly indicate retryable errors. For more information, refer to Retry on RESOURCE_EXHAUSTED failure.

Cost overview tab Use the Cost Overview tab to see a 90-day view of total compute cost, average cost per Pod, and average Pod count. This 90-day period is divided into the prior 30 days, the last 30 days from the current date, and an estimate of the next 30 days. Network data On every detail page for Cluster, namespace, workload, Node, and Pod, you can view network bandwith and saturation data.

For the past few months we’ve been working on a major update of our Dashboards architecture and migrated it to the Scenes library. This migration provides us with more stable, dynamic, and flexible dashboards as well as setting the foundation for what we envision the future of Grafana dashboards will be. Here are two of the improvements that are being introduced as part of this work: Edit mode It can be difficult to efficiently navigate through the visually cluttered options during the dashboard editing process.

GeoMap keyboard support The GeoMap panel can now be used with a keyboard! Focus the map area, move around with the arrows keys and zoom in and out using + and -. Panel shortcut keyboard support We have panel shortcuts, which previously only worked on whichever panel you hovered over. It now also takes into account the keyboard focus. Heading improvements The majority of screen reader users find things on a web page using headings.

We have recently released v2 of the GitLab data source plugin. The plugin was updated to the latest GitLab API version which unfortunately comes with some potential breaking changes to the Projects queries public field has been removed. Instead the already existing visibility field should be used public_builds are now called public_jobs For more information please refer to the official GitLab API documentation

Kubernetes Monitoring has added more troubleshooting tools: Find deleted Clusters, Nodes, Pods, containers, workloads, and namespace Zoom into an area on the graph to narrow the time range Jump directly to the list of Clusters, Nodes, and workloads from the home page Find deleted objects You can find deleted objects, such as a Node shown in this example: Zoom in to refine a time range Zoom in on a graph to narrow a time range for more analysis.

Kubernetes Monitoring has added more troubleshooting tools: Find deleted Clusters, Nodes, Pods, containers, workloads, and namespaces Zoom into an area on the graph to narrow the time range Jump directly to the list of Clusters, Nodes, workloads, and alerts from the home page Find deleted objects You can find deleted objects within a 30-day time period, such as a Node shown in this example: Zoom in to refine a time range