What conditions and operators can I use in Alert Rules?
Rules support metric-based conditions (uptime, response time, SSL, status code, visual diff, SEO score) with numeric, boolean, and change operators.
Quick answer#
Supported operators: >, >=, <, <=, ==, !=, changed, increased by %, decreased by %, and for duration. Supported metrics span uptime, response time, SSL days-to-expiry, HTTP status, visual diff %, and SEO score.
Supported metric families#
Where to find it in Lemwatch#
Settings → Alerts → Rules → New rule → Add condition.
How to combine conditions#
for duration to require the condition to hold (kills flapping).FAQ#
What does "changed" mean for numeric metrics?#
Any non-zero delta from the previous check. Use % change for smoother triggers.
Can I compare two metrics?#
Not yet — every condition compares one metric to a constant.
Related#
Related Articles
How does the Alert Rules builder work?
The Alert Rules builder lets you compose conditions (metric + operator + threshold + duration) and route matching alerts to specific channels.
How do I route and suppress alerts from a rule?
Every rule has a routing block: pick channels, set quiet hours, dedupe windows, and escalation paths so noisy rules never wake the wrong person.
How does API endpoint degradation alerting work?
Lemwatch compares each endpoint's current response time against a rolling 24-hour baseline and alerts when it degrades by 2× or more.
AI alert noise reduction
Suppresses flapping alerts, deduplicates simultaneous incidents, and silences known-noise patterns — cuts alert volume by 50–80% for most teams.