flashduty-knowledge-base 1.3.1 → 1.3.3

package/dist/esm/zh.js

@@ -318,7 +318,7 @@ attachment_stripped = true
 ## 严重程度映射关系
 ---
 
-当前邮件集成推送到 Flashduty 的告警等级均为Warning。
+当前邮件集成推送到 Flashduty 的告警等级均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
 
 `,e=`---
 title: "夜莺/FlahCat集成"
@@ -3445,7 +3445,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aws-eventbridge-integration-guide
 ### 步骤1：在 API destinations 中创建 Connerction
 1. 登录您的 AWS 控制台，检索 \`Amazon Eventbridge\` 产品，并进入对应产品控制台。
 2. 在左侧导航栏选择 \`Integration=>API destinations\`。
-3. 点击 \`Connerctions\`，并点击 \`Create connerction\` 创建链接。
+3. 点击 \`connection\`，并点击 \`Create connection\` 创建链接。
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-3.png" />
 
@@ -4059,7 +4059,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/appdynamics-integration-guide"
 |INFO|Info|提醒|
 
 </div>
-`,N=`---
+`,M=`---
 title: "SolarWinds 告警事件"
 description: "通过 webhook 的方式同步 SolarWinds 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -4164,7 +4164,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/solarwinds-integration-guide"
 |Info|Info|提醒|
 
 </div>
-`,M=`---
+`,N=`---
 title: "火山引擎云监控告警事件"
 description: "通过 webhook 的方式同步火山引擎云监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -4344,7 +4344,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-event-integration-guid
 |通知|Info|提醒|
 
 </div>
-`,E=`---
+`,W=`---
 title: "火山引擎日志服务 TLS 告警事件"
 description: "通过 webhook 的方式同步火山引擎日志服务 TLS 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4481,7 +4481,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-tls-integration-guide"
 |通知|Info|提醒|
 
 </div>
-`,W=`---
+`,E=`---
 title: "Opmanager 告警事件"
 description: "通过 webhook 的方式同步 Opmanager 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4616,7 +4616,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/opmanager-integration-guide"
 | Attention      | Info     | 提醒 |
 
 </div>
-`,j=`---
+`,z=`---
 title: "Meraki 告警事件"
 description: "通过 webhook 的方式同步 Meraki 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4692,7 +4692,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/meraki-integration-guide"
 | informational      | Info     | 提醒 |
 
 </div>
-`,$=`---
+`,j=`---
 title: "天翼云告警事件"
 description: "通过 webhook 的方式同步天翼云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4780,7 +4780,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 
 </div>
-`,z=`---
+`,$=`---
 title: "观测云告警事件"
 description: "通过 webhook 的方式同步观测云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -5423,7 +5423,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-alert-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning。
+当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
 
 `,G=`---
 title: "飞书告警集成"
@@ -5506,9 +5506,204 @@ url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning。
+当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
 
 `,J=`---
+title: "火山引擎云拨测告警事件"
+description: "通过 webhook 的方式同步 火山引擎云拨测的告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-detect-integration-guide"
+---
+
+通过 webhook 的方式同步 火山引擎云拨测的告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **火山引擎云拨测** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **火山引擎云拨测** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 \`路由\` 进行更多路由规则的配置）。
+  4. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在 火山引擎
+---
+
+<div class="md-block">
+
+## 一、告警推送配置
+
+### 步骤1：创建通知对象
+
+1. 登录您的 \`火山引擎\` 控制台，在 \`告警管理\` 菜单中，找到 \`通知对象管理\`。
+2. 点击 \`系统集成\`，点击\`创建系统集成\`或编辑已有的通知对象。
+3. 在编辑页面中，名称填写 \`Flashduty\` ，\`回调 URL\` 处填写告警集成的<span class='integration_url'>推送地址</span>。
+4. 点击 \`确定\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/volcengine-1.png" />
+
+### 步骤2：在告警策略中使用通知对象
+
+1. 登录您的 \`火山引擎\` 控制台，在 \`告警管理\` 菜单中，找到 \`告警策略\`。
+2. 点击\`创建告警策略\`或编辑已有的报警器。
+3. 在编辑页面中，\`通知对象\` 处选择创建的 \`Flashduty\` 通知对象。
+4. 其他按需配置即可，点击 \`确定\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/volcengine-2.png" />
+
+
+
+</dev>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| 火山引擎 |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| 严重告警  | Critical | 严重 |
+| 普通告警   | Warning  | 警告 |
+
+</div>
+
+`,K=`---
+title: "Monit 告警集成"
+description: "Flashduty Monit 告警集成，Monit 服务通过此集成上报告警"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/monit-alert-integration-guide"
+---
+
+当您开通 Monit 服务时，系统会自动为您创建此集成。此集成用于收集 Monit 服务产生的告警事件。
+
+:::tips
+您无法修改或删除此集成。但您可以管理集成下的标签增强、告警处理以及路由等规则。
+:::
+
+## 如何开启 Monit 告警
+
+前往\`Monit\`-\`告警规则\`-\`规则详情\`页面，配置监控指标和阈值等条件，并开启告警。您可以选择将告警投递至多个协作空间。告警的通知规则遵循协作空间下的分派策略，您可以为团队设定值班人员，在告警发生时分派给值班人。
+
+![2025-08-19-20-35-45](https://docs-cdn.flashcat.cloud/images/png/59c9d2566db9a0482fb2eabb729ea739.png)
+
+某些情况下，您可能希望将同一个告警规则产生的告警，按条件路由到不同的协作空间，这个时候您可以选择将告警直接投递到集成，而非协作空间列表。并在当前集成下，设置路由规则。`,Z=`---
+title: "RUM 告警集成"
+description: "Flashduty RUM 告警集成，RUM 服务通过此集成上报告警"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/rum-alert-integration-guide"
+---
+
+当您开通 RUM 服务时，系统会自动为您创建此集成。此集成用于收集 RUM 服务产生的告警事件。
+
+:::tips
+您无法修改或删除此集成。但您可以管理集成下的标签增强、告警处理以及路由等规则。
+:::
+
+## 如何开启 RUM 告警
+
+前往\`RUM\`-\`应用详情\`-\`告警设置\`页面，开启告警。您可以选择将告警投递至多个协作空间。告警的通知规则遵循协作空间下的分派策略，您可以为团队设定值班人员，在告警发生时分派给值班人。
+
+![2025-05-20-10-53-57](https://docs-cdn.flashcat.cloud/images/png/2bbd455a2ac702246e8399b6628f9158.png)
+
+更多内容，请您参考 [RUM Issue 告警](https://docs.flashcat.cloud/zh/flashduty/rum/issue-alerting)。`,Q=`---
+title: "Cloudflare 告警事件"
+description: "通过 webhook 的方式同步 Cloudflare 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-detect-integration-guide"
+---
+
+通过 webhook 的方式同步 Cloudflare 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **Cloudflare** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **Cloudflare** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 \`路由\` 进行更多路由规则的配置）。
+  4. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在 Cloudflare
+---
+
+<div class="md-block">
+
+## 一、告警推送配置
+
+1. 登录您的 \`Cloudflare\` 控制台，转到 \`通知\` 菜单中，。
+2. 在\`Webhooks\` 中点击创建。
+3. 在编辑页面中，名称填写 \`Flashduty\` ，\`URL\` 处填写告警集成的<span class='integration_url'>推送地址</span>。
+4. 点击 \`保存和测试\` 完成配置。
+
+配置 Webhook 通道后，即可在通知策略中使用。
+</dev>
+
+## 二、状态对照
+
+<div class="md-block">
+
+当前 Cloudflare 集成推送到 Flashduty 的告警等级均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+
+</div>
+
+`,X=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2025-05-19T10:00:00+08:00"
@@ -5565,7 +5760,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`,K=`---
+`,Y=`---
 title: "Jira 事件集成指引"
 description: "通过 webhook 的方式同步 Jira Issue 事件到 Flashduty，实现变更事件收集。"
 date: "2025-05-19T10:00:00+08:00"
