Alert Rules
Alert rules control when notifications are sent and to which channels.
Basic Alert Configuration
Every alert configuration has these settings:
Minimum Level
Set the minimum error level that triggers the alert:
- DEBUG: All events trigger alerts
- INFO: Info and above
- WARNING: Warnings and above
- ERROR: Only errors and fatal events (default)
- FATAL: Only fatal events
Cooldown Period
The cooldown prevents alert fatigue by setting a minimum time between notifications for the same issue. Range: 1 minute to 7 days (10,080 minutes). Default: 60 minutes.
During the cooldown, new events for the same issue are still processed and counted, but no additional alert is sent.
Per-Project Configuration
Alerts are configured per project. Each project can have multiple alert configurations targeting different channels with different settings.
Alert Routing
Alert routing rules let you direct specific alerts to specific channels based on conditions. Routing rules are associated with both a project and an alert configuration.
Uptime Alerts
Uptime monitors automatically send alerts to all configured alert channels when:
- Monitor goes DOWN: After the fail threshold is reached (default: 2 consecutive failures)
- Monitor recovers: When the monitor transitions back to UP
- Monitor degraded: When response time exceeds the degraded threshold
How Alerts Are Processed
- An event or monitor status change triggers the alert system
- The worker checks all alert configurations for the project
- For each matching config, it checks:
- Is the alert enabled?
- Does the event level meet the minimum level?
- Has the cooldown period elapsed since the last alert?
- If all conditions pass, the notification is sent via the configured channel
- The
lastAlertedAttimestamp is updated to enforce the cooldown
Subscriber Notifications
Status page subscribers (see Status Pages) receive notifications separately from alert channels. When a status page incident is created or updated, all subscribers are notified via email.