Incidents and notifications
If something is wrong, you should be the first to know. You decide who is informed about what and how.
How it works
-
1
Create channel
Email, Slack or webhook. Email addresses are confirmed beforehand.
-
2
Define rules
Choose for which event you're notified – such as an outage, an expiring certificate or a worse loading time – for all monitors or only for individual ones.
-
3
Quiet hours and escalation
In the Pro plan: no messages about small things at night and a second notification if an incident stays open longer – adjustable per rule.
-
4
Keep the history
Every incident and every sent message is in the history, even if a delivery failed.
What you see in fastry
- Sentence preview of what exactly a rule does
- Incidents of all monitors in one place
- Sent notifications with delivery status