public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Alerting docs: Specify Grafana alert rule evaluation (#88250)

Browse Source 
* 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
This commit is contained in:
Pepe Cano
2024-06-04 10:31:21 +02:00
committed by GitHub
parent 88a2485cc2
commit 7372c446a4
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md
+5 -1
View File
@@ -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
docs/sources/alerting/fundamentals/alert-rules/_index.md
-1
View File
@@ -118,6 +118,5 @@ When choosing which alert rule type to use, consider the following comparison be
| Add expressions to transform<wbr /> 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. |