Alerts & Notifications
How does alerting work?
Two pieces work together:
- Alert rules define when to alert: which monitors they apply to, what condition triggers (certificate expiring within N days, weak TLS configuration, uptime failures), and severity.
- Notification channels define where alerts go: email addresses or webhook URLs. A rule can send to multiple channels.
Both are managed in the dashboard or via /api/v1/alerts/rules and /api/v1/notifications/channels.
When do certificate alert emails arrive?
Certificate alerts are delivered as a daily email digest, sent at 08:00 UTC. The digest groups everything that needs attention (expiring, expired, and weak-TLS certificates) into one email instead of one email per certificate.
Do webhooks behave differently from email?
Yes. Webhook channels receive alert payloads as they happen, and unresolved certificate alerts are re-sent every 12 hours (configurable per channel) so downstream systems can’t miss them.
Are webhook payloads signed?
Yes. Every webhook request includes a signature header computed as an HMAC-SHA256 over "{timestamp}.{body}" using your channel’s signing secret, similar to Stripe’s scheme. Verify the signature and reject stale timestamps to protect against replay.
Can I snooze an alert?
Yes. Snoozing an alert suppresses its notifications until the snooze expires or you resolve it. Alerts also auto-resolve when the underlying condition clears, for example after you renew a certificate.
How do I test a channel before relying on it?
POST /api/v1/notifications/channels/{id}/test sends a test notification through the channel. The dashboard has the same button on each channel.
How do I stop emails I don’t want?
Every alert email includes an unsubscribe link scoped to that notification channel. Unsubscribing stops email from that channel; your alert rules and other channels are unaffected.