flashcatcloud · pijiang3 · Mar 26, 2026 · Mar 19, 2026 · Mar 26, 2026
diff --git a/... On-call/8. Integrations/8.1 Alerts integration/8.1.22 OceanBase Integration.md b/... On-call/8. Integrations/8.1 Alerts integration/8.1.22 OceanBase Integration.md
@@ -180,7 +180,7 @@ OCP Alert Notification - Single Alert
 |OceanBase|Flashduty|Status|
 |---|---|---|
 |Down|Critical|Critical|
-|Critical|Warning|Critical|
+|Critical|Critical|Critical|
 |Warning|Warning|Warning|
 |Caution|Info|Info|
 |Notice|Info|Info|

diff --git a/.... On-call/8. Integrations/8.1 Alerts integration/8.1.58 JD Cloud Integration.md b/.... On-call/8. Integrations/8.1 Alerts integration/8.1.58 JD Cloud Integration.md
@@ -0,0 +1,102 @@
+---
+title: "JD Cloud Monitoring Alert Events"
+description: "Sync JD Cloud monitoring alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jdcloud-integration-guide"
+---
+
+Sync JD Cloud monitoring 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 **JD Cloud Monitoring** 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 **JD Cloud Monitoring** 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 JD Cloud
+---
+
+### Step 1: Create Notification Template
+1. Login to your JD Cloud console, search for `Monitoring` product, and enter the corresponding product console.
+2. In the left menu, select `Alarm Management->Notice Templates`, and create or edit a notification template.
+3. Check `Alert Callback` on the template page, and enter the <span class='integration_url'>push URL</span> for the alert integration in the `URL` field.
+4. Enter the following template content in the `POST` input box.
+  ```
+    {
+      "resource_id": "${resourceId}",
+      "request_id": "${requestId}",
+      "metric": "${metric}",
+      "current_value": "${currentValue}",
+      "times": "${times}",
+      "tags": "${tags}",
+      "alert_time": "${alertTime}",
+      "region": "${region}",
+      "threshold": "${threshold}",
+      "service_code": "${serviceCode}",
+      "as_group_id": "${asGroupId}",
+      "unhealthy_instance": "${unhealthyInstance}",
+      "rule_policy_id": "${rulePolicyId}",
+      "service_code_en": "${serviceCodeEN}",
+      "service_code_cn": "${serviceCodeCN}",
+      "level": "${level}",
+      "resource_name": "${resourceName}",
+      "ip_address": "${ipAddress}",
+      "status": "${status}"
+    }
+
+  ```
+5. Configure other options as needed.
+6. Click `Save` to complete the configuration.
+
+### Step 2: Configure Alert Rules
+1. Login to your JD Cloud console, search for `Monitoring` product, and enter the corresponding product console.
+2. In the left menu, select `Alarm Management->Alarm Rules`, and create or edit an alert rule.
+3. In the **Notification Policy** section of the rule configuration page, select `Use Template` and choose the template created in **Step 1**.
+4. Configure other options as needed.
+5. Click `Save` to complete the configuration.
+
+## Severity Mapping
+---
+<div class="md-block">
+
+JD Cloud Monitoring to Flashduty severity mapping:
+
+| JD Cloud Monitoring | Flashduty | Status   |
+| ------------------- | --------- | -------- |
+| Critical            | Critical  | Critical |
+| Major               | Warning   | Warning  |
+| General             | Info      | Info     |
+
+</div>
diff --git a/...call/8. Integrations/8.3 IM integration/8.3.1 Feishu(Lark) Integration Guide.md b/...call/8. Integrations/8.3 IM integration/8.3.1 Feishu(Lark) Integration Guide.md
@@ -81,7 +81,8 @@ Go to the **Permission Management** page and apply for the following permissions
 
 - `im:chat`: Get and update group information
 - `im:message`: Get and send single chat and group messages
