Alerting

exit1.dev provides multi-channel alerting to keep you informed when your checks change status.

Alert Channels

How Alerting Works

1. A check runs and detects a status change (e.g., up to down)
2. Smart verification re-checks after 30 seconds to confirm
3. The consecutive failure threshold is evaluated
4. If the threshold is met, alerts are dispatched to all configured channels
5. When the check recovers, recovery alerts are sent

Flap Suppression

To prevent alert fatigue from flapping services (rapidly alternating between up and down), exit1.dev uses the minConsecutiveEvents setting. This requires a minimum number of consecutive events before triggering an alert, reducing noise from unstable endpoints.

Alert Configuration

Alerts can be configured at two levels:

• Account level - Default alert settings applied to all checks
• Per-check level - Override settings for individual checks

Check Severity (P1–P5)

Each check has a severity from P1 (Critical) to P5 (Minimal), set with a slider under Alert behavior in its settings. Severity lets channels that support notification priority treat important sites differently from low-stakes ones — page me for a P1 outage, stay quiet for a P5 dev box — without configuring separate integrations. Today severity drives Pushover priority; checks default to P3, which keeps each integration’s own priority behavior unchanged.

Getting Started

• Email Alerts - Configure email notifications
• SMS Alerts - Set up SMS notifications (Pro and Agency plans)
• Webhook Alerts - Integrate with your systems
• Alert Events - Full event reference