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

docs: add note about alert migration (#102741)

Browse Source 
* docs: add note about alert migration

added note about alert migration in 11.6.0.

* docs: add note about alert migration

adding documentation about the migrations to the performance limitation docs

* title edit

<-- vale = NO -->
This commit is contained in:
Johnny Kartheiser
2025-03-26 15:39:32 -05:00
committed by GitHub
parent 4539e007bb
commit 558773ed7f
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/alerting/set-up/performance-limitations/index.md
+4
View File
@@ -80,3 +80,7 @@ If Grafana crashes or is force killed, then the database can be up to `state_per
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.
## Alert rule migrations for Grafana 11.6.0
When you upgrade to Grafana 11.6.0, a migration is performed on the `alert_rule_versions` table. If you experience a 11.6.0 upgrade that causes a migration failure, then your `alert_rule_versions` table has too many rows. To fix this, you need to truncated the `alert_rule_versions` table for the migration to complete.