What’s new in Grafana Cloud

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.

You can use Grafana Cloud k6 cloud options to configure additional test parameters, such as how to distribute your test across load zones, or to use static IP addresses.

Before, you would use the options.ext.loadimpact object to pass any configuration parameters. Now, you can use the options.cloud object instead:

JavaScript Copy

export const options = {
  cloud: {
    name: 'Hello k6 cloud!',
    projectID: 123456,
    staticIPs: true,
  },
};

By leveraging structured metadata under the hood, Cloud Logs now provides a simplified syntax and better query performance for logs sent through our Cloud OTLP endpoint.

You now have the ability to customize specific colors for individual thresholds when using the Config from query results transformer. Previously, when you added multiple thresholds, they all defaulted to the same color, red. With this addition, you gain the flexibility to assign distinct colors to each threshold.

This feature addresses a common pain point highlighted by users. With customizable threshold colors, you now have greater control over your data representation, fostering more insightful and impactful analyses across diverse datasets.

You can now configure the Azure Monitor data source to authenticate as the logged-in Grafana user when making query and resource requests if you also use Azure Entra to sign your users into Grafana.

Current User authentication allows you to enforce Azure RBAC restrictions on your Grafana users by removing the need to provide broad service credentials. Once a data source is configured with Current User authentication a user will only have access to resources they can access directly in Azure.

We’ve made a number of improvements to the canvas visualization.

Enhanced flowcharting functionality

With the newly added Infinite panning editor option, you can now view and navigate very large canvases. This option is displayed when the Pan and zoom switch is enabled.

To try out this feature, you must first enable the canvasPanelPanZoom feature toggle.

The new alert rule detail view has a new look and feel with helpful metadata at the top. The namespace and group are shown in the breadcrumb navigation. This is interactive and can be used to filter rules by namespace or group. The rest of the alert detail content is split up into tabs:

Query and conditions