flashduty-knowledge-base 1.2.4 → 1.2.5-beta.2

package/dist/esm/en.js

@@ -469,7 +469,7 @@ Nightingale/Flashcat to Flashduty alert severity mapping:
     
 </details>
 
-`,o=`---
+`,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"
@@ -651,7 +651,7 @@ Prometheus to Flashduty severity mapping:
 
 
 
-`,i=`---
+`,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"
@@ -3124,7 +3124,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"
@@ -3226,7 +3226,7 @@ Choose this option when you need to route alerts to different channels based on
 
 </div>
 
-`,_=`---
+`,L=`---
 title: "Dynatrace Alert Events"
 description: "Sync Dynatrace alert events to Flashduty via webhook to achieve automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -3333,7 +3333,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`,F=`---
+`,_=`---
 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"
@@ -3446,7 +3446,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"
@@ -3875,7 +3875,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,E=`---
+`,D=`---
 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"
@@ -3964,7 +3964,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"
@@ -4745,6 +4745,94 @@ When you need to route alerts to different channels based on alert payload infor
 
 </div>
 
+`,j=`---
+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. 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. 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>
+
 `,O=`---
 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."
@@ -4802,7 +4890,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,j=`---
+`,H=`---
 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"
@@ -5011,7 +5099,7 @@ 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`,B=`---
 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"
@@ -5167,7 +5255,7 @@ 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=`---
+`,z=`---
 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"
@@ -5300,7 +5388,7 @@ 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`,z=`---
+   - If the error persists, contact customer support`,J=`---
 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"
@@ -5586,6 +5674,7 @@ The following event types are currently supported, with more potentially being a
 |    i_rslv    | Close incident (automatically or manually) |
 |   i_reopen   | Reopen incident |
 |   i_merge    | Manually merge incidents |
+|   i_comm     | Add comment |
 |  i_r_title   | Update incident title |
 |   i_r_desc   | Update incident description |
 |  i_r_impact  | Update incident impact |
@@ -5769,7 +5858,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`,J=`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`,Q=`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
 
@@ -6016,7 +6105,89 @@ 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`,X=`---
+title: "Jira Sync"
+description: "Sync incidents with Jira issues through Jira Sync Webhook."
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jira-sync"
+---
+
+Through Jira Sync Webhook, you can associate and synchronize Flashduty incidents with Jira Issues, enabling integration between Flashduty and Jira.
+
+## Prerequisites
+- This integration is compatible with Jira Cloud, as well as versions 7.x and 8.x of Jira Server and Jira Data Center.
+- Currently, only one-way synchronization of incident information and status to Jira is supported. Information in Jira will not sync back to Flashduty.
+- For Jira Cloud, use an API Token in the password field during authorization configuration; for Jira Server or Data Center, use your Jira account password.
+
+## Getting API Token in Jira Cloud （Jira Server and Data Center please skip）
+
+- After logging into Jira Cloud, click your profile picture in the top right corner and select **Manage Account**.
+- On the **Manage Account** page, select the **Security** tab.
+- On the **Security** page, click **Create and manage API tokens**.
+- In the **Create and manage API tokens** dialog, enter an API token name and select an expiration time.
+- Click **Create** to generate the API token.
+- Copy the API token value and paste it into the API token field in Flashduty's authorization configuration.
+
+## Configuring Integration in Flashduty
+
+### 1. Create and Authenticate Jira Integration
+<div class="hide">
+
+In the Integration Center, select **Webhook**, choose **Jira Sync** integration, and fill in the following authentication information.
+
+</div>
+
+- **Jira Platform Type**: Choose based on your version. For Data Center version, select Self-hosted (Server).
+- **Service URL**: For Cloud version, enter your actual access URL, e.g., https://your-domain.atlassian.net. For Server version, enter your service access URL, e.g., https://your-jira-server-url.com.
+- **Username**: Your Jira account name. For Cloud version, enter your email; for Server version, enter your Jira username.
+- **API Token/Password**: Your Jira account credentials. For Cloud version, enter API Token; for Server version, enter your Jira account password.
+- After completion, click **Next** to proceed with configuration.
+
+**About Permissions**: Ensure your Jira account has permissions to access relevant projects, issue types, and create issues. Using an administrator account is recommended.
+
+### 2. Jira Integration Configuration
+
+- **Integration Name**: Define a name for this integration.
+- **Trigger Mode**:
+    - Automatic: Configure conditions for Flashduty to automatically sync qualifying incidents to Jira.
+    - Manual: Manually trigger Jira sync from the incident details page's more actions menu (integration name serves as trigger name).
+- **Project ID**: Select the target Jira project for synchronization.
+- **Issue Type**: Select the target Jira issue type.
+- **Channel**: Select the channel where this integration will be active. Only incidents within this channel can sync to Jira.
+- **Severity Mapping**: If the selected issue type doesn't support priority fields, this mapping cannot be configured.
+- **Custom Field Mapping**: Choose to sync certain or all incident labels and custom field content to Jira fields (text type fields only).
+
+### 3. About Updates
+
+- For incidents with existing Jira issues, updates to severity or status will automatically update in Jira, but Jira updates won't sync back to Flashduty.
+- Comments sync to Jira, but Jira comments won't sync back to Flashduty.
+- Updates to incident title, description, labels, or other fields won't update in Jira.
+
+### 4. Flashduty to Jira Mapping
+
+#### Field Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Summary | Title |
+| Description | Description |
+| Priority | Severity |
+| Reporter | Integration configured user |
+| Comments | Comments |
+
+#### Status Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Todo | Pending |
+| In Progress | In Progress |
+| Done | Resolved |
+
+### 5. Important Notes
+
+- 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.
+`,ee=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -6031,25 +6202,25 @@ 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 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
+- 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
 
 ## What Variables Can I Reference?
 ---
 **Variable Reference Examples**:
 
