flashduty-knowledge-base 1.3.5 → 1.3.7

package/dist/esm/en.js

@@ -77,11 +77,20 @@ Field|Required|Type|Description
 
 Field|Required|Type|Description
 :-:|:-:|:-:|:---
-| title_rule | Yes | string | Alert title, no more than \`512\` characters, will be truncated if exceeded.<br><br>Supports dynamic title generation based on alert content, see [Customizing Incidents](https://docs.flashcat.cloud/en/flashduty/customize-incident-attrs) for generation rules.
+| title_rule | Yes | string | Alert title, no more than \`512\` characters, will be truncated if exceeded.<br><br>Supports dynamic title generation based on alert content, see [Customizing Incidents](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines) for generation rules.
 | event_status | Yes | string | Alert status.<br><br>Enumerated values (case-sensitive): *Critical*, *Warning*, *Info*, *Ok*.<br><br>When specified as Ok, it means automatic recovery of the alert.
 | alert_key | No | string | Alert identifier, used to update or automatically recover existing alerts.<br><br>You can customize this value, but it cannot exceed \`255\` characters. You can also rely on system auto-generation, this value will be returned in the response.<br><br>If you're reporting a recovery event, this value must exist.
 | description | No | string | Alert description, no more than \`2048\` characters, will be truncated if exceeded.
 | labels | No | map | Alert label collection, key is the label name, value is the label value:<br><br>1. Both key and value of labels are string type, case-sensitive.<br>2. Label key should not exceed \`128\` characters, following Prometheus label naming conventions. Value should not exceed \`2048\` characters, will be truncated if exceeded.<br>3. Maximum of \`50\` labels. See \`Label Content Reference\` in [Best Practices](#best-practices).<br><br>Example: "resource": "171.26.23.22", "check": "api latency > 500ms"
+| images | No | [][image](#image) | Array of images, used for image display in frontend or Feishu/DingTalk application notifications.The system merged/overwritten based on alt, for the same alt (including empty strings), only one is retained
+
+#### image Structure <span id="image"></span>
+
+Field|Required|Type|Description
+:-:|:-:|:-:|:---
+| alt | No | string | Image alternative text, limit 128 characters, truncated if exceeded.
+| src | Yes | string | Image source, value: http/https URL or image_key returned by [Image Upload API](https://developer.flashcat.cloud/api-344943718). Limit 256 characters, discarded if exceeded
+| href | No | string | Hyperlink reference path, limit 256 characters, truncated if exceeded
     
 </div>
 
@@ -209,7 +218,7 @@ 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> `,t=`---
 title: "Email Integration"
 description: "Generate a unique email address in Flashduty to synchronize alert triggers and recoveries through email"
@@ -309,7 +318,8 @@ 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).
+
 `,a=`---
 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"
@@ -387,7 +397,7 @@ In the new version, although you can configure the collaboration space directly
 #### Step 1: Add Notification Media
 
 1. Log in to your n9e console, select Alerting > Media types and click **Add**
-2. Fill in the media name and identifier, select **FlashDuty** type, and enter the integration push URL in the \`URL\` section
+2. Fill in the media name and identifier, select **Flashduty** type, and enter the integration push URL in the \`URL\` section
 3. Click **Save** and complete
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/n9e-1.png" />
@@ -396,7 +406,7 @@ In the new version, although you can configure the collaboration space directly
 
 1. Log in to your n9e console, select Alerting > Rules and click **Add** or edit the existing alert rules
 2. Configure the basic information as needed
-3. Select the \`FlashDuty\` notification media added in the previous step
+3. Select the \`Flashduty\` notification media added in the previous step
 4. Select the collaboration space (the collaboration space must be created in [Flashduty](https://console.flashcat.cloud/channel) in advance), and select other options as needed
 5. Click **Save** and complete
 
@@ -405,7 +415,7 @@ In the new version, although you can configure the collaboration space directly
 #### Step 3: Select Notification Rules in Alert Rules
 
 1. Log in to your n9e console, select Alerting > Alert Rules and click **Add** or edit the existing alert rules
-2. Select the \`FlashDuty\` notification rule added in the previous step, and select other options as needed
+2. Select the \`Flashduty\` notification rule added in the previous step, and select other options as needed
 3. Click **Save** and complete
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/n9e-3.png" />
@@ -506,7 +516,7 @@ Nightingale/Flashcat to Flashduty alert severity mapping:
     
 </details>
 
-`,i=`---
+`,o=`---
 title: "Prometheus Integration Guide"
 description: "Push Prometheus alert events to Flashduty through AlertManager using webhooks. When an alert is triggered, it sends a trigger event to Flashduty, and when the alert recovers, it sends a recovery event."
 date: "2025-05-19T10:00:00+08:00"
@@ -688,7 +698,7 @@ Prometheus to Flashduty severity mapping:
 
 
 
-`,o=`---
+`,i=`---
 title: "Grafana Integration"
 description: "Sync Grafana alert events to Flashduty via webhook to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -890,7 +900,7 @@ The media type must be associated with a user to send events. The user must have
 1. Log in to the Zabbix console, select \`Users > Users\`, select Admin user, select media, select Add to enter the editing window:
 
 - Type: Select the Flashduty media type created above
-- Send To: Fill in FlashDuty
+- Send To: Fill in Flashduty
 - Keep other configurations unchanged using default settings
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zabbix-3.png" />
@@ -904,7 +914,7 @@ Sending notifications is one of the operations executed by actions in Zabbix. Th
 
 1. Click \`Create action\` to enter the action editing page
 
-- Name: Fill in "Send To FlashDuty"
+- Name: Fill in "Send To Flashduty"
 
 2. Select \`Operations\`, add notification sending configurations for three scenarios respectively:
 
@@ -978,7 +988,7 @@ Sending notifications is one of the operations executed by actions in Zabbix. Th
 
 1. Click \`Create action\` to enter the action editing page
 
-- Name: Fill in "Send To FlashDuty"
+- Name: Fill in "Send To Flashduty"
 
 2. Select \`Operations\`, add notification sending configurations for three scenarios respectively:
 
@@ -1015,7 +1025,7 @@ Log in to the Zabbix console, select \`Monitoring > Problems\` to view the lates
 
 - \`{ALERT.SUBJECT}\`: Alert title, keep as first parameter
 - \`{ALERT.MESSAGE}\`: Alert message, keep as second parameter
-- \`FlashDuty webhook push URL\`, simply copy the integration push URL, keep as third parameter
+- \`Flashduty webhook push URL\`, simply copy the integration push URL, keep as third parameter
 - \`Zabbix console address\`, copy directly (if your page is configured with tomcat/nginx forwarding path, please include it), used to generate alert detail page links. Leave empty if none, keep as fourth parameter
 - \`HTTPProxy\`: If your Zabbix Server cannot directly access Flashduty services, you can set this parameter to a proxy address. Leave empty if none, keep as fifth parameter
 
@@ -1059,7 +1069,7 @@ Sending notifications is one of the operations executed by actions in Zabbix. Th
 
 1. Click \`Create action\` to enter the action editing page
 
-   - Name: Fill in "Send To FlashDuty"
+   - Name: Fill in "Send To Flashduty"
 
 2. Select \`Operations\`, update notification user configurations for three scenarios respectively:
 
@@ -1074,10 +1084,10 @@ Sending notifications is one of the operations executed by actions in Zabbix. Th
 
 3. Select \`Operations\`, update notification content configurations for three scenarios respectively:
 
-   - **In the Default Message configuration item, completely copy the following content and paste it after the default content**. FlashDuty will parse corresponding text after receiving events to find alert attribute information:
+   - **In the Default Message configuration item, completely copy the following content and paste it after the default content**. Flashduty will parse corresponding text after receiving events to find alert attribute information:
 
 \`\`\`
------FlashDuty Required Starts-----event_severity={TRIGGER.SEVERITY}||event_name={TRIGGER.NAME}||event_id={EVENT.ID}||event_tags={EVENT.TAGS}||event_ack={EVENT.ACK.STATUS}||event_value={EVENT.VALUE}||trigger_id={TRIGGER.ID}||trigger_desc={TRIGGER.DESCRIPTION}||trigger_expr={TRIGGER.EXPRESSION}||host_group={TRIGGER.HOSTGROUP.NAME}||host_ip={HOST.IP}||host_name={HOST.NAME}||item_name={ITEM.NAME}||item_value={ITEM.VALUE}-----FlashDuty Required Ends-----
+-----Flashduty Required Starts-----event_severity={TRIGGER.SEVERITY}||event_name={TRIGGER.NAME}||event_id={EVENT.ID}||event_tags={EVENT.TAGS}||event_ack={EVENT.ACK.STATUS}||event_value={EVENT.VALUE}||trigger_id={TRIGGER.ID}||trigger_desc={TRIGGER.DESCRIPTION}||trigger_expr={TRIGGER.EXPRESSION}||host_group={TRIGGER.HOSTGROUP.NAME}||host_ip={HOST.IP}||host_name={HOST.NAME}||item_name={ITEM.NAME}||item_value={ITEM.VALUE}-----Flashduty Required Ends-----
 \`\`\`
 
 - Repeat the above steps to complete the configuration of \`Recovery operations\` and \`Update operations\`
@@ -1163,7 +1173,7 @@ Choose this option when you need to route alerts to different channels based on
 **Step 1: Set up Notification Channel**
 
 1. Go to \`Settings -> Notifications\` page, click Setup to edit, as shown below;
-2. Select \`FlashDuty (Flashduty)\` as the \`Notification Type\`;
+2. Select \`Flashduty (Flashduty)\` as the \`Notification Type\`;
 3. Copy and paste the integration_key parameter value from the integration push URL into \`Integration Key\`;
 4. Select \`Severity\` as needed;
 5. Submit and save
@@ -1176,7 +1186,7 @@ Choose this option when you need to route alerts to different channels based on
 
 1. Click \`Add New Monitor\` or edit existing monitors, configure monitoring settings as needed;
 2. As shown, enable the notification method created in the previous step in the \`Notifications\` section;
-3. If needed, add \`Tags\`. Note that only tags with both Key/Value will be pushed to FlashDuty;
+3. If needed, add \`Tags\`. Note that only tags with both Key/Value will be pushed to Flashduty;
 4. Submit and save, then wait for alerts to trigger.
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/upk/upk-2.png" alt="drawing" width="500"/>
@@ -1575,7 +1585,7 @@ Choose this option when you need to route alerts to different channels based on
 <img src="https://download.flashcat.cloud/flashduty/doc/en/aliyun/sls-5.png" alt="drawing" width="500"/>
 
 4. Click the \`Confirm\` button to save
-5. Repeat these steps for all other rules to push all alerts to FlashDuty
+5. Repeat these steps for all other rules to push all alerts to Flashduty
 
 </div>
 
@@ -1594,7 +1604,7 @@ Alibaba Cloud SLS monitoring to Flashduty alert severity mapping:
 | 2                | Info      | Info |
 
 </div>
-`,h=`---
+`,u=`---
 title: "AWS CloudWatch Integration"
 description: "Sync AWS CloudWatch alert events to Flashduty via webhook to achieve automated alert noise reduction"
 date: "2025-05-19T10:00:00+08:00"
@@ -1646,10 +1656,10 @@ Choose this method when you need to route alerts to different channels based on
 
 1. Log in to your AWS Console, search for \`Simple Notification Service\` product and enter its console
 2. Go to the \`Topics\` page, click the \`Create topic\` button to start creating a topic
-3. Select \`Standard\` for \`Type\`, enter \`FlashDuty\` as the name
+3. Select \`Standard\` for \`Type\`, enter \`Flashduty\` as the name
 4. Click the \`Create Topic\` button to complete topic creation
 5. Go to the \`Subscriptions\` page, click the \`Create subscription\` button to create a subscription for the topic
-6. Select \`FlashDuty\` for \`Topic ARN\`, choose \`HTTPS\` for \`Protocol\`, enter the integration push URL for \`Endpoint\` (enter the integration name on the current page, the URL will be generated after saving)
+6. Select \`Flashduty\` for \`Topic ARN\`, choose \`HTTPS\` for \`Protocol\`, enter the integration push URL for \`Endpoint\` (enter the integration name on the current page, the URL will be generated after saving)
 7. Click the \`Create subscription\` button to complete subscription creation
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/aws-cloudwatch-subscribe.png" />
@@ -1657,7 +1667,7 @@ Choose this method when you need to route alerts to different channels based on
 8. Return to the \`Subscriptions\` page. When the subscription status shows \`Confirmed\`, the subscription URL verification is successful; otherwise, please contact Flashduty
 9. Search for the \`CloudWatch\` product and enter its console
 10. Go to the \`All alarms\` page, choose to create or edit existing alarm policies
-11. For the \`Notification\` step, select \`FlashDuty\` as the \`SNS topic\` for all three states: \`In alarm\`, \`OK\`, and \`Insufficient data\`, as shown below:
+11. For the \`Notification\` step, select \`Flashduty\` as the \`SNS topic\` for all three states: \`In alarm\`, \`OK\`, and \`Insufficient data\`, as shown below:
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/aws-cloudwatch-alram.png" />
 
@@ -1673,7 +1683,7 @@ Choose this method when you need to route alerts to different channels based on
 All CloudWatch metric alarms correspond to Flashduty "warning" severity level alerts.
 
 </div>
-`,u=`---
+`,h=`---
 title: "Baidu Cloud BCM Integration"
 description: "Sync Baidu Cloud BCM alerts to Flashduty via webhook for automated alert noise reduction"
 date: "2025-05-19T10:00:00+08:00"
@@ -1806,7 +1816,7 @@ Choose this method when you need to route alerts to different channels based on
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-1.png" alt="drawing" width="500"/>
 
 5. Go to \`Alarm-Alarm Notifications-Notification Groups\` page, click \`Create Notification Group\` button
-6. Enter \`FlashDuty\` as group name, check the \`flashduty\` notification object created earlier
+6. Enter \`Flashduty\` as group name, check the \`flashduty\` notification object created earlier
 7. Click \`OK\` button to complete notification group creation
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-2.png" alt="drawing" width="500"/>
@@ -1814,7 +1824,7 @@ Choose this method when you need to route alerts to different channels based on
 Note: When creating a notification group, Huawei Cloud will send a request to Flashduty to verify the push URL. Check the notification group's object list - alerts will only be pushed normally when the notification object status is \`Confirmed\`
 
 8. Go to \`Alarm-Alarm Rules\` page, edit existing alarm rules or create new ones to open the \`Alarm Rule Details\` page
-9. Select \`FlashDuty\` as the notification group, check both \`Alarm Triggered\` and \`Cleared\` conditions. Click \`OK\` button to save changes
+9. Select \`Flashduty\` as the notification group, check both \`Alarm Triggered\` and \`Cleared\` conditions. Click \`OK\` button to save changes
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-3.png" alt="drawing" width="500"/>
 
@@ -1891,7 +1901,7 @@ Supports Influxdata versions 1.x ~ 2.x, with different configurations for each v
 #### Step 1: Create Alert Channel
 1. Log in to your \`Influxdata\` console and navigate to the \`Alerts > Notification Endpoints\` page.
 2. Click \`Create\` to create an alert notification channel.
-3. Select \`HTTP\` for \`Destination\` and enter \`FlashDuty\` for \`Name\`.
+3. Select \`HTTP\` for \`Destination\` and enter \`Flashduty\` for \`Name\`.
 4. Choose \`POST\` for \`HTTP Method\` and enter the integration push URL.
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/influxdb-1.png" />
@@ -1900,7 +1910,7 @@ Supports Influxdata versions 1.x ~ 2.x, with different configurations for each v
 1. Log in to your \`Influxdata\` console and navigate to the \`Alerts > Notification Rules\` page.
 2. Click \`Create\` to create an alert notification rule.
 3. Configure \`About\` and \`Conditions\` as needed.
-4. Select \`FlashDuty\` created in Step 1 for \`Message\`.
+4. Select \`Flashduty\` created in Step 1 for \`Message\`.
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/influxdb-2.png" />
 
@@ -2164,7 +2174,7 @@ filter:
       query_string:
         query: "created_at:*"
 
-# ------- FlashDuty ----------------
+# ------- Flashduty ----------------
 alert: pagerduty
 pagerduty_service_key: xxx
 pagerduty_client_name: wahaha
@@ -2174,7 +2184,7 @@ pagerduty_v2_payload_component: mysql
 pagerduty_v2_payload_group: app-stack
 pagerduty_v2_payload_severity: error
 pagerduty_v2_payload_source: mysql.host.name
-# ------- FlashDuty ----------------
+# ------- Flashduty ----------------
 \`\`\`
 
 4. Step 4: Restart ElastAlert and wait for alerts to trigger
@@ -2238,7 +2248,7 @@ BlueKing alert policies can trigger \`Action Plans\`, which can integrate with e
 
 1. Log in to your BlueKing desktop and enter the \`Monitor Platform\`;
 2. Go to \`Configuration-Action Plans\` page, click the \`Add Plan\` button to start creating an action plan;
-3. Enter the name as \`Send To FlashDuty\`, select \`HTTP Callback\` as the plan type, choose \`POST\` as the push method, and fill in the integration push URL (obtained after saving the integration), as shown below:
+3. Enter the name as \`Send To Flashduty\`, select \`HTTP Callback\` as the plan type, choose \`POST\` as the push method, and fill in the integration push URL (obtained after saving the integration), as shown below:
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/integration/tencent-bk/create_package.jpg" />
 
@@ -2256,12 +2266,12 @@ BlueKing alert policies can trigger \`Action Plans\`, which can integrate with e
 <div class="md-block">
 
 1. Go to \`Configuration-Alert Policies\` page, select an existing policy to edit or create a new one;
-2. Scroll down to the \`Alert Processing\` section, select the \`Send To FlashDuty\` action plan for all three scenarios, and disable \`Defense Rules\`, as shown below:
+2. Scroll down to the \`Alert Processing\` section, select the \`Send To Flashduty\` action plan for all three scenarios, and disable \`Defense Rules\`, as shown below:
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/integration/tencent-bk/update_alert_rule.jpg" />
 
 3. Submit and save to complete;
-4. Repeat these steps for other alerts you want to push to FlashDuty.
+4. Repeat these steps for other alerts you want to push to Flashduty.
 
 </div>
 
@@ -2278,7 +2288,7 @@ Alert severity mapping between BlueKing and Flashduty:
 | Notice   | Info      | info |
 
 </div>
-`,v=`---
+`,b=`---
 title: "Tencent Cloud CLS Integration"
 description: "Sync Tencent Cloud Log Service (CLS) monitoring alerts to Flashduty via webhook for automated alert noise reduction"
 date: "2025-05-19T10:00:00+08:00"
@@ -2398,7 +2408,7 @@ Choose this option when you need to route alerts to different channels based on
     "record_group_id": "{{escape .RecordGroupId}}",
     "detail_url": "{{escape .DetailUrl}}",
     "query_url": "{{escape .QueryUrl}}",
-    "message": {{.Message}},
+    "message": "{{.Message}}",
     "query_result": {{.QueryResult}},
     "query_log": {{.QueryLog}},
     "analysis_result": {{.AnalysisResult}}
@@ -2420,7 +2430,7 @@ Tencent Cloud CLS monitoring alert level mapping to Flashduty:
 | Critical      | Critical  | Critical
 
 </div>
-`,b=`---
+`,v=`---
 title: "Tencent Cloud Monitor CM Integration"
 description: "Sync Tencent Cloud Monitor CM alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2025-05-19T10:00:00+08:00"
@@ -2545,7 +2555,7 @@ Choose this method when you need to route alerts to different channels based on
 
 1. Log in to your Tencent Cloud Console and select EventBridge service
 2. Go to the Event Rules page, click the New button to start editing rules
-3. Enter the name as FlashDuty, as shown below:
+3. Enter the name as Flashduty, as shown below:
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/tencent-eb-new-rule.png" />
 
@@ -2646,12 +2656,12 @@ Choose this method when you need to route alerts to different channels based on
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/oceanbase-1.png" />
 
-5. Copy the following script content into the channel configuration, and **please add the integration_key value from your FlashDuty push URL to the integration_key parameter in the script**
+5. Copy the following script content into the channel configuration, and **please add the integration_key value from your Flashduty push URL to the integration_key parameter in the script**
 
 \`\`\`
 #!/usr/bin/env bash
 
-function sendToFlashDuty() {
+function sendToFlashduty() {
     URL="\${address}/event/push/alert/standard?integration_key=\${integration_key}"
     curl -s -X POST \${URL} -H 'Content-Type: application/json' -d '{
         "event_status": "'\${alert_level}'",
@@ -2715,7 +2725,7 @@ elif [[ \${statusMd5} == "\${active}" ]];then
 fi
 
 if [[ \${statusMd5} == \${active} || \${statusMd5} == \${Inactive} ]];then
-    sendToFlashDuty
+    sendToFlashduty
 fi
 \`\`\`
 
@@ -2753,7 +2763,7 @@ OCP Alert Notification - Single Alert
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/oceanbase-2.png" />
 
 3. Select **English** for push language
-4. Select **FlashDuty** for alert channel
+4. Select **Flashduty** for alert channel
 5. Enable **Recovery Notification**
 6. Submit
 
@@ -2767,7 +2777,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|
@@ -2834,7 +2844,7 @@ Choose this option when you need to route alerts to different channels based on
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/graylog-2.png" />
 
-6. Enter the FlashDuty URL you obtained (URL whitelist required for first-time use)
+6. Enter the Flashduty URL you obtained (URL whitelist required for first-time use)
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/graylog-3.png" />
 
@@ -2846,11 +2856,11 @@ Choose this option when you need to route alerts to different channels based on
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/graylog-5.png" />
 
-### Step 2: Use FlashDuty Alert Channel in Alert Events
+### Step 2: Use Flashduty Alert Channel in Alert Events
 1. Create or edit existing Event Definition
 2. Skip other alert configurations here (configure alert conditions according to business requirements)
 3. Configure channel in Notifications
-4. Add Notification and select FlashDuty channel
+4. Add Notification and select Flashduty channel
 5. Click Done
 6. Complete the next step to finish
 
@@ -2936,7 +2946,7 @@ rules:
         tags:
             level: Warning
 \`\`\`
-4. Add the FlashDuty webhook URL
+4. Add the Flashduty webhook URL
 
 \`\`\`
 # Add at the bottom of the configuration file
@@ -3022,12 +3032,12 @@ Sentry provides two types of alert mechanisms: Issue Alerts and Metric Alerts. W
 
 ## II. Sentry Alert Push Configuration
 
-### Step 1: Add FlashDuty Custom Integrations 
+### Step 1: Add Flashduty Custom Integrations 
 
 1. Log in to the Sentry management console
 2. In the left navigation bar, locate **Settings => Custom Integrations**
 3. Click Create New Integration and select **Internal Integration**
-4. On the editing page, **enter FlashDuty for Name and paste the integration push URL into WebhookURL**
+4. On the editing page, **enter Flashduty for Name and paste the integration push URL into WebhookURL**
 5. Enable **Alert Rule Action**, configure as shown below:
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/sentry-1.png" />
@@ -3039,11 +3049,11 @@ Sentry provides two types of alert mechanisms: Issue Alerts and Metric Alerts. W
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/sentry-2.png" />
 
 **Special notes about WEBHOOKS configuration:** 
-1. After checking **issue**, FlashDuty can receive resolved events for issues, meaning when manually triggering resolved for an issue in the issue list, we will automatically recover the associated incident in FlashDuty
+1. After checking **issue**, Flashduty can receive resolved events for issues, meaning when manually triggering resolved for an issue in the issue list, we will automatically recover the associated incident in Flashduty
 2. Other issue events such as create, assigned, archived, and unresolved are not supported
-3. If error and comment are also checked, FlashDuty will not receive or process these types of events
+3. If error and comment are also checked, Flashduty will not receive or process these types of events
 
-### Step 2: Use FlashDuty Integration in Alerts
+### Step 2: Use Flashduty Integration in Alerts
 1. In the left navigation bar, locate **Alerts => Create Alert**
 2. Select the type of Alert to create, such as Issue
 
@@ -3055,7 +3065,7 @@ Sentry provides two types of alert mechanisms: Issue Alerts and Metric Alerts. W
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/sentry-4.png" />
 
-5. Select **FlashDuty** added above as the notification channel
+5. Select **Flashduty** added above as the notification channel
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/sentry-5.png" />
 
@@ -3136,7 +3146,7 @@ Choose this option when you need to route alerts to different channels based on
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/jkb-2.png" />
 
-4. Enter FlashDuty as the custom name, and input the copied integration push URL
+4. Enter Flashduty as the custom name, and input the copied integration push URL
 5. Select **POST** as the callback method and **JSON** as the data format
 6. Check **Enable URL Callback**, configure other options as needed, refer to the image below
 
@@ -3144,10 +3154,10 @@ Choose this option when you need to route alerts to different channels based on
 
 7. Click Save
 
-### Step 2: Use FlashDuty Alert Channel in Monitoring Tasks
+### Step 2: Use Flashduty Alert Channel in Monitoring Tasks
 1. Create or edit an existing monitoring task
 2. Other alert configurations are omitted here
-3. Under Webhook notification, select the FlashDuty channel
+3. Under Webhook notification, select the Flashduty channel
 
 <img alt="drawing" width="600" src="https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/doc/jkb-4.png" />
 
@@ -3164,7 +3174,7 @@ Choose this option when you need to route alerts to different channels based on
 |2|Info|Info|
 
 </div>
-`,F=`---
+`,x=`---
 title: "AWS EventBridge Alert Events"
 description: "Sync AWS EventBridge alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3225,10 +3235,10 @@ Choose this option when you need to route alerts to different channels based on
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-3.png" />
 
-4. In the \`Connection details\` section, enter \`FlashDuty\` for \`Connection name\`
+4. In the \`Connection details\` section, enter \`Flashduty\` for \`Connection name\`
 5. In the \`Authorization\` section, select \`Other\` for \`Destination type\`
 6. Select \`API Key\` for \`Authorization type\`
-7. Enter \`FlashDuty\` for \`API key name\`, and enter the \`integration_key\` from the integration push URL for \`Value\`
+7. Enter \`Flashduty\` for \`API key name\`, and enter the \`integration_key\` from the integration push URL for \`Value\`
 8. Click \`Create\` to save
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-4.png" />
@@ -3239,10 +3249,10 @@ Choose this option when you need to route alerts to different channels based on
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-5.png" />
 
-2. Fill in the information in the \`API destination detail\` editing interface, enter \`FlashDuty\` for \`Name\`
+2. Fill in the information in the \`API destination detail\` editing interface, enter \`Flashduty\` for \`Name\`
 3. Enter the integration push URL for \`API destination endpoint\`
 4. Select \`POST\` for \`HTTP method\`
-5. Select \`Use an existing connection\` for \`Connection type\` and choose the \`FlashDuty\` Connection added in Step 1
+5. Select \`Use an existing connection\` for \`Connection type\` and choose the \`Flashduty\` Connection added in Step 1
 6. Click \`Create\` to save
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-6.png" />
@@ -3252,7 +3262,7 @@ Choose this option when you need to route alerts to different channels based on
 2. Select \`Buses=>Rules\` from the left navigation bar, create or edit existing rules
 3. Other configurations are omitted here
 4. For \`Target types\`, select \`EventBridge API destination\` as the target type
-5. Under \`API destination\`, select \`Use an existing API destination\` and choose the \`FlashDuty\` API destination created in Step 2 from the dropdown
+5. Under \`API destination\`, select \`Use an existing API destination\` and choose the \`Flashduty\` API destination created in Step 2 from the dropdown
 6. Click \`Next\`, configure as needed, and save
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-7.png" />
@@ -3261,12 +3271,12 @@ Choose this option when you need to route alerts to different channels based on
 
 <div class="md-block">
   
-1. Since AWS EventBridge events don't have severity levels, all events pushed to FlashDuty will have a Warning severity
-2. AWS EventBridge events only have triggers without recovery states, so events received by FlashDuty won't automatically associate with recovery
+1. Since AWS EventBridge events don't have severity levels, all events pushed to Flashduty will have a Warning severity
+2. AWS EventBridge events only have triggers without recovery states, so events received by Flashduty won't automatically associate with recovery
 
 </div>
 
-`,x=`---
+`,F=`---
 title: "Dynatrace Alert Events"
 description: "Sync Dynatrace alert events to Flashduty via webhook to achieve automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -3335,7 +3345,7 @@ Choose this option when you need to route alerts to different channels based on
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/dyn-3.png" />
 
 5. Under \`Notification type\`, select \`Custom Integration\`
-6. Fill in \`Display name\` with \`FlashDuty\`
+6. Fill in \`Display name\` with \`Flashduty\`
 7. In \`Webhook URL\`, enter the integration push URL (generated after saving the integration name on the current page)
 8. Keep \`Call webhook if problem is closed\` enabled
 
@@ -3373,7 +3383,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`,L=`---
+`,_=`---
 title: "Huawei Cloud LTS Alert Events"
 description: "Sync Huawei Cloud Log Tank Service (LTS) alert events to Flashduty via webhook for automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -3426,14 +3436,14 @@ Choose this option when you need to route alerts to different channels based on
 
 ## I. Huawei Cloud LTS Alert Push Configuration
 
-### Step 1: Create FlashDuty Alert Channel
+### Step 1: Create Flashduty Alert Channel
 1. Log in to your Huawei Cloud Console, search for \`SMN\` (Simple Message Notification) service and enter its console
 2. Select \`Topic Management=>Topics\` from the left navigation bar
-3. Click \`Create Topic\`, enter \`FlashDuty\` as the topic name in the edit page and confirm
+3. Click \`Create Topic\`, enter \`Flashduty\` as the topic name in the edit page and confirm
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-1.png" alt="drawing" width="500"/>
 
-4. Return to the topic list and click \`Add Subscription\` in the newly created FlashDuty topic
+4. Return to the topic list and click \`Add Subscription\` in the newly created Flashduty topic
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-2.png" alt="drawing" width="500"/>
 
@@ -3452,14 +3462,14 @@ Choose this option when you need to route alerts to different channels based on
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-5.png" alt="drawing" width="500"/>
 
-3. In the template edit page, enter **FlashDuty** as the name, select \`English\` as the message header language
+3. In the template edit page, enter **Flashduty** as the name, select \`English\` as the message header language
 4. Select \`HTTP/HTTPS\` as notification type and \`JSON\` as data type
 5. Click \`Confirm\` to save
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-6.png" alt="drawing" width="500"/>
 
 6. Return to the \`Alert Action Rules\` list and click \`Create\`
-7. Enter **FlashDuty** as the rule name, select the previously created **FlashDuty** topic and template
+7. Enter **Flashduty** as the rule name, select the previously created **Flashduty** topic and template
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-7.png" alt="drawing" width="500"/>
 
@@ -3469,7 +3479,7 @@ Choose this option when you need to route alerts to different channels based on
 2. Create or edit existing alert rules
 3. Other configurations are omitted here
 4. In \`Advanced Settings\`, check both \`Alert Trigger\` and \`Alert Recovery\` in notification scenarios
-5. Enable action rules and select the **FlashDuty** rule created in \`Step 2\`
+5. Enable action rules and select the **Flashduty** rule created in \`Step 2\`
 6. Select \`English\` as language, click \`Confirm\` to save after configuration is complete
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-8.png" alt="drawing" width="500"/>
@@ -3486,7 +3496,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,_=`---
+`,R=`---
 title: "Google Cloud Monitoring Alert Events"
 description: "Sync Google Cloud Monitoring alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -3547,18 +3557,18 @@ Choose this option when you need to route alerts to different channels based on
 
 3. Find \`Webhooks\` on the Notification channels page and click \`ADD NEW\`
 4. Enter the integration push URL in the \`Endpoint URL\` field (the URL will be generated after saving the integration name on the current page)
-5. Enter **FlashDuty** in the \`Display Name\` field
+5. Enter **Flashduty** in the \`Display Name\` field
 6. Click \`TEST CONNECTION\` and then \`SAVE\` to complete
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/google-cm-2.png" />
 
-### Step 2: Use FlashDuty Alert Channel in Alert Policy
+### Step 2: Use Flashduty Alert Channel in Alert Policy
 
 1. Return to the \`Alerting\` page
 2. Create or edit an existing policy
 3. Skip other policy configurations (configure alert conditions according to business requirements)
 4. On the \`Notifications and name\` page, keep \`Use notification channel\` enabled
-5. Select the **FlashDuty** channel created in **Step 1** from the \`Notification channels\` dropdown, and check \`Notify on incident closure\`
+5. Select the **Flashduty** channel created in **Step 1** from the \`Notification channels\` dropdown, and check \`Notify on incident closure\`
 6. Complete other configurations and save the policy
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/google-cm-3.png" />
@@ -3577,7 +3587,7 @@ Choose this option when you need to route alerts to different channels based on
 |No severity|Info|Info|
 
 </div>
-`,R=`---
+`,L=`---
 title: "Splunk Alert Events"
 description: "Sync Splunk alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3705,14 +3715,14 @@ Choose this method when you need to route alerts to different channels based on
 
 ## I. AppDynamics Alert Push Configuration
 
-### Step 1: Configure FlashDuty Alert Channel
+### Step 1: Configure Flashduty Alert Channel
 
 1. Log in to your AppDynamics console
 2. Find \`Alert Respond\`, select \`HTTP Request Templates\`, and click \`New\` to create an alert channel
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/appdyn-1.png" />
 
-3. In the template configuration, enter **FlashDuty** as the \`Name\`
+3. In the template configuration, enter **Flashduty** as the \`Name\`
 4. In the \`Request URL\` section, select **POST** as the \`Method\`, and enter the integration push URL in \`Raw URL\` (enter the integration name on this page, and the URL will be generated after saving)
  
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/appdyn-2.png" />
@@ -3785,7 +3795,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/appdyn-6.png" />
 
-3. In the \`Create HTTP Action\` popup, enter a Name, select **FlashDuty** created in \`Step 1\` as the \`HTTP Request Template\`, and click \`SAVE\`
+3. In the \`Create HTTP Action\` popup, enter a Name, select **Flashduty** created in \`Step 1\` as the \`HTTP Request Template\`, and click \`SAVE\`
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/appdyn-7.png" />
 
@@ -3812,7 +3822,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 |INFO|Info|Info|
 
 </div>
-`,D=`---
+`,U=`---
 title: "SolarWinds Alert Events"
 description: "Sync SolarWinds alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3865,11 +3875,11 @@ Choose this option when you need to route alerts to different channels based on
 
 ## I. SolarWinds Alert Push Configuration
 
-### Step 1: Configure FlashDuty Alert Channel
+### Step 1: Configure Flashduty Alert Channel
 
 **Prerequisites**
 1. SolarWinds has five types of alerts (Anomaly, Entity, Event, Log, Metric Group), each requiring a different alert channel, so five alert channels need to be created
-2. When creating Webhook channels, it's recommended to name them using the format: Type_FlashDuty, for example: Anomaly_FlashDuty
+2. When creating Webhook channels, it's recommended to name them using the format: Type_Flashduty, for example: Anomaly_Flashduty
 3. When selecting **Select Custom Body Template Based On The Alert Types**, the system will generate a default **HTTP POST Body**. **Please do not modify the generated template content**
 
 **Getting Started**
@@ -3879,7 +3889,7 @@ Choose this option when you need to route alerts to different channels based on
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/sw-1.png" />
 
 3. Click \`CREATE CONFIGURATION\` to create the corresponding alert channel
-4. Select **POST** for \`Method\`, name it according to the prerequisites, e.g., Anomaly_FlashDuty
+4. Select **POST** for \`Method\`, name it according to the prerequisites, e.g., Anomaly_Flashduty
 5. Fill in the integration push URL in \`Destination URL\` (enter the integration name on the current page, save to generate the URL)
 6. Select **application/json** for \`Content Type\`
 7. Choose the type you need to create in \`Select Custom Body Template Based On The Alert Types\`, e.g., Anomaly Based Alert
@@ -3895,7 +3905,7 @@ Choose this option when you need to route alerts to different channels based on
 1. Find \`Alerts\` in the left navigation bar, select \`Alert Settings\`
 2. Create or edit existing policies (configure alert rules as needed, alert rule configuration is omitted here)
 3. In the \`Actions\` section of the policy configuration page, select **Webhook** for \`Services\`
-4. Select the Anomaly_FlashDuty channel created in Step 1 for \`Configuration\`
+4. Select the Anomaly_Flashduty channel created in Step 1 for \`Configuration\`
 5. Keep \`Send an additional notification when the Alert is cleared\` enabled
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/sw-4.png" />
@@ -3915,7 +3925,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,U=`---
+`,E=`---
 title: "Volcengine Cloud Monitor Alert Events"
 description: "Sync Volcengine Cloud Monitor alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3968,14 +3978,14 @@ Choose this method when you need to route alerts to different channels based on
 
 ## I. Volcengine Cloud Monitor Alert Push Configuration
 
