Routing rules decide which channel gets which alert. The delivery log shows what we sent.
How routing works
- Without rules, every enabled channel gets every alert.
- Each rule sends matching events to one channel.
- When one or more rules match an event, only the channels of those rules get it.
- Events that no rule matches go to all enabled channels.
The Alerting page shows each rule as a sentence, for example: "When Shop (HTTP check) goes down, notify On-call Slack".
Add a rule
- Open Alerting and click Add rule. You can also click Manage rules.
- Under Monitor, choose one monitor or Any monitor.
- Under Check type, choose one check type or Any check.
- Under Notify, choose the channel.
- Choose the Severity: Critical, Warning or Info.
- Select the events: Goes down, Recovers, TLS certificate expires soon, TLS certificate renewed, DNS records change, DNS records restored, New scan issue, Scan issue resolved, Gets slow and Is fast again.
- Click Add rule.
Gets slow and Is fast again work only with email and Telegram channels.
Examples
- Send one monitor to its own Slack channel: add a rule for that monitor with the events Goes down and Recovers, and choose the Slack channel.
- Send certificate warnings to email only: add a rule for Any monitor with TLS certificate expires soon and TLS certificate renewed, and choose the email channel.
Remember: when a rule matches, the other channels do not get that event.
The delivery log
The Delivery log at the bottom of the Alerting page lists each alert and each attempt: time, event, monitor, channel, status and details.
| Status | Meaning |
|---|---|
| Delivered | The destination accepted the alert. |
| Failed | All attempts failed. |
| Retrying | An attempt failed. We try again. |
| Queued | The alert waits to be sent. |
| Muted | The monitor was snoozed or in maintenance. We did not send the alert. |
| No channel | No channel was available for the alert. |
Filter the log by status and by channel. We keep the log for 90 days. For a longer list of alerts, open Full alert history.
An alert did not arrive
- Open the Delivery log and find the event.
- If there is no entry, check that an incident opened. See Incidents and quorum.
- If the status is Muted, check snoozes and maintenance windows.
- If the status is Failed, open the details and fix the channel. Then click Send test.
- Check your routing rules. A rule that matches sends the event only to its own channel.