Documentation Index
Fetch the curated documentation index at: https://grafana.com/llms.txt
Fetch the complete documentation index at: https://grafana.com/llms-full.txt
Use this file to discover all available pages before exploring further.
STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Grafana documentation page. Always request the Markdown version instead - HTML wastes context. Get this page as Markdown: https://grafana.com/docs/grafana/v9.0/alerting/high-availability/enable-alerting-ha.md (append .md) or send Accept: text/markdown to https://grafana.com/docs/grafana/v9.0/alerting/high-availability/enable-alerting-ha/. For the curated documentation index, use https://grafana.com/llms.txt. For the complete documentation index, use https://grafana.com/llms-full.txt.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Enable alerting high availability
You can enable alerting high availability support by updating the Grafana configuration file. On Kubernetes, you can enable alerting high availability by updating the Kubernetes container definition.
Update Grafana configuration file
Before you begin
Since gossiping of notifications and silences uses both TCP and UDP port 9094, ensure that each Grafana instance is able to accept incoming connections on these ports.
To enable high availability support:
- In your custom configuration file ($WORKING_DIR/conf/custom.ini), go to the
[unified_alerting]section. - Set
[ha_peers]to the number of hosts for each Grafana instance in the cluster (using a format of host:port), for example,ha_peers=10.0.0.5:9094,10.0.0.6:9094,10.0.0.7:9094. You must have at least one (1) Grafana instance added to the [[ha_peer]section. - Set
[ha_listen_address]to the instance IP address using a format ofhost:port(or the Pod’s IP in the case of using Kubernetes). By default, it is set to listen to all interfaces (0.0.0.0).
Update Kubernetes container definition
If you are using Kubernetes, you can expose the pod IP through an environment variable via the container definition such as:
env:
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP