Merge branch 'test' of github.com:flashcatcloud/knowledge-base into test

alick-liming · alick-liming · commit 56c4d6314379 · 2026-02-05T17:20:48.000+08:00
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.0 Standard Alert Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.0 Standard Alert Integration.md
@@ -218,5 +218,5 @@ Failed Response:
   3. The new event might be discarded due to matching exclusion, discard, suppression, or silence rules.
   4. When a new event triggers a new alert, the system enters the second layer of noise reduction check, determining if the new alert can be merged into an active incident. If possible, it will only merge into the existing incident without generating a new one.
 
-  For more information, please refer to [Alert Noise Reduction](https://docs.flashcat.cloud/en/flashduty/what-is-noise-reduction).
+  For more information, please refer to [Alert Noise Reduction](https://docs.flashcat.cloud/en/on-call/channel/noise-reduction).
 </details> 
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.1 Email Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.1 Email Integration.md
@@ -97,4 +97,4 @@ attachment_stripped = true
 ## Severity Mapping
 ---
 
-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).
+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/on-call/integration/alert-integration/alert-pipelines).
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.39 StateCloud Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.39 StateCloud Integration.md
@@ -7,7 +7,7 @@ url: "https://docs.flashcat.cloud/en/flashduty/statecloud-integration-guide"
 
 Sync StateCloud monitoring alert events to Flashduty via webhook for automated alert noise reduction.
 
-For resource monitoring events from StateCloud [secondary nodes](#secondary-nodes), please use Huawei Cloud integration. Refer to [Huawei Cloud Alert Integration Guide](https://docs.flashcat.cloud/en/flashduty/huawei-ces-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+For resource monitoring events from StateCloud [secondary nodes](#secondary-nodes), please use Huawei Cloud integration. Refer to [Huawei Cloud Alert Integration Guide](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-sources/huawei-ces).
 
 
 <div class="hide">
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.46 DingtalkAlert Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.46 DingtalkAlert Integration.md
@@ -79,4 +79,4 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-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).
+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/on-call/integration/alert-integration/alert-pipelines).
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.47 Feishu(Lark)Alert Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.47 Feishu(Lark)Alert Integration.md
@@ -79,4 +79,4 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-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).
+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/on-call/integration/alert-integration/alert-pipelines).
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.51 Cloudflare Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.51 Cloudflare Integration.md
@@ -65,7 +65,7 @@ After configuring the Webhook channel, you can use it in notification policies.
 
 <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).
+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/on-call/integration/alert-integration/alert-pipelines).
 
 </div>
 
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.52 WecomAlert Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.52 WecomAlert Integration.md
@@ -73,12 +73,12 @@ By default, the system always creates new alerts for each message, but you can s
 
 ### Notes
 - Wecom alert integration URL only supports Text and Markdown message types; other message types cannot be received
-- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines)"
+- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines)"
 
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 
 ---
 title: "Wecom Alert Integration"
@@ -155,9 +155,9 @@ By default, the system always creates new alerts for each message, but you can s
 
 ### Notes
 - Wecom alert integration URL only supports Text and Markdown message types; other message types cannot be received
-- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines)"
+- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines)"
 
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.53 Harbor Alert Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.53 Harbor Alert Integration.md
@@ -60,5 +60,5 @@ Choose this method when you need to route alerts to different channels based on
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Harbor integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Harbor integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.55 Volcengine RTC Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.55 Volcengine RTC Integration.md
@@ -0,0 +1,69 @@
+---
+title: "Volcengine RTC Alert Events"
+description: "Sync Volcengine RTC 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-rtc-integration-guide"
+---
+
+Sync Volcengine RTC 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 RTC** 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 RTC** 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
+---
+
+### Configure Alert Rules
+
+1. Login to your `Volcengine` console, find `RTC`, and enter the corresponding product console.
+2. In the left menu, select `Monitor->Alert Notifications`, and go to the `Alert Rules` page.
+3. Create or edit an alert rule, check `Alert Callback` on the rule page and fill in the <span class='integration_url'>push URL</span> for the alert integration.
+4. Configure other options as needed.
+5. Click `Confirm` to complete the configuration.
+
+![2026-02-04-17-11-27](https://docs-cdn.flashcat.cloud/images/png/f3a0d7b4943bd21b37fa34831ba120ff.png)
+
+## Status Mapping
+  
+|Volcengine RTC|Flashduty|Status|
+|---|---|---|
+|Critical|Critical|Critical|
+|Warning|Warning|Warning|
+|Notice|Info|Info|
+
+
+You can customize the severity through [Alert Processing Pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
diff --git a/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.56 Ucloud CloudWatch Integration.md b/flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.56 Ucloud CloudWatch Integration.md
@@ -0,0 +1,72 @@
+---
+title: "Ucloud CloudWatch Alert Events"
+description: "Sync Ucloud CloudWatch 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/ucloud-cloudwatch-integration-guide"
+---
+
+Sync Ucloud CloudWatch 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 **Ucloud CloudWatch** 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 **Ucloud CloudWatch** 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 Ucloud
+---
+
+### Step 1: Configure Notice Template
+
+1. Login to your Ucloud console, search for `CloudWatch` product, and enter the corresponding product console.
+2. In the menu, select `Notice Management`, and go to the `Contact Template` page.
+3. Create or edit a notification template, check `Webhook` on the template page.
+4. Select `English` for **Callback Language**, and enter the <span class='integration_url'>push URL</span> for the alert integration in the input box.
+5. Enter `Flashduty` or another name for the template name.
+6. Configure other options as needed.
+7. Click `Submit` to complete the configuration.
+
+![2026-02-05-14-16-00](https://docs-cdn.flashcat.cloud/images/png/9e6ee0943b6f3ee6b942229bd456cf75.png)
+
+### Step 2: Configure Alert Policy
+1. Login to your Ucloud console, search for `CloudWatch` product, and enter the corresponding product console.
+2. In the menu, select `Alarm Management`, and go to the `Alarm Policy` page.
+3. Create or edit an alert policy, find the **Notification Settings** on the policy configuration page, and select the notification template created in **Step 1**.
+4. Configure other options as needed.
+5. Click `Submit` to complete the configuration.
+
+
+## Severity Mapping
+---
+Currently, all Ucloud CloudWatch alert events pushed to Flashduty have a severity of Warning. You can customize the severity through [Alert Processing Pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.0 标准告警事件集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.0 标准告警事件集成指引.md
@@ -225,6 +225,6 @@ curl -X POST '{api_host}/event/push/alert/standard?integration_key={integration_
   3. 新的event可能由于匹配到排除、丢弃、抑制或静默规则，而被丢弃。
   4. 当新的event触发了新告警，则系统会进入第二层降噪检查，判断新告警是否可以被合并到某个活跃的故障中，如果可以，则只会并入已有的故障，而不会产生新故障。
 
-  更多内容请参考 [告警降噪](https://docs.flashcat.cloud/zh/flashduty/what-is-noise-reduction)。
+  更多内容请参考 [告警降噪](https://docs.flashcat.cloud/zh/on-call/channel/noise-reduction)。
 </details>
 
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.1 邮件 Email 集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.1 邮件 Email 集成指引.md
@@ -97,5 +97,5 @@ attachment_stripped = true
 ## 严重程度映射关系
 ---
 
-当前邮件集成推送到 Flashduty 的告警等级均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+当前邮件集成推送到 Flashduty 的告警等级均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。
 
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.39 天翼云告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.39 天翼云告警集成指引.md
@@ -7,7 +7,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 通过 webhook 的方式同步天翼云监控告警事件到 Flashduty，实现告警事件自动化降噪处理。
 
-天翼云[二级节点](#二级节点)的资源监控事件推送，请使用华为云集成，请参考 [华为云告警集成指引](https://docs.flashcat.cloud/zh/flashduty/huawei-ces-integration-guide)。
+天翼云[二级节点](#二级节点)的资源监控事件推送，请使用华为云集成，请参考 [华为云告警集成指引](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-sources/huawei-ces)。
 
 <div class="hide">
 
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.46 钉钉告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.46 钉钉告警集成指引.md
@@ -79,5 +79,5 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-alert-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。
 
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.47 飞书 Lark 告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.47 飞书 Lark 告警集成指引.md
@@ -79,5 +79,5 @@ url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。
 
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.51 Cloudflare 集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.51 Cloudflare 集成指引.md
@@ -64,7 +64,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-detect-integration-gui
 
 <div class="md-block">
 
-当前 Cloudflare 集成推送到 Flashduty 的告警等级均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+当前 Cloudflare 集成推送到 Flashduty 的告警等级均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。
 
 </div>
 
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.52 企微告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.52 企微告警集成指引.md
@@ -73,9 +73,9 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-alert-integration-guide"
 
 ### 注意事项
 - 企微告警集成地址仅支持接收 Text、Markdown 消息类型，其他消息无法接收。
-- Flashduty 会生成默认告警标题： “企微机器人告警”，如果您需要更改标题，可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义标题。
+- Flashduty 会生成默认告警标题： “企微机器人告警”，如果您需要更改标题，可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义标题。
 
 ## 严重程度映射关系
 ---
 
-当前企微告警集成推送到 Flashduty 的严重程度均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+当前企微告警集成推送到 Flashduty 的严重程度均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.53 Harbor 告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.53 Harbor 告警集成指引.md
@@ -65,4 +65,4 @@ url: "https://docs.flashcat.cloud/zh/flashduty/harboe-integration-guide"
 ## 严重程度映射关系
 ---
 
-当前 Harbor 告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
+当前 Harbor 告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.55 火山引擎 RTC 告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.55 火山引擎 RTC 告警集成指引.md
diff --git a/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.56 Ucloud CloudWatch 告警集成指引.md b/flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.56 Ucloud CloudWatch 告警集成指引.md
diff --git a/src/en.ts b/src/en.ts
diff --git a/src/zh.ts b/src/zh.ts
