Choose who gets alerted
Send outage notices to the right inbox, Slack or Discord channel, PagerDuty service or webhook, and control how often they repeat.
Last updated
An alert connects monitors to one destination. Create one alert per destination: one for the team inbox, one for the on-call Slack channel, and so on. A team can have up to 10 alerts.
Name it and pick its monitors
Open Alerts in the sidebar and click Create Alert.
Type a Name that says where it goes, such as "On-call Slack".
Choose a Scope:
Team-wide (every monitor) covers every monitor, including ones you add later.
Every HTTP monitor, Every cron job and the other "Every…" options cover one kind of monitor.
A single monitor's name covers only that monitor.
Pick the channel
Under Notification channel, choose a Channel and fill in its fields:
Channel What to enter Email Recipient, and optionally a Subject prefix (optional) to filter alerts in your inbox Slack The Webhook URL of a Slack Incoming Webhook Discord The Webhook URL from the channel's Server Settings → Integrations → Webhooks PagerDuty The Integration key of the service's Events API v2 integration Webhook The URL to post to, and optionally a Signing secret (optional) so your endpoint can verify it For webhook payloads and signature verification, see Alerts & Notifications.
Set the delivery rules
Under Delivery rules:
Notify on recovery (on by default) sends one more notice when the monitor is healthy again.
Cooldown (minutes) (60 by default) is how long to wait before repeating the notice while the monitor stays down. You can set 0 to 1440; repeats are never closer than 5 minutes apart.
Click Create Alert.
When an alert fires
On the first failing check. There is no confirming second check, and the cooldown never delays this first notice.
Again every cooldown while the monitor stays broken, with no limit on how many.
Once on recovery, if Notify on recovery is on.
What counts as broken depends on the monitor: an HTTP monitor alerts when it is down or degraded, and a cron job alerts when it is missed (and when it is late, if you turned on Alert on Late). A flow monitor alerts when a test fails, never when it cannot run.
Nothing is sent while a maintenance window with alert suppression covers the monitor. See Schedule maintenance.
How do I see what was sent?
Open Alerts and click View History. Each row shows the alert, the monitor, the event (Down, Degraded or Recovered) and whether it was Sent, Failed or Skipped (Cooldown).
An alert shows a Broken badge. What happened?
The destination answered that it no longer exists, for example a deleted Slack webhook. Open the alert with Edit Alert, enter a working destination and save; saving the channel clears the badge.
Who sends the emails?
Alert emails come from no-reply@uptime.sergiodxa.com. Add it to your contacts or allow-list so they don't land in spam.