PagerDuty uptime monitoring alerts

Open a PagerDuty incident on the right service when a monitor goes down, and resolve it automatically when the monitor recovers.

Set it up

In PagerDuty, open the service that should be paged, go to Integrations and add an Events API v2 integration.
Copy its Integration Key, also called the routing key.
In OpenUptime, open Alerting, choose Add channel and pick PagerDuty.
Paste the routing key.
Save, then press Test: a test message arrives within seconds, and the delivery log below the channels shows whether it went through.

What arrives

Request body

{
  "routing_key": "••••",
  "event_action": "trigger",
  "dedup_key": "<incident id>",
  "payload": {
    "summary": "🔴 Checkout API is down — Expected 200, got 503",
    "source": "https://api.example.com/health",
    "severity": "critical"
  }
}

Good to know about PagerDuty

Each OpenUptime incident uses its id as the dedup key, so an escalation updates the same PagerDuty incident instead of opening a new one.
Recovery sends a resolve event for the same key. Outages are sent as critical, and a changed MCP tool schema as a warning.
On-call schedules, escalation policies and phone calls are handled by PagerDuty.

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.

Get PagerDuty alerts

Add a monitor, connect the channel and press Test. The Free plan includes every alert channel.

Start monitoring Compare plans

Questions

Does acknowledging in PagerDuty acknowledge in OpenUptime?

No, the link is one way. Acknowledge in OpenUptime too if you use its own escalation, or leave it off and let PagerDuty handle escalation.

Which PagerDuty plan do I need?

Any plan that lets you add an Events API v2 integration to a service, which includes PagerDuty's free tier.

PagerDuty 可用性监控告警

监控宕机时在对应的 PagerDuty 服务上创建事件，监控恢复时自动解决它。

配置步骤

在 PagerDuty 中打开要呼叫的服务，进入 Integrations，添加 Events API v2 集成。
复制它的 Integration Key，也叫 routing key。
在 OpenUptime 中打开“告警”，点击“添加渠道”，选择 PagerDuty。
粘贴 routing key。
保存后点击“测试”：几秒内就会收到一条测试消息，渠道列表下方的投递记录会显示是否发送成功。

收到的内容

请求体

{
  "routing_key": "••••",
  "event_action": "trigger",
  "dedup_key": "<incident id>",
  "payload": {
    "summary": "🔴 Checkout API is down — Expected 200, got 503",
    "source": "https://api.example.com/health",
    "severity": "critical"
  }
}

关于 PagerDuty 的说明

每个 OpenUptime 事件都用自己的 id 作为去重键，所以升级时会更新同一个 PagerDuty 事件，而不会新建。
恢复时会对同一个键发送 resolve 事件。宕机以 critical 级别发送，MCP 工具结构变化以 warning 级别发送。
值班排班、升级策略和电话呼叫都由 PagerDuty 负责。

所有渠道通用

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

接收 PagerDuty 告警

添加一个监控，连接渠道并点击“测试”。免费版包含所有告警渠道。

开始监控比较套餐

常见问题

在 PagerDuty 里确认，OpenUptime 也会确认吗？

不会，这个连接是单向的。如果你同时用了 OpenUptime 自己的升级，需要在 OpenUptime 里也确认；也可以关闭它，交给 PagerDuty 处理升级。

需要哪个 PagerDuty 套餐？

任何能给服务添加 Events API v2 集成的套餐都可以，PagerDuty 的免费版也包括在内。