grafana/grafana

Alerting: Support AWS and Azure Managed Prometheus data sources in alert rule import/conversion

Open

#123144 opened on Apr 21, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (73,744 stars) (13,868 forks)batch import
area/alertinggood first issueinternal

Description

Summary

When importing/converting data-source-managed Prometheus alert rules to Grafana-managed alert rules, the conversion fails if the selected data source is AWS Managed Prometheus (grafana-amazonprometheus-datasource) or Azure Managed Prometheus (grafana-azureprometheus-datasource). Only native prometheus and loki types are currently accepted by the converter.

Steps to Reproduce

  1. Have an AWS Managed Prometheus or Azure Managed Prometheus data source configured.
  2. Navigate to Alerting → Alert rules and use the import/convert feature (data-source-managed → Grafana-managed).
  3. Select the AWS or Azure Prometheus data source.
  4. Attempt to import a valid Prometheus rules YAML.

Expected Behavior

The import should succeed. AWS Managed Prometheus and Azure Managed Prometheus are Prometheus-compatible data sources and their rule format is identical to native Prometheus. The converter should recognize and support them.

Actual Behavior

The conversion fails with:

Failed to create Prometheus converter
error="[alerting.invalidDatasourceType] invalid datasource type: grafana-amazonprometheus-datasource, must be prometheus or loki"

Failed to convert Prometheus rules to Grafana rules
error="[alerting.invalidDatasourceType] invalid datasource type: grafana-azureprometheus-datasource, must be prometheus or loki"

The same YAML imports successfully when a native prometheus type data source is selected.

Proposed Fix

Expand the datasource type allowlist in the Prometheus converter to include:

  • grafana-amazonprometheus-datasource
  • grafana-azureprometheus-datasource

These datasources expose the same Prometheus-compatible rule format and their inclusion is a natural extension of the existing logic.

Additional Context

  • Grafana version: 13.0.0-23772453380
  • Affected datasource types: grafana-amazonprometheus-datasource, grafana-azureprometheus-datasource
  • Unaffected: native prometheus datasource type

Contributor guide

Tech stack
go
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go knowledgeGrafana alerting codebase familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
The issue is in the Prometheus alert rule converter, likely in the Go backend. The validation logic currently accepts only 'prometheus' and 'loki' datasource types. Add 'grafana amazonprometheus datasource' and 'grafana azureprometheus datasource' to the allowlist. Search for the error message 'invalid datasource type' to locate the exact file. No existing PRs or comments provide further guidance.