flashduty-knowledge-base 1.2.6 → 1.2.7

package/dist/en.d.ts

@@ -58,5 +58,6 @@ declare const docs: {
     Keep: string;
     ElastAlert2: string;
     DingtalkAlert: string;
+    FeishuAlert: string;
 };
 export default docs;

package/dist/esm/en.js

@@ -5160,6 +5160,89 @@ By default, the system always creates new alerts for each message, but you can s
 Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
 
 `,B=`---
+title: "Feishu Alert Integration"
+description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/Feishu-alert-integration-guide"
+---
+
+Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu.
+
+<div class="hide">
+
+## Operation Steps
+---
+
+### Create Feishu Alert Integration
+
+You can obtain a Feishu alert integration address through either of these two methods:
+
+#### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a specific channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **Feishu Alert** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Feishu Alert Integration URL**, copy it for later use, and you're done
+    
+</details>
+
+#### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
+  2. Select **Feishu Alert** integration:
+        - **Integration Name**: Define a name for the current integration
+        - **Message Type**: Select Feishu alert message type, currently only Text and Markdown are supported
+        - **Push Mode**: Choose when to trigger or recover alerts for Feishu notifications
+  3. Copy the **Feishu Alert Integration URL** for later use
+  4. Configure the default route and select the corresponding channel (after integration creation, you can go to \`Routes\` to configure more routing rules)
+  5. Done
+    
+</details>
+</div>
+
+### Customize Feishu Alert Integration
+
+#### Feishu Alert Integration URL
+
+The system will generate a unique Feishu alert integration URL for you. This URL is compatible with Feishu robot message protocol. When platforms only support Feishu robot channels, you can use this URL to receive corresponding messages.
+
+#### Push Mode
+
+By default, the system always creates new alerts for each message, but you can switch to these modes:
+
+1. **Trigger or Update Alert Based on Message Title**: In this mode, when receiving a new message, the system searches for open alerts based on the message title. If an alert is found, it will be updated; otherwise, a new alert will be triggered.
+2. **Trigger or Close Alert Based on Rules**: In this mode, when receiving a new message, the system matches messages according to your rules and triggers new alerts or closes existing alerts based on the matching results.
+
+   - You need to fill in at least one **trigger** rule
+   - You must set up regex extraction rules for Alert Key. The system uses this field to find historical alerts for updates or closure. **If regex extraction fails, the system will use the message title to generate an Alert Key** to ensure alerts won't be lost due to configuration errors
+   - You can choose whether to discard messages when none of the rules match
+
+   Configuration example:
+
+   - Receive all messages, close the alert when the message content contains **RESOLVED**, otherwise trigger a new alert
+   - Extract Alert Key from message title using the rule **/(.*)/**.
+
+
+### Notes
+- Feishu alert integration URL only supports Text and post message types; other message types cannot be received
+- When Feishu message type is Text, Flashduty will generate a default alert title "Feishu Alert"
+
+## Severity Mapping
+---
+
+Currently, all alerts pushed to Flashduty through Feishu Alert integration are set to Warning severity.
+
+`,z=`---
 title: "Custom Change Event Integration Guide"
 description: "Push change events from your own systems to Flashduty using standard protocols. Most incidents are caused by changes, and the correlation between changes and alerts helps quickly identify incident causes."
 date: "2025-05-19T10:00:00+08:00"
@@ -5216,7 +5299,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,z=`---
+`,V=`---
 title: "Jira Issue Events"
 description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
 date: "2025-05-19T10:00:00+08:00"
@@ -5290,7 +5373,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,V=`---
+`,K=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5425,7 +5508,7 @@ Once published, you can access the application via mobile/PC client. First-time
     |Group Bot Webhook|Maximum 100 calls/minute|
     |Sending messages to the same user or group|Maximum 5 calls/second|
 
-    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,K=`---
+    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,J=`---
 title: "Dingtalk Integration"
 description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
 date: "2025-05-19T10:00:00+08:00"
@@ -5581,7 +5664,7 @@ After the application is released, you can access it via mobile/PC client. First
 |Enterprise|5,500,000|60|1st of each month|
 
 **Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
-`,J=`---
+`,Z=`---
 title: "WeCom Integration"
 description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
 date: "2025-05-19T10:00:00+08:00"
@@ -5660,7 +5743,7 @@ Integrate WeCom third-party application to receive and respond to alerts within
 7. **Incident notification fails with \`WeCom License Not Activated\`?**
 
    - Contact Flashduty customer service or dedicated support for license purchase and activation
-`,Z=`---
+`,Q=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2025-05-19T10:00:00+08:00"
@@ -5714,7 +5797,7 @@ Integrate with Slack to receive and respond to alerts within Slack.
 
 8. **Slack App shows Other questions error**
    - Try again, as this might be an unrecorded issue
-   - If the error persists, contact customer support`,Q=`---
+   - If the error persists, contact customer support`,X=`---
 title: "Microsoft Teams Integration"
 description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
 date: "2025-05-19T10:00:00+08:00"
@@ -5809,7 +5892,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`,X=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
+`,ee=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -5977,7 +6060,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
    - May be updated in the future, please check periodically
-`,ee=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
+`,ne=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -6184,7 +6267,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
-   - May be updated in the future, please check periodically`,ne=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
+   - May be updated in the future, please check periodically`,te=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
 
 ## I. Creating Actions
 
@@ -6431,7 +6514,7 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
 
 ### Update Status Page
 
-When an incident is confirmed to affect online services, trigger external status page updates to prompt`,te=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,ae=`---
 title: "Jira Sync"
 description: "Sync incidents with Jira issues through Jira Sync Webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -6513,7 +6596,7 @@ In the Integration Center, select **Webhook**, choose **Jira Sync** integration,
 
 - Flashduty syncs information according to default field mappings and your custom field configurations. If your Jira issue type has required fields without mapping relationships, Jira issue creation may fail.
 - Jira issue details are accessed using project KEY + number format. If you modify the project KEY, saved issue URLs in Flashduty may become inaccessible, so please modify project KEYs with caution.
-`,ae=`---
+`,ie=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -7559,4 +7642,4 @@ As shown in the image below:
 
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
-</div>`,ie={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:_,HuaweiyunLTS:L,GoogleCM:F,Zilliz:q,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:B,Jira:z,Lark:V,Dingtalk:K,Wecom:J,Slack:Z,MicrosoftTeams:Q,AlertWebhook:X,IncidentWebhook:ee,CustomAction:ne,Templates:ae,HuaweiyunAPM:O,JiraSync:te,ZStack:Y,Keep:H,ElastAlert2:$,DingtalkAlert:j};module.exports=ie;
+</div>`,oe={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:_,HuaweiyunLTS:L,GoogleCM:F,Zilliz:q,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:z,Jira:V,Lark:K,Dingtalk:J,Wecom:Z,Slack:Q,MicrosoftTeams:X,AlertWebhook:ee,IncidentWebhook:ne,CustomAction:te,Templates:ie,HuaweiyunAPM:O,JiraSync:ae,ZStack:Y,Keep:H,ElastAlert2:$,DingtalkAlert:j,FeishuAlert:B};module.exports=oe;

package/dist/esm/zh.js

@@ -5423,9 +5423,92 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-alert-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前邮件集成推送到 Flashduty 的告警等级均为Warning。
+当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning。
 
 `,G=`---
+title: "飞书告警集成"
+description: "在 Flashduty 生成唯一的飞书机器人地址，通过飞书的方式将告警的发生与恢复同步到 Flashduty"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
+---
+
+在 Flashduty 生成唯一的飞书告警地址，通过飞书告警地址将告警的发生与恢复同步到 Flashduty。
+
+<div class="hide">
+
+## 操作步骤
+---
+
+### 创建飞书告警集成
+
+您可通过以下2种方式，获取一个飞书告警集成地址，任选其一即可。
+
+#### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **飞书告警** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **飞书告警集成地址**，复制备用，完成。
+    
+</details>
+
+#### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **飞书告警** 集成：
+        - **集成名称**：为当前集成定义一个名称。
+        - **消息类型**：选择飞书告警消息类型，目前仅支持 Text、Markdown。
+        - **推送模式**：选择飞书告警在何种情况下触发或恢复告警。
+  3. 复制当前页面的 **飞书告警集成地址** 备用。
+  4. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 \`路由\` 进行更多路由规则的配置）。
+  5. 完成。
+    
+</details>
+</div>
+
+### 定制飞书告警集成
+
+#### 飞书告警集成地址
+
+系统会帮您生成一个唯一的飞书告警集成地址，该地址兼容飞书机器人消息的协议，在有的平台仅支持飞书机器人通道时，您可以使用该地址来接收对应的消息。
+
+#### 推送模式
+
+默认系统总是为每一条消息创建新的告警，但您可以切换模式为：
+
+1. **根据消息标题触发或更新告警**：该模式下，每当接收到新消息，系统会根据消息标题查找未关闭告警。如果找到告警则进行更新，否则系统会触发一条新的告警。
+2. **根据规则触发或关闭告警**：该模式下，每当接收到新消息，系统会根据您的规则进行消息匹配，匹配到的消息按照规则去触发新告警或关闭已有告警。
+
+   - 您至少需要填写一条**触发**规则；
+   - 您必须设置 Alert Key 的正则提取规则。系统使用该字段来查找历史告警，以便对其进行更新或关闭；**如果正则提取失败，系统将使用消息标题来生成 Alert Key**，以确保告警不会因为配置错误而丢失；
+   - 您可以选择，当所有的规则都不匹配时，是否丢弃消息。
+
+   配置示例：
+
+   - 接收所有消息，当消息内容中包含 **RESOVED** 字样时，关闭告警，否则触发新告警；
+   - Alert Key 从消息标题中提取，规则为 **/(.\\*)/**。
+
+
+### 注意事项
+- 飞书告警集成地址仅支持接收文本、富文本中 text 和 markdown 的消息类型，其他消息无法接收。
+- 当飞书消息类型是Text 时，Flashduty 会生成默认告警标题 “飞书告警”。
+
+## 严重程度映射关系
+---
+
+当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning。
+
+`,V=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2025-05-19T10:00:00+08:00"
@@ -5482,7 +5565,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`,V=`---
+`,K=`---
 title: "Jira 事件集成指引"
 description: "通过 webhook 的方式同步 Jira Issue 事件到 Flashduty，实现变更事件收集。"
 date: "2025-05-19T10:00:00+08:00"
@@ -5556,7 +5639,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`,K=`---
+`,Z=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5693,7 +5776,7 @@ sidebarDepth: 3
     |给同一个用户或同一个群发消息|最高频率 5 次/秒|
 
     **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
-`,Z=`---
+`,X=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -5853,7 +5936,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
 |专属版|550万次|60|     每月1日          |
 
 **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
-`,X=`---
+`,Y=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -5933,7 +6016,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`,Y=`---
+`,Q=`---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -5987,7 +6070,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 8. **Slack App 内 Other questions，报错**
    - 重新操作，遇到了还没被记录的问题
-   - 重试后仍然报错，联系客服`,Q=`---
+   - 重试后仍然报错，联系客服`,nn=`---
 title: "Microsoft Teams集成"
 description: "通过集成 Microsoft Teams 第三方应用，实现在 Microsoft Teams 内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -6082,7 +6165,7 @@ Microsoft Teams 集成现处于 Beta 阶段，在关联前您需要先完成以
 暂不支持
 </details>
 
-`,nn=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
+`,tn=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -6250,7 +6333,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`,tn=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`,en=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -6458,7 +6541,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,en=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,an=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6717,7 +6800,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,an=`---
+   - 未来可能会更新，请定期查验`,sn=`---
 title: "Jira 同步"
 description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
 date: "2025-05-19T10:00:00+08:00"
@@ -6802,7 +6885,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
 
 - Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
 - Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
-`,sn=`---
+`,ln=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -7855,4 +7938,4 @@ msg_type 必填，值为 post
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
 </div>
-`,ln={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:S,Dynatrace:C,HuaweiyunLTS:I,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:W,OpManager:$,Meraki:R,Zilliz:U,StateCloud:z,Guance:j,CustomChange:G,Jira:V,Lark:K,Dingtalk:Z,Wecom:X,Slack:Y,MicrosoftTeams:Q,AlertWebhook:nn,IncidentWebhook:tn,CustomAction:en,Templates:sn,HuaweiyunAPM:H,JiraSync:an,ZStack:O,Keep:q,ElastAlert2:B,DingtalkAlert:J};module.exports=ln;
+`,dn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:S,Dynatrace:C,HuaweiyunLTS:I,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:W,OpManager:$,Meraki:R,Zilliz:U,StateCloud:z,Guance:j,CustomChange:V,Jira:K,Lark:Z,Dingtalk:X,Wecom:Y,Slack:Q,MicrosoftTeams:nn,AlertWebhook:tn,IncidentWebhook:en,CustomAction:an,Templates:ln,HuaweiyunAPM:H,JiraSync:sn,ZStack:O,Keep:q,ElastAlert2:B,DingtalkAlert:J,FeishuAlert:G};module.exports=dn;

package/dist/iife/en.js

@@ -7559,4 +7559,87 @@ By default, the system always creates new alerts for each message, but you can s
 
 Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
 
+`,FeishuAlert:`---
+title: "Feishu Alert Integration"
+description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/Feishu-alert-integration-guide"
+---
+
+Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu.
+
+<div class="hide">
+
+## Operation Steps
+---
+
+### Create Feishu Alert Integration
+
+You can obtain a Feishu alert integration address through either of these two methods:
+
+#### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a specific channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **Feishu Alert** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Feishu Alert Integration URL**, copy it for later use, and you're done
+    
+</details>
+
+#### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
+  2. Select **Feishu Alert** integration:
+        - **Integration Name**: Define a name for the current integration
+        - **Message Type**: Select Feishu alert message type, currently only Text and Markdown are supported
+        - **Push Mode**: Choose when to trigger or recover alerts for Feishu notifications
+  3. Copy the **Feishu Alert Integration URL** for later use
+  4. Configure the default route and select the corresponding channel (after integration creation, you can go to \`Routes\` to configure more routing rules)
+  5. Done
+    
+</details>
+</div>
+
+### Customize Feishu Alert Integration
+
+#### Feishu Alert Integration URL
+
+The system will generate a unique Feishu alert integration URL for you. This URL is compatible with Feishu robot message protocol. When platforms only support Feishu robot channels, you can use this URL to receive corresponding messages.
+
+#### Push Mode
+
+By default, the system always creates new alerts for each message, but you can switch to these modes:
+
+1. **Trigger or Update Alert Based on Message Title**: In this mode, when receiving a new message, the system searches for open alerts based on the message title. If an alert is found, it will be updated; otherwise, a new alert will be triggered.
+2. **Trigger or Close Alert Based on Rules**: In this mode, when receiving a new message, the system matches messages according to your rules and triggers new alerts or closes existing alerts based on the matching results.
+
+   - You need to fill in at least one **trigger** rule
+   - You must set up regex extraction rules for Alert Key. The system uses this field to find historical alerts for updates or closure. **If regex extraction fails, the system will use the message title to generate an Alert Key** to ensure alerts won't be lost due to configuration errors
+   - You can choose whether to discard messages when none of the rules match
+
+   Configuration example:
+
+   - Receive all messages, close the alert when the message content contains **RESOLVED**, otherwise trigger a new alert
+   - Extract Alert Key from message title using the rule **/(.*)/**.
+
+
+### Notes
+- Feishu alert integration URL only supports Text and post message types; other message types cannot be received
+- When Feishu message type is Text, Flashduty will generate a default alert title "Feishu Alert"
+
+## Severity Mapping
+---
+
+Currently, all alerts pushed to Flashduty through Feishu Alert integration are set to Warning severity.
+
 `};n.FlashDocsEn=u})(window);

