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

[release-12.0.4] docs: clarifying alert rule limits in Grafana cloud for migration assistant (#108798)

Browse Source 
Co-authored-by: Jacob Valdez <jacob.valdez@grafana.com>
This commit is contained in:
grafana-delivery-bot[bot]
2025-07-28 09:08:27 -05:00
committed by GitHub
co-authored by Jacob Valdez
parent 809a7078cf
commit 5e1298ba48
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/administration/migration-guide/cloud-migration-assistant.md
+12
View File
@@ -197,8 +197,20 @@ The `grafana-default-email` contact point that's provisioned with every new Graf
This is sufficient to have your Alerting configuration up and running in Grafana Cloud with minimal effort.
#### Migration assistant limitations on Grafana Alerting resources
Migration of Silences is not supported by the migration assistant and needs to be configured manually. Alert History is also not available for migration.
Attempting to migrate a large number of alert rules might result in the following error:
```
Maximum number of alert rule groups reached: Delete some alert rule groups or upgrade your plan and try again.
```
To avoid this, refer to the [Alert rule limits in Grafana Cloud](https://grafana.com/docs/grafana-cloud/alerting-and-irm/alerting/alerting-rules/create-grafana-managed-rule/#alert-rule-limits-in-grafana-cloud) when migrating alert rules.
#### Prevent duplicated alert notifications
Successfully migrating Alerting resources to your Grafana Cloud instance could result in 2 sets of notifications being generated:
1. From your OSS/Enterprise instance