-- `contact:user.id:readonly`: Get user ID by phone number or email <span id="war-room-scope"></span>
+- `contact:user.id:readonly`: Get user ID by phone number or email
+- `im:message.group_msg`: Read group chat history (required for AI-generated post-mortem to access war room conversations) <span id="war-room-scope"></span>
 
 ![2025-09-17-19-59-38](https://docs-cdn.flashcat.cloud/images/png/61cb9fbc295e94b4d9acd7e44ac75e13.png)
 
@@ -144,4 +145,4 @@ After completing the previous steps, in the **Enhanced Features** module of the
    > After exceeding API call limits, the Feishu/Lark application will not be able to push messages normally. It is recommended to use notification channels reasonably. See [Feishu/Lark official documentation](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit) for details.
 5. **Why is the war room feature not working as expected?**
    - Please check again whether you have configured the [required permissions](#war-room-scope) for the war room feature.
-   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
diff --git a/.../1. On-call/8. Integrations/8.3 IM integration/8.3.4 Slack Integration Guide.md b/.../1. On-call/8. Integrations/8.3 IM integration/8.3.4 Slack Integration Guide.md
@@ -22,6 +22,8 @@ By integrating the Slack third-party application, you can receive and respond to
 
 After completing the previous steps, in the **Enhanced Features** module of the Flashduty integration configuration page, check **Enable War Room** to enable this feature without additional configuration.
 
+To enable AI-generated post-mortem with war room chat history, the app requires additional `channels:history` permission. For existing Slack integrations, you need to manually re-authorize to grant this permission.
+
 ## 3. FAQ
 
 ---
@@ -52,4 +54,4 @@ After completing the previous steps, in the **Enhanced Features** module of the
    - If the error persists after retrying, please contact customer service to record and resolve new issues.
 9. **Why is the war room feature not working as expected?**
    - For previously authorized Slack IM integrations, you need to manually reauthorize Slack in the Flashduty integration configuration page to grant the application the additional permissions required for the war room feature.
-   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.22 OceanBase 告警事件集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.22 OceanBase 告警事件集成指引.md
@@ -191,22 +191,7 @@ OCP告警通知-单条告警
 |OceanBase| Flashduty|状态|
 |---|---|---|
 |停服|Critical|严重|
-|严重|Warning|严重|
-|警告|Warning|警告|
-|注意|Info|提醒|
-|提醒|Info|提醒|
-
-</div>
-
-
-## 状态对照
----
-<div class="md-block">
-
-|OceanBase| Flashduty|状态|
-|---|---|---|
-|停服|Critical|严重|
-|严重|Warning|严重|
+|严重|Critical|严重|
 |警告|Warning|警告|
 |注意|Info|提醒|
 |提醒|Info|提醒|

diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.58 京东云告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.58 京东云告警集成指引.md
@@ -0,0 +1,105 @@
+---
+title: "京东云监控告警集成"
+description: "通过 webhook 的方式同步京东云监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/jdcloud-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>
+
+## 在京东云
+---
+
+一、在京东云监控配置告警推送
+
+### 步骤 1：创建通知模版
+1. 登录您的京东云控制台，检索 `云监控` 产品，并进入对应产品控制台。
+2. 在左侧菜单中选择 `告警管理->通知模版`，选择创建或编辑通知模版。
+3. 在页面中勾选 `告警回调`， `URL`中输入告警集成的<span class='integration_url'>推送地址</span>。
+4. `POST` 编辑框中输入以下模版内容。
+  ```
+    {
+      "resource_id": "${resourceId}",
+      "request_id": "${requestId}",
+      "metric": "${metric}",
+      "current_value": "${currentValue}",
+      "times": "${times}",
+      "tags": "${tags}",
+      "alert_time": "${alertTime}",
+      "region": "${region}",
+      "threshold": "${threshold}",
+      "service_code": "${serviceCode}",
+      "as_group_id": "${asGroupId}",
+      "unhealthy_instance": "${unhealthyInstance}",
+      "rule_policy_id": "${rulePolicyId}",
+      "service_code_en": "${serviceCodeEN}",
+      "service_code_cn": "${serviceCodeCN}",
+      "level": "${level}",
+      "resource_name": "${resourceName}",
+      "ip_address": "${ipAddress}",
+      "status": "${status}"
+    }
+
+  ```
+5. 其他选项按需配置。
+6. 点击 `保存` 完成配置。
+
+### 步骤 2：配置告警规则
+1. 登录您的京东云控制台，检索 `云监控` 产品，并进入对应产品控制台。
+2. 在左侧菜单中选择 `告警管理->全部告警规则`，选择创建或编辑告警规则。
+3. 在规则编辑页面中的 `通知策略` 处选择 `使用模版` 且模版选择**步骤1**创建的模版。
+4. 其他选项按需配置。
+5. 点击 `保存` 完成配置。
+
+## 二、状态对照
+---
+<div class="md-block">
+
+京东云监控 到 Flashduty 告警等级映射关系：
+
+| 京东云监控          | Flashduty | 状态 |
+| --------------- | --------- | ---- |
+| 紧急        | Critical  | 紧急 |
+| 严重         | Warning   | 警告 |
+| 一般         | Info      | 提醒 |
+
+</div>
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.3即时消息/8.3.1 飞书 Lark 集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.3即时消息/8.3.1 飞书 Lark 集成指引.md
@@ -87,7 +87,8 @@ url: "https://docs.flashcat.cloud/zh/flashduty/lark-integration-guide"
 
 - `im:chat`：获取与更新群组信息
 - `im:message`：获取与发送单聊、群组消息
-- `contact:user.id:readonly`：通过手机号或邮箱获取用户 ID <span id="war-room-scope"></span>
+- `contact:user.id:readonly`：通过手机号或邮箱获取用户 ID
+- `im:message.group_msg`：读取群聊历史消息（AI 生成复盘报告需要读取作战室聊天记录） <span id="war-room-scope"></span>
 
 ![2025-09-18-10-55-14](https://docs-cdn.flashcat.cloud/images/png/d919be62107f6b9d0c662f440d620e61.png)
 

diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.3即时消息/8.3.4 Slack 集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.3即时消息/8.3.4 Slack 集成指引.md
@@ -22,6 +22,8 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 完成先前步骤后，在 Flashduty 集成配置页面的 **增强功能** 模块，勾选 **开启作战室** 即可启用该功能，无需额外配置。
 
+若需启用 AI 生成复盘报告（读取作战室聊天记录），应用需要额外的 `channels:history` 权限。对于已授权的 Slack 集成，您需要手动重新授权以获取该权限。
+
 ## 二、常见问题
 
 ---

diff --git a/src/en.ts b/src/en.ts
@@ -56,6 +56,7 @@ import Harbor from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integr
 import VolcEngineRTC from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.55 Volcengine RTC Integration.md?raw";
 import UcloudCloudWatch from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.56 Ucloud CloudWatch Integration.md?raw";
 import Nagios from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.57 Nagios Integration.md?raw";
+import JDCloudMonitor from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.58 JD Cloud Monitoring Integration.md?raw";
 /** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
 
 /** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -166,6 +167,7 @@ const docs = {
   LabelMappingAPI,
   VolcEngineRTC,
   UcloudCloudWatch,
-  Nagios
+  Nagios,
+  JDCloudMonitor
 };
 export default docs;
diff --git a/src/zh.ts b/src/zh.ts
@@ -56,6 +56,7 @@ import Harbor from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/
 import VolcEngineRTC from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.55 火山引擎 RTC 告警集成指引.md?raw";
 import UcloudCloudWatch from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.56 Ucloud CloudWatch 告警集成指引.md?raw";
 import Nagios from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.57 Nagios 告警集成指引.md?raw";
+import JDCloudMonitor from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.58 京东云监控告警集成指引.md?raw";
 /** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
 
 /** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -164,6 +165,7 @@ const docs = {
   LabelMappingAPI,
   VolcEngineRTC,
   UcloudCloudWatch,
-  Nagios
+  Nagios,
+  JDCloudMonitor
 };
 export default docs;
-Original file line number
+Diff line change
@@ Expand Up @@
     完成先前步骤后，在 Flashduty 集成配置页面的 **增强功能** 模块，勾选 **开启作战室** 即可启用该功能，无需额外配置。
+    若需启用 AI 生成复盘报告（读取作战室聊天记录），应用需要额外的 `channels:history` 权限。对于已授权的 Slack 集成，您需要手动重新授权以获取该权限。
     ## 二、常见问题
     ---
@@ Expand Down @@