What’s new in Grafana Cloud

The TraceQL query editor has been improved to facilitate the creation of TraceQL queries. In particular, it now features improved autocompletion, syntax highlighting, and error reporting.

To provide quicker identification and troubleshooting, the home page contains a snapshot of issues that reach the following thresholds: Pods that have been in a non-running state for more than 15 minutes Nodes with CPU usage above 90% for more than five minutes Nodes using more than 90% of memory for more than five minutes Persistent Volumes with capacity above 90% Node disks with capacity above 90% (Release 1.3.1)

With recorded queries, a single recorded query can now record multiple metrics.

The SAP HANA® data source now supports tenant databases connections by using the database name and/or instance number. For more information, refer to SAP HANA® configuration.

You can now use the Grafana Cloud Traces integration with Grafana Cloud k6 to quickly debug failed performance tests and proactively improve application reliability. Distributed tracing in Grafana Cloud k6 only requires two things: An application instrumented for tracing with Grafana Cloud Traces. Adding a few lines of code to your existing k6 scripts. The integration works by having k6 inject tracing metadata into the requests it sends to your backend services when you run a test.

The new browse dashboards interface features a more compact design, making it easier to navigate, search for, and manage for your folders and dashboards. The new interface also has many performance improvements, especially for instances with a large number of folders and dashboards. To make using folders easier and more consistent, there is no longer a special General folder. Dashboards without a folder, or dashboards previously in General, are now shown at the root level.

Configure with Grafana Kubernetes Monitoring Helm chart using a streamlined process. With this method, you can set on/off switches to gather metrics, logs, events, traces, and cost metrics. (Release 1.2.0)

You can change the data source you are viewing on the Cost and Efficiency views. (Release 1.2.1)

The Kafka integration is available for use in Kubernetes Monitoring. (Release 1.3.6)

Click Predict Memory usage to predict namespace memory usage on the namespace detail page. (Release 1.2.1)

Quickly switch between the Cluster, namespace, workload, and Node views on the Cluster Navigation page using tabs. (Release 1.3.0)

Collect traces when you configure Kubernetes Monitoring, and then use Tempo to create search queries. Refer to Navigate to traces for more information. (Release 1.3.0)

You can now create correlations using either the Administration page or provisioning, regardless of whether a data source was provisioned or not. In previous versions of Grafana, if a data source was provisioned, the only way to add correlations to it was also with provisioning. Now, that’s no longer the case, and you can easily create new correlations mixing both methods—using the Administration page or provisioning. To enable this feature, contact Grafana Support.

Use the Grafana Alerting - Grafana OnCall integration to effortlessly connect alerts generated by Grafana Alerting with Grafana OnCall. From there, you can route them according to defined escalation chains and schedules. To learn more, refer to the Grafana OnCall integration for Alerting documentation.

The Tempo data source now supports query-type template variables. With this update, you can create variables for which the values are a list of attribute names or attribute values seen on spans received by Tempo. To learn more, refer to the following video demo, as well as the Grafana Variables documentation.