From ea202513cd9058569b45244bd344be84f75c4ef7 Mon Sep 17 00:00:00 2001 From: Sofia Papagiannaki Date: Tue, 6 Apr 2021 19:58:22 +0300 Subject: [PATCH] Docs: Rephrase Alert execution section in Alerting (#32631) * Docs: Rephrase Alert execution section in Alerting * Small fix datasources -> data sources * Rephrase alert execution --- docs/sources/alerting/_index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/sources/alerting/_index.md b/docs/sources/alerting/_index.md index e2a766a4448..e420c23118d 100644 --- a/docs/sources/alerting/_index.md +++ b/docs/sources/alerting/_index.md @@ -37,8 +37,10 @@ The actual notifications are configured and shared between multiple alerts. ## Alert execution Alert rules are evaluated in the Grafana backend in a scheduler and query execution engine that is part -of core Grafana. Only some data sources are supported right now. They include `Graphite`, `Prometheus`, `Loki`, `InfluxDB`, `Elasticsearch`, -`Google Cloud Monitoring`, `Cloudwatch`, `Azure Monitor`, `MySQL`, `PostgreSQL`, `MSSQL`, `OpenTSDB`, `Oracle`, and `Azure Data Explorer`. +of core Grafana. Alert rules can query only backend data sources with alerting enabled. Such data sources are: +- builtin or developed and maintained by grafana, such as: `Graphite`, `Prometheus`, `Loki`, `InfluxDB`, `Elasticsearch`, +`Google Cloud Monitoring`, `Cloudwatch`, `Azure Monitor`, `MySQL`, `PostgreSQL`, `MSSQL`, `OpenTSDB`, `Oracle`, and `Azure Data Explorer` +- any community backend data sources with alerting enabled (`backend` and `alerting` properties are set in the [plugin.json]({{< relref "../developers/plugins/metadata.md" >}})) ## Metrics from the alert engine