In recent versions of Grafana, starting from version 11, not all changes in rules cause the state to be reset. Interval and annotations now do not cause the state reset.
We are looking into reducing it even more Alerting: Reduce set of fields that could trigger alert state change by benoittgt · Pull Request #83496 · grafana/grafana · GitHub
I see that the Alerting Rule History annotates the state as “OK (Updating)”. Is it possible that the next fired alert could identify itself as being triggered after an update?
No, it’s not possible
Could you clarify about whether the “OK (Updating)” forced state is a Grafana implementation detail, a Loki one, or an AlertManager one?
This is the implementation details of Grafana Alerting. Changes in rules can affect the changes in alerts created by evaluating them. The Alertmanager will treat them as different alerts and therefore, there will be two alerts that belong to the same evaluated dimension. Read more in the issue Alerting: Reduce set of fields that could trigger alert state change by benoittgt · Pull Request #83496 · grafana/grafana · GitHub