-### Step 1: Create FlashDuty Alert Channel
+### Step 1: Create Flashduty Alert Channel
 1. Log in to your Volcengine console, search for \`Cloud Monitor\` product, and enter the corresponding product console
 2. Select \`Notification Groups=>Callback\` from the left navigation bar
 3. Click \`Create Callback URL\`
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/event-1.png" alt="drawing" width="500"/>
 
-4. Fill in the information on the edit page, enter \`FlashDuty_Metric\` as the callback URL name
+4. Fill in the information on the edit page, enter \`Flashduty_Metric\` as the callback URL name
 5. Select \`General Callback URL\` as the callback URL type
 6. Enter the **integration push URL** (enter the integration name on the current page, save to generate the URL)
 7. Click \`Confirm\` to complete the creation (connectivity testing is not supported; even if the test shows connectivity failure, it won't affect alert reception)
@@ -3988,7 +3998,7 @@ Choose this method when you need to route alerts to different channels based on
 2. Create or edit existing alert policies (configure policies as needed, skipped here)
 3. On the policy edit page, select \`Rules and Resources\` for \`Send Aggregation Policy\`
 4. Keep \`Alert Recovery Notification\` enabled
-5. Check \`Alert Callback\` in \`Alert Channels\`, and select the \`FlashDuty_Metric\` channel created in **Step 1** from the dropdown menu
+5. Check \`Alert Callback\` in \`Alert Channels\`, and select the \`Flashduty_Metric\` channel created in **Step 1** from the dropdown menu
 6. After completing other configurations, click \`Confirm\` to finish
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/event-3.png" alt="drawing" width="500"/>
@@ -4004,7 +4014,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,E=`---
+`,P=`---
 title: "Volcengine Cloud Monitor Event Center Alert Events"
 description: "Sync Volcengine Cloud Monitor Event Center alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4057,14 +4067,14 @@ Choose this method when you need to route alerts to different channels based on
 
 ## I. Volcengine Cloud Monitor Event Center Alert Push Configuration
 
