From 7372c446a41fb286faeb85fd257d353a518b3699 Mon Sep 17 00:00:00 2001 From: Pepe Cano <825430+ppcano@users.noreply.github.com> Date: Tue, 4 Jun 2024 10:31:21 +0200 Subject: [PATCH] Alerting docs: Specify Grafana alert rule evaluation (#88250) * Alerting docs: Specify Grafana alert rule evaluation * Mention alerts can display the same evaluation timestamp * Specify `concurrent` behavior in alert rule evaluation * Include a minor `Evaluation strategies` section --- .../alerting/fundamentals/alert-rule-evaluation/_index.md | 6 +++++- docs/sources/alerting/fundamentals/alert-rules/_index.md | 1 - 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md b/docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md index d9ac8005a4e..5de512dd012 100644 --- a/docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md +++ b/docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md @@ -37,9 +37,13 @@ Every alert rule is assigned to an evaluation group. You can assign the alert ru Each evaluation group contains an **evaluation interval** that determines how frequently the alert rule is checked. For instance, the evaluation may occur every `10s`, `30s`, `1m`, `10m`, etc. +**Evaluation strategies** + Alert rules in different groups can be evaluated simultaneously. -**Grafana-managed** alert rules within the same group are evaluated simultaneously. However, **data-source managed** alert rules within the same group are evaluated one after the other—this is necessary to ensure that recording rules are evaluated before alert rules. +- **Grafana-managed** alert rules within the same group are evaluated concurrently—they are evaluated at different times over the same evaluation interval but display the same evaluation timestamp. + +- **Data-source managed** alert rules within the same group are evaluated sequentially, one after the other—this is necessary to ensure that recording rules are evaluated before alert rules. ## Pending period diff --git a/docs/sources/alerting/fundamentals/alert-rules/_index.md b/docs/sources/alerting/fundamentals/alert-rules/_index.md index ee8f31d3f03..5cdc3b5442a 100644 --- a/docs/sources/alerting/fundamentals/alert-rules/_index.md +++ b/docs/sources/alerting/fundamentals/alert-rules/_index.md @@ -118,6 +118,5 @@ When choosing which alert rule type to use, consider the following comparison be | Add expressions to transform your data and set alert conditions | Yes | No | | Use images in alert notifications | Yes | No | | Organization | Organize and manage access with folders | Use namespaces | -| Evaluation of alert rules in the same evaluation group | Concurrent evaluation | Sequential evaluation | | Scaling | More resource intensive, depend on the database, and are likely to suffer from transient errors. They only scale vertically. | Store alert rules within the data source itself and allow for “infinite” scaling. Generate and send alert notifications from the location of your data. | | Alert rule evaluation and delivery | Alert rule evaluation and delivery is done from within Grafana, using an external Alertmanager; or both. | Alert rule evaluation and alert delivery is distributed, meaning there is no single point of failure. |