Last checked and updated on 01 Jun 2026
What Is New in Grafana 10.4
| Category | Highlights |
|---|---|
| New Features | Simplified Alert Notification Routing, UI-driven SSO/OAuth configuration, Return to Previous navigation, PagerDuty enterprise data source, SurrealDB data source, Table visualization for logs GA |
| Improvements | Geomap GeoJSON styling, Canvas element snapping & alignment, Inline data links in tables, Group-to-nested-table transformation, New tooltip capabilities, Rule evaluation spread over interval, UTF-8 support for Prometheus/Mimir Alertmanager |
| Deprecations | AngularJS plugin warnings added; AngularJS support will be disabled by default in Grafana v11 |
How does Grafana 10.4 simplify alert notification routing?
Grafana 10.4 lets you pick a contact point directly in the alert rule form, removing the need to manage matching notification policies.
- Enable the feature with
alertingSimplifiedRoutingtoggle. - Set optional muting, grouping, and timing right on the rule.
- Routing inherits the rule's RBAC, preventing accidental policy changes.
In practice this reduces the number of steps from three clicks to one, speeding up incident response setup.
What new UI and automation options are available for SSO/OAuth configuration in Grafana 10.4?
Grafana 10.4 introduces a self-serve UI, Terraform resource, and API endpoints for all supported OAuth providers.
- Configure Generic OAuth and other providers (GitHub, GitLab, Google, Azure AD, Okta) from the Grafana UI under the new SSO Settings page.
- Terraform example:
resource "grafana_oauth_provider" "github" { name = "github" client_id = var.github_client_id client_secret = var.github_client_secret scopes = ["read:user", "repo"] } - No service restarts required; changes apply instantly.
This matters if you manage large fleets of Grafana instances and need repeatable, code-driven SSO setups.
Which visualizations and panel features have been enhanced in Grafana 10.4?
Grafana 10.4 adds styling for GeoJSON layers, canvas snapping, inline data links, and new table capabilities.
- Geomap: style polygons, points, lines directly in the layer configuration.
- Canvas: elements now snap to a grid and align with each other for precise layouts.
- Tables: view data links inline and use the "Group to nested tables" transformation (enable
groupToNestedTableTransformation). - Tooltips: copy-on-click, scrollable content, hover proximity control, and candlestick tooltip options.
Most teams will see cleaner dashboards and less time spent on manual CSS tweaks.
How can I prepare for the upcoming AngularJS deprecation in Grafana?
Grafana 10.4 now shows warning banners on dashboards that depend on AngularJS plugins and adds warning icons on affected panels.
- Run the open-source
detect-angular-dashboardstool to generate a full report of impacted dashboards. - Plan migration to React-based plugins listed in the deprecation guide.
- Use the warnings on the Plugins admin page as a quick health check.
Watch out for hidden AngularJS dependencies in private plugins; the detection tool supports them from Grafana v10.1 onward.
Frequently Asked Questions
Can I enable Simplified Alert Notification Routing without restarting Grafana?
Yes you just toggle the alertingSimplifiedRouting feature flag and the UI updates immediately.
Do I need to upgrade my OAuth provider configuration when moving from Grafana 9 to 10.4?
No existing configurations continue to work; the new UI only adds additional management options.
Is the Group to nested tables transformation available by default?
No you must enable the groupToNestedTableTransformation feature toggle in the Grafana config.
How do I view the AngularJS plugin warnings on a dashboard?
Open the dashboard and look for a yellow banner at the top and warning icons on each affected panel.
What command runs the AngularJS detection tool against my instance?
Run npx @grafana/detect-angular-dashboards --url http://my-grafana:3000 --api-key YOUR_API_KEY.
Does the new PagerDuty enterprise data source support annotations out of the box?
Yes you can add PagerDuty incidents as annotations directly from the data source query editor.