GrafanaimplicitmediumCluster of 2 signals
Card #3343 · Grafana

Lack of UI import for native Grafana alerts

Merchants struggle to migrate alert rules between Grafana instances because there is no UI-based import functionality. Current alternatives like file provisioning lock alerts from being edited in the browser, while the API is difficult to use and lacks portable formats.

GrafanaUpdated 7d ago0.61
Pain score
0.61/ 1.00 · weighted product of four components
Reach0.50
distinct authors (log-normalized)
Recency1.00
freshness decay, half-life months
Engagement1.00
upvotes + comments, normalized
Monetization0.50
willingness-to-pay cues in evidence
§ Evidence — 4 verified quotes
It is super easy to export an alert rule from the UI, but there is absolutely no way to import that rule into another instance using the UI.
Forum·@anshusingh4nov2000··source ↗
If we ask our server admins to manually load the alert files onto the backend folder, Grafana puts a “Provisioned” lock on them. This means we can’t edit our own alerts in the browser
Forum·@anshusingh4nov2000··source ↗
I’d like to extract my configured alert-rules from a self-hosted Grafana instance and port them over to another instance for initial provisioning.
Forum·@monsdarnbagrid··source ↗
Provision via File : Not suitable to my usecase because user needs to be able to modify alert rules after initial provisioning
Forum·@monsdarnbagrid··source ↗

Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.

Upgrade to Pro