Skip to main content
UptimeIO sends alerts through notification destinations that belong to your organization and are assigned directly to monitors. There is no separate alert-profile step.

​
How it works

1

Create destinations

Add one or more channels under Destinations in the sidebar: email, Slack, webhook, Telegram or Pushover.
2

Choose events per destination

Each destination has its own event preferences, so email can receive everything while a pager channel receives only outages.
3

Assign destinations to monitors

Select the destinations in each monitor’s Notifications section (or send notification_target_ids through the API).
4

Receive alerts

When an event occurs, every verified destination assigned to the monitor with that event enabled is notified.
Telegram and Pushover destinations can only be set up from the dashboard; an API key cannot create them. Step-by-step instructions are in Setting Up Alerts.

​
Events

Monitor goes down

on_failure. An incident opened after failures were confirmed from multiple probe locations.

Monitor recovers

on_recovery. The incident resolved after recovery was confirmed.

SSL certificate warnings

on_ssl_expiry. A certificate is 30, 15, 7 or 1 days from expiry (your selection per monitor). No incident is opened.

Domain expiry warnings

on_domain_expiry. A domain registration is 30, 15, 7 or 1 days from expiry. No incident is opened.

Response time exceeds threshold

on_slow_response. A slow-response incident opened.

Response time returns to normal

on_slow_response_resolved. The slow-response incident resolved.
DNS monitor failures are delivered as regular “Monitor goes down” and “Monitor recovers” events. There is no separate DNS event.
All six events are enabled when you create a destination, and at least one must stay enabled.

​
Event filtering

Each destination receives only the events enabled in its own preferences:
With the preferences above, this destination is notified about outages, recoveries and expiry warnings, but never about slow responses.

​
Delivery

  • Notifications are sent as soon as the event occurs.
  • Failed deliveries are retried automatically a limited number of times. Webhook requests time out after 10 seconds.
  • For each incident you can see the delivery result of every notification on the incident page, under Notification delivery: Sent, Failed or Pending.
A destination assigned to a monitor receives one notification per event, even if it appears more than once in the monitor’s settings.

​
Message content

Every notification identifies the monitor, what happened and why, and links back to the incident.
The email subject names the event and monitor, for example [UptimeIO] Monitor Down: API Server. The body includes the monitor name and URL, the start time, the error details and a link to the incident.

​
Best practices

Use names like Production Slack or On-call Pushover so they are easy to pick when configuring a monitor.
  • Email: all events, as an audit trail.
  • Slack: outages and recoveries.
  • Pushover or Telegram: outages only, for urgent attention.
  • Webhook: whatever your receiving system needs.
Use Test on the destination, then confirm end to end with a test monitor you can make fail.

​
Team access

Organization owners and admins manage members and notification destinations. Paid plans do not charge per team member.

​
Next steps

Setting Up Alerts

Create and assign destinations

Email

Email destinations and verification

Slack

Post alerts to a channel

Webhooks

Signed JSON to your own endpoint