Browse Source
The resolution countdown now only starts once every failing service has recovered. While any service is still firing the timer is cancelled, so the incident cannot auto-resolve and spawn a new incident for the same ongoing failure between alerts. High latency is a warning signal (no explicit recovery event) and therefore does not block resolution — only FAILING services do.pull/15456/head
2 changed files with 35 additions and 2 deletions
Loading…
Reference in new issue