docs(alerting): alert instance state resets when rule changes (#102038)
* docs(alerting): alert instance state resets when rule changes
* specify that annotations updates are not affected
* enumerate exception fields
(cherry picked from commit 3e1513a6df)
@ -52,14 +52,16 @@ An alert instance can be in either of the following states:
| **No Data<sup>\*</sup>** | The state of an alert whose query returns no data or all values are null. <br/> An alert in this state generates a new [DatasourceNoData alert](#no-data-and-error-alerts). You can [modify the default behavior of the no data state](#modify-the-no-data-or-error-state). |
| **Error<sup>\*</sup>** | The state of an alert when an error or timeout occurred evaluating the alert rule. <br/> An alert in this state generates a new [DatasourceError alert](#no-data-and-error-alerts). You can [modify the default behavior of the error state](#modify-the-no-data-or-error-state). |
If an alert rule changes (except for updates to annotations, the evaluation interval, or other internal fields), its alert instances reset to the `Normal` state. The alert instance state then updates accordingly during the next evaluation.
{{<figuresrc="/media/docs/alerting/alert-instance-states-v3.png"caption="Alert instance state diagram"alt="A diagram of the distinct alert instance states and transitions."max-width="750px">}}
{{<admonitiontype="note">}}
`No Data` and `Error` states are supported only for Grafana-managed alert rules.
{{</admonition>}}
{{<figuresrc="/media/docs/alerting/alert-instance-states-v3.png"caption="Alert instance state diagram"alt="A diagram of the distinct alert instance states and transitions."max-width="750px">}}
### Notification routing
Alert instances will be routed for [notifications](ref:notifications) when they are in the `Alerting` state or have been `Resolved`, transitioning from `Alerting` to `Normal` state.