You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@hertzbeat.apache.org by zh...@apache.org on 2024/09/09 02:30:54 UTC

(hertzbeat) branch master updated: [doc] update doc for feishu notification (#2694)

This is an automated email from the ASF dual-hosted git repository.

zhengqiwei pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git


The following commit(s) were added to refs/heads/master by this push:
     new dab66d4f1 [doc] update doc for feishu notification (#2694)
dab66d4f1 is described below

commit dab66d4f16400d0764b98bfc2471f82cb2ac17b0
Author: liutianyou <ti...@qq.com>
AuthorDate: Mon Sep 9 10:30:49 2024 +0800

    [doc] update doc for feishu notification (#2694)
    
    Co-authored-by: Logic <zq...@dromara.org>
---
 home/docs/help/alert_feishu.md                                 |  6 +++++-
 .../current/help/alert_feishu.md                               | 10 +++++++---
 2 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/home/docs/help/alert_feishu.md b/home/docs/help/alert_feishu.md
index 80efffd03..7aaf1a1e9 100644
--- a/home/docs/help/alert_feishu.md
+++ b/home/docs/help/alert_feishu.md
@@ -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】**
 
@@ -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!
diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_feishu.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_feishu.md
index bc6f3672d..31b0bd638 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_feishu.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_feishu.md
@@ -9,7 +9,7 @@ keywords: [告警飞书机器人通知, 开源告警系统, 开源监控告警
 
 ### 操作步骤
 
-1. **【飞书客户端】-> 【群设置】-> 【群机器人】-> 【添加新建机器人】-> 【设置机器人名称头像】-> 【添加成功后复制其WebHook地址】**
+1. **【飞书客户端】-> 【群设置】-> 【群机器人】-> 【添加机器人】 -> 【自定义机器人】 -> 【设置机器人名称头像】-> 【添加成功后复制其WebHook地址】**
 
 2. **【保存机器人的WebHook地址的KEY值】**
 
@@ -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反馈哦!


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@hertzbeat.apache.org
For additional commands, e-mail: notifications-help@hertzbeat.apache.org