Grafana 9.0: What's New, Release History & Support Lifecycle

What Is New in Grafana 9.0

How do the new visual query builders make Prometheus and Loki queries easier?

The new UI query builders let you construct PromQL and LogQL expressions without typing the raw syntax.

• Start by selecting a metric or label filter; both act as mutual filters.
• Operations (functions, aggregations, binary ops) are added via a "+ Operation" button and displayed in execution order.
• Range vectors are auto-added for functions like rate or increase.
• Switch between the visual builder and raw code while preserving changes, thanks to a full-featured parser.

In practice, a team can onboard new SREs faster because the builder shows parameter names, documentation links, and a live preview of the generated query.

# Example: adding a rate function in the builder
metric: http_requests_total
operation: rate[5m]

What changes does Grafana 9 bring to alerting and how can I revert to legacy alerts?

Grafana Alerting (formerly unified alerting) is now enabled by default and all existing legacy rules are migrated automatically.

• Alert state history now distinguishes "Alerting (NoData)" and "Alerting (Error)".
• Images of dashboard panels can be attached to notifications when the alert references a specific panel UID and ID.
• To switch back, set GF_UNIFIED_ALERTING_ENABLED=false (or GF_UNIFIED_ALERTING_ENABLED = false in grafana.ini) before starting Grafana.

This matters if you rely on custom legacy UI extensions that have not yet been ported to the new alerting engine.

Why is the new heatmap panel considered a major performance upgrade?

The new heatmap panel uses the modern panel option architecture and renders up to 10× faster than the old version.

• Supports exemplars overlay, Prometheus sparse histograms, and configurable color steps.
• Smart auto-bucket sizing for unbucketed data and filters out near-zero bucket values.
• Assumes pre-bucketed data by default, allowing thousands of series with high-resolution points without UI lag.

Most production teams see a noticeable reduction in browser memory usage when visualizing large time-series datasets.

What are the key breaking changes I need to address before upgrading to Grafana 9?

Several core components have changed semantics or APIs, so a careful audit is required.

• RBAC: Built-in roles renamed to "basic roles", permission inheritance removed, provisioning schema updated.
• Loki logs format: Logs now come as a single dataframe with a labels field; replace "Labels to fields" transformation with "Extract fields".
• NaN handling: Both Prometheus and Loki now keep NaN values unchanged for all query types.
• Elasticsearch: Versions older than 7.10.0 and browser-access mode are no longer supported.
• Envelope encryption: Enabled by default; older nodes must have disableEnvelopeEncryption=true if you need to keep compatibility.
• Plugins & panels: Update clock panel to ≥ 2.0.0 and polystat panel to ≥ 1.2.10; adjust code that uses removed UI helpers.

Watch out for CI pipelines that generate dashboards programmatically; they may need to adapt to the new role names and transformation changes.

How do the UI/UX enhancements like the command palette and expanded navigation improve daily workflows?

The command palette (⌘K / Ctrl K) provides instant access to navigation, panel creation, and common actions without leaving the keyboard.

• Expanded navigation bar shows all installed integrations at a glance.
• Starred dashboards appear directly in the nav when the savedItems flag is enabled.
• Dashboard previews (beta) give a thumbnail overview of all dashboards, speeding up discovery.
• Panel-title full-text search (beta) enables fast lookup of panels by name.

In practice, engineers report a 20 % reduction in time spent navigating large Grafana instances.