-\`\`\`
+\`\`\`go
 // Reference title
 {{.Title}}
 
@@ -6071,7 +6242,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
@@ -6080,19 +6251,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
@@ -6109,11 +6280,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):
@@ -6136,44 +6307,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}}
@@ -6183,24 +6354,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"}}
 
@@ -6208,9 +6379,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}}
@@ -6230,36 +6401,38 @@ 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. **Where can I find more functions and usage examples?**
+10. **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}}
@@ -6268,15 +6441,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}}
@@ -6298,12 +6470,15 @@ If you want to display only key label information, you can refer to the code sni
 {{if (index .Labels "mode")}}mode：{{index .Labels "mode"}}{{end}}
 {{if (index .Labels "runbook_url")}}runbook_url：{{toHtml (index .Labels "runbook_url")}}{{end}}
 \`\`\`
+</div>
+
+<div class="dingtalk_app hide">
 
 ## 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}}
@@ -6311,15 +6486,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}}
@@ -6340,15 +6515,19 @@ If you want to display only key label information, you can refer to the code sni
 {{if (index .Labels "mode")}}**mode**：{{index .Labels "mode"}}{{end}}
 {{if (index .Labels "runbook_url")}}**runbook_url**：{{index .Labels "runbook_url"}}{{end}}
 \`\`\`
+</div>
+
+<div class="wecom_app hide">
 
 ## 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}}
@@ -6372,16 +6551,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**
 
+</div>
 
-**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 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}}
@@ -6392,18 +6574,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}}
@@ -6418,16 +6600,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>
 
-## Zoom Bot
+<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
 ---
-- 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:
+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 \`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": {
@@ -6439,7 +6997,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
@@ -6447,7 +7005,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,
@@ -6456,7 +7014,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
@@ -6464,7 +7022,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
@@ -6472,7 +7030,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
@@ -6480,7 +7038,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
@@ -6488,7 +7046,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
@@ -6496,12 +7054,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
@@ -6509,7 +7067,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
@@ -6518,105 +7076,112 @@ 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>
+
+<div class="email hide">
 
 ## 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"/>
 
-`,X={CustomAlert:n,Email:t,N9e:a,Prometheus:o,Grafana:i,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor: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:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:V,MicrosoftTeams:z,AlertWebhook:K,IncidentWebhook:Z,CustomAction:J,Templates:Q,HuaweiyunAPM:q};module.exports=X;
+</div>`,ne={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:L,HuaweiyunLTS:_,GoogleCM:F,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:D,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:H,Lark:$,Dingtalk:B,Wecom:z,Slack:V,MicrosoftTeams:J,AlertWebhook:K,IncidentWebhook:Z,CustomAction:Q,Templates:ee,HuaweiyunAPM:q,JiraSync:X,ZStack:j};module.exports=ne;