@@ -5639,7 +5834,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`,Z=`---
+`,nn=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5776,7 +5971,7 @@ sidebarDepth: 3
     |给同一个用户或同一个群发消息|最高频率 5 次/秒|
 
     **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
-`,Q=`---
+`,tn=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -5937,7 +6132,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
 |专属版|550万次|60|     每月1日          |
 
 **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
-`,X=`---
+`,en=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -6017,7 +6212,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`,Y=`---
+`,an=`---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -6071,7 +6266,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 8. **Slack App 内 Other questions，报错**
    - 重新操作，遇到了还没被记录的问题
-   - 重试后仍然报错，联系客服`,nn=`---
+   - 重试后仍然报错，联系客服`,sn=`---
 title: "Microsoft Teams集成"
 description: "通过集成 Microsoft Teams 第三方应用，实现在 Microsoft Teams 内接收和响应告警的能力"
 date: "2025-05-19T10:00:00+08:00"
@@ -6202,7 +6397,7 @@ Microsoft Teams 集成现处于 Beta 阶段，在关联前您需要先完成以
 暂不支持
 </details>
 
-`,tn=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
+`,ln=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -6370,7 +6565,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`,en=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`,dn=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -6470,7 +6665,7 @@ acknowledged_at | int64| 否 | 认领时间
 |      fields       |  map[string]interface{}  |  否  | 自定义字段 KV，Key 为字符串，Value 可能为任意类型，取决于字段类型|
 |      creator      |  [Person](#Person)  |  否  | 创建人员信息，仅手动创建故障时存在 |
 |       closer      |  [Person](#Person)  |  否  | 关闭人员信息，仅手动关闭故障时存在 |
-|    responders     | [][Responder](#Responder) |  否  | 处理人员信息列表 |
+|    responders     | [][Responder](#Responder) |  否  | 处理人员信息列表，仅故障被分派后存在。对于i_new事件，此值可能为空 |
 |     alert_cnt     |        int64        |  否  | 关联告警个数 |
 |     channel_id     |        int64        |  否  | 协作空间ID，为0代表不属于任何空间 |
 |     channel_name   |        string        |  否  | 协作空间名称 |
@@ -6578,7 +6773,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,an=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,on=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6837,7 +7032,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,sn=`---
+   - 未来可能会更新，请定期查验`,rn=`---
 title: "Jira 同步"
 description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
 date: "2025-05-19T10:00:00+08:00"
