Update set-up-for-high-availability.md (#75356)

* Update set-up-for-high-availability.md

Added a note to Enforce the need to setup separately the Alerting HA, as some customers keep opening tickets complaining about duplicate alerts when setting up Grafana HA.

* Update set-up-for-high-availability.md

Corrected note (alerts instead of wueries)

* Update docs/sources/setup-grafana/set-up-for-high-availability.md

Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com>

* Update docs/sources/setup-grafana/set-up-for-high-availability.md

Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com>

* Update docs/sources/setup-grafana/set-up-for-high-availability.md

* Update docs/sources/setup-grafana/set-up-for-high-availability.md

---------

Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com>
This commit is contained in:
Marin N 2023-09-26 17:00:42 +03:00 committed by GitHub
parent bd452fe904
commit 1ff116e85c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -19,6 +19,12 @@ weight: 900
# Set up Grafana for high availability
{{% admonition type="note" %}}
To prevent duplicate alerts in Grafana high availability, additional steps are required.
Please refer to [Alerting high availability](#alerting-high-availability) for more information.
{{% /admonition %}}
Grafana uses an embedded sqlite3 database to store users, dashboards, and other persistent data by default. For high availability, you must use a shared database to store this data. This shared database can be either MySQL or Postgres.
<div class="text-center">