package/dist/iife/zh.js

@@ -7853,6 +7853,89 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-alert-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前邮件集成推送到 Flashduty 的告警等级均为Warning。
+当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning。
+
+`,FeishuAlert:`---
+title: "飞书告警集成"
+description: "在 Flashduty 生成唯一的飞书机器人地址，通过飞书的方式将告警的发生与恢复同步到 Flashduty"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
+---
+
+在 Flashduty 生成唯一的飞书告警地址，通过飞书告警地址将告警的发生与恢复同步到 Flashduty。
+
+<div class="hide">
+
+## 操作步骤
+---
+
+### 创建飞书告警集成
+
+您可通过以下2种方式，获取一个飞书告警集成地址，任选其一即可。
+
+#### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **飞书告警** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **飞书告警集成地址**，复制备用，完成。
+    
+</details>
+
+#### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **飞书告警** 集成：
+        - **集成名称**：为当前集成定义一个名称。
+        - **消息类型**：选择飞书告警消息类型，目前仅支持 Text、Markdown。
+        - **推送模式**：选择飞书告警在何种情况下触发或恢复告警。
+  3. 复制当前页面的 **飞书告警集成地址** 备用。
+  4. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 \`路由\` 进行更多路由规则的配置）。
+  5. 完成。
+    
+</details>
+</div>
+
+### 定制飞书告警集成
+
+#### 飞书告警集成地址
+
+系统会帮您生成一个唯一的飞书告警集成地址，该地址兼容飞书机器人消息的协议，在有的平台仅支持飞书机器人通道时，您可以使用该地址来接收对应的消息。
+
+#### 推送模式
+
+默认系统总是为每一条消息创建新的告警，但您可以切换模式为：
+
+1. **根据消息标题触发或更新告警**：该模式下，每当接收到新消息，系统会根据消息标题查找未关闭告警。如果找到告警则进行更新，否则系统会触发一条新的告警。
+2. **根据规则触发或关闭告警**：该模式下，每当接收到新消息，系统会根据您的规则进行消息匹配，匹配到的消息按照规则去触发新告警或关闭已有告警。
+
+   - 您至少需要填写一条**触发**规则；
+   - 您必须设置 Alert Key 的正则提取规则。系统使用该字段来查找历史告警，以便对其进行更新或关闭；**如果正则提取失败，系统将使用消息标题来生成 Alert Key**，以确保告警不会因为配置错误而丢失；
+   - 您可以选择，当所有的规则都不匹配时，是否丢弃消息。
+
+   配置示例：
+
+   - 接收所有消息，当消息内容中包含 **RESOVED** 字样时，关闭告警，否则触发新告警；
+   - Alert Key 从消息标题中提取，规则为 **/(.\\*)/**。
+
+
+### 注意事项
+- 飞书告警集成地址仅支持接收文本、富文本中 text 和 markdown 的消息类型，其他消息无法接收。
+- 当飞书消息类型是Text 时，Flashduty 会生成默认告警标题 “飞书告警”。
+
+## 严重程度映射关系
+---
+
+当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning。
 
 `};n.FlashDocsZh=t})(window);

package/dist/zh.d.ts

@@ -58,5 +58,6 @@ declare const docs: {
     Keep: string;
     ElastAlert2: string;
     DingtalkAlert: string;
+    FeishuAlert: string;
 };
 export default docs;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.2.6",
+  "version": "1.2.7",
   "description": "flashduty knowledge base",
   "type": "module",
   "engines": {