-### Step 1: Create FlashDuty Alert Channel
+### Step 1: Create Flashduty Alert Channel
 1. Log in to your Volcengine console, search for \`Cloud Monitor\` product, and enter the corresponding product console
 2. Select \`Notification Groups=>Callback\` from the left navigation bar
 3. Click \`Create Callback URL\`
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/event-1.png" alt="drawing" width="500"/>
 
-4. Fill in the information on the edit page, enter \`FlashDuty_Event\` as the callback URL name
+4. Fill in the information on the edit page, enter \`Flashduty_Event\` as the callback URL name
 5. Select \`General Callback URL\` as the callback URL type
 6. Enter the **integration push URL** (enter the integration name on the current page, save to generate the URL)
 7. Click \`Confirm\` to complete the creation (connectivity testing is not supported; even if the test shows connectivity failure, it won't affect alert reception)
@@ -4075,7 +4085,7 @@ Choose this method when you need to route alerts to different channels based on
 
 1. Select \`Event Center=>Event Rules\` from the left navigation bar
 2. Create or edit existing event rules (configure rules as needed, skipped here)
-3. On the rule editing page, check \`Alert Callback\` under delivery channels, and select the \`FlashDuty_Event\` channel created in **Step 1** from the alert callback dropdown
+3. On the rule editing page, check \`Alert Callback\` under delivery channels, and select the \`Flashduty_Event\` channel created in **Step 1** from the alert callback dropdown
 4. After completing other configurations, click \`Confirm\` to finish
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/metric-3.png" alt="drawing" width="500"/>
@@ -4144,14 +4154,14 @@ Choose this method when you need to route alerts to different channels based on
 
 ## I. Volcengine Log Service (TLS) Alert Push Configuration
 
-### Step 1: Create FlashDuty Alert Channel
+### Step 1: Create Flashduty Alert Channel
 1. Log in to your Volcengine console, search for \`TLS\` Log Service product, and enter the corresponding product console
 2. Select \`Alert=>Notification Management\` from the left navigation bar
 3. Choose \`Webhook Alert Integration\` and click \`Create Webhook Alert Integration\`
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/tls-1.png" alt="drawing" width="500"/>
 
-4. Fill in the information in the pop-up editor, enter \`FlashDuty\` as the name
+4. Fill in the information in the pop-up editor, enter \`Flashduty\` as the name
 5. Select \`Custom Webhook\` as type and \`POST\` as request method
 6. Enter the **Integration Push URL** as the request URL (generated after saving the integration name on the current page)
 7. Keep the request headers as default and click \`Create\`
@@ -4162,7 +4172,7 @@ Choose this method when you need to route alerts to different channels based on
 
 1. Return to the \`Notification Management\` page
 2. Select \`Content Templates\` and click \`Create Content Template\`
-3. Fill in the relevant information, enter \`FlashDuty\` as the template name
+3. Fill in the relevant information, enter \`Flashduty\` as the template name
 4. Other channel content can be empty. In the \`Custom Webhook\` notification content, enter the following template:
 
 \`\`\`
@@ -4195,11 +4205,11 @@ Choose this method when you need to route alerts to different channels based on
 
 1. Return to the \`Notification Management\` page
 2. Select \`Notification Groups\` and click \`Create Notification Group\`
-3. Fill in the relevant information, enter \`FlashDuty\` as the group name
+3. Fill in the relevant information, enter \`Flashduty\` as the group name
 4. Configure notification rules and other settings as needed (skipped here)
 5. In notification channel configuration, keep \`Custom Webhook\` checked
-6. Select the **FlashDuty** channel created in **Step 1** for \`Webhook\`
-7. Select the **FlashDuty** template created in **Step 2** for \`Content Template\`
+6. Select the **Flashduty** channel created in **Step 1** for \`Webhook\`
+7. Select the **Flashduty** template created in **Step 2** for \`Content Template\`
 8. Click \`Save\` after completing other configurations
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/tls-4.png" alt="drawing" width="500"/>
@@ -4210,7 +4220,7 @@ Choose this method when you need to route alerts to different channels based on
 2. Create a new or edit an existing alert policy
 3. Configure alert rules as needed (skipped here)
 4. Click \`Associate Notification Group\` in the \`Notification Group\` section
-5. In the pop-up selection box, choose the **FlashDuty** notification group created in **Step 3**, then click \`Associate\`
+5. In the pop-up selection box, choose the **Flashduty** notification group created in **Step 3**, then click \`Associate\`
 6. Click \`Create/Save\` after configuring other settings
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/volcengine/tls-5.png" alt="drawing" width="500"/>
@@ -4228,7 +4238,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 </div>
-`,P=`---
+`,D=`---
 title: "OpManager Alert Events"
 description: "Sync OpManager alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4346,7 +4356,7 @@ Choose this method when you need to route alerts to different channels based on
 
 10. Select the devices you want to apply this configuration to, move them to the selected devices window using the right arrow, then click next
 11. Configure Time Window/Delayed Trigger/Recurring Trigger as needed, then click next
-12. Add the name \`FlashDuty\` for this configuration profile, then click \`Save\` to complete the setup
+12. Add the name \`Flashduty\` for this configuration profile, then click \`Save\` to complete the setup
 
 </dev>
 
@@ -4418,7 +4428,7 @@ Choose this option when you need to route alerts to different channels based on
 1. Log in to your \`Meraki\` console and select the device you want to configure alerts for
 2. On the \`Alerts\` page, configure \`Cellular gateway\` and other sections as needed
 3. Under \`Webhooks\`, configure \`HTTPS receivers\`
-4. Enter \`FlashDuty\` for \`Name\`, and enter the **integration push URL** for \`URL\`
+4. Enter \`Flashduty\` for \`Name\`, and enter the **integration push URL** for \`URL\`
 5. Leave \`Shared secret\` empty, and keep \`Payload template\` as the default \`Meraki(included)\`
 6. Click \`Save\` to save the settings
 
@@ -4443,7 +4453,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">
@@ -4586,7 +4596,7 @@ Choose this option when you need to route alerts to different channels based on
 
 1. Log in to your \`Guance\` console, select \`Alert Strategies\` under \`Monitoring\`
 2. Create new or modify existing alert policies on the \`Alert Strategies\` page
-3. In the notification configuration section of the alert strategies editing page, select \`severity\` and choose \`FlashDuty\` created in Step 1 as the \`Notification Tragets\`
+3. In the notification configuration section of the alert strategies editing page, select \`severity\` and choose \`Flashduty\` created in Step 1 as the \`Notification Tragets\`
 4. Configure other options as needed and click \`Save\` to complete
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/guance-2.png" />
@@ -4732,15 +4742,15 @@ When you need to route alerts to different channels based on alert payload infor
 
 ## I. Huawei Cloud APM Alert Push Configuration
 
-### Create FlashDuty Alert Channel
+### Create Flashduty Alert Channel
 
 1. Log in to your Huawei Cloud Console, search for \`SMN\` (Simple Message Notification) service and enter its console
 2. Select \`Topic Management=>Topics\` from the left navigation bar
-3. Click \`Create Topic\`, enter \`FlashDuty\` as the topic name in the edit page and confirm
+3. Click \`Create Topic\`, enter \`Flashduty\` as the topic name in the edit page and confirm
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-1.png" alt="drawing" width="500"/>
 
-4. Return to the topic list and click \`Add Subscription\` in the newly created FlashDuty topic
+4. Return to the topic list and click \`Add Subscription\` in the newly created Flashduty topic
 
 <img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-2.png" alt="drawing" width="500"/>
 
@@ -4756,7 +4766,7 @@ When you need to route alerts to different channels based on alert payload infor
 
 #### Step 1: Add Notification Configuration
 1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
-2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
+2. Select the corresponding region, click \`Add\`, and select the created \`Flashduty\` topic
 3. Click \`Confirm\` to complete the configuration
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
@@ -4766,7 +4776,7 @@ When you need to route alerts to different channels based on alert payload infor
 2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
 3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
 4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
-5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
+5. In \`Notification Object\`, select the created \`Flashduty\` notification channel
 6. Click \`Confirm\` to complete the configuration
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
@@ -4873,7 +4883,7 @@ Choose this method when you need to route alerts to different channels based on
 
 </div>
 
-`,j=`---
+`,H=`---
 title: "Keep Alert Integration Guide"
 description: "Push alert events to Flashduty through Keep's Provider to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -4954,7 +4964,7 @@ Field|Required|Type|Definition
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/keep-2.png" />
 
-`,H=`---
+`,j=`---
 title: "ElastAlert2 Alert Integration Guide"
 description: "Push alert events to Flashduty through ElastAlert2's Provider to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -5005,7 +5015,7 @@ Choose this method when you need to route alerts to different channels based on
 ---
 
 ### Configure ElastAlert 2 Alerts
-Follow the [ElastAlert FlashDuty](https://elastalert2.readthedocs.io/en/latest/alerts.html#flashduty) push configuration document
+Follow the [ElastAlert Flashduty](https://elastalert2.readthedocs.io/en/latest/alerts.html#flashduty) push configuration document
 
 1. Create or edit the alert rule file, for example \`rules/elastalert2_alert.yaml\`.
 2. Fill in the \`flashduty\` alert type in the \`alert\` field.
@@ -5057,7 +5067,7 @@ filter:
       query_string:
         query: "created_at:*"
 
-# ------- FlashDuty ----------------
+# ------- Flashduty ----------------
 alert: flashduty
 flashduty_integration_key: "xxxx"
 flashduty_title: "elastalert2 alert"
@@ -5072,7 +5082,7 @@ flashduty_group: "group1"
 flashduty_cluster: "bj"
 flashduty_app: "app1"
 flashduty_env: "dev"
-# ------- FlashDuty ----------------
+# ------- Flashduty ----------------
 \`\`\`
 
 5. Restart ElastAlert and wait for the alert to trigger.`,Y=`---
@@ -5156,7 +5166,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 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).
 `,z=`---
 title: "Feishu Alert Integration"
 description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
@@ -5238,7 +5248,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 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).
 `,B=`---
 title: "Volcengine Cloud-Detect Alert Events"
 description: "Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction"
@@ -5428,7 +5438,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>
 
@@ -5496,7 +5506,7 @@ By default, the system always creates new alerts for each message, but you can s
 **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 random to generate an Alert Key** to ensure alerts won't be lost due to configuration errors
+   - 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:
@@ -5507,186 +5517,921 @@ 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).`,Q=`---
-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."
+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"
+description: "Generate a unique Wecom robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Wecom"
 date: "2025-05-19T10:00:00+08:00"
-url: "https://docs.flashcat.cloud/en/flashduty/custom-change-integration-guide"
+url: "https://docs.flashcat.cloud/en/flashduty/Wecom-alert-integration-guide"
 ---
 
-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.
+Generate a unique Wecom robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Wecom.
 
-:::tips
-Flashduty has already adapted webhook protocols for several commonly used ticketing and deployment systems. For these systems, you should first use their corresponding integrations for simplicity. This integration provides a standard HTTP interface that requires development adaptation. The advantage is that you can integrate with any deployment system.
-:::
+<div class="hide">
 
-## Steps
+## Operation Steps
 ---
 
-### In Flashduty
-
-  1. Go to the Flashduty console, select **Integration Center=>Change Events** to enter the integration selection page.
-  2. Select **Custom Events** integration:
-        - **Integration Name**: Define a name for the current integration.
-  3. Click **Save** and copy the newly generated **push URL** for later use.
-  4. Done.
-
-
-## Implementation Protocol
---- 
-
-Please refer to the [Developer Documentation](https://developer-en.flashcat.cloud/en/flashduty/event-api/change-event) to complete the protocol development.
+### Create Wecom Alert Integration
 
-## Best Practices
----
+You can obtain a Wecom alert integration address through either of these two methods:
 
-Labels are descriptions of events. You should enrich label content as much as possible, such as:
-1. The scope of changes, like host, cluster, etc.
-1. Change ownership information, such as team, owner, etc.
+#### Using Dedicated Integration
 
-## FAQ
----
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
 
 <details>
-  <summary>Why haven't I received changes in Flashduty?</summary>
-
-  #### In Flashduty
+  <summary>Expand</summary>
   
-  1. Check if the integration shows **Latest Event Time**? If not, it means Flashduty hasn't received any pushes, prioritize checking your system first.
+  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 **Wecom Alert** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Wecom Alert Integration URL**, copy it for later use, and you're done
+    
+</details>
 
-  #### In Your System
+#### Using Shared Integration
 
-  1. Confirm that your request URL exactly matches the URL in the integration details.
-  2. Verify that your service can access the internet domain api.flashcat.cloud. If not, you need to enable internet access for your server or specifically allow access to Flashduty's domain.
-  3. Print the response from Flashduty service to check for any specific messages.
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
 
-  If you still can't identify the root cause after following these steps, please contact us with the **request_id** from the request response.
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
+  2. Select **Wecom Alert** integration:
+        - **Integration Name**: Define a name for the current integration
+        - **Message Type**: Select Wecom alert message type, currently only Text and Markdown are supported
+        - **Push Mode**: Choose when to trigger or recover alerts for Wecom notifications
+  3. Copy the **Wecom 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>
 
-`,X=`---
-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"
-url: "https://docs.flashcat.cloud/en/flashduty/jira-integration-guide"
----
-
-Synchronize Jira Issue events to Flashduty via webhooks to collect change events.
+### Customize Wecom Alert Integration
 
-## Limitations
----
+#### Wecom Alert Integration URL
 
-### In Jira
+The system will generate a unique Wecom alert integration URL for you. This URL is compatible with Wecom robot message protocol. When platforms only support Wecom robot channels, you can use this URL to receive corresponding messages.
 
-- You must have permission to modify **Settings=>System=>Webhooks**.
-- (For self-hosted deployments) Your Jira server must be able to access the domain api.flashcat.cloud.
+#### Push Mode
 
-## Supported Versions
----
+By default, the system always creates new alerts for each message, but you can switch to these modes:
 
-This guide is compatible with both **Jira Cloud and Self-hosted** versions.
+**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.
 
-## Setup Steps
----
+   - 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 random 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
 
-### In Flashduty
+   Configuration example:
 
-  1. Go to the Flashduty console, select **Integration Center=>Change Events** to enter the integration selection page.
-  2. Select **Jira** integration:
-        - **Integration Name**: Define a name for this integration.
-  3. Click **Save** and copy the newly generated **push URL** for later use.
-  4. Done.
+   - Receive all messages, close the alert when the message content contains **RESOLVED**, otherwise trigger a new alert
+   - Extract Alert Key from messages using the rule **/(.*)/**.
 
-### In Jira
 
-<div class="md-block">
+### 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/on-call/integration/alert-integration/alert-pipelines)"
 
-1. Log in to your Jira
-2. Go to **Settings=>System=>Webhooks** page, click the Create button
-3. Enter the callback URL as the push URL from your integration, and check Issue Created/Updated/Deleted event types
-4. Optionally, enter JQL to further narrow down the scope of events to sync (such as specific Projects)
-5. Click the Save button to submit the configuration
+## Severity Mapping
+---
 
-<img alt="drawing" src="http://download.flashcat.cloud/jira-webhook.png" />
+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).`,Q=`---
+title: "Harbor Alert Events"
+description: "Sync Harbor 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"
+---
 
-5. Done
+Sync Harbor alert events to Flashduty via webhook for automated alert noise reduction.
 
-</div>
+<div class="hide">
 
-## Status Mapping
+## In Flashduty
 ---
+You can obtain an integration push URL through either of these two methods:
 
-<div class="md-block">
+### 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>
   
-Flashduty extracts the status.name information from the webhook payload by default and converts the status according to the following mapping:
+  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 **Harbor** 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>
 
-| Jira        | Flashduty   | Status              |
-| ----------- | ---------- | ------------------- |
-| planned     | planned    | Created             |
-| to do       | planned    | Created             |
-| ready       | ready      | About to Start      |
-| processing  | processing | In Progress         |
-| open        | processing | In Progress         |
-| reopen      | processing | In Progress         |
-| in progress | processing | In Progress         |
-| canceled    | canceled   | Canceled/Rolled Back|
-| aborted     | canceled   | Canceled/Rolled Back|
-| done        | done       | Completed           |
-| resolved    | done       | Completed           |
-| closed      | done       | Completed           |
+### Using Shared Integration
 
-Please contact Flashduty if you wish to modify this mapping.
+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 **Harbor** 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>
-`,ee=`---
-title: "Feishu/Lark Integration"
-description: "By integrating a custom Feishu/Lark application, you can receive and respond to alerts within Feishu/Lark."
-date: "2025-05-19T10:00:00+08:00"
-url: "https://docs.flashcat.cloud/en/flashduty/lark-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
----
-By integrating a custom Feishu/Lark application, you can receive and respond to alerts within Feishu/Lark.
 
-## 1. Create Feishu/Lark application
+## In Harbor
 ---
 
-### 1. Create a custom application
-
-Visit [Feishu/Lark Developer Console](https://open.feishu.cn/app) and create an internal custom application. You can use the [official Flashduty icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the application icon.
-
-For details, see the Feishu/Lark development documentation [Create an internal custom application](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step1#132c1aac).
-
-![2025-09-17-19-20-33](https://docs-cdn.flashcat.cloud/images/png/9af11beec76ef03b935e5ba71ac2f5f5.png)
-### 2. Copy credential information
+### Configure Webhooks
 
-Go to the **Credentials and Basic Information** page and copy the \`App ID\` and \`App Secret\` for later use.
+1. Log in to the Harbor interface with an account that has at least project administrator privileges.
+2. Go to \`Projects\`, select a project, and select \`Webhooks\`.
+3. Select notify type \`HTTP\`, so the webhook will be send to a HTTP endpoint.
+4. Select payload format as \`Default or CloudEvents\` when choose the HTTP notify type.
+5. Select events that you want to subscribe.
+6. Enter the alert integration's <span class='integration_url'>PUSH URL</span> in the Endpoint URL field.
+7. Click Add to create the webhook.
 
+## Severity Mapping
+---
 
-![2025-09-17-19-24-11](https://docs-cdn.flashcat.cloud/images/png/9b72a772eaa94a7115e8568e9ae7b496.png)
+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).
 
-### 3. Copy the event callback Token information
+`,X=`---
+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"
+---
 
-Go to Development Configuration → Events & Callbacks → **Encryption Strategy** page, generate and copy the \`Encrypt Key\` (recommended for better security) and \`Verification Token\` for later use.
+Sync Volcengine RTC alert events to Flashduty via webhook for automated alert noise reduction.
 
-![2025-09-17-19-27-24](https://docs-cdn.flashcat.cloud/images/png/48d8ef62cef639cb433078c878c3a4a0.png)
+<div class="hide">
 
-## 2. Add Feishu/Lark integration
+## In Flashduty
 ---
+You can obtain an integration push URL through either of these two methods:
 
-Return to the Flashduty **Integration Center** page, select IM → **Feishu/Lark**, fill in the \`Name\` and the \`App ID\`, \`App Secret\`, \`Verification Token\`, and \`Encrypt Key\` copied in the previous step, then click **Save** to complete the creation.
+### Using Private Integration
 
-After successful creation, you will see the added Feishu/Lark integration in the list. Click its name to enter the details page, where you can view the **Web Configuration** address, **Redirect URL**, and **Message Card Request URL**, which will be used in subsequent steps.
+Choose this method when you don't need to route alert events to different channels - it's simpler.
 
-![2025-09-17-19-32-56](https://docs-cdn.flashcat.cloud/images/png/b4bfa3d7fdf1af9b8006be168d454700.png)
+<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>
 
-## 3. Configure Feishu/Lark application
----
+### Using Shared Integration
 
-### 1. Enable and configure application capabilities
+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-05-17-32-39](https://docs-cdn.flashcat.cloud/images/png/21908f6a040f61ad2e8091226874fe97.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).`,ee=`---
+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).`,ne=`---
+title: "Nagios Integration"
+description: "Synchronize Nagios alert events to Flashduty via script to achieve automated alert noise reduction"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/nagios-integration-guide"
+---
+
+Sync Nagios alert events to Flashduty via script to achieve 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 **Nagios** 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 **Nagios** 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 Nagios
+
+---
+
+Nagios installation paths may vary depending on the system and installation method. Please adjust the paths in the following configuration according to your actual environment.
+
+### Step 1: Download Notification Script
+
+<div class="md-block">
+
+Log in to the Nagios Server host and download the notification script to the Nagios plugin directory:
+
+- **Debian/Ubuntu systems** (typically \`/usr/lib/nagios/plugins/\`):
+
+\`\`\`bash
+cd /usr/lib/nagios/plugins/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/send_to_flashduty.sh
+chmod +x send_to_flashduty.sh
+\`\`\`
+
+- **RHEL/CentOS systems** (typically \`/usr/lib64/nagios/plugins/\`):
+
+\`\`\`bash
+cd /usr/lib64/nagios/plugins/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/send_to_flashduty.sh
+chmod +x send_to_flashduty.sh
+\`\`\`
+
+- **Source installation** (typically \`/usr/local/nagios/libexec/\`):
+
+\`\`\`bash
+cd /usr/local/nagios/libexec/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/send_to_flashduty.sh
+chmod +x send_to_flashduty.sh
+\`\`\`
+
+#### Note: The script uses the \`curl\` command. Please ensure curl is installed on your Nagios Server.
+
+</div>
+
+### Step 2: Create Flashduty Configuration File
+
+<div class="md-block">
+
+Download the Flashduty configuration file to the Nagios configuration directory:
+
+- **Debian/Ubuntu systems** (typically \`/etc/nagios3/conf.d/\`):
+
+\`\`\`bash
+cd /etc/nagios3/conf.d/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/flashduty.cfg
+\`\`\`
+
+- **RHEL/CentOS systems** (typically \`/etc/nagios/objects/\`):
+
+\`\`\`bash
+cd /etc/nagios/objects/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/flashduty.cfg
+\`\`\`
+
+- **Source installation** (typically \`/usr/local/nagios/etc/objects/\`):
+
+\`\`\`bash
+cd /usr/local/nagios/etc/objects/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/flashduty.cfg
+\`\`\`
+
+</div>
+
+### Step 3: Modify Configuration File
+
+<div class="md-block">
+
+Edit the downloaded \`flashduty.cfg\` file and modify the following:
+
+1. Replace the \`pager\` field value with the integration push URL obtained from the Flashduty console
+2. Modify the script path in \`command_line\` according to your Nagios installation path
+
+Configuration file example:
+
+\`\`\`
+define contact {
+    contact_name                    Flashduty
+    alias                           Flashduty Alert Receiver
+    service_notification_commands   notify-service-by-Flashduty
+    host_notification_commands      notify-host-by-Flashduty
+    service_notification_options    w,u,c,r
+    host_notification_options       d,u,r
+    service_notification_period     24x7   
+    host_notification_period        24x7   
+    pager                           <YOUR_FLASHDUTY_PUSH_URL>
+}
+
+
+define command {
+    command_name    notify-host-by-Flashduty
+    command_line    <NAGIOS_PLUGIN_PATH>/send_to_flashduty.sh type=HOST WEBHOOK_URL="$CONTACTPAGER$" hostname="$HOSTNAME$" state="$HOSTSTATE$" output="$HOSTOUTPUT$" notification_type="$NOTIFICATIONTYPE$" time="$LONGDATETIME$" host_address="$HOSTADDRESS$" host_alias="$HOSTALIAS$" check_command="$HOSTCHECKCOMMAND$"
+}
+
+define command {
+    command_name    notify-service-by-Flashduty
+    command_line    <NAGIOS_PLUGIN_PATH>/send_to_flashduty.sh type=SERVICE WEBHOOK_URL="$CONTACTPAGER$" hostname="$HOSTNAME$" state="$SERVICESTATE$" output="$SERVICEOUTPUT$" notification_type="$NOTIFICATIONTYPE$" time="$LONGDATETIME$" host_address="$HOSTADDRESS$" service_desc="$SERVICEDESC$" host_alias="$HOSTALIAS$" max_attempts="$MAXSERVICEATTEMPTS$" 
+}
+\`\`\`
+
+Parameter descriptions:
+- \`pager\`: Flashduty push URL, the integration push URL obtained from the Flashduty console
+- \`<NAGIOS_PLUGIN_PATH>\`: Replace with the actual script path, such as \`/usr/local/nagios/libexec\`
+- \`service_notification_options\`: Service alert notification options, w=warning, u=unknown, c=critical, r=recovery
+- \`host_notification_options\`: Host alert notification options, d=down, u=unreachable, r=recovery
+
+**To include additional information in alerts, you can append parameters in \`key=value\` format at the end of \`command_line\`, for example: \`environment="production" region="$_HOSTREGION$"\`. These parameters will be pushed to Flashduty as labels.**
+
+</div>
+
+### Step 4: Include Configuration File
+
+<div class="md-block">
+
+If you are using **RHEL/CentOS systems** or **source installation**, you need to include the Flashduty configuration file in the Nagios main configuration file.
+
+- **RHEL/CentOS systems**: Edit \`/etc/nagios/nagios.cfg\` and add:
+
+\`\`\`
+cfg_file=/etc/nagios/objects/flashduty.cfg
+\`\`\`
+
+- **Source installation**: Edit \`/usr/local/nagios/etc/nagios.cfg\` and add:
+
+\`\`\`
+cfg_file=/usr/local/nagios/etc/objects/flashduty.cfg
+\`\`\`
+
+:::tips
+Debian/Ubuntu systems typically auto-load all configuration files in the \`/etc/nagios3/conf.d/\` directory, so manual inclusion is not required.
+:::
+
+</div>
+
+### Step 5: Add Flashduty to Contact Group
+
+<div class="md-block">
+
+Edit the contacts configuration file to add the Flashduty contact to the \`admins\` contact group (or another contact group you use):
+
+- **Debian/Ubuntu systems**: Edit \`/etc/nagios3/conf.d/contacts_nagios2.cfg\`
+- **RHEL/CentOS systems**: Edit \`/etc/nagios/objects/contacts.cfg\`
+- **Source installation**: Edit \`/usr/local/nagios/etc/objects/contacts.cfg\`
+
+Find the contact group definition and add Flashduty to the members list:
+
+\`\`\`
+define contactgroup {
+    contactgroup_name       admins
+    alias                   Nagios Administrators
+    members                 nagiosadmin,Flashduty
+}
+\`\`\`
+
+</div>
+
+### Step 6: Verify Configuration and Restart Service
+
+<div class="md-block">
+
+1. Verify the Nagios configuration file:
+
+- **Debian/Ubuntu systems**:
+
+\`\`\`bash
+/usr/sbin/nagios3 -v /etc/nagios3/nagios.cfg
+\`\`\`
+
+- **RHEL/CentOS systems**:
+
+\`\`\`bash
+/usr/sbin/nagios -v /etc/nagios/nagios.cfg
+\`\`\`
+
+- **Source installation**:
+
+\`\`\`bash
+/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
+\`\`\`
+
+2. If verification passes, restart the Nagios service:
+
+\`\`\`bash
+# Debian/Ubuntu
+systemctl restart nagios3
+# or
+service nagios3 restart
+
+# RHEL/CentOS/Source installation
+systemctl restart nagios
+# or
+service nagios restart
+\`\`\`
+
+3. After configuration is complete, Nagios will automatically push alerts to Flashduty when detected
+
+</div>
+
+## Status Mapping
+
+---
+
+<div class="md-block">
+
+Nagios to Flashduty alert severity mapping:
+
+| Nagios          | Flashduty | Status   |
+| --------------- | --------- | -------- |
+| CRITICAL        | Critical  | Critical |
+| DOWN            | Critical  | Critical |
+| UNREACHABLE     | Critical  | Critical |
+| WARNING         | Warning   | Warning  |
+| OK              | Ok        | Recovered |
+| UP              | Ok        | Recovered |
+| UNKNOWN         | Info      | Info     |
+
+</div>
+`,te=`---
+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>
+`,ae=`---
+title: "Alibaba Cloud Monitor Prometheus"
+description: "Sync Alibaba Cloud Monitor Prometheus 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/aliyun-prometheus-integration-guide"
+---
+
+Sync Alibaba Cloud Monitor Prometheus 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 **Alibaba Cloud Monitor Prometheus** 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 **Alibaba Cloud Monitor Prometheus** 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 Alibaba Cloud
+---
+
+### Step 1: Create a Custom Webhook
+1. Login to your Alibaba Cloud console, search for \`Cloud Monitor\` product, and enter the corresponding product console.
+2. In the left menu, select \`Prometheus Monitoring->Notification Objects\`, and create or edit a \`Custom Webhook\`.
+3. On the edit page, enter \`Flashduty\` for both the name and identifier, and enter the <span class='integration_url'>push URL</span> for the alert integration in the \`URL\` field.
+4. In the \`Headers\` section, set **Header Key** to **Content-Type** and **Header Value** to **application/json**.
+5. Select **POST** for \`Method\` and **JSON** for \`Data Format\`.
+6. Click \`OK\` to complete the configuration.
+
+### Step 2: Configure Alert Rules
+1. Login to your Alibaba Cloud console, search for \`Cloud Monitor\` product, and enter the corresponding product console.
+2. In the left menu, select \`Prometheus Monitoring->Alert Rules\`, and create or edit an alert rule.
+3. In the **Notification Mode** section of the rule configuration page, select \`Simple Mode\`.
+4. For \`Notification Object\`, select the custom webhook created in **Step 1**.
+5. Click \`OK\` to complete the configuration.
+
+## Severity Mapping
+---
+<div class="md-block">
+
+Alibaba Cloud Prometheus to Flashduty severity mapping:
+
+| Alibaba Cloud Monitor | Flashduty | Status   |
+| --------------------- | --------- | -------- |
+| Critical              | Critical  | Critical |
+| Error                 | Critical  | Critical |
+| Warning               | Warning   | Warning  |
+| Normal                | Info      | Info     |
+
+</div>
+`,oe=`---
+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"
+url: "https://docs.flashcat.cloud/en/flashduty/custom-change-integration-guide"
+---
+
+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.
+
+:::tips
+Flashduty has already adapted webhook protocols for several commonly used ticketing and deployment systems. For these systems, you should first use their corresponding integrations for simplicity. This integration provides a standard HTTP interface that requires development adaptation. The advantage is that you can integrate with any deployment system.
+:::
+
+## Steps
+---
+
+### In Flashduty
+
+  1. Go to the Flashduty console, select **Integration Center=>Change Events** to enter the integration selection page.
+  2. Select **Custom Events** integration:
+        - **Integration Name**: Define a name for the current integration.
+  3. Click **Save** and copy the newly generated **push URL** for later use.
+  4. Done.
+
+
+## Implementation Protocol
+--- 
+
+Please refer to the [Developer Documentation](https://developer-en.flashcat.cloud/en/flashduty/event-api/change-event) to complete the protocol development.
+
+## Best Practices
+---
+
+Labels are descriptions of events. You should enrich label content as much as possible, such as:
+1. The scope of changes, like host, cluster, etc.
+1. Change ownership information, such as team, owner, etc.
+
+## FAQ
+---
+
+<details>
+  <summary>Why haven't I received changes in Flashduty?</summary>
+
+  #### In Flashduty
+  
+  1. Check if the integration shows **Latest Event Time**? If not, it means Flashduty hasn't received any pushes, prioritize checking your system first.
+
+  #### In Your System
+
+  1. Confirm that your request URL exactly matches the URL in the integration details.
+  2. Verify that your service can access the internet domain api.flashcat.cloud. If not, you need to enable internet access for your server or specifically allow access to Flashduty's domain.
+  3. Print the response from Flashduty service to check for any specific messages.
+
+  If you still can't identify the root cause after following these steps, please contact us with the **request_id** from the request response.
+    
+</details>
+
+`,ie=`---
+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"
+url: "https://docs.flashcat.cloud/en/flashduty/jira-integration-guide"
+---
+
+Synchronize Jira Issue events to Flashduty via webhooks to collect change events.
+
+## Limitations
+---
+
+### In Jira
+
+- You must have permission to modify **Settings=>System=>Webhooks**.
+- (For self-hosted deployments) Your Jira server must be able to access the domain api.flashcat.cloud.
+
+## Supported Versions
+---
+
+This guide is compatible with both **Jira Cloud and Self-hosted** versions.
+
+## Setup Steps
+---
+
+### In Flashduty
+
+  1. Go to the Flashduty console, select **Integration Center=>Change Events** to enter the integration selection page.
+  2. Select **Jira** integration:
+        - **Integration Name**: Define a name for this integration.
+  3. Click **Save** and copy the newly generated **push URL** for later use.
+  4. Done.
+
+### In Jira
+
+<div class="md-block">
+
+1. Log in to your Jira
+2. Go to **Settings=>System=>Webhooks** page, click the Create button
+3. Enter the callback URL as the push URL from your integration, and check Issue Created/Updated/Deleted event types
+4. Optionally, enter JQL to further narrow down the scope of events to sync (such as specific Projects)
+5. Click the Save button to submit the configuration
+
+<img alt="drawing" src="http://download.flashcat.cloud/jira-webhook.png" />
+
+5. Done
+
+</div>
+
+## Status Mapping
+---
+
+<div class="md-block">
+  
+Flashduty extracts the status.name information from the webhook payload by default and converts the status according to the following mapping:
+
+| Jira        | Flashduty   | Status              |
+| ----------- | ---------- | ------------------- |
+| planned     | planned    | Created             |
+| to do       | planned    | Created             |
+| ready       | ready      | About to Start      |
+| processing  | processing | In Progress         |
+| open        | processing | In Progress         |
+| reopen      | processing | In Progress         |
+| in progress | processing | In Progress         |
+| canceled    | canceled   | Canceled/Rolled Back|
+| aborted     | canceled   | Canceled/Rolled Back|
+| done        | done       | Completed           |
+| resolved    | done       | Completed           |
+| closed      | done       | Completed           |
+
+Please contact Flashduty if you wish to modify this mapping.
+
+</div>
+`,se=`---
+title: "Feishu/Lark Integration"
+description: "By integrating a custom Feishu/Lark application, you can receive and respond to alerts within Feishu/Lark."
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/lark-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+By integrating a custom Feishu/Lark application, you can receive and respond to alerts within Feishu/Lark.
+
+## 1. Create Feishu/Lark application
+---
+
+### 1. Create a custom application
+
+Visit [Feishu/Lark Developer Console](https://open.feishu.cn/app) and create an internal custom application. You can use the [official Flashduty icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the application icon.
+
+For details, see the Feishu/Lark development documentation [Create an internal custom application](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step1#132c1aac).
+
+![2025-09-17-19-20-33](https://docs-cdn.flashcat.cloud/images/png/9af11beec76ef03b935e5ba71ac2f5f5.png)
+### 2. Copy credential information
+
+Go to the **Credentials and Basic Information** page and copy the \`App ID\` and \`App Secret\` for later use.
+
+
+![2025-09-17-19-24-11](https://docs-cdn.flashcat.cloud/images/png/9b72a772eaa94a7115e8568e9ae7b496.png)
+
+### 3. Copy the event callback Token information
+
+Go to Development Configuration → Events & Callbacks → **Encryption Strategy** page, generate and copy the \`Encrypt Key\` (recommended for better security) and \`Verification Token\` for later use.
+
+![2025-09-17-19-27-24](https://docs-cdn.flashcat.cloud/images/png/48d8ef62cef639cb433078c878c3a4a0.png)
+
+## 2. Add Feishu/Lark integration
+---
+
+Return to the Flashduty **Integration Center** page, select IM → **Feishu/Lark**, fill in the \`Name\` and the \`App ID\`, \`App Secret\`, \`Verification Token\`, and \`Encrypt Key\` copied in the previous step, then click **Save** to complete the creation.
+
+After successful creation, you will see the added Feishu/Lark integration in the list. Click its name to enter the details page, where you can view the **Web Configuration** address, **Redirect URL**, and **Message Card Request URL**, which will be used in subsequent steps.
+
+![2025-09-17-19-32-56](https://docs-cdn.flashcat.cloud/images/png/b4bfa3d7fdf1af9b8006be168d454700.png)
+
+## 3. Configure Feishu/Lark application
+---
+
+### 1. Enable and configure application capabilities
 
 1. Return to the Feishu/Lark Developer Console, enter the created Feishu/Lark application, go to Add Application Capabilities → **Add by Capability** page, and enable both **Web Application** and **Bot** capabilities.
 
@@ -5726,7 +6471,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)
 
@@ -5789,7 +6535,8 @@ 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).`,ne=`---
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+`,re=`---
 title: "Dingtalk Integration"
 description: "By integrating a custom Dingtalk application, you can receive and respond to alerts within Dingtalk."
 date: "2025-05-19T10:00:00+08:00"
@@ -6012,7 +6759,7 @@ After the application is published, you can access it via the **mobile client**
    | Professional | 500,000 | 40 | 1st of each month |
    | Exclusive | 5,500,000 | 60 | 1st of each month |
 
-   > After exceeding the API call limit, the Dingtalk application will not be able to push messages normally. It is recommended to use notification channels reasonably. For details, see the [official Dingtalk documentation](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI).`,te=`---
+   > After exceeding the API call limit, the Dingtalk application will not be able to push messages normally. It is recommended to use notification channels reasonably. For details, see the [official Dingtalk documentation](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI).`,le=`---
 title: "WeCom Integration"
 description: "By integrating a WeCom application, you can receive and respond to alerts within WeCom."
 date: "2025-05-19T10:00:00+08:00"
@@ -6078,13 +6825,13 @@ This document supports both [integrating third-party applications](#third-party)
 
 6. On the application details page, obtain the \`Secret\` and fill it in the Flashduty integration configuration page.
 
-7. On the application details page, go to **Web Authorization and JS-SDK** page, click **Set Trusted Domain**, and configure **Callback domain for application OAuth 2.0 web authorization** as required.
+7. On the application details page, go to **Web Authorization and JS-SDK** page, click **Set Trusted Domain**.
 
    > The trusted domain needs to point to Flashduty's backend address \`{api_host}\` (can be achieved through CNAME or proxy forwarding).
    >
    > For trusted domain requirements, see the official WeCom documentation [《Internal Development Domain Configuration Guide》](https://open.work.weixin.qq.com/wwopen/common/readDocument/40754).
 
-   ![2025-09-18-13-08-43](https://docs-cdn.flashcat.cloud/images/png/8509e75449c933c3f750c93ce621e641.png)
+![2025-10-15-10-30-03](https://docs-cdn.flashcat.cloud/images/png/993ba70e9a13ee0256120b491dda007a.png)
 
    Return to the Flashduty integration configuration page, fill in this domain, and complete the verification.
 
@@ -6098,9 +6845,20 @@ This document supports both [integrating third-party applications](#third-party)
 
    ![2025-09-18-13-10-56](https://docs-cdn.flashcat.cloud/images/png/9a1bee272010ceaa38d2f39025215379.png)
 
-10. Company's Trusted IP : 47.94.95.118; 123.56.8.183; 47.94.193.81; 1.13.19.96
 
-   ![2025-09-19-11-06-36](https://docs-cdn.flashcat.cloud/images/png/0aa3c0129f7c99785ea77d088cd65774.png)
+10. Configure **Frontend Trusted Domain**
+
+   > The trusted domain needs to point to Flashduty's frontend address \`console.flashcat.cloud\` (can be implemented through CNAME or proxy forwarding).
+   >
+   > For requirements regarding trusted domains, please refer to the WeCom official documentation ['Enterprise Internal Development Domain Configuration Guide'](https://open.work.weixin.qq.com/wwopen/common/readDocument/40754).
+
+   After the frontend trusted domain verification passes, configure the generated **homepage address** to the WeCom application's **workbench application homepage**.
+
+   ![2025-10-14-19-52-19](https://docs-cdn.flashcat.cloud/images/png/cfd963b52a332082fc46ae12021ae73d.png)
+
+11. Configure **Trusted IP Address**: \`47.93.12.134\`
+
+   ![2025-10-14-20-28-20](https://docs-cdn.flashcat.cloud/images/png/d9c2184ba459bda0c3302e7634ccf48c.png)
 
 ## 3. Configure war room
 
@@ -6141,7 +6899,9 @@ After completing the previous steps, in the **Enhanced Features** module of the
 7. **Incident notification failed with prompt \`WeCom license not activated\`?**
    - Please contact Flashduty customer service or your dedicated technical support to purchase and activate the license for you.
 8. **Why is the war room feature not working as expected?**
-   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).`,ae=`---
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+9. **Why does it prompt "redirect_uri needs to use the application's trusted domain" when opening the app in the WeCom workspace?**
+   - Please confirm whether the domain in the \`redirect_uri\` parameter of the **App Homepage** URL has completed the domain ownership verification required by WeCom. For details, see the WeCom official documentation ['Enterprise Internal Development Domain Configuration Guide'](https://open.work.weixin.qq.com/wwopen/common/readDocument/40754).`,de=`---
 title: "Slack Integration"
 description: "By integrating the Slack third-party application, you can receive and respond to alerts within Slack."
 date: "2025-05-19T10:00:00+08:00"
@@ -6165,6 +6925,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
 
 ---
@@ -6195,7 +6957,8 @@ 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).`,ie=`---
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+`,ce=`---
 title: "Microsoft Teams Integration"
 description: "By integrating the Microsoft Teams third-party application, you can receive and respond to alerts within Microsoft Teams."
 date: "2025-05-19T10:00:00+08:00"
@@ -6213,10 +6976,10 @@ This step needs to be completed by a Microsoft Teams administrator.
 :::
 
 ### 1. Download application
-Download [FlashDutyBot-v1.0.3.zip](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/docs/FlashdutyBot-v1.0.3.zip) to your local device.
+Download [FlashdutyBot-v1.0.3.zip](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/docs/FlashdutyBot-v1.0.3.zip) to your local device.
 
 ### 2. Install application
-In Microsoft Teams, navigate to +Apps → Manage your apps → Upload an app → **Upload an app to your org's app catalog**, then upload the application package \`FlashDutyBot.zip\`.
+In Microsoft Teams, navigate to +Apps → Manage your apps → Upload an app → **Upload an app to your org's app catalog**, then upload the application package \`FlashdutyBot.zip\`.
 
 ![2025-09-18-13-48-04](https://docs-cdn.flashcat.cloud/images/png/bfa4afaf489c3582e858cad99eb76ae5.png)
 
@@ -6310,7 +7073,7 @@ Copy and send the command \`linkUser {}\` to the chat, then click **Link Now**.
 2. **How to view linked teams and users?**
    - Please go to Integration Center → IM → **Microsoft Teams** to view in **Linked Teams** and **Linked Users**.
 3. **How to cancel linked teams and users?**
-   - This feature is not currently supported.`,oe=`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.
+   - This feature is not currently supported.`,ue=`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>
 
@@ -6376,13 +7139,11 @@ email | string | Yes | Email address
 | alert_key | string | Yes | Alert correlation basis |
 | alert_severity | string | Yes | Severity level, enum: Critical, Warning, Info |
 | alert_status | string | Yes | Alert status, enum: Critical, Warning, Info, Ok |
-| progress | string | Yes | Processing progress, enum: Triggered, Closed |
 | created_at | int64 | Yes | Creation time |
 | updated_at | int64 | Yes | Update time |
 | start_time | int64 | Yes | First trigger time (time of first event received by platform), Unix timestamp in seconds |
 | last_time | int64 | Yes | Latest event time (time of most recent event received by platform), Unix timestamp in seconds |
 | end_time | int64 | No | Alert recovery time (time when platform last received end-type event), Unix timestamp in seconds, defaults to 0 |
-| close_time | int64 | No | Closure time, different from end_time, this indicates progress closure, not actual alert recovery. Unix timestamp in seconds, defaults to 0 |
 | labels | map[string]string | No | Label key-value pairs, both Key and Value are strings |
 | event_cnt | int64 | No | Number of associated events |
 | incident | [Incident](#Incident) | No | Associated incident |
@@ -6415,13 +7176,12 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
         "alert_status":"Warning",
         "channel_id":1163577812973,
         "channel_name":"Order System",
-        "close_time":0,
         "created_at":1683766015,
         "data_source_id":1571358104973,
         "data_source_name":"Aliyun SLS",
         "data_source_ref_id":"",
         "data_source_type":"aliyun-sls.alert",
-        "description":"Test alert trigger to FlashDuty",
+        "description":"Test alert trigger to Flashduty",
         "end_time":0,
         "event_cnt":1,
         "incident":{
@@ -6433,7 +7193,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
             "alert_type":"sls_alert",
             "alert_url":"https://sls.console.aliyun.com/lognext/project/sls-api-testing/alert/alert-1683548531-071659",
             "aliuid":"1082109605037616",
-            "check":"Test send to FlashDuty",
+            "check":"Test send to Flashduty",
             "fire_results":"{\\"_col0\\":\\"true\\"}",
             "fire_results_count":"1",
             "project":"sls-api-testing",
@@ -6443,9 +7203,8 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
             "severity":"6"
         },
         "last_time":1683809153,
-        "progress":"Triggered",
         "start_time":1683766013,
-        "title":"Test alert trigger to FlashDuty",
+        "title":"Test alert trigger to Flashduty",
         "title_rule":"$resource::$check",
         "updated_at":1683809170
     },
@@ -6464,11 +7223,14 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 
 1. **Is there a response timeout for the service?**
 
-   - The service must respond within 1 second, after which the response is considered failed
+   - Services must respond within 2 second, responses after 2 second are considered failed
 
 2. **Will failed pushes continue to be pushed?**
 
-   - Currently, FlashDuty pushes only once, though retry mechanisms may be introduced in the future. Retries may also occur due to middleware timeouts, so implement idempotent processing
+  For specific network errors, retries will be attempted up to a maximum of 1 times:
+    - context deadline exceeded (excluding cases involving "awaiting headers")
+    - i/o timeout
+    - eof
 
 3. **How is push order guaranteed?**
 
@@ -6478,7 +7240,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
-`,se=`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.
+`,he=`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>
 
@@ -6672,11 +7434,14 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 1. **Is there a response timeout for the service?**
 
-   - Services must respond within 1 second, responses after 1 second are considered failed
+   - Services must respond within 2 second, responses after 2 second are considered failed
 
 2. **Will failed pushes continue to be pushed?**
 
-   - Currently, FlashDuty pushes only once, though retry mechanisms may be introduced in the future. Retries may also occur due to middleware timeouts, so implement idempotent processing
+  For specific network errors, retries will be attempted up to a maximum of 1 times:
+    - context deadline exceeded (excluding cases involving "awaiting headers")
+    - i/o timeout
+    - eof
 
 3. **How is push order guaranteed?**
 
@@ -6685,11 +7450,11 @@ 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`,re=`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`,ge=`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
 
-1. Log in to the FlashDuty console and navigate to [Integration Center-Webhook]
+1. Log in to the Flashduty console and navigate to [Integration Center-Webhook]
 2. Click to add a Custom Action integration
 3. Configure the action name, which will appear as a button in the incident details
 4. Configure channels (multiple can be configured, but each channel can have up to three custom actions)
@@ -6782,13 +7547,11 @@ acknowledged_at | int64| No | Acknowledgment time
 | alert_key | string | Yes | Alert correlation basis |
 | alert_severity | string | Yes | Severity level, enum: Critical, Warning, Info |
 | alert_status | string | Yes | Alert status, enum: Critical, Warning, Info, Ok |
-| progress | string | Yes | Processing progress, enum: Triggered, Closed |
 | created_at | int64 | Yes | Creation time |
 | updated_at | int64 | Yes | Update time |
 | start_time | int64 | Yes | First trigger time (time of first event received by platform), Unix timestamp in seconds |
 | last_time | int64 | Yes | Latest event time (time of latest event received by platform), Unix timestamp in seconds |
 | end_time | int64 | No | Alert recovery time (time of last end-type event received by platform), Unix timestamp in seconds, default 0 |
-| close_time | int64 | No | Close time, different from end_time, this is processing progress closure, doesn't mean alert actually recovered. Unix timestamp in seconds, default 0 |
 | labels | map[string]string | No | Label KV pairs, both Key and Value are strings |
 
 </div>
@@ -6819,7 +7582,6 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
                 "alert_key": "asdflasdfl2xzasd112621",
                 "alert_severity": "Critical",
                 "alert_status": "Critical",
-                "close_time": 0,
                 "created_at": 1699869567,
                 "data_source_id": 2398086111504,
                 "description": "cpu.idle < 20%",
@@ -6835,10 +7597,6 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
                     "v": "v"
                 },
                 "last_time": 1699869562,
-                "progress": "Triggered",
-                "responder_email": "",
-                "responder_id": 0,
-                "responder_name": "",
                 "start_time": 1699869562,
                 "title": "nj / es.nj.01 - 自定义字段测试",
                 "title_rule": "$cluster::$resource::$check",
@@ -6924,7 +7682,7 @@ When host memory or CPU is maxed out, trigger host restart scripts for quick rec
 
 ### Information Enrichment
 
-When an incident occurs, callback to your service to retrieve Tracing, Logging, topology, and other information based on alert details. Actively call FlashDuty Open API to update incident information, such as adding labels or setting custom fields to assist troubleshooting.
+When an incident occurs, callback to your service to retrieve Tracing, Logging, topology, and other information based on alert details. Actively call Flashduty Open API to update incident information, such as adding labels or setting custom fields to assist troubleshooting.
 
 ### Rollback Changes
 
@@ -6932,7 +7690,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`,le=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,pe=`---
 title: "Jira Sync"
 description: "Sync incidents with Jira issues through Jira Sync Webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -7014,7 +7772,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.
-`,de=`---
+`,me=`---
 title: "ServiceNow Sync"
 description: "Sync incidents with ServiceNow Incidents through ServiceNow sync webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -7330,7 +8088,7 @@ Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
 <details>
   <summary>Getting 401 error when configuring integration</summary>
   A 401 error is generally caused by an incorrect password. Please check if the password is correct, or reset a new password (when setting the password, do not check the "Password needs reset" option).
-</details>`,ce=`---
+</details>`,fe=`---
 title: "ServiceDesk Plus Sync"
 description: "Sync incidents with ServiceDesk Plus requests through ServiceDesk Plus sync webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -7402,30 +8160,19 @@ Please select the corresponding API Endpoint and Accounts Server URL according t
     - Manual Trigger: Requires manual triggering of ServiceDesk Plus sync in the More Actions section of the incident details page (the integration configuration name is the trigger name).
 
 5. **Channel:** Select the channel where this integration takes effect.
-6. **Request Template:** Select the template to use when creating requests.
-7. **Severity Mapping:** The mapping relationship between Flashduty severity and ServiceDesk Plus priority. For default mapping relationship, please refer to [Priority Mapping](#priority-mapping).
+6. **Request Template:** Select the template to use when creating requests. If empty, the default template will be used to create the request.
+7. **Severity Mapping:** You can choose to map the values of severity, incident labels, or custom fields to the Priority field in ServiceDesk Plus. If empty, this field will not be passed when creating requests.
 8. **Custom Field Mapping:** You can map labels or custom fields in incidents to corresponding text fields in ServiceDesk Plus tickets to achieve automatic information filling. This feature supports syncing common context information (such as service name, instance address, metric name, etc.) to ServiceDesk Plus for subsequent troubleshooting and tracking.
     - Only supports target fields of single-line text or multi-line text type.
     - Supports extracting values from incident labels (such as service, instance) or custom attributes.
     - If the source field is empty, the target field will also remain empty and will not overwrite existing content.
-    - Mapping configuration is managed uniformly in integration settings without manual filling each time.
 
 9. **Assignee Mapping:** When Flashduty incidents are synced to ServiceDesk Plus and need to be automatically assigned to Technician or Group, you can get the value of Flashduty incident labels as the assignee (if the corresponding assignee does not exist, it will cause sync failure, please choose carefully).
-
-10. Click \`Save\` to complete the configuration.
+10. **Requester:** The requester to be specified when creating a request. This needs to be configured if the field is mandatory when creating requests.
+11. Click \`Save\` to complete the configuration.
 
 ### In ServiceDesk Plus
-#### Step 2 Create Requester
-When Flashduty incidents are synced to ServiceDesk Plus, the Requester automatically set by the system
-
-1. Log in to the ServiceDesk Plus console and find the \`Setup\` configuration page.
-2. Select \`Users & Permissions\`, then enter the \`Users\` creation page and select \`New Requester\`.
-3. Fill in **flashduty** for \`Name (Display Name)\` and \`First Name\`, fill in **flashduty-sync@flashcat.cloud** for \`Email\`.
-4. Other settings can be configured as needed, click \`Save\` to save the configuration.
-
-![2025-09-24-15-03-31](https://docs-cdn.flashcat.cloud/images/png/9ee174f85ac918476888efd759511d31.png)
-
-#### Step 3 Configure Sync <span id="configure-sync"></span>
+#### Step 2 Configure Sync <span id="configure-sync"></span>
 To achieve synchronization of ServiceDesk Plus requests to Flashduty, please refer to this configuration item. **Note:** Different versions may have slightly different paths, but the configuration method is the same.
 ##### Create Webhook
 1. Log in to the ServiceDesk Plus console and find the \`Setup\` configuration page.
@@ -7464,7 +8211,7 @@ To achieve synchronization of ServiceDesk Plus requests to Flashduty, please ref
 
 ![2025-09-23-13-32-32](https://docs-cdn.flashcat.cloud/images/png/94ca1d094ed38ebcaf299364eddfd0ac.png)
 
-##### Create Trigger
+##### Step 3 Create Trigger
 1. Log in to the ServiceDesk Plus console and find the \`Setup\` configuration page.
 2. Select \`Automation\`, then enter the \`Triggers\` page and select \`Request\`.
 3. Click \`New Trigger\`, fill in **to_Flashduty** for \`Name\` in the edit page.
@@ -7504,14 +8251,6 @@ To achieve synchronization of ServiceDesk Plus requests to Flashduty, please ref
 | Canceled    | CLosed     |                        |
 | Rejected    | CLosed     |                        |
 
-### Priority Mapping <span id="priority-mapping"></span>
-
-| ServiceDesk Plus | Flashduty | Notes |
-| ---------- | --------- | ----- |
-| Low        | Info      |       |
-| Medium     | Warning   |       |
-| High       | Critical  |       |
-
 
 ## FAQ
 
@@ -7519,7 +8258,7 @@ To achieve synchronization of ServiceDesk Plus requests to Flashduty, please ref
   <summary> Can the Scope be changed</summary>
   No, the Scope currently used is already the smallest unit. Flashduty needs to perform get/create/update operations when syncing requests with ServiceDesk Plus, and needs to obtain priority/custom field lists when configuring integration, so corresponding permission support is required.
 </details>
-`,he=`---
+`,ye=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -7653,10 +8392,8 @@ Title | string | Yes | Alert title
 Description | string | Yes | Alert description, can be empty
 AlertSeverity | string | Yes | Severity level, enum values: Critical, Warning, Info
 AlertStatus | string | Yes | Alert status, enum values: Critical, Warning, Info, Ok
