What's new from Grafana Labs

Introducing LogicMonitor data source plugin.

The LogicMonitor Devices data source plugin enables you to query and visualize Device Instance Data, and to list Devices, Datasources, and Instances directly within Grafana.

We’re excited to announce the public preview release of new alerting capabilities for Synthetic Monitoring. These new capabilities are available to all Grafana Cloud users.

You can now create alerts for each check in your Synthetic Monitoring application. For example, you can create an alert based on the number of check failures in a specific time window, with different settings for each one of your checks.

The pipeline history feature in Fleet Management now offers you the chance to restore versions of existing configuration pipelines. From the History details page, choose a version and click Restore.

Here’s how it works:

• Restoring a pipeline version overwrites the configuration of the current pipeline.
• A restored pipeline is set to the same Active or Inactive state as the pipeline it overwrites.
• When a pipeline version is restored, its matching attributes can also be restored, or the matching attributes from the overwritten pipeline can be persisted in the restored version.

Pipelines in Grafana Fleet Management can now leverage the Alloy export block  to share their components with other pipelines. With pipeline export injection, you can export components from one configuration pipeline and inject them into another using the syntax argument.pipeline_exports.value["PIPELINE_NAME"]["EXPORT_NAME"]. This powerful feature enables you to create dynamic configurations that adapt to each pipeline’s exported values, allowing for flexible and reusable pipeline configurations.

Sort and filter logs with ease in the Logs and Events tables. You can use multiple filters, including:

• Time period
• Component
• Cloud region
• Error level

Find any non-standard workloads using filters on the Workloads main page. Filtering includes:

• Argo Rollouts
• Strimzi Pod sets
• Unmanaged (or static) Pods
• CronJobs
• Bare Pods

The memory tab and panels are accessible on any detail page beyond the container level. Now you can view memory usage in correlation with relevant data points, as shown in the screen capture of a namespace.

In this case, you can see at a glance key data such as:

With early detection patterns, Adaptive Logs now shows log patterns without waiting to see how often they are queried. This feature allows you to proactively detect and filter out wasteful logs, ensuring only the most valuable telemetry is ever shipped to Grafana Cloud.

We’ve updated the main navigation in Grafana Cloud to bring all observability tools together under a single menu called Observability. You’ll now find App Observability, Frontend Observability, Kubernetes Monitoring, Infrastructure Monitoring, Cloud Provider Observability, and more grouped in one place.

This change is part of our effort to provide:

• A simpler, more consistent experience across observability tools
• Faster access to relevant signals and workflows
• A foundation for deeper, context-aware troubleshooting powered by Grafana’s Knowledge Graph

We’re excited to introduce SLO Reports—a powerful new feature in Grafana SLO that enables users to report on multiple service level objectives (SLOs) on a weekly or monthly basis.

With SLO Reports, you can now:

• Consolidate multiple SLOs into a single, easy-to-digest report
• View individual and combined SLI (Service Level Indicator) metrics
• Understand weighted contributions of each SLO to the overall SLI performance

You can now sync Grafana IRM’s phone numbers to your mobile contacts. This helps you recognize IRM calls and allows you to bypass Do Not Disturb (DnD) for urgent alerts.

Benefits

• Incoming IRM calls and SMS messages appear with the contact name Grafana IRM instead of an unknown number.
• You can configure your phone to allow calls and messages from Grafana IRM to override DnD or silent mode.

How it works

1. In the IRM mobile app, go to Settings > Sync Grafana IRM contact.
2. Toggle the setting on to enable.
3. The app will create a contact named Grafana IRM using known IRM phone numbers.

The list of phone numbers is updated automatically whenever you open the app and new numbers are available. Once enabled, this setting adds a contact card with our verified SMS and call numbers.

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.