Notifications
Notifications alert the right people and systems when monitor state changes. Configure defaults at the organization level, then let monitors inherit those defaults or override them individually.
Organization Defaults
Monitor settings include default notification targets, new comment notifications, check success notifications, SSL expiry warning days, and domain expiry warning days. New monitors can use these defaults automatically.
Per-Monitor Notifications
Each monitor has a Notifications panel. Keep Use Default Notifications enabled to inherit organization settings, or disable it to customize targets and event types for that monitor.
Events
- Incidents - Alert when a monitor opens or resolves an incident.
- New comments - Alert when a monitor or incident receives a comment.
- Check success - Alert on successful checks when enabled.
- SSL expiry - HTTP monitors can warn before, on, or after certificate expiry.
- Domain expiry - HTTP monitors can warn before, on, or after domain expiry.
Expiry Warning Days
SSL and domain expiry warning days are comma-separated numbers. For example, 30,7,0,-1 sends reminders 30 days before, 7 days before, on the expiry day, and one day after expiry.
Targets
Notification targets are managed in the shared notifications table. Depending on organization configuration, targets can include email, messaging integrations, webhooks, SMS, voice, WhatsApp, Microsoft Teams, Slack, Amazon SNS, or other supported channels.
Best Practices
- Use organization defaults for common routing and override only exceptional monitors.
- Send high-urgency monitors to fewer, more reliable channels.
- Use maintenance windows so planned work does not page responders.
- Enable comment notifications for monitors where incident collaboration matters.
- Use SSL and domain expiry notifications on customer-facing HTTP monitors.