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

Alerting docs: update Comparison between alert rule types (#87252)

Browse Source
This commit is contained in:
Pepe Cano
2024-05-06 17:32:33 +02:00
committed by GitHub
parent 10afa5a5a0
commit 1b69d647be
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/alerting/fundamentals/alert-rules/_index.md
+11 -9
View File
@@ -75,15 +75,17 @@ Alternatively, Grafana Enterprise and Grafana Cloud offer [recorded queries][rec
When choosing which alert rule type to use, consider the following comparison between Grafana-managed and data source-managed alert rules.
| <div style="width:200px">Feature</div> | <div style="width:200px">Grafana-managed alert rule</div> | <div style="width:200px">Data source-managed alert rule |
| ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Create alert rules<wbr /> based on data from any of the supported data sources | Yes | No. You can only create alert rules that are based on Prometheus-based data. |
| Mix and match data sources | Yes | No |
| Includes support for recording rules | No | Yes |
| Add expressions to transform<wbr /> your data and set alert conditions | Yes | No |
| Use images in alert notifications | Yes | No |
| 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. |
| <div style="width:200px">Feature</div> | <div style="width:200px">Grafana-managed alert rule</div> | <div style="width:200px">Data source-managed alert rule |
| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Create alert rules<wbr /> based any [supported data sources](#supported-data-sources) | Yes | No. Only Prometheus-based or Loki data sources. |
| Mix and match data sources | Yes | No |
| Add [expressions][expression-queries] to transform<wbr /> queried data and set alert conditions | Yes | No |
| Use [images in alert notifications][notification-images] | Yes | No |
| Create [recording rules](#recording-rules) | No | Yes |
| Support for [inhibition rules](https://prometheus.io/docs/alerting/latest/configuration/#inhibition-related-settings) | No | Yes |
| Alert rule storage and evaluation | Within Grafana | Within the data source |
| Alert delivery | Alerts are sent to either the [Grafana Alertmanager or an external Alertmanager][alert-manager]. | Alerts from the data source are sent to the Alertmanager configured in the data source. |
| Scalability | More resource-intensive as it depends on the Grafana instance and its database. It only scales vertically. | Evaluate and generate alerts from the data source. A distributed architecture allows for horizontal scaling. |
{{% docs/reference %}}