grafana/grafana

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

Open

#123,144 建立於 2026年4月21日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)TypeScript (73,744 star) (13,868 fork)batch import
area/alertinggood first issueinternal

描述

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

貢獻者指南

技術棧
go
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
1
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go knowledgeGrafana alerting codebase familiarity
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
85
研究方向
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.