Skip to content

Commit

Permalink
[doc] update doc for feishu notification (apache#2694)
Browse files Browse the repository at this point in the history 
Co-authored-by: Logic <[email protected]>
  • Loading branch information
@LiuTianyou @zqr10159
LiuTianyou and zqr10159 authored Sep 9, 2024
1 parent cd028d8 commit dab66d4
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 4 deletions.
6 changes: 5 additions & 1 deletion home/docs/help/alert_feishu.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ keywords: [open source monitoring tool, open source alerter, open source feishu
### Operation steps

1. **【FeiShu client】-> 【Group settings】-> 【Group robot】-> 【Add new robot】-> 【Set robot name and avatar】-> 【Copy its webhook address after adding successfully】**
1. **【FeiShu client】-> 【Group settings】-> 【Bots】-> 【Add Bot】-> 【Custom Bot】 -> 【Set robot name and avatar】-> 【Copy its webhook URL after adding successfully】**

2. **【Save the key value of the WebHook address of the robot】**

Expand All @@ -31,4 +31,8 @@ keywords: [open source monitoring tool, open source alerter, open source feishu
> Please check whether there is any triggered alarm information in the alarm center.
> Please check whether the robot key is configured correctly and whether the alarm strategy association is configured.
2. How to @someone in alarm notification

> In the form for adding recipients, fill in the `User ID`. If you need to @everyone, you can enter `all` in the `User ID` field. Multiple user IDs are also supported, separated by commas `,`. For detailed instructions on how to get the Feishu user ID, please refer to: [Get feishu user id](https://open.feishu.cn/document/faq/trouble-shooting/how-to-get-internal-user-id).
Other issues can be fed back through the communication group ISSUE!
10 changes: 7 additions & 3 deletions home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_feishu.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ keywords: [告警飞书机器人通知, 开源告警系统, 开源监控告警
### 操作步骤

1. **【飞书客户端】-> 【群设置】-> 【群机器人】-> 【添加新建机器人】-> 【设置机器人名称头像】-> 【添加成功后复制其WebHook地址】**
1. **【飞书客户端】-> 【群设置】-> 【群机器人】-> 【添加机器人】 -> 【自定义机器人】 -> 【设置机器人名称头像】-> 【添加成功后复制其WebHook地址】**

2. **【保存机器人的WebHook地址的KEY值】**

Expand All @@ -29,7 +29,11 @@ keywords: [告警飞书机器人通知, 开源告警系统, 开源监控告警

1. 飞书群未收到机器人告警通知

> 请排查在告警中心是否已有触发的告警信息
> 请排查是否配置正确机器人KEY，是否已配置告警策略关联
> 请排查在告警中心是否已有触发的告警信息
> 请排查是否配置正确机器人KEY，是否已配置告警策略关联
2. 如何在告警通知中@某人

> 在新增接收人的表单中，填写 `用户ID` 。如果需要 @所有人，可以在 `用户ID` 字段中填入 `all`。同时支持填写多个用户id，用逗号 `,` 分隔。获取飞书用户id的具体方法，请参考：[获取飞书用户ID](https://open.feishu.cn/document/faq/trouble-shooting/how-to-get-internal-user-id)
其它问题可以通过交流群ISSUE反馈哦！

0 comments on commit dab66d4

Please sign in to comment.