npm - flashduty-knowledge-base - Versions diffs - 1.2.5 → 1.2.6 - Mend

flashduty-knowledge-base 1.2.5 → 1.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

package/dist/esm/en.js CHANGED Viewed

@@ -8,7 +8,7 @@ url: "https://docs.flashcat.cloud/en/flashduty/custom-alert-integration-guide"
 Push alert events from your own system to Flashduty through standard protocols to achieve automated alert noise reduction.
 :::tips
-Flashduty has already adapted webhook protocols for most common alert systems. For these systems, you should first use the corresponding integration for simplicity. This integration provides a standard HTTP interface that requires your development for adaptation. The advantage is that you can push any alert events you want to handle through on-call.
+Flashduty has already adapted webhook protocols for most common alert systems. For these systems, you should first use the corresponding integration for simplicity. This integration provides a standard HTTP interface that requires your development for adaptation. The advantage is that you can push any alert events you want to handle through On-call.
 :::
 ## Steps
@@ -42,9 +42,9 @@ When you need to route alert events to different collaboration spaces based on t
   1. Enter the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
   2. Select **Standard Alert Event** integration:
         - **Integration Name**: Define a name for the current integration
-  3. Click **Save** and copy the newly generated **Push URL** on the current page for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different collaboration spaces based on conditions, or set a default collaboration space as a fallback, and adjust as needed later
-  5. Complete
+  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>
@@ -213,7 +213,7 @@ Failed Response:
 </details> `,t=`---
 title: "Email Integration"
 description: "Generate a unique email address in Flashduty to synchronize alert triggers and recoveries through email"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/email-integration-guide"
 ---
@@ -255,8 +255,8 @@ Choose this option when you need to route alerts to different channels based on
         - **Email Address**: Set an easy-to-remember prefix for the email, which must be unique within your account
         - **Push Mode**: Choose when the email should trigger or recover alerts
   3. Copy the **Email Address** from the current page for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
-  5. Complete
+  4. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  5. Done
 </details>
 </div>
@@ -312,14 +312,18 @@ attachment_stripped = true
 Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
 `,a=`---
-title: "Nightingale/FlashCat Integration"
+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"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/nightingale-integration-guide"
 ---
 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.
