docs: clarifying alert rule limits in Grafana cloud for migration assistant #108722
+12
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this feature?
Adds information on alert rule limits in Grafana Cloud and adds subheadings for alerting resources section of migration assistant docs
Why do we need this feature?
Currently, when trying to migrate alert rules in excess of the limits in Grafana Cloud, users are simply met with an error telling them to delete alert rules or change their cloud plan. This is not helpful as they have no context as to what the limits are so there is no way they can triage (even paid customers need to contact support manually to exceed the soft limit in cloud). This PR adds a reference to what the limits are so people reading the docs are provided actionable information. Additionally, this PR breaks the "Grafana Alerting" subheading into 2 sections, previously it all kind of ran together. This way the information is more structured and clear as to what the sections are describing.
Who is this feature for?
All users of the Grafana Cloud Migration Assistant.
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Please check that: