What Is New in Grafana 12.1
| Category | Highlights |
|---|---|
| New Features | Alert rule list page redesign; Trendline (regression) transformation; Custom variable support in visualization actions; Entra Workload Identity authentication; Grafana Advisor health checks; LogicMonitor Enterprise data source; BigQuery Service Account Impersonation; Server-configurable quick time ranges; Exact-value currency formatting |
| Improvements | Mute Timings renamed to Active Time Intervals; Ability to import Prometheus-style rules via the alerting UI |
| Breaking Changes | Mute Timings field removed - replaced by Active Time Intervals, requiring dashboard and alert config updates |
How does the new Alert Rule List page simplify alert management?
The new Alert Rule List page provides a faster, more flexible UI for creating, editing, and searching alert rules. In practice, the redesign introduces a searchable table, bulk actions, and inline status indicators, reducing the clicks needed to locate a rule. Key benefits for production teams:- Instant filtering by rule name, datasource, or severity.
- Bulk enable/disable or mute operations without leaving the page.
- Responsive layout that scales on large rule sets.
What is the Trendline transformation and how can it be used for regression analysis?
The Trendline transformation adds a regression-fitted series to any query result, enabling forward-looking predictions or gap filling. You can select linear or polynomial models directly in the panel editor, then style the generated series like any other metric. Typical use cases:- Projecting future load based on recent trends.
- Estimating missing points in sparse IoT telemetry.
- Visually confirming whether a noisy series follows an expected growth curve.
How can custom variables make visualization actions more dynamic?
Custom variables let you prompt users for input when an action (e.g., API call, webhook) is triggered, without editing the dashboard JSON. In practice, you define a variable placeholder in the action URL or payload, and Grafana displays a modal dialog for the value at runtime. This is especially useful for:- Sending alerts with a user-selected ticket ID.
- Filtering external API requests based on a chosen region.
- Passing ad-hoc parameters to downstream automation tools.
{
"url": "https://example.com/trigger?env=${customEnv}",
"method": "POST"
}
When the action runs, Grafana asks for "customEnv" and injects the entered value into the request.
Why is Entra Workload Identity a game-changer for Azure-based deployments?
Entra Workload Identity lets Grafana obtain federated Azure credentials without storing long-lived client secrets. This simplifies the OAuth flow: Grafana authenticates using the Azure workload identity endpoint, and token exchange happens automatically. Security teams benefit from reduced secret sprawl and compliance with zero-trust principles. Most teams will only need to enable the feature in the auth settings and point the datasource to the Azure tenant ID.How do server-configurable quick time ranges improve dashboard usability?
Server administrators can now pre-define custom time range presets that appear in the dashboard time picker. In production, this means you can enforce organization-wide windows such as "Last Business Day" or "Quarter-to-Date" without requiring each user to type a custom range. Implementation steps:- Edit the Grafana configuration file to add a `quick_ranges` block.
- Restart the server; the new presets appear automatically on all dashboards.
Frequently Asked Questions
Can existing alert rules be migrated to the new Alert Rule List page without changes?
Yes, all existing rules are imported automatically, but you should review any use of the renamed Active Time Intervals field.
Is the Trendline transformation available for all panel types?
It works with any time-series panel that supports transformations, such as Graph, Time series, and Bar gauge.
Do I need to restart Grafana after enabling Entra Workload Identity?
Yes, a server restart is required for the new authentication provider to be loaded.
How do I define a custom variable for a visualization action?
You add a placeholder like ${myVar} in the action definition and Grafana will prompt for myVar when the action is triggered.
What syntax should I use to import Prometheus rules via the UI?
Upload the Prometheus YAML file in the Import Rules dialog; the UI will map rule groups to Grafana Managed alerts.
Can I test the quick time ranges before applying them globally?
You can add them to the config file on a staging instance and verify they appear in the picker before rolling out.