+In the Nightingale/Flashcat v8.0.0-beta.7+ version, you can configure the collaboration space in the alert notification rules, no longer need to use routing rules.
+- [v8.0.0-beta.7 +](#v8)
+- [v5~v8.0.0-beta.6](#v7)
 <div class="hide">
 ## Prerequisites
@@ -368,16 +372,50 @@ Choose this method when you need to route alert events to different channels bas
   2. Select **Nightingale/Flashcat** integration:
         - **Integration Name**: Define a name for the current integration
         - **Console URL**: (Optional) Enter the Nightingale console URL (domain part only), and Flashduty will generate a Nightingale details link for new alerts
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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. Complete
 </details>
 </div>
-### In Nightingale/Flashcat
+## In Nightingale/Flashcat
+### Configure in Nightingale/Flashcat v8.0.0-beta.7 + <span id="v8"></span>
+In the new version, although you can configure the collaboration space directly in the alert notification rules, you still need to create a collaboration space in Flashduty and configure the dispatch strategy.
+#### 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
+3. Click **Save** and complete
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/n9e-1.png" />
+#### Step 2: Configure Notification Rules
+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
+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
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/n9e-2.png" />
+#### 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
+3. Click **Save** and complete
-Choose either of these two configuration methods.
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/n9e-3.png" />
+### Configure in Nightingale/Flashcat v5~v8.0.0-beta.6 <span id="v7"></span>
+Choose one of the following two methods:
 #### Method 1: Configure by Strategy
@@ -472,7 +510,7 @@ Nightingale/Flashcat to Flashduty alert severity mapping:
 `,i=`---
 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: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/prometheus-integration-guide"
 ---
@@ -524,8 +562,8 @@ Choose this method when you need to route alert events to different channels bas
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Prometheus** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -654,7 +692,7 @@ Prometheus to Flashduty severity mapping:
 `,o=`---
 title: "Grafana Integration"
 description: "Sync Grafana alert events to Flashduty via webhook to achieve automated alert noise reduction."
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/grafana-integration-guide"
 ---
@@ -690,9 +728,9 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Grafana** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
-  5. Complete
+  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>
@@ -767,7 +805,7 @@ The system extracts the \`severity\`, \`priority\`, and \`level\` labels from al
 `,s=`---
 title: "Zabbix Integration"
 description: "Synchronize Zabbix alert events to Flashduty via webhook (supports Zabbix 3.x ~ 6.x versions, with different configuration requirements) to achieve automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/zabbix-integration-guide"
 ---
@@ -776,7 +814,9 @@ Synchronize Zabbix alert events to Flashduty via webhook (supports Zabbix 3.x ~
 <div class="hide">
 ## In Flashduty
 ---
 You can obtain an integration push URL through either of these two methods:
 ### Using Private Integration
@@ -803,14 +843,15 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
   2. Select **Zabbix** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
-  5. Complete
+  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 Zabbix
+## In Zabbix
 ---
 - [7.x version](#v7)
@@ -822,6 +863,7 @@ Choose this method when you need to route alerts to different channels based on
 ### Version 7.x
 #### Step 1: Define Flashduty Media Type
 <div class="md-block">
 1. Media type is a transport channel used for sending notifications and alerts in Zabbix. Enter the terminal and download the complete configuration using the following command:
@@ -830,6 +872,7 @@ Choose this method when you need to route alerts to different channels based on
 wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/zabbix/zbx_mediatype_flashcat_v7.yml
 \`\`\`
 2. Log in to the Zabbix console, select \`Alert > Media Types\`, click the Import button in the top right corner, enter the editing page, select the configuration file downloaded above, and click Import to complete the import
 3. Return to the Media Types page to see the imported media type. Click the name to enter the editing page, complete the URL, zabbix_url, and HTTPProxy content:
@@ -841,7 +884,6 @@ wget --header="Referer: https://console.flashcat.cloud" https://download.flashca
 4. Click Update to save the configuration
 #### Step 2: Associate Media Type with User
 The media type must be associated with a user to send events. The user must have at least read permission for hosts. It is recommended to associate directly with the Admin user. Taking the Admin user as an example:
@@ -857,7 +899,6 @@ The media type must be associated with a user to send events. The user must have
 2. Click Add button to exit the add media window
 3. Click Update button to exit the edit user page
 #### Step 3: Create Action
 Sending notifications is one of the operations executed by actions in Zabbix. Therefore, to establish a notification, log in to the Zabbix console, select \`Alerts > Actions > Trigger actions\`, then:
@@ -878,7 +919,6 @@ Sending notifications is one of the operations executed by actions in Zabbix. Th
    <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zabbix-5.png" />
    <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zabbix-4.png" />
 #### Step 4: Send Events to Flashduty
 Log in to the Zabbix console, select \`Monitoring > Problems\` to view the latest alert list.
@@ -1062,18 +1102,19 @@ Log in to the Zabbix console, select Monitoring > Problems to view the latest al
 Zabbix to Flashduty alert severity mapping:
 | Zabbix         | Flashduty | Status   |
-| -------------- | -------------- | -------- |
-| Disaster       | Critical       | Critical |
-| High           | Critical       | Critical |
-| Average        | Warning        | Warning  |
-| Warning        | Warning        | Warning  |
-| Information    | Info           | Info     |
-| Not classified | Info           | Info     |
-</dv>`,r=`---
+| -------------- | --------- | -------- |
+| Disaster       | Critical  | Critical |
+| High           | Critical  | Critical |
+| Average        | Warning   | Warning  |
+| Warning        | Warning   | Warning  |
+| Information    | Info      | Info     |
+| Not classified | Info      | Info     |
+</dv>
+`,r=`---
 title: "Uptime Kuma Integration"
 description: "Sync Uptime Kuma alert events to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/uptime-kuma-integration-guide"
 ---
@@ -1109,9 +1150,9 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Uptime Kuma** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
-  5. Complete
+  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>
@@ -1159,7 +1200,7 @@ Uptime Kuma to Flashduty alert severity mapping:
 </div>`,l=`---
 title: "Alibaba Cloud ARMS Integration"
 description: "Sync Alibaba Cloud ARMS monitoring alerts to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/aliyun-arms-integration-guide"
 ---
@@ -1195,9 +1236,9 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Alibaba Cloud ARMS** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
-  5. Complete
+  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>
@@ -1245,7 +1286,7 @@ Alibaba Cloud ARMS monitoring to Flashduty alert severity mapping:
 `,d=`---
 title: "Alibaba Cloud Monitor CM Event Integration"
 description: "Sync Alibaba Cloud Monitor event center alerts to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/aliyun-cm-event-integration-guide"
 ---
@@ -1281,9 +1322,9 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Alibaba Cloud CM Event** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
-  5. Complete
+  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>
@@ -1332,7 +1373,7 @@ Alibaba Cloud Monitor event alert to Flashduty severity level mapping:
 </div>`,c=`---
 title: "Alibaba Cloud Monitor CM Metrics Integration"
 description: "Sync Alibaba Cloud Monitor alert events to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/aliyun-cm-metric-integration-guide"
 ---
@@ -1368,9 +1409,9 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Alibaba Cloud CM Metrics** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
-  5. Complete
+  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>
@@ -1430,7 +1471,7 @@ Severity level mapping from Alibaba Cloud Monitor to Flashduty:
 `,e=`---
 title: "Alibaba Cloud SLS Integration"
 description: "Sync Alibaba Cloud Log Service (SLS) monitoring alert events to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/aliyun-sls-integration-guide"
 ---
@@ -1466,9 +1507,9 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Alibaba Cloud SLS** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
-  5. Complete
+  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>
@@ -1557,7 +1598,7 @@ Alibaba Cloud SLS monitoring to Flashduty alert severity mapping:
 `,h=`---
 title: "AWS CloudWatch Integration"
 description: "Sync AWS CloudWatch alert events to Flashduty via webhook to achieve automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/aws-cloudwatch-integration-guide"
 ---
@@ -1593,9 +1634,9 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **AWS CloudWatch** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
-  5. Complete
+  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>
@@ -1636,7 +1677,7 @@ All CloudWatch metric alarms correspond to Flashduty "warning" severity level al
 `,u=`---
 title: "Baidu Cloud BCM Integration"
 description: "Sync Baidu Cloud BCM alerts to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/baidu-bcm-integration-guide"
 ---
@@ -1672,8 +1713,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Baidu Cloud BCM** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -1711,7 +1752,7 @@ Severity level mapping from Baidu Cloud Monitor to Flashduty:
 `,g=`---
 title: "Huawei Cloud CES Integration"
 description: "Sync Huawei Cloud CES alerts to Flashduty via webhook to achieve automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/huawei-ces-integration-guide"
 ---
@@ -1747,8 +1788,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Huawei Cloud CES** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -1829,8 +1870,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Influxdata** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -1897,7 +1938,7 @@ Mapping relationship between Influxdata alert events and Flashduty alert severit
 `,m=`---
 title: "Open Falcon Integration"
 description: "Sync Open-Falcon alert events to Flashduty via webhook to achieve automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/open-falcon-integration-guide"
 ---
@@ -1933,8 +1974,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Falcon** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -1981,7 +2022,7 @@ Open-Falcon to Flashduty alert severity mapping:
 `,f=`---
 title: "PagerDuty Integration"
 description: "Push alert events to Flashduty through PagerDuty protocol for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/pagerduty-integration-guide"
 ---
@@ -2021,8 +2062,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **PagerDuty** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -2143,7 +2184,7 @@ pagerduty_v2_payload_source: mysql.host.name
 `,y=`---
 title: "Tencent BlueKing Integration"
 description: "Sync Tencent BlueKing monitoring events to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/tencent-bk-integration-guide"
 ---
@@ -2179,8 +2220,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Tencent BlueKing** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -2241,7 +2282,7 @@ Alert severity mapping between BlueKing and Flashduty:
 `,v=`---
 title: "Tencent Cloud CLS Integration"
 description: "Sync Tencent Cloud Log Service (CLS) monitoring alerts to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/tencent-cls-integration-guide"
 ---
@@ -2277,8 +2318,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Tencent Cloud CLS** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -2383,7 +2424,7 @@ Tencent Cloud CLS monitoring alert level mapping to Flashduty:
 `,b=`---
 title: "Tencent Cloud Monitor CM Integration"
 description: "Sync Tencent Cloud Monitor CM alert events to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/tencent-cm-integration-guide"
 ---
@@ -2419,8 +2460,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Tencent Cloud Monitor CM** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -2456,7 +2497,7 @@ All metric alerts from Tencent Cloud Monitor correspond to "warning" severity le
 `,w=`---
 title: "Tencent Cloud EventBridge"
 description: "Sync Tencent Cloud EventBridge events to Flashduty via webhook for automated alert noise reduction"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/tencent-event-bridge-integration-guide"
 ---
@@ -2492,8 +2533,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center => Alerts** to enter the integration selection page
   2. Select **Tencent Cloud EventBridge** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -2584,8 +2625,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **OceanBase** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -2772,8 +2813,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Graylog** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -2867,8 +2908,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Skywalking** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -2882,11 +2923,11 @@ Choose this method when you need to route alerts to different channels based on
 1. Log in to the Skywalking server
 2. Locate the Skywalking configuration file ./config/alarm-settings.yml
-3. Add Level tags to the alert rules
+3. Add level tags to the alert rules
 \`\`\`
 # Tags are supported in v8.6.0+ versions only, can be omitted for other versions
-# Level values: Critical, Warning, Info
+# level values: Critical, Warning, Info
 # Case sensitive
 rules:
     endpoint_relation_resp_time_rule:
@@ -2894,7 +2935,7 @@ rules:
         period: 10
         message: Response time of endpoint relation {name} is more than 1000ms in 2 minutes of last 10 minutes
         tags:
-            Level: Warning
+            level: Warning
 \`\`\`
 4. Add the FlashDuty webhook URL
@@ -2966,8 +3007,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Sentry** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -3072,8 +3113,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Jiankongbao** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -3124,7 +3165,7 @@ Choose this option when you need to route alerts to different channels based on
 |2|Info|Info|
 </div>
-`,L=`---
+`,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"
@@ -3163,8 +3204,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **AWS EventBridge** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -3265,8 +3306,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Dynatrace** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -3333,7 +3374,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 </div>
-`,F=`---
+`,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"
@@ -3372,8 +3413,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Huawei Cloud LTS** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -3446,7 +3487,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 </div>
-`,x=`---
+`,F=`---
 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"
@@ -3485,8 +3526,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
   2. Select **Google Cloud Monitoring** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -3576,8 +3617,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Splunk** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -3651,8 +3692,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alerts**, and enter the integration selection page
   2. Select **AppDynamics** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **Push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -3772,7 +3813,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 |INFO|Info|Info|
 </div>
-`,U=`---
+`,D=`---
 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"
@@ -3811,8 +3852,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **SolarWinds** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -3875,7 +3916,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 </div>
-`,E=`---
+`,U=`---
 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"
@@ -3914,8 +3955,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Volcengine CM Metrics** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -3964,7 +4005,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 </div>
-`,D=`---
+`,E=`---
 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"
@@ -4003,8 +4044,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Volcengine CM Metrics** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -4051,7 +4092,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 </div>
-`,P=`---
+`,N=`---
 title: "Volcengine Log Service (TLS) Alert Events"
 description: "Sync Volcengine Log Service (TLS) alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4090,8 +4131,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Volcengine TLS** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **Push URL** for later use
-  4. Click **Create Route** to configure routing rules. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -4188,7 +4229,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 </div>
-`,N=`---
+`,P=`---
 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"
@@ -4227,8 +4268,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **OpManager** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -4361,8 +4402,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Meraki** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -4436,8 +4477,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **StateCloud** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -4520,8 +4561,8 @@ Choose this option when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Guance** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -4566,7 +4607,7 @@ Choose this option when you need to route alerts to different channels based on
 | Data Missing | Info | Info |
 </div>
-`,Y=`---
+`,q=`---
 title: "Zilliz Alert Events"
 description: "Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4605,8 +4646,8 @@ Choose this method when you need to route alerts to different channels based on
   1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
   2. Select **Zilliz** integration:
         - **Integration Name**: Define a name for this integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  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>
@@ -4639,7 +4680,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
-`,q=`---
+`,O=`---
 title: "Huawei Cloud APM Alerts"
 description: "Sync Huawei Cloud APM alerts to Flashduty through webhook to achieve automatic alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4678,8 +4719,8 @@ When you need to route alerts to different channels based on alert payload infor
   1. Go to Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
   2. Select **Huawei Cloud APM** integration:
         - **Integration Name**: Define a name for the current integration
-  3. Click **Save** and copy the newly generated **push URL** for later use
-  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback, and adjust as needed later
+  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>
@@ -4745,10 +4786,383 @@ When you need to route alerts to different channels based on alert payload infor
 </div>
-`,O=`---
+`,Y=`---
+title: "zstack integration"
+description: "Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction."
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/zstack-integration-guide"
+---
+Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction.
+<div class="hide">
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+### Using Dedicated Integration
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+<details>
+  <summary>Expand</summary>
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **ZStack** 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's payload information.
+<details>
+  <summary>Expand</summary>
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **ZStack** 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 ZStack
+---
+<div class="md-block">
+## 一、Create Notification Object
+### Step 1: Create Notification Object
+1. Login to your \`ZStack\` console, find \`Cloud Monitoring\` in the \`Platform O&M\` menu
+2. Click \`Endpoint\`, click \`Create Endpoint\` or edit the existing endpoint
+3. In the edit page, Name it \`Flashduty\`, select \`Webhook\` type, and fill in the <span class='integration_url'>push URL</span> of the alert integration
+4. Click \`Send Test Message\`, if the message is sent successfully, it means the configuration is successful
+5. Click \`OK\` to complete the configuration
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/zstack-1.png" />
+### Step 2: Use Notification Object in Alert Policy
+1. Login to your \`ZStack\` console, find \`Cloud Monitoring\` in the \`Platform O&M\` menu
+2. Click \`Alarm\`, click \`Create Resource Alarm\` or \`Create Event Alarm\`, or edit the existing alarm object
+3. In the edit page, select the created \`Flashduty\` Endpoint (\`Resource Alarm\` is recommended to open the recovery notification)
+4. Configure other settings as needed, and click \`OK\` to complete the configuration
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/zstack-2.png" />
+</dev>
+## 二、Status Mapping
+<div class="md-block">
+| ZStack |  Flashduty | Status |
+| ---------- | -------- | ---- |
+| Emergent  | Critical | Critical |
+| Major   | Warning  | Warning |
+| Info     | Info     | Info |
+</div>
+`,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"
+url: "https://docs.flashcat.cloud/en/flashduty/keep-alert-integration-guide"
+---
+Push alert events to Flashduty through Keep's Flashduty Provider to achieve automated alert noise reduction.
+<div class="hide">
+## In Flashduty
+You can obtain an integration key through either of these 2 methods:
+#### Using Dedicated Integration
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+<details>
+  <summary>Expand</summary>
+  1. Enter the Flashduty console, select **Channel**, and go to a specific channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Keep** integration, click **Save** to generate a card
+  4. Click the generated card to view the **Integration Key**, copy it for later use, and you're done
+</details>
+#### Using Shared Integration
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+<details>
+  <summary>Expand</summary>
+  1. Enter the Flashduty console, select **Integration Center=>Alert Events** to access the integration selection page
+  2. Select **Keep** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure default routing 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 **Integration Key** for later use
+  5. Done
+</details>
+</div>
+## In Keep
+---
+### Field Definitions
+Field|Required|Type|Definition
+:-:|:-:|:-:|:---
+| title       | Yes   | string | Alert title, maximum \`512\` characters, will be truncated if exceeded
+| event_status | Yes   | string | Alert status.<br><br>Enumerated values (\`First letter capitalized\`): *Critical*: Critical, *Warning*: Warning, *Info*: Info, *Ok*: Recovery.<br><br>When set to Ok, it indicates automatic recovery of the alert
+| alert_key    | No   | string | Alert identifier, used for updating or automatically recovering existing alerts.<br><br>You can customize this value, but it cannot exceed \`255\` characters. You can also rely on system-generated values, which will be returned in the response.<br><br>This value must exist if you're reporting a recovery event
+| description  | No   | string | Alert description, maximum \`2048\` characters, will be truncated if exceeded
+| labels       | No   | map    | Alert label collection, where key is the label name and value is the label value:<br><br>1. Both label key and value are case-sensitive strings<br>2. Label keys should not exceed \`128\` characters and follow Prometheus label naming conventions. Values should not exceed \`2048\` characters, will be truncated if exceeded<br>3. Maximum \`50\` labels allowed. \`Label content refers to\` [Best Practices](#best-practices)<br><br>Example: "resource": "171.26.23.22", "check": "api latency > 500ms"
+### Configuration Method
+#### Step 1: Configure Flashduty Provider
+1. Login to Keep console, enter \`Providers\` list, select and click \`Flashduty\`.
+2. Fill in the \`Flashduty Integration Key\` field with the \`Integration Key\` of Flashduty.
+3. Click \`Save\` to save the configuration.
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/keep-1.png" />
+#### Step 2: Configure WorkFlows
+1. Login to Keep console, enter \`WorkFlows\` , create or edit an existing Workflow.
+2. Configure the \`Trigger\` section as needed.
+3. In the \`Steps\` section, select \`flashduty-action\` and select the \`Flashduty Provider\` configured in the previous step.
+4. In the \`flashduty-action\`'s \`Configure\` section, configure the alert title, alert status, alert description, and alert labels (for details on the field definitions, please refer to [Field Definitions](#field-definitions)).
+5. Click \`Save\` to save the configuration.
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/keep-2.png" />
+`,$=`---
+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"
+url: "https://docs.flashcat.cloud/en/flashduty/elastalert2-alert-integration-guide"
+---
+Push ElastAlert2 alerts to Flashduty via webhook, to achieve automatic alert noise reduction.
+<div class="hide">
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+### Using Dedicated Integration
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+<details>
+  <summary>Expand</summary>
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **ElastAlert 2** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Integration Key**, copy it for later use, and you're done
+</details>
+### Using Shared Integration
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+<details>
+  <summary>Expand</summary>
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **ElastAlert 2** 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 **Integration Key** for later use
+  5. Done
+</details>
+</div>
+## In ElastAlert 2
+---
+### Configure ElastAlert 2 Alerts
+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.
+3. Fill in the integrated \`integration key\` in the \`flashduty_integration_key\` field.
+4. The \`flashduty_title\` and \`flashduty_event_status\` are required fields, and other fields can be filled in as needed. For the field definitions, please refer to the following table.
+Field|Required|Type|Definition
+:-:|:-:|:-:|:---
+| title       | 是   | string | The alert title, it cannot exceed \`512\` characters.
+| event_status | 是   | string | The alert status.<br><br>Enum values (capitalized): *Critical*：severe, *Warning*：warning, *Info*：reminder, *Ok*：recovery.<br><br>When specified as Ok, it means automatic recovery of the alert.
+| alert_key    | 否   | string | The alert identifier, used to update or automatically recover existing alerts. You can customize this value, but it cannot exceed \`255\` characters. You can also rely on the system to automatically generate this value, which will be returned in the response. If you report a recovery event, this value must exist.
+| description  | 否   | string | The alert description
+|   check     | 否   | string | The alert check item
+|   resource     | 否   | string | The alert resource
+|   service     | 否   | string  | The alert service name
+|   metric     | 否   | string | The alert metric name
+|   group     | 否   | string | The alert group
+|   cluster     | 否   | string | The alert cluster
+|   app     | 否   | string | The alert application
+|   env     | 否   | string | The alert environment
+\`\`\`yaml
+name: "elastalert2 alert"
+type: "frequency"
+index: "pgy_audit*"
+is_enabled: true
+num_events: 1
+realert:
+  minutes: 1
+terms_size: 50
+scan_entire_timeframe: true
+timeframe:
+  minutes: 60
+timestamp_field: "created_at"
+timestamp_type: "unix_ms"
+use_strftime_index: false
+alert_subject: "Test {0} 123 aa☃ {1}"
+alert_subject_args:
+  - "account_id"
+  - "operation"
+alert_text: "Test {0}  123 bb☃ {1}"
+alert_text_args:
+  - "request_id"
+  - "operation_name"
+filter:
+  - query:
+      query_string:
+        query: "created_at:*"
+# ------- FlashDuty ----------------
+alert: flashduty
+flashduty_integration_key: "xxxx"
+flashduty_title: "elastalert2 alert"
+flashduty_event_status: "Warning"
+flashduty_alert_key: "abc"
+flashduty_description: "log error"
+flashduty_check: "log error"
+flashduty_resource: "10.1.1.1"
+flashduty_service: "service1"
+flashduty_metric: "error"
+flashduty_group: "group1"
+flashduty_cluster: "bj"
+flashduty_app: "app1"
+flashduty_env: "dev"
+# ------- FlashDuty ----------------
+\`\`\`
+5. Restart ElastAlert and wait for the alert to trigger.`,j=`---
+title: "Dingtalk Alert Integration"
+description: "Generate a unique Dingtalk robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Dingtalk"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/dingtalk-alert-integration-guide"
+---
+Generate a unique Dingtalk robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Dingtalk.
+<div class="hide">
+## Operation Steps
+---
+### Create Dingtalk Alert Integration
+You can obtain a Dingtalk alert integration address through either of these two methods:
+#### Using Dedicated Integration
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+<details>
+  <summary>Expand</summary>
+  1. Go to the Flashduty console, select **Channel**, and enter a specific channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **Dingtalk Alert** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Dingtalk Alert Integration URL**, copy it for later use, and you're done
+</details>
+#### Using Shared Integration
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+<details>
+  <summary>Expand</summary>
+  1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
+  2. Select **Dingtalk Alert** integration:
+        - **Integration Name**: Define a name for the current integration
+        - **Message Type**: Select Dingtalk alert message type, currently only Text and Markdown are supported
+        - **Push Mode**: Choose when to trigger or recover alerts for Dingtalk notifications
+  3. Copy the **Dingtalk Alert Integration URL** for later use
+  4. Configure the default route and select the corresponding channel (after integration creation, you can go to \`Routes\` to configure more routing rules)
+  5. Done
+</details>
+</div>
+### Customize Dingtalk Alert Integration
+#### Dingtalk Alert Integration URL
+The system will generate a unique Dingtalk alert integration URL for you. This URL is compatible with Dingtalk robot message protocol. When platforms only support Dingtalk robot channels, you can use this URL to receive corresponding messages.
+#### Push Mode
+By default, the system always creates new alerts for each message, but you can switch to these modes:
+1. **Trigger or Update Alert Based on Message Title**: In this mode, when receiving a new message, the system searches for open alerts based on the message title. If an alert is found, it will be updated; otherwise, a new alert will be triggered.
+2. **Trigger or Close Alert Based on Rules**: In this mode, when receiving a new message, the system matches messages according to your rules and triggers new alerts or closes existing alerts based on the matching results.
+   - You need to fill in at least one **trigger** rule
+   - You must set up regex extraction rules for Alert Key. The system uses this field to find historical alerts for updates or closure. **If regex extraction fails, the system will use the message title to generate an Alert Key** to ensure alerts won't be lost due to configuration errors
+   - You can choose whether to discard messages when none of the rules match
+   Configuration example:
+   - Receive all messages, close the alert when the message content contains **RESOLVED**, otherwise trigger a new alert
+   - Extract Alert Key from message title using the rule **/(.*)/**.
+### Notes
+- Dingtalk alert integration URL only supports Text and Markdown message types; other message types cannot be received
+- When Dingtalk message type is Text, Flashduty will generate a default alert title "Dingtalk Alert"
+## Severity Mapping
+---
+Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
+`,B=`---
 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: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/custom-change-integration-guide"
 ---
@@ -4802,10 +5216,10 @@ Labels are descriptions of events. You should enrich label content as much as po
 </details>
-`,j=`---
+`,z=`---
 title: "Jira Issue Events"
 description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/jira-integration-guide"
 ---
@@ -4876,7 +5290,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 </div>
-`,$=`---
+`,V=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5011,10 +5425,10 @@ Once published, you can access the application via mobile/PC client. First-time
     |Group Bot Webhook|Maximum 100 calls/minute|
     |Sending messages to the same user or group|Maximum 5 calls/second|
-    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,H=`---
+    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,K=`---
 title: "Dingtalk Integration"
 description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/dingtalk-integration-guide"
 ---
@@ -5167,10 +5581,10 @@ After the application is released, you can access it via mobile/PC client. First
 |Enterprise|5,500,000|60|1st of each month|
 **Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
-`,B=`---
+`,J=`---
 title: "WeCom Integration"
 description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/wecom-integration-guide"
 ---
@@ -5246,10 +5660,10 @@ Integrate WeCom third-party application to receive and respond to alerts within
 7. **Incident notification fails with \`WeCom License Not Activated\`?**
    - Contact Flashduty customer service or dedicated support for license purchase and activation
-`,z=`---
+`,Z=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/slack-integration-guide"
 ---
@@ -5300,10 +5714,10 @@ Integrate with Slack to receive and respond to alerts within Slack.
 8. **Slack App shows Other questions error**
    - Try again, as this might be an unrecorded issue
-   - If the error persists, contact customer support`,V=`---
+   - If the error persists, contact customer support`,Q=`---
 title: "Microsoft Teams Integration"
 description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/microsoft-teams-integration-guide"
 ---
@@ -5395,7 +5809,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
-`,J=`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.
+`,X=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
 <span id="EventTypes"></span>
@@ -5563,7 +5977,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
-`,K=`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.
+`,ee=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
 <span id="EventTypes"></span>
@@ -5770,7 +6184,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
-   - May be updated in the future, please check periodically`,Z=`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`,ne=`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
@@ -6017,10 +6431,10 @@ 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`,Q=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,te=`---
 title: "Jira Sync"
 description: "Sync incidents with Jira issues through Jira Sync Webhook."
-date: "2024-05-11T10:00:00+08:00"
+date: "2025-05-19T10:00:00+08:00"
 url: "https://docs.flashcat.cloud/en/flashduty/jira-sync"
 ---
@@ -6099,7 +6513,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.
-`,X=`---
+`,ae=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -6114,25 +6528,42 @@ url: "https://docs.flashcat.cloud/en/flashduty/template-settings"
 ## When Are Templates Used?
 ---
-The system uses templates to render [Incident](#Incident) and trigger notifications when assigning incidents. Assignment may occur in the following scenarios:
+The system uses templates to render [Incident](#Incident) when assigning incidents, which may occur in the following scenarios:
 1. Manually create and assign an incident
 2. When an alert event is reported, the system automatically generates an incident and assigns it according to the matched escalation rule
 3. After an incident is created, manually change the assignment (reassign)
-4. Automatically escalate assignment according to escalation rule settings
+4. System automatically escalates according to escalation rule settings
 5. When reopening a closed incident, reassign according to previous settings
-We use \`Golang template syntax\` [template/html](https://pkg.go.dev/html/template@go1.18.1) to parse data, allowing you to accomplish any complex rendering requirements.
+We use \`Golang template syntax\` [template/html](https://pkg.go.dev/html/template@go1.18.1) to parse data, enabling you to accomplish any complex rendering requirements.
+- For documentation, please refer to [here](https://www.topgoer.com/%E5%B8%B8%E7%94%A8%E6%A0%87%E5%87%86%E5%BA%93/template.html#%E6%A8%A1%E6%9D%BF%E8%AF%AD%E6%B3%95), supporting logical conditions, loops, pipelines, and common functions;
+- We've incorporated the open-source library [sprig](https://github.com/flashcatcloud/sprig/tree/flashcat), which includes hundreds of common functions that you can directly call in templates;
+- If you wish to introduce more functions, feel free to submit a merge request
+## How to Configure Notification Templates?
+---
+### Configure Notification Templates
+The system uses the default template when notifying incidents, which cannot be modified. If you need to customize the notification content, you should create a custom template.
+1. Enter the \`Templates\` page, click the \`Create Custom Template\` button or \`Copy Default Template\`, and enter the editing page.
+2. In the editing page, you can edit the content according to the notification channel used, and reference the content in the template can refer to [What Variables Can I Reference?](#What Variables Can I Reference?)
+3. After editing, click the \`Save\` button to save the template.
+### Use Notification Templates
+1. Enter the \`Channel\` -> \`Escalation Rules\` page, click the \`Edit\` button, and enter the editing page.
+2. In the strategy configuration section, you can select the template to use **which template** for notification, and select the notification template to use.
+3. Other configurations can refer to [Escalation Rules Configuration](https://docs.flashcat.cloud/en/flashduty/escalate-rule-settings).
+4. After configuration, click the \`Save\` button to save the escalation policy.
-- For documentation, please refer to [here](https://www.topgoer.com/%E5%B8%B8%E7%94%A8%E6%A0%87%E5%87%86%E5%BA%93/template.html#%E6%A8%A1%E6%9D%BF%E8%AF%AD%E6%B3%95), supporting logical conditions, loops, pipelines and common functions
-- We reference the open source library [sprig](https://github.com/flashcatcloud/sprig/tree/flashcat), which includes hundreds of common functions that you can call directly in templates
-- If you want to introduce more functions, feel free to submit a merge request
 ## What Variables Can I Reference?
 ---
 **Variable Reference Examples**:
-\`\`\`
+\`\`\`go
 // Reference title
 {{.Title}}
@@ -6154,7 +6585,7 @@ ID | string | Yes | Incident ID
 \`Title\` | string | Yes | Incident title
 \`Description\` | string | Yes | Incident description, can be empty
 DetailUrl | string | Yes | Incident detail page URL
-Num | string | Yes | Short incident identifier, for easy visual recognition only, may be duplicate
+Num | string | Yes | Short incident identifier, for easy visual recognition, may be duplicate
 \`IncidentSeverity\` | string | Yes | Severity level, enum values: Critical, Warning, Info
 IncidentStatus | string | Yes | Incident status, enum values: Critical, Warning, Info, Ok
 \`Progress\` | string | Yes | Processing progress, enum values: Triggered, Processing, Closed
@@ -6163,19 +6594,19 @@ LastTime | int64 | No | Latest event time, latest incorporated event time in ass
 EndTime | int64 | No | Recovery time, when all associated alerts recover, the incident will automatically recover and close. Unix timestamp in seconds, default 0
 SnoozedBefore | int64 | No | Snooze end time, Unix timestamp in seconds, default 0
 AckTime | int64 | No | First acknowledgment time, Unix timestamp in seconds, default 0
-CloseTime | int64 | No | Close time, end_time is incident recovery time, close_time is processing progress close time. Incident automatically closes on recovery, manual closure does not affect recovery. Unix timestamp in seconds, default 0
-Creator | [Person](#Person) | No | Creator information, does not exist when automatically generated by system
-Closer | [Person](#Person) | No | Closer information, does not exist when incident recovers automatically
+CloseTime | int64 | No | Close time, end_time is incident recovery time, close_time is processing progress close time. Incident automatically closes upon recovery, manual closure doesn't affect recovery. Unix timestamp in seconds, default 0
+Creator | [Person](#Person) | No | Creator information, not present when automatically generated by system
+Closer | [Person](#Person) | No | Closer information, not present when incident recovers automatically
 AssignedTo | [Assignment](Assignment) | No | Assignment configuration
-Responders | [][Responder](#Responder) | No | List of responders, initialized based on assignment configuration, will also have corresponding records if non-assigned personnel acknowledge the incident
+Responders | [][Responder](#Responder) | No | Responder list, initialized based on assignment configuration, also includes records if non-assigned personnel acknowledge the incident
 ChannelID | int64 | No | Channel ID, value is 0 when manually creating global incident
 ChannelName | string | No | Channel name
 GroupMethod | string | No | Grouping method, enum values: n: no grouping, p: rule-based grouping, i: intelligent grouping
-\`Labels\` | map[string]string | No | Label key-value pairs, both Key and Value are strings. No information when manually created, label information from first alert when automatically created
+\`Labels\` | map[string]string | No | Label key-value pairs, both Key and Value are strings. No information when manually created, contains first alert's label information when automatically created
 AlertCnt | int64 | Yes | Number of associated alerts
 Alerts | [][Alert](#Alert) | No | Associated alert details, no information when manually created
 FireType | string | No | Notification type, enum values: fire: notify, refire: loop notification
-IsFlapping | bool | No | Whether in flapping state, i.e. frequent occurrence and recovery, related to convergence configuration
+IsFlapping | bool | No | Whether in flapping state, i.e., frequent occurrence and recovery, related to convergence configuration
 Impact | string | No | Incident impact, filled after incident closure
 RootCause | string | No | Root cause, filled after incident closure
 Resolution | string | No | Resolution, filled after incident closure
@@ -6192,11 +6623,11 @@ email | string | Yes | Email address
 **Assignment** (Indirect Reference):
 Field|Type|Required|Description
 :-:|:-:|:-:|:---
-PersonIDs | []string| No | List of person IDs, exists only when assigning by person
+PersonIDs | []string| No | Person ID list, exists only when assigning by person
 EscalateRuleID | string | No | Escalation rule ID, exists only when assigning by rule
 EscalateRuleName | string | No | Escalation rule name
 LayerIdx | string | No | Assignment level, corresponds to escalation rule level index, starts from 0
-Type | string | Yes | Assignment type, enum values: assign: assign, reassign: reassign, escalate: escalate assignment, reopen: reopen assignment
+Type | string | Yes | Assignment type, enum values: assign: assign, reassign: reassign, escalate: escalation assign, reopen: reopen assign
 <span id="Responder"></span>
 **Responder** (Indirect Reference):
@@ -6219,44 +6650,44 @@ AlertStatus | string | Yes | Alert status, enum values: Critical, Warning, Info,
 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 on recovery, manual closure does not affect recovery. 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
-## FAQ
+## Common Questions
 ---
-1. **How do I know what label information is in \`Labels\`?**
+1. **How do I know what label information is available in \`Labels\`?**
    - Manually created incidents have no labels
-   - Automatically created incidents have labels, same as the labels of the first incorporated alert. Go to the \`Alerts\` page, find an incident and view its details to see all label information
+   - Automatically created incidents have labels, matching the first incorporated alert's labels. Go to the \`Incidents\` page, find an incident and view its details to see all label information
 2. **Why is the \`default template\` used when I configured custom template rendering?**
    - When creating a custom template, the system uses mock data to render the template to check for syntax errors
-   - Mock data has limited coverage and may not match some logical branches in your template, which could fail during actual execution
-   - After rendering fails, the system will use the default template as a fallback to ensure message delivery
-   - When unsure if a referenced variable exists, it's recommended to use logical conditions to avoid rendering exceptions, e.g. for the \`resource\` label:
+   - Mock data has limited coverage and may not match some logic branches in your template during actual operation
+   - If rendering fails, the system will use the default template as a fallback to ensure message delivery
+   - When unsure if a referenced variable exists, it's recommended to use logical conditions to avoid rendering errors, e.g., for the \`resource\` label:
-   \`\`\`
+   \`\`\`go
    // Wrong approach: directly read label
    {{.Labels.resource}}
-   // Recommended approach: check first, then read label
+   // Recommended: check first, then read label
    {{if .Labels.resource}}{{.Labels.resource}}{{end}}
    \`\`\`
-3. **Why are characters like ">" \`escaped\` in the incident title?**
+3. **Why are characters like ">" \`escaped\` in incident titles?**
-   \`\`\`
+   \`\`\`go
    // Use toHtml function
    {{toHtml .Title}}
-   // Use first non-empty value for rendering, avoid writing complex if logic
+   // Use first non-empty value for rendering, avoiding complex if logic
    {{toHtml .Title .TitleEnglish}}
    \`\`\`
-4. **Time variables are timestamps, how to \`format time\`?**
+4. **Time variables are timestamps, how do I \`convert time formats\`?**
-   \`\`\`
+   \`\`\`go
    // date function converts timestamp to readable format
    // "2006-01-02 15:04:05" is a common format, search online for more formats
    {{date "2006-01-02 15:04:05" .StartTime}}
@@ -6266,24 +6697,24 @@ CloseTime | int64 | No | Close time, EndTime is alert recovery time, CloseTime i
    \`\`\`
 5. **How to reference external variables inside a for loop?**
-   \`\`\`
+   \`\`\`go
    // Add "$" before external variables
    {{range .Responders}}
-    {{if eq $.Progress "Triggered"}}
-      [Pending]{{.Email}}
-    {{end}}
+   	{{if eq $.Progress "Triggered"}}
+   		[Pending]{{.Email}}
+   	{{end}}
    {{end}}
    \`\`\`
-6. **How to extract field values with "." in names, like "obj.instance" in labels?**
+6. **How do I extract field values with "." in names, like "obj.instance" in labels?**
-   \`\`\`
+   \`\`\`go
    // Use index function
    {{index .Labels "obj.instance"}}
    \`\`\`
-7. **How to extract and deduplicate label information from incident associated alerts?**
+7. **How do I extract and deduplicate label information from incident-associated alerts?**
-   \`\`\`
+   \`\`\`go
    // Use alertLabels function to get deduplicated array
    {{alertLabels . "resource"}}
@@ -6291,9 +6722,9 @@ CloseTime | int64 | No | Close time, EndTime is alert recovery time, CloseTime i
    {{joinAlertLabels . "resource" "sep"}}
    \`\`\`
-8. **How to iterate and print labels?**
+8. **How do I iterate and print labels?**
-   \`\`\`
+   \`\`\`go
    // Complete iteration
    {{range $k, $v := .Labels}}
      {{$k}} : {{toHtml $v}}
@@ -6313,38 +6744,70 @@ CloseTime | int64 | No | Close time, EndTime is alert recovery time, CloseTime i
      {{end}}
    {{end}}
-9. **How to extract information from JSON fields?**
+9. **How do I extract information from JSON fields?**
-   - The jsonGet function helps you extract values matching conditions from JSON format data via path
-   - Target data extracted by jsonGet function must be valid JSON
+   - jsonGet function helps extract values from JSON format data using path
+   - Target data for jsonGet function must be valid JSON
    - Basic usage: {{jsonGet .Labels.xxx "yyy"}}, where xxx must be valid JSON and yyy is a valid extraction path
    - For JSON path syntax, refer to [gjson.dev](https://gjson.dev/), where you can input target data and extraction path for real-time preview
-    \`\`\`
+    \`\`\`go
     // Extract detail_url field from rule_note label
     {{jsonGet .Labels.rule_note "detail_url"}}
     // Extract name field from first element in JSON array
     {{jsonGet .Labels.slice "0.name"}}
-    // Iterate each element in JSON array, match instanceId field of object with userId==7777
+    // Iterate through JSON array elements, match instanceId field of object with userId==7777
     {{jsonGet .Labels.rule_note "#(userId==7777)#.instanceId" }}
+    \`\`\`
+10. **如何使用逻辑与、或等条件进行内容显示判断？**
+    \`\`\`
+    # Supported functions
+    - Use \`and\` function for logical AND judgment
+    - Use \`or\` function for logical OR judgment
+    - Use \`not\` function for logical NOT judgment
+    - Use \`eq\` function for logical equal judgment
+    - Use \`ne\` function for logical not equal judgment
+    - Use \`gt\` function for logical greater than judgment
+    - Use \`ge\` function for logical greater than or equal judgment
+    - Use \`lt\` function for logical less than judgment
+    - Use \`le\` function for logical less than or equal judgment
+    # Example usage
+    # Use and function for logical AND judgment
+    {{if and (eq .Labels.resource "cpu") (eq .Labels.metric "cpu_usage")}}
+      {{.Labels.resource}} CPU usage exceeds 80%
+    {{end}}
+    # Use or function for logical OR judgment
+    {{if or (eq .Labels.resource "cpu") (eq .Labels.metric "cpu_usage")}}
+      {{.Labels.resource}} CPU usage exceeds 80%
+    {{end}}
+    # Use not function for logical NOT judgment
+    {{if not (eq .Labels.metric "cpu_usage")}}
+      {{.Labels.metric}} is not CPU usage
+    {{end}}
     \`\`\`
-10. **Where can I find more functions and usage examples?**
+11. **How do I find more functions and their usage examples?**
    - Function list: https://github.com/flashcatcloud/sprig/blob/master/functions.go#L97
-   - Usage examples: Check corresponding _test.go files, e.g. date function test cases at https://github.com/flashcatcloud/sprig/blob/master/date_test.go
+   - Usage examples: Check corresponding _test.go files, e.g., date function test cases at https://github.com/flashcatcloud/sprig/blob/master/date_test.go
-Below are specific instructions for each notification channel.
+Below are specific instructions for each notification channel.
 <div class="feishu_app hide">
 ## Feishu/Lark App
 ---
-You need to configure \`Integration Center - IM - Feishu/Lark\` integration first to send message cards. If custom content is not set, the system default template will be used to render all label information:
+You need to configure \`Integration Center-Instant Message-Feishu\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering all label information:
-\`\`\`
+\`\`\`go
 {{if .Description}}**description** :{{toHtml .Labels.body_text .Description}}{{end}}
 {{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{range $k, $v := .Labels}}
@@ -6353,15 +6816,14 @@ You need to configure \`Integration Center - IM - Feishu/Lark\` integration firs
 As shown below:
-<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-feishu-1.png" width="800">
+<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/feishu_app_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
+If you want to display only key label information, you can refer to the code segment below:
-If you want to display only key label information, you can refer to the code snippet below:
+- We've listed some common labels, you can add or remove as needed
+- In Feishu app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely
-- We've listed some common labels that you can add or remove as needed
-- In Feishu/Lark app, the system will automatically remove empty lines (caused by non-existent labels) during rendering, so you can configure freely
-\`\`\`
+\`\`\`go
 {{if (index .Labels "resource")}}resource：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{if (index .Labels "check")}}check：{{toHtml (index .Labels "check")}}{{end}}
 {{if (index .Labels "metric")}}metric：{{index .Labels "metric"}}{{end}}
@@ -6389,9 +6851,9 @@ If you want to display only key label information, you can refer to the code sni
 ## Dingtalk App
 ---
-You need to configure \`Integration Center - IM - Dingtalk\` integration first to send message cards. If custom content is not set, the system default template will be used to render all label information:
+You need to configure \`Integration Center-Instant Message-Dingtalk\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering all label information:
-\`\`\`
+\`\`\`go
 {{if .Description}}**description** :{{toHtml .Labels.body_text .Description}}{{end}}
 {{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{range $k, $v := .Labels}}
@@ -6399,15 +6861,15 @@ You need to configure \`Integration Center - IM - Dingtalk\` integration first t
 \`\`\`
 As shown below:
-<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-ding-1.png" width="800">
+<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/dingtalk_app_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
-If you want to display only key label information, you can refer to the code snippet below:
+If you want to display only key label information, you can refer to the code segment below:
-- We've listed some common labels that you can add or remove as needed
-- In Dingtalk app, the system will automatically remove empty lines (caused by non-existent labels) during rendering, so you can configure freely
+- We've listed some common labels, you can add or remove as needed
+- In Dingtalk app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely
-\`\`\`
+\`\`\`go
 {{if (index .Labels "resource")}}**resource**：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{if (index .Labels "metric")}}**metric**：{{index .Labels "metric"}}{{end}}
 {{if (index .Labels "prom_ql")}}**prom_ql**：{{toHtml (index .Labels "prom_ql")}}{{end}}
@@ -6434,12 +6896,13 @@ If you want to display only key label information, you can refer to the code sni
 ## WeCom App
 ---
-You need to configure \`Integration Center - IM - WeCom\` integration first to send message cards. If custom content is not set, the system default template will be used to render only common label information:
-- We've listed some common labels that you can add or remove as needed
-- In WeCom app, the system will automatically remove empty lines (caused by non-existent labels) during rendering, so you can configure freely
+You need to configure \`Integration Center-Instant Message-WeCom\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:
-\`\`\`
+- We've listed some common labels, you can add or remove as needed
+- In WeCom app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely
+\`\`\`go
 {{if (index .Labels "resource")}}resource：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{if (index .Labels "metric")}}metric：{{index .Labels "metric"}}{{end}}
 {{if (index .Labels "prom_ql")}}prom_ql：{{toHtml (index .Labels "prom_ql")}}{{end}}
@@ -6463,19 +6926,19 @@ You need to configure \`Integration Center - IM - WeCom\` integration first to s
 As shown below:
-<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-wecom-1.png" width="800">
+<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/wecom_app_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
+**Note: WeCom limits card length. In the template rendering area, you can render no more than 8 lines of content. Content beyond 8 lines will be hidden**
-**Note: WeCom limits card length. In the template rendering area, you can render up to 8 lines of content. Content beyond 8 lines will be hidden**
 </div>
 <div class="slack_app hide">
 ## Slack App
 ---
-You need to configure \`Integration Center - IM - Slack\` integration first to send message cards. If custom content is not set, the system default template will be used to render only common label information:
+You need to configure \`Integration Center-Instant Message-Slack\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:
-\`\`\`
+\`\`\`go
 {{if .Description}}*description* :{{toHtml .Labels.body_text .Description}}{{end}}
 {{if .Labels.resource}}*resource* : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{range $k, $v := .Labels}}
@@ -6486,18 +6949,18 @@ As shown below:
 <img src="https://download.flashcat.cloud/flashduty/integration/slack/slack_app_message.png" alt="drawing" style="display: block; margin: 0 auto;" width="600"/>
-If you want to display only key label information, you can refer to the code snippet below:
+If you want to display only key label information, you can refer to the code segment below:
-- We've listed some common labels that you can add or remove as needed
-- Messages can be around 15000 characters long, content beyond that will be truncated
-- In Slack app, the system will automatically remove empty lines (caused by non-existent labels) during rendering, so you can configure freely
+- We've listed some common labels, you can add or remove as needed
+- Messages can be around 15000 characters long, content beyond this will be truncated
+- In Slack app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely
-\`\`\`
+\`\`\`go
 {{if (index .Labels "resource")}}*resource*：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{if (index .Labels "metric")}}*metric*：{{index .Labels "metric"}}{{end}}
 {{if (index .Labels "prom_ql")}}*prom_ql*：{{toHtml (index .Labels "prom_ql")}}{{end}}
 {{if (index .Labels "trigger_value")}}*trigger_value*：{{index .Labels "trigger_value"}}{{end}}
-{{if (index .Labels "host_ql")}}*host_ql*：{{toHtml (index .Labels "host_ql")}}{{end}}
+{{if (index .Labels "host_ql")}}*host_ql*：{{index .Labels "host_ql"}}{{end}}
 {{if (index .Labels "region")}}*region*：{{index .Labels "region"}}{{end}}
 {{if (index .Labels "cluster")}}*cluster*：{{index .Labels "cluster"}}{{end}}
 {{if (index .Labels "business")}}*business*：{{index .Labels "business"}}{{end}}
@@ -6512,19 +6975,392 @@ If you want to display only key label information, you can refer to the code sni
 {{if (index .Labels "name")}}*name*：{{index .Labels "name"}}{{end}}
 {{if (index .Labels "mode")}}*mode*：{{index .Labels "mode"}}{{end}}
 {{if (index .Labels "runbook_url")}}*runbook_url*：{{index .Labels "runbook_url"}}{{end}}
-\`\`\`
+\`\`\`
+</div>
+<div class="teams_app hide">
+## Microsoft Teams App
+---
+You need to configure \`Integration Center-Instant Message-Microsoft Teams\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:
+\`\`\`
+{{if .Description}}**description** :{{toHtml .Labels.body_text .Description}}{{end}}
+{{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
+{{range $k, $v := .Labels}}
+{{if not (in $k "resource" "body_text" "body_text_with_table")}}**{{$k}}** : {{toHtml $v}}{{end}}{{end}}
+\`\`\`
+As shown below:
+<img src="https://download.flashcat.cloud/flashduty/integration/microsoft-teams/teams_app_message.png" alt="drawing" style="display: block; margin: 0 auto;" width="300"/>
+If you want to display only key label information, you can refer to the code segment below:
+- We've listed some common labels, you can add or remove as needed
+- Messages can be around 28KB in size, content beyond this will result in an error
+- In Microsoft Teams app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely
+\`\`\`
+{{if (index .Labels "resource")}}**resource**：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
+{{if (index .Labels "metric")}}**metric**：{{index .Labels "metric"}}{{end}}
+{{if (index .Labels "prom_ql")}}**prom_ql**：{{toHtml (index .Labels "prom_ql")}}{{end}}
+{{if (index .Labels "trigger_value")}}**trigger_value**：{{index .Labels "trigger_value"}}{{end}}
+{{if (index .Labels "host_ql")}}**host_ql**：{{index .Labels "host_ql"}}{{end}}
+{{if (index .Labels "region")}}**region**：{{index .Labels "region"}}{{end}}
+{{if (index .Labels "cluster")}}**cluster**：{{index .Labels "cluster"}}{{end}}
+{{if (index .Labels "business")}}**business**：{{index .Labels "business"}}{{end}}
+{{if (index .Labels "service")}}**service**：{{index .Labels "service"}}{{end}}
+{{if (index .Labels "env")}}**env**：{{index .Labels "env"}}{{end}}
+{{if (index .Labels "type")}}**type**：{{index .Labels "type"}}{{end}}
+{{if (index .Labels "topic")}}**topic**：{{index .Labels "topic"}}{{end}}
+{{if (index .Labels "cpu")}}**cpu**：{{index .Labels "cpu"}}{{end}}
+{{if (index .Labels "device")}}**device**：{{index .Labels "device"}}{{end}}
+{{if (index .Labels "path")}}**path**：{{index .Labels "path"}}{{end}}
+{{if (index .Labels "fstype")}}**fstype**：{{index .Labels "fstype"}}{{end}}
+{{if (index .Labels "name")}}**name**：{{index .Labels "name"}}{{end}}
+{{if (index .Labels "mode")}}**mode**：{{index .Labels "mode"}}{{end}}
+{{if (index .Labels "runbook_url")}}**runbook_url**：{{index .Labels "runbook_url"}}{{end}}
+\`\`\`
+</div>
+<div class="sms hide">
+## Feishu/Lark Bot
+---
+Feishu/Lark bot supports message cards, rich text, and plain text formats. The default template is in message card format.
+- The msg_type field is required for message cards and rich text, otherwise it will be sent as plain text format
+- The maximum message length is \`4000 bytes, content exceeding this limit will be truncated\`
+- If no custom content is set, the system default template will be used to display key information:
+1. Message Card
+msg_type is required, value should be interactive
+\`\`\`
+{
+  "msg_type": "interactive",
+  "card": {
+    "config": {
+      "wide_screen_mode": true,
+      "enable_forward": true
+    },
+    "header": {
+      "template": "{{if eq .IncidentSeverity "Critical"}}red{{else if eq .IncidentSeverity "Warning"}}orange{{else}}yellow{{end}}",
+      "title": {
+        "content": "{{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
+        "tag": "plain_text"
+      }
+    },
+    "elements": [{
+      "tag": "div",
+      "fields": [{
+          "text": {
+            "tag": "lark_md",
+            "content": "**🏢 Channel:**{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} Severity:**{{.IncidentSeverity}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**⏰ Triggered at:**{{date "2006-01-02 15:04:05" .StartTime}}{{if gt .AlertCnt 1}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**🔔 Grouped alerts:**{{.AlertCnt}} {{end}}{{if .Labels.resource}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**📌 Alert targets:**{{toHtml (joinAlertLabels . "resource" ",")}} {{end}}{{if .Description}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**🔍 Description:**{{.Description}}{{end}}{{if gt (len .Responders) 0}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**👨‍💻 Responders:**{{range .Responders}}@{{.PersonName}} {{end}}{{end}}"
+          }
+        }
+      ]
+    },
+    {
+      "tag": "hr"
+    },
+    {
+      "tag": "action",
+      "actions": [{
+          "tag": "button",
+          "text": {
+            "tag": "plain_text",
+            "content": "Details"
+          },
+          "type": "primary",
+          "url": "{{.DetailUrl}}"
+        },
+        {
+          "tag": "button",
+          "text": {
+            "tag": "plain_text",
+            "content": "Acknowledge"
+          },
+          "type": "primary",
+          "url": "{{.DetailUrl}}?ack=1"
+        }
+      ]
+    }]
+  }
+}
+\`\`\`
+2. Rich Text
+msg_type is required, value should be post
+\`\`\`
+{
+    "msg_type": "post",
+    "post": {
+        "zh_cn": {
+            "title": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} {{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
+            "content": [
+                [{
+                    "tag": "text",
+                    "text": "🏢 "
+                }, {
+                    "tag": "text",
+                    "text": "Channel：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}\\n"
+                }],
+                [{
+                    "tag": "text",
+                    "text": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} "
+                }, {
+                    "tag": "text",
+                    "text": "Severity：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{.IncidentSeverity}}\\n",
+                    "text_type": "{{if eq .IncidentSeverity "Critical"}}bold{{end}}"
+                }],
+                [{
+                    "tag": "text",
+                    "text": "⏰ "
+                }, {
+                    "tag": "text",
+                    "text": "Triggered at：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{date "2006-01-02 15:04:05" .StartTime}}\\n"
+                }],
+                {{if gt .AlertCnt 1}}[{
+                    "tag": "text",
+                    "text": "🔔 "
+                }, {
+                    "tag": "text",
+                    "text": "Grouped alerts：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{.AlertCnt}}\\n"
+                }],{{end}}
+                {{if .Labels.resource}}[{
+                    "tag": "text",
+                    "text": "📋 "
+                }, {
+                    "tag": "text",
+                    "text": "Alert targets：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{toHtml (joinAlertLabels . "resource" ", ")}}\\n"
+                }],{{end}}
+                {{if .Description}}[{
+                    "tag": "text",
+                    "text": "📝 "
+                }, {
+                    "tag": "text",
+                    "text": "Description：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{toHtml .Description}}\\n"
+                }],{{end}}
+                {{if gt (len .Responders) 0}}[{
+                    "tag": "text",
+                    "text": "👨‍💻 "
+                }, {
+                    "tag": "text",
+                    "text": "Responders：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{range .Responders}}@{{.PersonName}} {{end}}\\n"
+                }],{{end}}
+                [{
+                    "tag": "a",
+                    "href": "{{.DetailUrl}}",
+                    "text": "Details"
+                },{
+                    "tag": "text",
+                    "text": "  "
+                },{
+                    "tag": "a",
+                    "href": "{{.DetailUrl}}?ack=1",
+                    "text": "Acknowledge"
+                }]
+            ]
+        }
+    }
+}
+\`\`\`
+3. Plain Text
+\`\`\`
+{{fireReason .}}INC #{{.Num}} {{toHtml .Title}}
+-----
+Channel：{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
+Severity：{{.IncidentSeverity}}
+Triggered at：{{date "2006-01-02 15:04:05" .StartTime}}
+Duration：{{ago .StartTime}}{{if gt .AlertCnt 1}}
+Grouped alerts：{{.AlertCnt}}{{end}}{{if .Labels.resource}}
+Alert targets：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
+Description：{{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
+Responders：{{range .Responders}}@{{.PersonName}} {{end}}{{end}}
+<br>Details：{{.DetailUrl}}
+\`\`\`
+</div>
+<div class="dingtalk hide">
+## Dingtalk Bot
+---
+Dingtalk bot only supports sending Markdown messages ([syntax restrictions](https://open.dingtalk.com/document/robots/custom-robot-access#title-7ur-3ok-s1a)).
+- The maximum message length is \`4000 bytes, content exceeding this limit will be truncated\`
+- If the text contains \`<br>\`, when rendering, the system will \`first remove empty lines, then replace <br> with line breaks\`
+- If no custom content is set, the system default template will be used to display key information:
+\`\`\`
+{{fireReason .}}INC [#{{.Num}}]({{.DetailUrl}}) {{toHtml .Title}}
+---
+- Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
+- Severity: {{$s := colorSeverity .IncidentSeverity}}{{toHtml $s}}
+- Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
+- Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
+- Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
+- Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
+- Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
+- Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
+---
+<br>[Details]({{.DetailUrl}})|[Acknowledge]({{.DetailUrl}}?ack=1)
+\`\`\`
+</div>
+<div class="wecom hide">
+## WeCom Bot
+---
+WeCom bot only supports sending Markdown messages ([syntax restrictions](https://developer.work.weixin.qq.com/document/path/91770#markdown%E7%B1%BB%E5%9E%8B)).
+- The maximum message length is \`4000 bytes, content exceeding this limit will be truncated\`
+- If the text contains \`<br>\`, when rendering, the system will \`first remove empty lines, then replace <br> with line breaks\`
+- If no custom content is set, the system default template will be used to display key information:
+\`\`\`
+{{fireReason .}}**INC [#{{.Num}}]({{.DetailUrl}}) {{toHtml .Title}}**
+> Channel: <font color="warning">{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}</font>
+> Severity: <font color="warning">{{.IncidentSeverity}}</font>
+> Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
+> Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
+> Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
+> Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
+> Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
+> Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
+<br>[Details]({{.DetailUrl}})|[Acknowledge]({{.DetailUrl}}?ack=1)
+\`\`\`
+</div>
+<div class="telegram hide">
+## Telegram Bot
+---
+- Configure a Telegram service address accessible in mainland China
+- The maximum message length is \`4096 characters, content exceeding this limit will not be sent\`
+- If the text contains \`<br>\`, when rendering, the system will \`first remove empty lines, then replace <br> with line breaks\`
+- If no custom content is set, the system default template will be used to display key information:
+\`\`\`
+{{fireReason .}}INC [#{{.Num}}]({{.DetailUrl}}) {{toHtml .Title}}
+-----
+Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
+Severity: {{.IncidentSeverity}}
+Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
+Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
+Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
+Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}({{.Labels.resource}}){{end}}{{if .Description}}
+Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
+Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
+<br>[Details]({{.DetailUrl}})|[Acknowledge]({{.DetailUrl}}?ack=1)
+\`\`\`
+</div>
+<div class="slack hide">
+## Slack Bot
+---
+- Messages can be \`approximately 15000 characters long, content exceeding this limit will be truncated\`
+- If the text contains \`<br>\`, when rendering, the system will \`first remove empty lines, then replace <br> with line breaks\`
+- If no custom content is set, the system default template will be used to display key information:
+\`\`\`
+{{fireReason .}}INC <{{.DetailUrl}}|#{{.Num}}> {{toHtml .Title}}
+-----
+Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
+Severity: {{.IncidentSeverity}}
+Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
+Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
+Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
+Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
+Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
+Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
+-----
+<br><{{.DetailUrl}}|Details>|<{{.DetailUrl}}?ack=1|Acknowledge>
+\`\`\`
 </div>
 <div class="zoom hide">
 ## Zoom Bot
 ---
-- Messages \`can be around 4000 characters long, content beyond that will be truncated\`
-- If text contains \`<br>\`, during rendering the system will \`first remove empty lines, then replace <br> with newline\`
-- Message format \`follows Zoom message format\`. Current bot application doesn't support Markdown, refer to official website for other formats: https://developers.zoom.us/docs/team-chat-apps/customizing-messages/
-- If custom content is not set, the system default template will be used to display only key information:
+- Messages can be \`approximately 4000 characters long, content exceeding this limit will be truncated\`
+- If the text contains \`<br>\`, when rendering, the system will \`first remove empty lines, then replace <br> with line breaks\`
+- Message format \`follows Zoom message format\`. The current bot application doesn't support Markdown. For other formats, please refer to the official documentation: https://developers.zoom.us/docs/team-chat-apps/customizing-messages/
+- If no custom content is set, the system default template will be used to display key information:
-\`\`\`
+\`\`\`json
 {"head": {
     "text": "{{fireReason .}}INC [#{{.Num}}] {{toHtml .Title}}",
     "style": {
@@ -6536,7 +7372,7 @@ If you want to display only key label information, you can refer to the code sni
   "body": [
     {
       "type": "message",
-      "text": "Channel：{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}",
+      "text": "Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}",
       "style": {
         "bold": false,
         "italic": false
@@ -6544,7 +7380,7 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
       "type": "message",
-      "text": "Severity：{{.IncidentSeverity}}",
+      "text": "Severity: {{.IncidentSeverity}}",
       "style": {
         "bold": false,
         "italic": false,
@@ -6553,7 +7389,7 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
       "type": "message",
-      "text": "Duration：{{ago .StartTime}}{{if gt .AlertCnt 1}}",
+      "text": "Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}",
       "style": {
         "bold": false,
         "italic": false
@@ -6561,7 +7397,7 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
       "type": "message",
-      "text": "Grouped alerts：{{.AlertCnt}}{{end}}{{if .Labels.resource}}",
+      "text": "Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}",
       "style": {
         "bold": false,
         "italic": false
@@ -6569,7 +7405,7 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
         "type": "message",
-        "text": "Resource：{{.Labels.resource}}{{end}}{{if .Description}}",
+        "text": "Alert targets: {{.Labels.resource}}{{end}}{{if .Description}}",
         "style": {
           "bold": false,
           "italic": false
@@ -6577,7 +7413,7 @@ If you want to display only key label information, you can refer to the code sni
       },
     {
       "type": "message",
-      "text": "Description：{{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}",
+      "text": "Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}",
       "style": {
         "bold": false,
         "italic": false
@@ -6585,7 +7421,7 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
       "type": "message",
-      "text": "Responders：{{range .Responders}}@{{.PersonName}}{{end}}{{end}}",
+      "text": "Responders: {{range .Responders}}@{{.PersonName}}{{end}}{{end}}",
       "style": {
         "bold": false,
         "italic": false
@@ -6593,12 +7429,12 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
         "type": "message",
-        "text": "View details",
+        "text": "View Details",
         "link": "{{.DetailUrl}}{{if .IsFlapping}}"
     },
     {
       "type": "message",
-      "text": "Note: Current incident status changes frequently, notifications will be suppressed for {{.Flapping.MuteMinutes}} minutes. Please optimize your alert policy.{{end}}{{if .IsInStorm}}",
+      "text": "Note: The current incident status is changing frequently. Notifications will be suppressed for {{.Flapping.MuteMinutes}} minutes. Please optimize your alert policy.{{end}}{{if .IsInStorm}}",
       "style": {
         "bold": true,
         "italic": false
@@ -6606,7 +7442,7 @@ If you want to display only key label information, you can refer to the code sni
     },
     {
       "type": "message",
-      "text": "Note: Current incident has grouped {{.AlertCnt}} alerts, triggering alert storm. Please handle urgently!{{end}}",
+      "text": "Note: The current incident has grouped {{.AlertCnt}} alerts, triggering an alert storm. Please handle with urgency!{{end}}",
       "style": {
         "bold": true,
         "italic": false
@@ -6617,14 +7453,13 @@ If you want to display only key label information, you can refer to the code sni
 \`\`\`
 </div>
 <div class="sms hide">
 ## SMS
 ---
-If custom content is not set, the system default template will be used for notification:
+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>
@@ -6633,94 +7468,95 @@ You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Sever
 ## Email
 ---
-If custom content is not set, the system default template will be used for notification:
+If no custom content is set, the system default template will be used for notifications:
-\`\`\`
+\`\`\`html
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
 <title>{{.Title}}</title>
 <html lang="en">
   <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)}
-  </style>
+	<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)}
+	</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;">Resource</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>
+	<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>
 </html>
 \`\`\`
-As shown below:
-<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
+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"/>
-`,ee={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:L,Dynatrace:_,HuaweiyunLTS:F,GoogleCM:x,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:E,VolcEngineEvent:D,VolcEngineTLS:P,OpManager:N,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:z,MicrosoftTeams:V,AlertWebhook:J,IncidentWebhook:K,CustomAction:Z,Templates:X,HuaweiyunAPM:q,JiraSync:Q};module.exports=ee;
+</div>`,ie={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:_,HuaweiyunLTS:L,GoogleCM:F,Zilliz:q,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:B,Jira:z,Lark:V,Dingtalk:K,Wecom:J,Slack:Z,MicrosoftTeams:Q,AlertWebhook:X,IncidentWebhook:ee,CustomAction:ne,Templates:ae,HuaweiyunAPM:O,JiraSync:te,ZStack:Y,Keep:H,ElastAlert2:$,DingtalkAlert:j};module.exports=ie;