What's new from Grafana Labsbreadcrumb arrow Manage Prometheus, Mimir, and Loki alerting with a dedicated plugin
What's new from Grafana Labs
What's new from Grafana Labs
Grafana Cloud Available in public preview Open Source Enterprise Experimental Alerting
Release date
2026-10-20
Self-managed release
Grafana v13.3.0

Manage Prometheus, Mimir, and Loki alerting with a dedicated plugin

Managing alert rules in Prometheus, Mimir, and Loki is moving into a dedicated Grafana app plugin, Prometheus Alerting. The plugin is built around how those systems actually work. It manages rule groups and namespaces in a Prometheus-compatible ruler, along with routes, receivers, templates, silences, time intervals, and inhibition rules in an external Alertmanager.

With the plugin installed and the hand-off enabled, Grafana routes data source managed alerting URLs to the matching page in the plugin. Shared links, bookmarks, and in-product links keep working — they land in the plugin instead of the core alerting UI. Grafana-managed alerting stays in core, and both experiences run side by side in the same Grafana instance.

TODO: Screenshot of the Prometheus Alerting plugin's rule list, showing rule groups and namespaces from a Mimir data source.

What moves to the plugin

When the hand-off is active, Grafana sends data source managed URLs to the matching page in the plugin. That covers:

  • View and edit of individual rules.
  • Group pages.
  • External Alertmanager pages for receivers, templates, routes, time intervals, and silences.

The rule list in core alerting stops showing data source managed rules. A notice names how many data sources moved and links to the plugin’s rule list, carrying over the current search. The alert rule editor in core becomes Grafana-managed only; the data source managed rule type is created in the plugin.

TODO: Screenshot of the core Grafana rule list showing the 'N data sources are managed by the Prometheus Alerting plugin' notice with a link into the plugin.

What stays in core Grafana

Grafana-managed alert rules and the built-in Grafana Alertmanager keep their current UI. The alert list panel keeps working for both kinds of rule, including rules from external data sources. Only its link to the rule list changes: for data source managed rules, it points at the plugin.

In Alerting > Settings, you can still enable or disable individual Alertmanagers to receive Grafana-managed alerts — that control stays in core.

Enable the hand-off

Three conditions have to agree before Grafana defers to the plugin:

  • The alerting.dataSourceManagedRouteProxy feature toggle is enabled.
  • Unified alerting is enabled.
  • The Prometheus Alerting plugin is installed and enabled.

To try out the hand-off, enable the alerting.dataSourceManagedRouteProxy feature toggle. It’s experimental and off by default. With the toggle off or the plugin absent, every page behaves as it does today.

What’s coming next

The Prometheus Alerting plugin is the planned long-term home for data source managed alerting. Data source managed rules will be removed from the core alerting experience in a future release.

The internal “lotex” APIs that the core alerting UI uses for data source managed rules will be removed in the next major Grafana release. If you depend on them, for example for custom access control, move to the data source APIs instead.

Grafana-managed alerting isn’t going anywhere, and Prometheus, Mimir, and Loki alerting isn’t being deprecated. If you’d prefer to consolidate on Grafana-managed alerting, an import tool is available in public preview; refer to Import of Alertmanager configuration.


Related What's new posts