Alerts & Notifications

Health Alert Threshold

Set the health-score number that triggers an alert. Range 0–100, default 70. Setting 0 is valid and disables score-based alerts.

Updated 2026-06-15

1 min read

health score

threshold

alert

Health Alert Threshold#

Every site gets a health score from 0–100 after each check. The Health alert threshold is the number you drop below before LemWatch fires a "health degraded" alert.

Default#

70 — sensible starting point for production sites

Range#

0 → 100 — both ends inclusive

0 is a valid setting and means *never* fire a score-based alert (useful for staging or low-priority sites)

The form preserves 0 explicitly — earlier versions silently turned 0 into the default 70

How to pick a value#

Site type	Suggested threshold
Critical production	80–90 (any degradation pages you)
Marketing site	65–75 (default behaviour)
Staging / dev	0 or 30 (rarely fires)
Multi-region SaaS	75 + use response-time thresholds for tighter SLAs

How it interacts with other alerts#

Down detection (HTTP 5xx, timeout) always fires regardless of this threshold

The threshold only governs the score-degradation alert

Combine with response-time thresholds and expected body content for layered alerting

Was this article helpful?

Suppressed alerts in the inbox

Flapping detection

How Health Scores Work

Deep dive into how LemWatch calculates and attributes health scores.

Setting Up Alerts

Configure 11 notification channels — email, push, chat, on-call, and automation tools.

Response Time Threshold Alerts

Get alerted when response times consistently exceed your limits.

Can I send alerts for one site to a different email?

Yes — override the default notification email on any site to route its alerts to a client or team-specific inbox.

Back to Help Center