OpenUptime

Alert integrations

Where OpenUptime can tell you that a monitor is down. Each page shows how to connect the channel and what the alert looks like.

SlackPost a message to a Slack channel when a monitor goes down, and another when it recovers, through a Slack incoming webhook.DiscordSend down and recovery messages to a Discord channel through a channel webhook, with no bot to run.Microsoft TeamsPost down and recovery alerts to a Teams channel through a Workflows webhook, the way Microsoft now recommends instead of Office 365 connectors.TelegramHave your own Telegram bot message you, a group or a channel when a monitor goes down and when it recovers.PagerDutyOpen a PagerDuty incident on the right service when a monitor goes down, and resolve it automatically when the monitor recovers.EmailSend an email to a person or an on-call alias when a monitor goes down, with the error and start time, and another with the downtime once it recovers.WebhookHave OpenUptime POST a small JSON document to your URL whenever an incident opens, escalates or resolves, and route it wherever you like.Lark / FeishuPost down and recovery alerts to a Lark or Feishu group through a custom bot.ntfyPublish alerts to an ntfy topic, on ntfy.sh or your own server, and get them as push notifications wherever you subscribe.

On every channel

  • Every channel is available on every plan, Free included.
  • Choose per monitor which channels it alerts, or turn a channel on for every new monitor.
  • Until someone acknowledges an incident, it can repeat on the mobile app (up to 10 times, by email too if you choose) and escalate to other channels in up to 3 levels.
  • A failed delivery is retried, and the delivery log shows what was sent to which channel and why anything failed.
Start monitoringRead the docs

Questions

Which alert channels does OpenUptime support?

Email, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Lark / Feishu, ntfy, outgoing webhooks and the OpenUptime mobile app.

Are integrations limited by plan?

No. Every channel is available on every plan, Free included. Email has a monthly allowance per plan; when it is used up, the other channels keep sending.

Can one monitor alert several channels?

Yes. Pick the channels on the monitor, or leave the choice empty and it alerts every enabled channel.

How do I connect a tool that is not listed?

Use the webhook channel: OpenUptime posts a JSON body to any public URL, which works with Zapier, n8n, Make or your own service.

告警集成

监控宕机时，OpenUptime 可以通过这些渠道通知你。每一页都会说明如何连接渠道，以及告警长什么样。

Slack监控宕机时向 Slack 频道发一条消息，恢复时再发一条，通过 Slack 的 Incoming Webhook 发送。Discord通过频道 Webhook 把宕机和恢复消息发到 Discord 频道，不用自己运行机器人。Microsoft Teams通过 Workflows Webhook 把宕机和恢复告警发到 Teams 频道，这是微软目前推荐的方式，用来替代 Office 365 连接器。Telegram监控宕机和恢复时，让你自己的 Telegram 机器人给你、群组或频道发消息。PagerDuty监控宕机时在对应的 PagerDuty 服务上创建事件，监控恢复时自动解决它。Email监控宕机时给某个人或值班邮件组发一封邮件，写明错误原因和开始时间；恢复后再发一封，写明宕机时长。Webhook每当事件开始、升级或结束时，OpenUptime 都会向你的地址 POST 一段简短的 JSON，你可以把它转发到任何地方。Lark / Feishu通过自定义机器人把宕机和恢复告警发到飞书或 Lark 群。ntfy把告警发布到 ntfy 主题（ntfy.sh 或你自己的服务器），在任何订阅了它的地方收到推送通知。

所有渠道通用

  • 所有渠道在所有套餐中都可用，包括免费版。
  • 可以为每个监控选择要通知的渠道，也可以让某个渠道默认对所有新监控开启。
  • 在有人确认事件之前，告警可以在手机 App 上重复提醒（最多 10 次，也可以选择同时发邮件），并最多分 3 级升级到其他渠道。
  • 投递失败会自动重试，投递记录会显示发到了哪个渠道、失败的原因是什么。
开始监控阅读文档

常见问题

OpenUptime 支持哪些告警渠道？

邮件、Slack、Discord、Microsoft Teams、Telegram、PagerDuty、飞书 / Lark、ntfy、Webhook 以及 OpenUptime 手机 App。

集成会受套餐限制吗？

不会。所有渠道在所有套餐中都可用，包括免费版。邮件按套餐有每月额度，用完后其他渠道照常发送。

一个监控能同时通知多个渠道吗？

可以。在监控上选择要通知的渠道；如果不选，就会通知所有已启用的渠道。

没有列出的工具怎么接入？

使用 Webhook 渠道：OpenUptime 会向任意公网地址 POST 一段 JSON，可以配合 Zapier、n8n、Make 或你自己的服务使用。