-Progress | string | Yes | Processing progress, enum values: Triggered, Processing, Closed
 StartTime | int64 | Yes | Trigger time, Unix timestamp in seconds
 EndTime | int64 | No | Recovery time, Unix timestamp in seconds, default 0
-CloseTime | int64 | No | Close time, EndTime is alert recovery time, CloseTime is processing progress close time. Alert automatically closes upon recovery, manual closure doesn't affect alert recovery. Unix timestamp in seconds, default 0
 \`Labels\` | map[string]string | No | Label key-value pairs, both Key and Value are strings
 
 ## Common Questions
@@ -8078,7 +8815,8 @@ If you want to display only key label information, you can refer to the code seg
 \`\`\`
 </div>
 
-<div class="sms hide">
+<div class="feishu hide">
+
 
 ## Feishu/Lark Bot
 ---
@@ -8348,6 +9086,7 @@ Description：{{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
 Responders：{{range .Responders}}@{{.PersonName}} {{end}}{{end}}
 <br>Details：{{.DetailUrl}}
 \`\`\`
+
 </div>
 
 <div class="dingtalk hide">
@@ -8592,6 +9331,19 @@ You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Sever
 \`\`\`
 </div>
 
+
+<div class="voice hide">
+
+## Voice
+---
+If no custom content is set, the system default template will be used for notifications:
+
+\`\`\`go
+You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Severity: {{.IncidentSeverity}}{{if gt .AlertCnt 1}}, Grouped {{.AlertCnt}} alerts{{end}}
+\`\`\`
+</div>
+
+
 <div class="email hide">
 
 ## Email
@@ -8606,80 +9358,319 @@ If no custom content is set, the system default template will be used for notifi
 
   <head data-id="__react-email-head">
 	<style>
-	  .bg-Critical { background-color: #C80000; }
-	  .bg-Warning { background-color: #FA7D00; }
-	  .bg-Info { background-color: #FABE00; }
-	  .bg-Ok { background-color: rgb(132 204 22); }
-	  .text-Critical { color: #C80000; }
-	  .text-Warning { color: #FA7D00; }
-	  .text-Info { color: #FABE00; }
-	  .text-Ok { color: rgb(132 204 22); }
-	  .text-title {font-weight:500;width:6rem;flex-shrink:0}
-	  .text-content {color:rgb(55,65,81)}
+	  /* Light mode colors */
+	  :root {
+		--bg-color: rgb(255, 255, 255);
+		--text-color: rgb(55, 65, 81);
+		--label-key-color: #000;
+		--section-bg: rgb(255, 255, 255);
+		--border-color: rgb(229, 231, 235);
+	  }
+
+	  /* Dark mode colors */
+	  @media (prefers-color-scheme: dark) {
+		:root {
+		  --bg-color: rgb(31, 41, 55);
+		  --text-color: rgb(209, 213, 219);
+		  --label-key-color: rgb(229, 231, 235);
+		  --section-bg: rgb(17, 24, 39);
+		  --border-color: rgb(75, 85, 99);
+		}
+	  }
+
+	  /* Severity background colors */
+	  .severity-Critical { 
+		background-color: #C80000; 
+		color: #ffffff;
+		padding: 4px 12px;
+		border-radius: 12px;
+		display: inline-block;
+		font-weight: 600;
+		font-size: 13px;
+	  }
+	  .severity-Warning { 
+		background-color: #fef3c7;
+		color: #92400e;
+		padding: 4px 12px;
+		border-radius: 12px;
+		display: inline-block;
+		font-weight: 600;
+		font-size: 13px;
+	  }
+	  .severity-Info { 
+		background-color: rgb(108,83,177); 
+		color: #ffffff;
+		padding: 0.25rem 0.75rem;
+		border-radius: 0.25rem;
+		display: inline-block;
+		font-weight: 500;
+	  }
+	  .severity-Ok { 
+		background-color: rgb(132 204 22);  
+		color:rgb(100, 239, 73);
+		padding: 0.25rem 0.75rem;
+		border-radius: 0.25rem;
+		display: inline-block;
+		font-weight: 500;
+	  }
+
+	  /* Progress status colors */
+	  .progress-Triggered { 
+		background-color: #dbeafe;
+		color: #1e40af;
+		padding: 4px 12px;
+		border-radius: 12px;
+		display: inline-block;
+		font-weight: 600;
+		font-size: 13px;
+	  }
+	  .progress-Acknowledged { 
+		background-color: #ede9fe;
+		color: #6b21a8;
+		padding: 4px 12px;
+		border-radius: 12px;
+		display: inline-block;
+		font-weight: 600;
+		font-size: 13px;
+	  }
+	  .progress-Resolved { 
+		background-color: #d1fae5;
+		color: #065f46;
+		padding: 4px 12px;
+		border-radius: 12px;
+		display: inline-block;
+		font-weight: 600;
+		font-size: 13px;
+	  }
+	  .progress-Closed { 
+		background-color: #f3f4f6;
+		color: #374151;
+		padding: 4px 12px;
+		border-radius: 12px;
+		display: inline-block;
+		font-weight: 600;
+		font-size: 13px;
+	  }
+
+	  /* Field row styles */
+	  .field-row {
+		padding: 1rem 0;
+		border-bottom: 1px solid var(--border-color);
+	  }
+	  .field-row:first-child {
+		padding-top: 0;
+	  }
+	  .field-row:last-child {
+		border-bottom: none;
+	  }
+	  .field-label {
+		color: #6b7280;
+		font-size: 0.875rem;
+		margin-bottom: 0.25rem;
+	  }
+	  .field-value {
+		color: var(--text-color);
+		word-break: break-word;
+		overflow-wrap: break-word;
+	  }
+
+	  body {
+		background-color: var(--bg-color);
+		color: var(--text-color);
+	  }
+
+	  .labels-section {
+		background-color: #f3f4f6;
+		padding: 1rem;
+		border-radius: 0.375rem;
+		margin-top: 0.5rem;
+	  }
+	  @media (prefers-color-scheme: dark) {
+		.labels-section {
+		  background-color: rgb(55, 65, 81);
+		}
+	  }
 	</style>
   </head>
 
-  <body data-id="__react-email-body" style="background-color:rgb(255,255,255);border-radius:0.25rem;margin-top:2.5rem;margin-bottom:2.5rem;margin-left:auto;margin-right:auto;padding:1rem;min-width:400px;max-width:660px;font-family:ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica Neue, Arial, Noto Sans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol, Noto Color Emoji">
-	<div style="width:100%;height:0.375rem;margin-bottom:2rem" class="bg-{{.IncidentSeverity}}"></div>
-	<div style="display:flex;align-items:center;margin-bottom:1.5rem">
-	  <div style="display:flex;align-items:flex-end;gap:1rem"><img witdh="120" data-id="react-email-img" src="https://console.flashcat.cloud/image/saas-logo.png" height="40" style="display:block;outline:none;border:none;text-decoration:none" /><span style="font-size:1.25rem;line-height:1.75rem;font-weight:600">You have a pending incident</span></div>
-	</div>
-	<div style="background-color:rgb(243,244,246);padding:2rem;margin-top:1rem;border-radius:0.5rem">
-	  <div style="display:flex;flex-direction:column;gap:0.75rem">
-		<div style="display:flex">
-		  <div class="text-title">Title</div>
-		  <div class="text-content">{{.Title}}</div>
-		</div>
-		<div style="display:flex">
-		  <div class="text-title">Severity</div>
-		  <div class="text-{{.IncidentSeverity}}">{{.IncidentSeverity}}</div>
-		</div>
-		<div style="display:flex">
-		  <div class="text-title">Channel</div>
-		  <div class="text-content">{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}</div>
-		</div>
-		<div style="display:flex">
-		  <div class="text-title">Triggered at</div>
-		  <div class="text-content">{{date "2006-01-02 15:04:05" .StartTime}}</div>
-		</div>
-		{{if .CreatorID}}
-		<div style="display:flex">
-		  <div class="text-title">Creator</div>
-		  <div class="text-content">{{.Creator.PersonName}}</div>
-		</div>
-		{{end}}
-		{{if gt (len .Responders) 0}}
-		<div style="display:flex">
-		  <div class="text-title">Responders</div>
-		  <div class="text-content">{{range .Responders}}@{{.PersonName}} {{end}}</div>
-		</div>
-		{{end}}
-		<div style="display:flex">
-		  <div class="text-title">Progress</div>
-		  <div class="text-content">{{.Progress}}</div>
-		</div>
-		<div style="display:flex">
-		  <div class="text-title">Description</div>
-		  <div style="color:rgb(55,65,81);margin-top:0.125rem">
-			<div data-id="react-email-markdown">{{toHtml .Description}}</div>
-		  </div>
-		</div>
-		{{if .Labels.resource}}
-		<div style="display:flex;margin-bottom:0.5rem;">
-		  <div style="color:#000;font-weight:500;width:6rem;margin-right:1rem;">Alert targets</div>
-		  <div style="color:rgb(55,65,81);margin-top:0.125rem">
-			<div data-id="react-email-markdown">{{toHtml (joinAlertLabels . "resource" ", ")}}</div>
-		  </div>
-		</div>
-		{{end}}
-	  </div>
-	  <div style="display:flex;gap:1rem;margin-top:2rem"><a href="{{.DetailUrl}}?ack=1" data-id="react-email-button" target="_blank" style="line-height:100%;text-decoration:none;display:inline-block;max-width:100%;padding:0px 0px"><span></span><span style="max-width:100%;display:inline-block;line-height:120%;mso-padding-alt:0px;mso-text-raise:0"><div style="padding-left:2rem;padding-right:2rem;padding-top:0.5rem;padding-bottom:0.5rem;background-color:rgb(108,83,177);border-radius:0.25rem;font-size:1rem;line-height:1.5rem;color:rgb(255,255,255);font-weight:600;transition-property:color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter;transition-timing-function:cubic-bezier(0.4, 0, 0.2, 1);transition-duration:150ms">Acknowledge</div></span><span></span></a><a href="{{.DetailUrl}}" data-id="react-email-button" target="_blank" style="color:#61dafb;line-height:100%;text-decoration:none;display:inline-block;max-width:100%;padding:0px 0px"><span></span><span style="max-width:100%;display:inline-block;line-height:120%;mso-padding-alt:0px;mso-text-raise:0"><div style="padding-left:2rem;padding-right:2rem;padding-top:0.5rem;padding-bottom:0.5rem;background-color:rgb(255,255,255);border-width: 1px;border-style:solid;border-color:rgb(229,231,235);border-radius:0.25rem;font-size:1rem;line-height:1.5rem;color:rgb(0,0,0);font-weight:600">View Details</div></span><span></span></a></div>
-	</div>
-	<div style="display:flex;justify-content:flex-end;align-items:flex-end;margin-top:2rem">
-	  <div style="font-size:0.875rem;line-height:1.25rem;font-weight:500">ALL RIGHTS RESERVED © Beijing Flashcat Cloud Technology Co.,Ltd.</div>
-	</div>
+  <body data-id="__react-email-body" style="margin:0;padding:0;background-color:#f3f4f6;font-family:ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica Neue, Arial, Noto Sans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol, Noto Color Emoji">
+	<!-- Outer wrapper table for centering -->
+	<table width="100%" cellpadding="0" cellspacing="0" border="0" style="background-color:#f3f4f6">
+	  <tr>
+		<td align="center" style="padding:40px 20px">
+		  <!-- Main container table with fixed width -->
+		  <table width="600" cellpadding="0" cellspacing="0" border="0" style="background-color:#ffffff;max-width:600px">
+			<!-- Purple header bar with logo -->
+			<tr>
+			  <td style="padding:32px 0 32px 32px;text-align:left">
+				<img data-id="react-email-img" src="https://flashduty-public.oss-cn-beijing.aliyuncs.com/icons/flashduty-20251216.png" height="70" style="display:block;outline:none;border:none;text-decoration:none;height:70px;width:auto" alt="Flashduty" />
+			  </td>
+			</tr>
+			
+			<!-- Divider after logo -->
+			<tr>
+			  <td style="padding:0 32px">
+				<div style="border-top:1px solid #e5e7eb"></div>
+			  </td>
+			</tr>
+			
+			<!-- Main content -->
+			<tr>
+			  <td style="padding:16px 32px 32px 32px">
+				<!-- Title and Description -->
+				<table width="100%" cellpadding="0" cellspacing="0" border="0">
+				  <tr>
+					<td>
+					  <h1 style="margin:0;font-size:24px;font-weight:600;color:#111827;line-height:1.5">{{.Title}}</h1>
+					  {{if .Description}}
+					  <p style="margin:8px 0 0 0;font-size:16px;color:#6b7280;line-height:1.5">{{toHtml .Description}}</p>
+					  {{end}}
+					</td>
+				  </tr>
+				</table>
+				
+				<!-- Divider after title -->
+				<div style="border-top:1px solid #e5e7eb;margin:32px 0"></div>
+
+				<!-- Fields section -->
+				<table width="100%" cellpadding="0" cellspacing="0" border="0" style="margin-bottom:30px">
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Severity</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px"><span class="severity-{{.IncidentSeverity}}">{{.IncidentSeverity}}</span></td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Channel</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px">{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}</td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Triggered at</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px">{{date "2006-01-02 15:04:05" .StartTime}}</td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+
+				  {{if .CreatorID}}
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Creator</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px">{{.Creator.PersonName}}</td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+				  {{end}}
+
+				  {{if gt (len .Responders) 0}}
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Responders</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px">{{range .Responders}}@{{.PersonName}} {{end}}</td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+				  {{end}}
+
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Progress</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px"><span class="progress-{{.Progress}}">{{.Progress}}</span></td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+
+				  {{if .Labels.resource}}
+				  <tr>
+					<td style="padding:16px 0;border-bottom:1px solid #e5e7eb;background-color:#ffffff">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Resource</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px">{{(joinAlertLabels . "resource" ", ")}}</td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+				  {{end}}
+
+				  {{if gt (len .Labels) 0}}
+				  <tr>
+					<td style="padding:16px 0">
+					  <table width="100%" cellpadding="0" cellspacing="0" border="0">
+						<tr>
+						  <td width="120" style="font-weight:600;color:#374151;font-size:14px;vertical-align:top;padding-left:16px">Labels</td>
+						  <td style="color:#6b7280;font-size:14px;word-break:break-word;padding-right:16px;background-color:#f9fafb;padding:16px">
+							<pre style="margin:0;font-family:'Courier New',monospace;font-size:13px;color:#374151;white-space:pre-wrap;word-break:break-word">{{mustToPrettyJson .Labels}}</pre>
+						  </td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+				  {{end}}
+				</table>
+
+				<!-- Action buttons -->
+				<table width="100%" cellpadding="0" cellspacing="0" border="0" style="margin-top:32px">
+				  <tr>
+					<td width="48%" align="center" style="padding:0">
+					  <table cellpadding="0" cellspacing="0" border="0" style="width:100%">
+						<tr>
+						  <td align="center" style="background-color:rgb(108,83,177);border-radius:6px;padding:14px 32px">
+							<a href="{{.DetailUrl}}?ack=1" data-id="react-email-button" target="_blank" style="color:#ffffff;font-size:16px;font-weight:600;text-decoration:none;display:block">Acknowledge Now</a>
+						  </td>
+						</tr>
+					  </table>
+					</td>
+					<td width="4%" style="padding:0"></td>
+					<td width="48%" align="center" style="padding:0">
+					  <table cellpadding="0" cellspacing="0" border="0" style="width:100%">
+						<tr>
+						  <td align="center" style="background-color:#ffffff;border:2px solid rgb(108,83,177);border-radius:6px;padding:14px 32px">
+							<a href="{{.DetailUrl}}" data-id="react-email-button" target="_blank" style="color:rgb(108,83,177);font-size:16px;font-weight:600;text-decoration:none;display:block">View Details</a>
+						  </td>
+						</tr>
+					  </table>
+					</td>
+				  </tr>
+				</table>
+			  </td>
+			</tr>
+			
+			<!-- Footer -->
+			<tr>
+			  <td style="background-color:#f9fafb;padding:20px;text-align:center">
+				<p style="margin:0;font-size:12px;color:#9ca3af">ALL RIGHTS RESERVED © FLASHCAT.CLOUD</p>
+			  </td>
+			</tr>
+		  </table>
+		</td>
+	  </tr>
+	</table>
   </body>
-
 </html>
 \`\`\`
 
@@ -8687,7 +9678,7 @@ 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>`,ue=`---
+</div>`,be=`---
 title: "Link Integration"
 description: "Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information"
 date: "2025-05-19T10:00:00+08:00"
@@ -8744,4 +9735,208 @@ https://cmdb.com/vm?sn=VM123456
 1. When referenced content does not exist, Link integration will still generate the corresponding link but will not be able to retrieve the value
 2. Each channel can bind up to three Link integrations
 3. Pay attention to reference syntax; improper variable reference formatting will result in failure to retrieve corresponding values
-`,ge={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:F,Dynatrace:x,HuaweiyunLTS:L,GoogleCM:_,Zilliz:G,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:q,CustomChange:Q,Jira:X,Lark:ee,Dingtalk:ne,Wecom:te,Slack:ae,MicrosoftTeams:ie,AlertWebhook:oe,IncidentWebhook:se,CustomAction:re,Templates:he,HuaweiyunAPM:O,JiraSync:le,ZStack:$,Keep:j,ElastAlert2:H,DingtalkAlert:Y,FeishuAlert:z,VolcEngineDetect:B,Link:ue,ServiceNowSync:de,Monit:V,Rum:K,Cloudflare:J,WecomAlert:Z,ServiceDeskPlusSync:ce};module.exports=ge;
+`,ve=`Configure Label Mapping API to automatically call your external API when alert events arrive, enabling dynamic enrichment and correlation of alert information. With this feature, you can automatically attach information from external data sources such as CMDB, HR systems, and more to your alerts.
+
+## I. Overview
+
+The Label Mapping API allows you to build custom external services to enrich alert labels. The workflow is as follows:
+
+1. Flashduty receives an alert event
+2. The system sends event information and the list of expected labels to your API based on configuration
+3. Your API queries external data sources (such as CMDB, databases, etc.)
+4. The API returns the computed enrichment labels
+5. Flashduty attaches the returned labels to the alert
+
+<span id="ApiSpec"></span>
+
+## II. API Specification
+
+### Request Method
+
+<div class="md-block">
+
+POST, Content-Type:"application/json"
+
+</div>
+
+### Request Payload:
+
+<div class="md-block">
+
+| Field | Type | Required | Description |
+| :--------: | :-------------------: | :--: | :--------- |
+| result_label_keys | []string | Yes | List of expected label keys to return, configured by users in Flashduty |
+| event | [Event](#Event) | Yes | Complete information of the current alert event |
+
+<span id="Event"></span>
+**Event**:
+
+| Field | Type | Required | Description |
+| :--------: | :-------------------: | :--: | :--------- |
+| account_id | int64 | Yes | Account ID |
+| channel_id | int64 | Yes | Channel ID |
+| data_source_id | int64 | Yes | Data source ID |
+| data_source_type | string | Yes | Data source type, e.g., prometheus, zabbix, etc. |
+| title | string | Yes | Alert title |
+| title_rule | string | No | Title rule |
+| description | string | No | Alert description |
+| alert_key | string | Yes | Alert unique identifier |
+| alert_id | string | Yes | Alert ID |
+| event_severity | string | Yes | Event severity, enum: Critical, Warning, Info |
+| event_status | string | Yes | Event status, enum: Critical, Warning, Info, Ok |
+| event_time | int64 | Yes | Event time, Unix timestamp in seconds |
+| labels | map[string]string | No | Alert original label key-value pairs |
+| images | []string | No | List of alert-related images |
+
+</div>
+
+### Request Example
+
+<div class="md-block">
+
+\`\`\`json
+{
+  "result_label_keys": ["owner_team", "service_tier", "host_ip"],
+  "event": {
+    "account_id": 1,
+    "channel_id": 20,
+    "data_source_id": 15,
+    "data_source_type": "prometheus",
+    "description": "CPU usage for instance '10.0.1.101:9100' is over 95%",
+    "title": "High CPU Usage on instance 10.0.1.101:9100",
+    "title_rule": "",
+    "alert_key": "d41d8cd98f00b204e9800998ecf8427e",
+    "alert_id": "62d6c0f6b8f1b2b3c4d5e6f7",
+    "event_severity": "Critical",
+    "event_status": "Critical",
+    "event_time": 1678886400,
+    "labels": {
+      "region": "us-east-1",
+      "service": "service-A",
+      "env": "production",
+      "instance": "10.0.1.101:9100"
+    },
+    "images": []
+  }
+}
+\`\`\`
+
+</div>
+
+### Response Specification
+
+<div class="md-block">
+
+**Successful Response:**
+
+| Field | Type | Required | Description |
+| :--------: | :-------------------: | :--: | :--------- |
+| result_labels | map[string]string | Yes | Returned enrichment label key-value object |
+
+- HTTP Status Code: \`200 OK\`
+- Response body must be a JSON object containing the \`result_labels\` field
+- Keys in \`result_labels\` must be label names specified in the request's \`result_label_keys\`
+- If a label cannot be retrieved, it **should not** be included in the response
+
+**Successful Response Example:**
+
+\`\`\`json
+{
+  "result_labels": {
+    "owner_team": "team-database",
+    "service_tier": "tier-1",
+    "host_ip": "10.0.1.101"
+  }
+}
+\`\`\`
+
+**Failure Response:**
+
+| Status Code | Meaning |
+| :--------: | :--------- |
+| 404 Not Found | No data available for enrichment based on the event information |
+| 400 Bad Request | Request body format error or event object missing required fields |
+| 5xx | Unexpected internal API error (e.g., database connection failure) |
+
+> **Note:** Returning \`200 OK\` status code with an empty \`result_labels: {}\` object will also be treated as "no results", but using the \`404\` status code is the more standard approach.
+
+</div>
+
+<span id="ServiceConfig"></span>
+
+## III. Configure Mapping Service
+
+When configuring label mapping in Flashduty, you need to first create a mapping service, then reference that service in your label enrichment rules.
+
+### Mapping Service Field Description
+
+<div class="md-block">
+
+| Field | Type | Required | Description |
+| :--------: | :-------------------: | :--: | :--------- |
+| api_name | string | Yes | Human-readable service name for selection and reference in the UI, e.g., "CMDB Asset Query API" |
+| description | string | No | Detailed description of the service |
+| url | string | Yes | API request URL, supports template variables |
+| headers | map[string]string | No | HTTP request headers for passing custom authentication, subject to [security blacklist](#HeaderBlacklist) restrictions |
+| timeout | int | No | Request timeout (in seconds)，scope: 1~3 |
+| retry_count | int | No | Number of retries after request failure, ，scope: 0~1  |
+| insecure_skip_verify | bool | No | Skip certificate verification for HTTPS requests |
+| status | string | No | Service status, e.g., enabled, disabled |
+
+</div>
+
+### Label Enrichment Rule Configuration
+
+When configuring label enrichment rules, you only need to focus on the following settings:
+
+1. **result_label_keys**: Specify the list of labels you expect to retrieve from the API. Flashduty will automatically combine this list with the current \`event\` object into a request body and send it to your API
+2. **Mapping Service**: Select or configure the API service URL, Headers, and other information
+
+<span id="HeaderBlacklist"></span>
+
+## IV. Header Security Constraints
+
+To prevent security bypasses, request smuggling, IP spoofing, and cache poisoning, the following Headers are **prohibited** when customizing API request headers. The system gateway will automatically filter or reject requests containing these Headers.
+
+<div class="md-block">
+
+| Category | Blacklisted Headers | Risk Description |
+| :--- | :--- | :--- |
+| **Authentication & Authorization** | \`authorization\`, \`proxy-authorization\`, \`cookie\`, \`x-api-key\`, \`x-access-token\` | Prevents credential leakage or unauthorized hijacking of existing authentication contexts |
+| **IP & Geolocation Spoofing** | \`x-forwarded-for\`, \`x-real-ip\`, \`true-client-ip\`, \`x-client-ip\` | Prevents clients from spoofing source IP to bypass rate limits or allowlists/blocklists |
+| **Host & Routing Manipulation** | \`host\`, \`x-forwarded-host\`, \`x-forwarded-proto\`, \`x-internal-id\`, \`x-user-id\` | Prevents Host injection attacks, redirect loops, or spoofing internal system IDs |
+| **Protocol & Request Smuggling** | \`transfer-encoding\`, \`upgrade\`, \`connection\` | Prevents request smuggling attacks exploiting HTTP protocol differences |
+
+</div>
+
+### Header Best Practices
+
+1. **Allowlist Mode**: It is recommended to only allow custom Headers prefixed with \`X-Custom-\` or \`X-Enrich-\`
+2. **Length Limits**: The Key length of a single Header should not exceed 1024 bytes, the Value length of a single Header should not exceed 4096 bytes
+3. **Format Validation**: Header Values must not contain line breaks (\`\\r\`, \`\\n\`) to prevent Header injection attacks
+
+## V. Best Practices
+
+1. **Performance First:** This API is on the critical path of alert processing and must ensure low latency. Queries to external data sources should be as fast as possible, and implementing caching is recommended.
+
+2. **Clear Error Handling:** Make good use of HTTP status codes (especially \`404\`) to convey clear execution results.
+
+3. **Idempotency:** The API design should be as idempotent as possible. Multiple calls for the same \`event\` should return the same result.
+
+4. **Security:** The API must be protected through authentication and authorization mechanisms. Using custom Headers (e.g., \`X-Custom-Auth\`) for passing authentication information is recommended.
+
+## VI. FAQ
+
+1. **Is there a response timeout for the service?**
+
+   - The service must respond within the configured timeout period; exceeding this is considered a failure
+
+2. **What happens if the API returns a failure?**
+
+   - The alert will be processed normally, but no enrichment labels will be attached
+   - Based on the configured retry count, the system may retry the request
+
+3. **Can result_label_keys be changed dynamically?**
+
+   - Yes, you can modify the list of expected labels in Flashduty at any time without modifying the API code
+`,we={CustomAlert:n,Email:t,N9e:a,Prometheus:o,Grafana:i,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:u,BaiDuBCM:h,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:b,TencentCm:v,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:F,HuaweiyunLTS:_,GoogleCM:R,Zilliz:G,Splunk:L,AppDynamics:T,SolarWinds:U,VolcEngineMetric:E,VolcEngineEvent:P,VolcEngineTLS:N,OpManager:D,Meraki:M,StateCloud:W,Guance:q,CustomChange:oe,Jira:ie,Lark:se,Dingtalk:re,Wecom:le,Slack:de,MicrosoftTeams:ce,AlertWebhook:ue,IncidentWebhook:he,CustomAction:ge,Templates:ye,HuaweiyunAPM:O,JiraSync:pe,ZStack:$,Keep:H,ElastAlert2:j,DingtalkAlert:Y,FeishuAlert:z,VolcEngineDetect:B,Link:be,ServiceNowSync:me,Monit:V,Rum:K,Cloudflare:J,WecomAlert:Z,ServiceDeskPlusSync:fe,Harbor:Q,LabelMappingAPI:ve,VolcEngineRTC:X,UcloudCloudWatch:ee,Nagios:ne,JDCloudMonitor:te,AliyunPrometheus:ae};module.exports=we;