@@ -6922,7 +7117,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
 
 - Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
 - Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
-`,ln=`---
+`,cn=`---
 title: "ServiceNow 同步"
 description: "通过 ServiceNow 同步 Webhook，实现故障与 ServiceNow Incident 的关联。"
 date: "2025-05-19T10:00:00+08:00"
@@ -7204,7 +7399,7 @@ IncidentWebhookHelper.prototype = {
 | Low        | Info      |      |
 | Medium     | Warning   |      |
 | High       | Critical  |      |
-`,dn=`---
+`,un=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -8331,7 +8526,7 @@ 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>
-`,on=`---
+`,hn=`---
 title: "Link 集成"
 description: "通过 Link 集成，可直接从故障属性、标签等信息中获取访问外部链接所需的关键参数，实现快速访问"
 date: "2025-05-19T10:00:00+08:00"
@@ -8388,4 +8583,4 @@ https://cmdb.com/vm?sn=VM123456
 1. 当引用的内容不存在时，Link 集成会正常生成对应的链接，但无法获取到值
 2. 同一个协作空间至多绑定三个 Link 集成
 3. 注意引用语法，如未按照要求进行书写引用变量，会导致无法正常获取对应值
-`,rn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:s,Zabbix:i,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:p,HuaWeiCES:m,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:S,Jiankongbao:T,AWSEventBridge:A,Dynatrace:I,HuaweiyunLTS:C,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:N,VolcEngineMetric:M,VolcEngineEvent:R,VolcEngineTLS:E,OpManager:W,Meraki:j,Zilliz:U,StateCloud:$,Guance:z,CustomChange:J,Jira:K,Lark:Z,Dingtalk:Q,Wecom:X,Slack:Y,MicrosoftTeams:nn,AlertWebhook:tn,IncidentWebhook:en,CustomAction:an,Templates:dn,HuaweiyunAPM:O,JiraSync:sn,ZStack:H,Keep:q,ElastAlert2:B,DingtalkAlert:V,FeishuAlert:G,Link:on,ServiceNowSync:ln};module.exports=rn;
+`,pn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:s,Zabbix:i,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:p,HuaWeiCES:m,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:S,Jiankongbao:T,AWSEventBridge:A,Dynatrace:I,HuaweiyunLTS:C,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:R,VolcEngineTLS:W,OpManager:E,Meraki:z,Zilliz:U,StateCloud:j,Guance:$,CustomChange:X,Jira:Y,Lark:nn,Dingtalk:tn,Wecom:en,Slack:an,MicrosoftTeams:sn,AlertWebhook:ln,IncidentWebhook:dn,CustomAction:on,Templates:un,HuaweiyunAPM:O,JiraSync:rn,ZStack:H,Keep:q,ElastAlert2:B,DingtalkAlert:V,FeishuAlert:G,VolcEngineDetect:J,Link:hn,ServiceNowSync:cn,Monit:K,Rum:Z,Cloudflare:Q};module.exports=pn;

package/dist/iife/en.js

@@ -309,8 +309,7 @@ attachment_stripped = true
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
-
+Currently, all alerts pushed to Flashduty through the email integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
 `,i=`---
 title: "Nightingale/Flashcat Integration"
 description: "Push alert events from Nightingale (n9e) or Flashcat to Flashduty via webhook. When an alert is triggered, send a trigger event to Flashduty; when an alert recovers, send a recovery event to Flashduty"
@@ -4708,7 +4707,7 @@ Flashduty has already adapted webhook protocols for several commonly used ticket
 ## Implementation Protocol
 --- 
 
-Please refer to the [Developer Documentation](https://developer.flashcat.cloud/en/flashduty/event-api/change-event) to complete the protocol development.
+Please refer to the [Developer Documentation](https://developer-en.flashcat.cloud/en/flashduty/event-api/change-event) to complete the protocol development.
 
 ## Best Practices
 ---
@@ -5631,7 +5630,7 @@ acknowledged_at | int64| No | Acknowledgment time
 |      fields       |  map[string]interface{}  |  No   | Custom field key-value pairs, Key is string, Value can be any type depending on field type |
 |      creator      |  [Person](#Person)  |  No   | Creator information, exists only for manually created incidents |
 |       closer      |  [Person](#Person)  |  No   | Closer information, exists only for manually closed incidents |
-|    responders     | [][Responder](#Responder) |  No   | List of responder information |
+|    responders     | [][Responder](#Responder) |  No   | List of responder information, only exists after the incident is assigned. For i_new events, this value may be empty |
 |     alert_cnt     |        int64        |  No   | Number of associated alerts |
 |     channel_id     |        int64        |  No   | Channel ID, 0 means not belonging to any channel |
 |     channel_name   |        string        |  No   | Channel name |
@@ -7664,8 +7663,7 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
-
+Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
 `,FeishuAlert:`---
 title: "Feishu Alert Integration"
 description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
@@ -7747,7 +7745,88 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through Feishu Alert integration are set to Warning severity.
+Currently, all alerts pushed to Flashduty through the Feishu(lark) integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+`,VolcEngineDetect:`---
+title: "Volcengine Cloud-Detect Alert Events"
+description: "Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/volcengine-tls-integration-guide"
+---
+
+Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Volcengine Detect** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push 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 payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Volcengine Detect** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+## In Volcengine
+---
+
+<div class="md-block">
+
+## 一、Create Notification Object
+
+### Step 1: Create Notification Object
+1. Login to your \`Volcengine\` console, find \`Alert Manager\` in the \`Notify Object\` menu
+2. Click \`System Integration\`, click \`Create System Integration\` or edit the existing endpoint
+3. In the edit page, enter Flashduty as the name and fill in the <span class='integration_url'>push URL</span> for the alert integration in the URL field.
+5. Click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/volcengine-1.png" />
+
+### Step 2: Use Notification Object in Alert Policy
+1. Login to your \`Volcengine\` console, find \`Alert Manager\` in the \`Alert Policy\` menu
+2. Click \`Create Alert Policy\` or edit the existing alert policy
+3. In the edit page, select the created \`Flashduty\` Endpoint
+4. Configure other settings as needed, and click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/volcengine-2.png" />
+
+</dev>
+
+## 二、Status Mapping
+
+<div class="md-block">
+
+| Detect |  Flashduty | Status |
+| ---------- | -------- | ---- |
+| P0  | Critical | Critical|
+| P2   | Warning  |  Warning|
+
+</div>
 
 `,Link:`---
 title: "Link Integration"
@@ -8090,4 +8169,115 @@ Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
 | Low        | Info      |       |
 | Medium     | Warning   |       |
 | High       | Critical  |       |
+`,Monit:`---
+title: "Monit Alert Integration"
+description: "Flashduty Monit alert integration, Monit service reports alerts through this integration"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/monit-alert-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+
+When you enable the Monit service, the system will automatically create this integration for you. This integration is used to collect alert events generated by the Monit service.
+
+:::tips
+You cannot modify or delete this integration. However, you can manage the label enrichment, alert pipeline, and routing rules under the integration.
+:::
+
+## How to Enable Monit Alerts
+
+Go to the \`Monit\` - \`Alert Rules\` - \`Rule Details\` page to configure monitoring metrics and threshold conditions, and enable alerts. You can choose to deliver alerts to multiple channels. Alert notification rules follow the escalation rules under the channel, and you can set responders for the team to assign to responders when alerts occur.
+
+![2025-08-19-20-35-45](https://docs-cdn.flashcat.cloud/images/png/59c9d2566db9a0482fb2eabb729ea739.png)
+
+In some cases, you may want to route alerts generated by the same alert rule to different channels based on conditions. In this case, you can choose to deliver alerts directly to the integration rather than to the channels, and set routing rules under the current integration.
+`,Rum:`---
+title: "RUM Alert Integration"
+description: "Flashduty RUM alert integration, RUM service reports alerts through this integration"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/rum-alert-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+
+When you enable the RUM service, the system will automatically create this integration for you. This integration is used to collect alert events generated by the RUM service.
+
+:::tips
+You cannot modify or delete this integration. However, you can manage the label enrichment, alert pipeline, and routing rules under the integration.
+:::
+
+## How to Enable RUM Alerts
+
+Go to the \`RUM\` - \`Application Details\` - \`Alert Settings\` page to enable alerts. You can choose to deliver alerts to multiple channels. Alert notification rules follow the escalation rules under the channel, and you can set responders for the team to assign to responders when alerts occur.
+
+![2025-08-20-10-16-14](https://docs-cdn.flashcat.cloud/images/png/b6ad24809a2ee8f0b3c0b38988b46030.png)
+
+For more information, please refer to [RUM Issue Alerting](https://docs.flashcat.cloud/en/flashduty/rum/issue-alerting?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+`,Cloudflare:`---
+title: "Cloudflare Alert Events"
+description: "Sync Cloudflaret alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/Cloudflare-integration-guide"
+---
+
+Sync Cloudflare alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Cloudflare** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push 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 payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Cloudflare** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+
+## In Cloudflare
+---
+
+<div class="md-block">
+
+## 一、Create Notification Object
+1. Log in to the \`Cloudflare dashboard\` and select your account.
+2. Go to \`Notifications\` > \`Destinations\`.
+3. In the \`Webhooks\` card, select Create.
+4. In the edit page, enter Flashduty as the name and fill in the <span class='integration_url'>push URL</span> for the alert integration in the URL field.
+5. Select \`Save and Test\` to finish setting up your webhook.
+
+After configuring the Webhook channel, you can use it in notification policies.
+
+</dev>
+
+## 二、Status Mapping
+
+<div class="md-block">
+
+Currently, all alerts pushed to Flashduty through the Cloudflare integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+
+</div>
+
 `};n.FlashDocsEn=h})(window);