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

Removed content as per MarcusE's suggestion in https://github.com/grafana/grafana/issues/33822. (#33870) (#33872)

Browse Source 
(cherry picked from commit 076f076961)

Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>
This commit is contained in:
Grot (@grafanabot)
2021-05-10 20:22:18 +02:00
committed by GitHub
co-authored by achatterjee-grafana
parent cf389959d2
commit d2837c50f9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/administration/set-up-for-high-availability.md
+1 -1
View File
@@ -26,4 +26,4 @@ Currently alerting supports a limited form of high availability. [Alert notifica
## 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. If you want to offload the login session data from the database, then you can configure [remote_cache]({{< relref "../administration/configuration.md" >}}#remote-cache).
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.