Skip to Content
AlertingAlert Events

Alert Events

This page documents all alert event types generated by exit1.dev.

Website & API Events

EventDescriptionTriggered When
website_downWebsite or API check is downCheck fails and meets consecutive failure threshold
website_upWebsite or API check recoveredCheck succeeds after being down
website_errorCheck encountered an errorUnexpected error during check execution

SSL Events

EventDescriptionTriggered When
ssl_errorSSL certificate errorCertificate is invalid, expired, or has chain issues
ssl_warningSSL certificate warningCertificate is approaching expiration

Domain Events

EventDescriptionTriggered When
domain_expiringDomain approaching expirationDomain expiry is within a configured threshold
domain_expiredDomain has expiredDomain has passed its expiration date
domain_renewedDomain has been renewedDomain expiration date has been extended

Event Payload Structure

All events share a common payload structure:

{ "event": "website_down", "check": { "id": "abc123", "name": "Production Website", "url": "https://example.com", "type": "website", "method": "GET" }, "status": { "current": "down", "previous": "up", "statusCode": 503, "responseTime": null, "error": "Connection timeout" }, "region": "us-central", "timestamp": "2025-01-15T14:30:00Z", "consecutive_failures": 3 }

Flap Suppression

Flapping occurs when a check rapidly alternates between up and down status. exit1.dev suppresses alerts from flapping checks using the minConsecutiveEvents setting.

How It Works

  • Each check tracks the number of consecutive same-status events
  • Alerts are only sent when the consecutive count reaches minConsecutiveEvents
  • This prevents alert storms from unstable endpoints

Configuration

The minConsecutiveEvents value can be set per check:

ValueBehavior
1 (default)Alert on every status change
2Require 2 consecutive events before alerting
3Require 3 consecutive events before alerting

Example

With minConsecutiveEvents: 3:

  1. Check fails (count: 1) - No alert
  2. Check fails (count: 2) - No alert
  3. Check fails (count: 3) - Alert sent: website_down
  4. Check succeeds (count: 1) - No alert
  5. Check succeeds (count: 2) - No alert
  6. Check succeeds (count: 3) - Alert sent: website_up
Last updated on