From 4b6b5a92edc2df7031ec1603674e1ddad8d893e3 Mon Sep 17 00:00:00 2001 From: "grafana-delivery-bot[bot]" <132647405+grafana-delivery-bot[bot]@users.noreply.github.com> Date: Mon, 22 Apr 2024 12:43:42 +0300 Subject: [PATCH] [v10.4.x] Update the docs for state_periodic_save_interval (#86667) Update the docs for state_periodic_save_interval (#86611) This commit updates the docs for state_periodic_save_interval following a question in the forums about what the consequences of this change could be. (cherry picked from commit 30d38c1775381d84328ea0006b62ec97577ff13e) Co-authored-by: George Robinson --- .../sources/alerting/set-up/performance-limitations/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/sources/alerting/set-up/performance-limitations/index.md b/docs/sources/alerting/set-up/performance-limitations/index.md index fda55b92932..935a889459d 100644 --- a/docs/sources/alerting/set-up/performance-limitations/index.md +++ b/docs/sources/alerting/set-up/performance-limitations/index.md @@ -67,3 +67,8 @@ can also be configured using the `state_periodic_save_interval` configuration fl The time it takes to write to the database periodically can be monitored using the `state_full_sync_duration_seconds` metric that is exposed by Grafana. + +If Grafana crashes or is force killed, then the database can be up to `state_periodic_save_interval` seconds out of date. +When Grafana restarts, the UI might show incorrect state for some alerts until the alerts are re-evaluated. +In some cases, alerts that were firing before the crash might fire again. +If this happens, Grafana might send duplicate notifications for firing alerts.