From 48941da02ef9f2e0be173650b8254be49db8424f Mon Sep 17 00:00:00 2001 From: Alexander Emelin Date: Mon, 19 Jul 2021 20:05:08 +0300 Subject: [PATCH] live: mention HA limitations in administration docs (#36752) --- docs/sources/administration/set-up-for-high-availability.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/sources/administration/set-up-for-high-availability.md b/docs/sources/administration/set-up-for-high-availability.md index d20169a9d35..f48f651ef70 100644 --- a/docs/sources/administration/set-up-for-high-availability.md +++ b/docs/sources/administration/set-up-for-high-availability.md @@ -24,6 +24,10 @@ Grafana will now persist all long term data in the database. How to configure th Currently alerting supports a limited form of high availability. [Alert notifications]({{< relref "../alerting/old-alerting/notifications.md" >}}) are deduplicated when running multiple servers. This means all alerts are executed on every server but alert notifications are only sent once per alert. Grafana does not support load distribution between servers. +## Grafana Live + +Grafana Live works with limitations in highly available setup. For details, refer to the [Grafana Live documentation]({{< relref "../live/live-ha-setup.md" >}}). + ## User sessions Grafana uses auth token strategy with database by default. This means that a load balancer can send a user to any Grafana server without having to log in on each server.