From d442068cdce3b70610e00166cde26f180c2364e0 Mon Sep 17 00:00:00 2001 From: "grafana-delivery-bot[bot]" <132647405+grafana-delivery-bot[bot]@users.noreply.github.com> Date: Wed, 13 Sep 2023 15:35:54 +0300 Subject: [PATCH] [v9.4.x] Alerting docs: adds roll back warning to config grafana (#74828) Alerting docs: adds roll back warning to config grafana (#74785) (cherry picked from commit 38c3483594080b6d7e12d94f95bcacf67c3ac368) Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> --- docs/sources/setup-grafana/configure-grafana/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/sources/setup-grafana/configure-grafana/_index.md b/docs/sources/setup-grafana/configure-grafana/_index.md index 636baf97b70..4a19f3993b0 100644 --- a/docs/sources/setup-grafana/configure-grafana/_index.md +++ b/docs/sources/setup-grafana/configure-grafana/_index.md @@ -144,6 +144,8 @@ environment variable `HOSTNAME`, if that is empty or does not exist Grafana will Force migration will run migrations that might cause data loss. Default is `false`. +Set force_migration=true in your grafana.ini and restart Grafana to roll back and delete Unified Alerting configuration data. Any alert rules created while using Unified Alerting will be deleted by rolling back. +
## [paths]