From 50d1b2e786404d9fba16c25d239e6838a34c6a1d Mon Sep 17 00:00:00 2001 From: Alexander Akhmetov Date: Mon, 12 May 2025 23:34:06 +0200 Subject: [PATCH] Alerting: Document grafanaManagedRecordingRulesDatasources feature flag (#105227) --- .../create-grafana-managed-recording-rules.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/sources/alerting/alerting-rules/create-recording-rules/create-grafana-managed-recording-rules.md b/docs/sources/alerting/alerting-rules/create-recording-rules/create-grafana-managed-recording-rules.md index d3b0db3632f..13b5a957ffd 100644 --- a/docs/sources/alerting/alerting-rules/create-recording-rules/create-grafana-managed-recording-rules.md +++ b/docs/sources/alerting/alerting-rules/create-recording-rules/create-grafana-managed-recording-rules.md @@ -78,6 +78,18 @@ basic_auth_password = my-pass X-My-Header = MyValue ``` +### Per-rule data source + +To choose the remote-write Prometheus data source individually for each recording rule, also enable the `grafanaManagedRecordingRulesDatasources` feature flag. + +When this flag is on, Grafana does not use the `url` defined in the configuration file, and the rule editor shows a dropdown to select the target data source. If a rule does not specify a target, for example it was created before the flag was enabled, Grafana writes to the data source identified by `default_datasource_uid` in the Grafana configuration: + +``` +[recording_rules] + +default_datasource_uid = my-uid +``` + ## Add new recording rule To create a new Grafana-managed recording rule: