Alert confirmation gates
Lemwatch confirms a failure from multiple regions before alerting, so single-region blips stay quiet.
Quick answer
Before firing a down alert, Lemwatch re-checks from 2 additional regions. If any region succeeds, the alert is suppressed as a single-region blip.
What it does
- Detects a failure from the primary region
- Immediately runs a confirmation check from 2 backup regions
- Fires the alert only if all 3 regions confirm the failure
- Otherwise logs the incident as suppressed with reason "single-region"
Where to find it in Lemwatch
Site → Settings → Alert accuracy → Confirmation gate.
How to tune it
- Open the site's Alert accuracy settings.
- Toggle Multi-region confirmation on (default).
- Choose how many regions must agree (default 2 of 3).
- For critical sites, set All regions must fail — reduces false positives further.
- Save.
FAQ
Does confirmation delay real alerts?
By 20–40 seconds at most. That's the cost of skipping a false page.
Can I see which region failed?
Yes — every incident record lists per-region status.
Related