OpenUptime

Uptime alerts in Lark and Feishu

Post down and recovery alerts to a Lark or Feishu group through a custom bot.

Set it up

  1. In the group, open Settings, then Bots, add a Custom Bot and copy its webhook address.
  2. Under security settings, turn on signature verification and copy the secret. This is optional but recommended over keywords or IP lists.
  3. In OpenUptime, open Alerting, choose Add channel and pick Lark / Feishu.
  4. Paste the webhook address and, if you turned it on, the signing secret.
  5. Save, then press Test: a test message arrives within seconds, and the delivery log below the channels shows whether it went through.

What arrives

When a monitor goes down

🔴 Checkout API is down — Expected 200, got 503

When it recovers

✅ Checkout API has recovered

Good to know about Lark / Feishu

  • With a signing secret, every request carries a timestamp and an HMAC-SHA256 signature, so the bot ignores requests from anyone else.
  • If the bot rejects a message, the delivery log shows Lark's error code and message.

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 Lark / Feishu alerts

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

Questions

Does it work with both Feishu and Lark?

Yes. Paste the webhook address the bot gives you, whether it is on open.feishu.cn or open.larksuite.com.

I set a keyword and messages are rejected. Why?

The bot only accepts messages that contain the keyword, and alert text varies. Use signature verification instead, or a keyword every alert contains, such as a word in your monitor names.

飞书网站宕机告警

通过自定义机器人把宕机和恢复告警发到飞书或 Lark 群。

配置步骤

  1. 在群里打开“设置”,进入“群机器人”,添加“自定义机器人”,复制它的 Webhook 地址。
  2. 在安全设置中开启“签名校验”并复制密钥。这一步可选,但比关键词或 IP 白名单更推荐。
  3. 在 OpenUptime 中打开“告警”,点击“添加渠道”,选择 Lark / Feishu。
  4. 粘贴 Webhook 地址;如果开启了签名校验,再粘贴签名密钥。
  5. 保存后点击“测试”:几秒内就会收到一条测试消息,渠道列表下方的投递记录会显示是否发送成功。

收到的内容

监控宕机时

🔴 Checkout API is down — Expected 200, got 503

恢复时

✅ Checkout API has recovered

关于 Lark / Feishu 的说明

  • 填写签名密钥后,每个请求都会带上时间戳和 HMAC-SHA256 签名,机器人会忽略其他来源的请求。
  • 如果机器人拒收消息,投递记录会显示飞书返回的错误码和说明。

所有渠道通用

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

接收 Lark / Feishu 告警

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

常见问题

飞书和 Lark 都能用吗?

都可以。直接粘贴机器人给你的 Webhook 地址,无论它在 open.feishu.cn 还是 open.larksuite.com 上。

设置了关键词后消息被拒收,为什么?

机器人只接受包含关键词的消息,而告警内容各不相同。请改用签名校验,或者设置一个每条告警都会包含的关键词,例如监控名称中的某个词。