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

[v9.5.x] fix: ha_peer to ha_peers (#78396)

Browse Source 
fix: ha_peer to ha_peers (#75724)

(cherry picked from commit b3bf38ad68)

Co-authored-by: Arkadip Bhattacharya <in2arkadipb13@gmail.com>
This commit is contained in:
grafana-delivery-bot[bot]
2023-11-20 14:35:51 +01:00
committed by GitHub
co-authored by Arkadip Bhattacharya
parent 1069ba6e30
commit 0f3360514e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/alerting/set-up/configure-high-availability/_index.md
+1 -1
View File
@@ -28,7 +28,7 @@ Since gossiping of notifications and silences uses both TCP and UDP port `9094`,
1. In your custom configuration file ($WORKING_DIR/conf/custom.ini), go to the `[unified_alerting]` section.
2. 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.
You must have at least one (1) Grafana instance added to the `ha_peers` section.
3. Set `[ha_listen_address]` to the instance IP address using a format of `host:port` (or the [Pod's](https://kubernetes.io/docs/concepts/workloads/pods/) IP in the case of using Kubernetes).
By default, it is set to listen to all interfaces (`0.0.0.0`).