Back to features
Alerts
Put the alert where the right human will see it.
Route failures to chat, on-call tools, SMS, email, or webhooks. Keep low-priority signals quiet and make urgent production failures impossible to miss.
- Feature
- Slack, Discord, Telegram, and Microsoft Teams
- Feature
- Email and SMS notifications
- Feature
- PagerDuty, Opsgenie, incident.io, and Grafana OnCall
- Feature
- Webhooks for anything else
- Alert by severity.
- Send urgent production failures to on-call and lower-priority notifications to chat or email, so every event gets the right amount of attention.
- Priority routing
- Reminder alerts
- Timezone settings
- Connect every team.
- Different teams respond in different places. OnlineOrNot supports the tools teams already use.
- Chat
- On-call
- Webhooks
- Recoveries matter too.
- Your team needs to know when a service comes back, not just when it breaks. Recovery alerts close the loop without forcing someone to keep refreshing a dashboard.
- Down alerts
- Reminder alerts
- Recovery alerts
- Use webhooks for everything else.
- If your workflow is custom, send OnlineOrNot events to your own endpoint and transform them into tickets, internal notifications, automations, or incident records.
- Custom workflows
- Internal tools
- Incident automation
Frequently asked questions
The short version. The docs have the details when you need them.
- Can I send alerts to multiple places?
- Yes. Configure the destinations that match how your team responds.
- Can I use webhooks?
- Yes. Webhooks let you route OnlineOrNot events into your own systems.
- Can I keep noisy checks out of on-call?
- Yes. Use priority and destination choices to keep lower-priority signals in chat or email while high-priority checks can page on-call or send SMS.
- Which products use alerts?
- Website checks, API checks, browser checks, cron jobs, and heartbeats can all use OnlineOrNot alert channels.
Start with alerts.
Start with the alert route your team will actually notice, then tune priority as your checks grow.