Why am I getting false alerts?
Diagnose flapping monitors, rotating content, and single-region blips that fire alerts you can ignore.
Quick answer#
Most false alerts come from three sources: single-region network blips, flapping monitors, and rotating page content. Lemwatch already filters the first two with confirmation gates and hysteresis — this article helps you tune them.
What causes false alerts#
Where to check#
Alerts inbox → Suppressed tab shows alerts Lemwatch caught but held back. That's your evidence base.
How to reduce false alerts#
FAQ#
Will these settings make me miss real outages?#
No — every setting is a *confirmation delay*, not a threshold change. A real outage still alerts within 60–120 seconds.
Can I turn all filters off?#
Yes, but you'll see 3–5× more alerts. Not recommended.
Related#
Related Articles
Flapping detection
How Lemwatch suppresses monitors that flip up/down repeatedly instead of paging you every flip.
Alert confirmation gates
Lemwatch confirms a failure from multiple regions before alerting, so single-region blips stay quiet.
Hysteresis band explained
Lemwatch requires response time to fully clear a threshold before recovering, preventing oscillation alerts.
I'm Not Receiving Alerts
Triage missing or delayed alerts: quiet hours, channels, spam, thresholds, maintenance mode, escalation policies, and acks.