Alerts & Notifications
Stay informed when issues occur. FlareWarden supports email notifications and webhooks to integrate with your existing tools.
Email Notifications
Receive alerts directly in your inbox. Each team member can configure which notifications they receive.
Learn more →Webhooks
Integrate with Slack, Discord, PagerDuty, or any HTTP endpoint. Receive real-time event data with HMAC signing.
View documentation →Email Notifications
Configure which alerts each team member receives
Email notifications are enabled by default for all team members. Each person can customize which types of alerts they receive.
Available Email Alerts
| Alert Type | Description | Default |
|---|---|---|
| Incident Started | When a monitor goes DOWN or DEGRADED | On |
| Incident Recovery | When a monitor returns to UP status | On |
| SSL Expiry | When certificates are expiring soon | On |
| SSL Changes | When certificates are renewed or changed | Off |
| Certificate Changes | When certificate details change | Off |
| Issuer Changes | When certificate authority changes | Off |
| DNS Changes | When DNS records change | Off |
Configure your preferences in Settings → Notification Preferences
How Alerts Work
Understanding the alert flow from detection to notification
Check Runs
FlareWarden checks your monitor at the configured interval
Issue Detected
If a check fails, cross-region validation confirms the issue
Incident Created
An incident is created and the monitor status changes
Notifications Sent
Emails and webhooks are triggered based on each user's preferences
Recovery
When the issue resolves, recovery notifications are sent
Reducing False Alarms
Cross-region validation prevents unnecessary alerts
FlareWarden uses cross-region validation to prevent false alarms from temporary network issues:
- When a check fails, additional checks run from different geographic regions
- Incidents are only created when multiple regions confirm the failure
- Configure the validation threshold in your preferences (default: 2 confirmations)