apitech
/
grafana
mirror of https://github.com/grafana/grafana
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35327 Commits
2179 Branches
608 Tags
1.9 GiB
 
 
 
 
 
 
Tag: Branch: Tree: b84294dd27
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b84294dd27'
${ noResults }
grafana/docs/sources/alerting/high-availability/_index.md

1.7 KiB
Raw Blame History

aliases description keywords title weight
[/docs/grafana/latest/alerting/high-availability/ /docs/grafana/latest/alerting/unified-alerting/high-availability/] High availability [grafana alerting tutorials ha high availability] Alerting high availability 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.md" >}}), 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. 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.md" >}}).