Alerting
exit1.dev provides multi-channel alerting to keep you informed when your checks change status.
Alert Channels
| Channel | Free | Nano | Pro | Agency |
|---|---|---|---|---|
| 10/hr, 10/mo | 50/hr, 1,000/mo | 500/hr, 10,000/mo | 1,000/hr, 50,000/mo | |
| SMS | — | — | 25/hr, 50/mo | 50/hr, 100/mo |
| Webhooks | 1 | 5 | 25 | 50 |
| Slack | — | — | Yes | Yes |
| Discord | — | — | Yes | Yes |
| Microsoft Teams | — | — | Yes | Yes |
How Alerting Works
- A check runs and detects a status change (e.g., up to down)
- Smart verification re-checks after 30 seconds to confirm
- The consecutive failure threshold is evaluated
- If the threshold is met, alerts are dispatched to all configured channels
- 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
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
Last updated on