mirror of
https://github.com/grafana/grafana.git
synced 2025-02-25 18:55:37 -06:00
a568d421f8
* builds out refactored setup topics * Automatically fix some relrefs with mv-manager Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Use refs for tutorials content which is outside of this repository Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Manually fix complicated relrefs Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * consolidates team sync and db encryption topics * Fix relrefs Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * updates setup index file * Convert TOML to YAML Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Add current alias for new alerting content Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Add current aliases to new setup-grafana and configure-security pages Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/setup-grafana/configure-grafana/_index.md Co-authored-by: Torkel Ödegaard <torkel@grafana.com> * moves saml docs, updates order in TOC * Manually fix relrefs Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * added usage insights topics, adjusted weights * corrected relrefs * Fix relrefs broken in rebase Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Co-authored-by: Jack Baldry <jack.baldry@grafana.com> Co-authored-by: Torkel Ödegaard <torkel@grafana.com>
34 lines
1.7 KiB
Markdown
34 lines
1.7 KiB
Markdown
---
|
|
aliases:
|
|
- /docs/grafana/latest/alerting/high-availability/
|
|
- /docs/grafana/latest/alerting/unified-alerting/high-availability/
|
|
description: High availability
|
|
keywords:
|
|
- grafana
|
|
- alerting
|
|
- tutorials
|
|
- ha
|
|
- high availability
|
|
title: ' Alerting high availability'
|
|
weight: 450
|
|
---
|
|
|
|
# About alerting high availability
|
|
|
|
The Grafana alerting system has two main components: a `Scheduler` and an internal `Alertmanager`. The `Scheduler` evaluates your [alert rules]({{< relref "../fundamentals/evaluate-grafana-alerts/" >}}), while the internal Alertmanager manages **routing** and **grouping**.
|
|
|
|
When running Grafana alerting in high availability, the operational mode of the scheduler remains unaffected, and each Grafana instance evaluates all alerts. The operational change happens in the Alertmanager when it deduplicates alert notifications across Grafana instances.
|
|
|
|
{{< figure src="/static/img/docs/alerting/unified/high-availability-ua.png" class="docs-image--no-shadow" max-width= "750px" caption="High availability" >}}
|
|
|
|
The coordination between Grafana instances happens via [a Gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol). Alerts are not gossiped between instances and each scheduler delivers the same volume of alerts to each Alertmanager.
|
|
|
|
The two types of messages gossiped between Grafana instances are:
|
|
|
|
- Notification logs: Who (which instance) notified what (which alert).
|
|
- Silences: If an alert should fire or not.
|
|
|
|
The notification logs and silences are persisted in the database periodically and during a graceful Grafana shut down.
|
|
|
|
For configuration instructions, refer to [enable alerting high availability]({{< relref "enable-alerting-ha/" >}}).
|