flashduty-knowledge-base 1.1.1 → 1.2.0-beta.2

package/dist/{en.js → iife/en.js}

@@ -1,4 +1,4 @@
-const e = `---
+(function(n){"use strict";const t=`---
 title: "Standard Alert Event Integration Guide"
 description: "Push alert events from your own system to Flashduty through standard protocols to achieve automated alert noise reduction."
 date: "2025-01-20T10:00:00+08:00"
@@ -210,7 +210,7 @@ Failed Response:
   4. When a new event triggers a new alert, the system enters the second layer of noise reduction check, determining if the new alert can be merged into an active incident. If possible, it will only merge into the existing incident without generating a new one.
 
   For more information, please refer to [Alert Noise Reduction](https://docs.flashcat.cloud/en/flashduty/what-is-noise-reduction).
-</details> `, n = `---
+</details> `,a=`---
 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"
@@ -311,7 +311,7 @@ attachment_stripped = true
 
 Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
 
-`, t = `---
+`,o=`---
 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"
@@ -469,7 +469,7 @@ Nightingale/Flashcat to Flashduty alert severity mapping:
     
 </details>
 
-`, a = `---
+`,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 = `---
+`,s=`---
 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"
@@ -764,7 +764,7 @@ The system extracts the \`severity\`, \`priority\`, and \`level\` labels from al
 | ok               | Ok       | Resolved |
 
 </div>
-`, o = `---
+`,r=`---
 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"
@@ -1070,7 +1070,7 @@ Zabbix to Flashduty alert severity mapping:
 | Information    | Info           | Info     |
 | Not classified | Info           | Info     |
 
-</dv>`, s = `---
+</dv>`,l=`---
 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"
@@ -1156,7 +1156,7 @@ Uptime Kuma to Flashduty alert severity mapping:
 | Warning     | Warning  | Warning |
 | Info     | Info     | Info |
 
-</div>`, r = `---
+</div>`,d=`---
 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"
@@ -1242,7 +1242,7 @@ Alibaba Cloud ARMS monitoring to Flashduty alert severity mapping:
 | P4     | Info     | Info |
 
 </div>
-`, l = `---
+`,c=`---
 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"
@@ -1329,7 +1329,7 @@ Alibaba Cloud Monitor event alert to Flashduty severity level mapping:
 | WARNING              | Warning   | Warning |
 | INFO                 | Info      | Info |
 
-</div>`, d = `---
+</div>`,h=`---
 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"
@@ -1427,7 +1427,7 @@ Severity level mapping from Alibaba Cloud Monitor to Flashduty:
 | NODATA               | Info      | Info |
 
 </div>
-`, c = `---
+`,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"
@@ -1554,7 +1554,7 @@ Alibaba Cloud SLS monitoring to Flashduty alert severity mapping:
 | 2                | Info      | Info |
 
 </div>
-`, h = `---
+`,u={CustomAlert:t,Email:a,N9e:o,Prometheus:i,Grafana:s,Zabbix:r,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:c,AliyunCm:h,AliyunSLS:e,AWSCW:e,AzureMonitor:`---
 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"
@@ -1633,7 +1633,7 @@ Choose this method when you need to route alerts to different channels based on
 All CloudWatch metric alarms correspond to Flashduty "warning" severity level alerts.
 
 </div>
-`, u = `---
+`,BaiDuBCM:`---
 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"
@@ -1708,7 +1708,7 @@ Severity level mapping from Baidu Cloud Monitor to Flashduty:
 | Notice   | Info      | Info     |
 
 </div>
-`, g = `---
+`,HuaWeiCES:`---
 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"
@@ -1797,7 +1797,7 @@ Huawei Cloud CES to Flashduty alert severity mapping:
 | Info     | Info      | info     |
 
 </div>
-`, p = `Sync Influxdata alert events to Flashduty via webhook to achieve automated alert noise reduction.
+`,InfluxDB:`Sync Influxdata alert events to Flashduty via webhook to achieve automated alert noise reduction.
 
 <div class="hide">
 
@@ -1894,7 +1894,7 @@ Mapping relationship between Influxdata alert events and Flashduty alert severit
 | unknow     | Info           | Info |
 
 </div>
-`, m = `---
+`,OpenFalcon:`---
 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"
@@ -1978,7 +1978,7 @@ Open-Falcon to Flashduty alert severity mapping:
 | 6           | Info     | Info |
 
 </div>
-`, f = `---
+`,PagerDuty:`---
 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"
@@ -2140,7 +2140,7 @@ pagerduty_v2_payload_source: mysql.host.name
 4. Step 4: Restart ElastAlert and wait for alerts to trigger
 
 </div>
-`, y = `---
+`,TencentBK:`---
 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"
@@ -2238,7 +2238,7 @@ Alert severity mapping between BlueKing and Flashduty:
 | Notice   | Info      | info |
 
 </div>
-`, v = `---
+`,TencentCLS:`---
 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"
@@ -2380,7 +2380,7 @@ Tencent Cloud CLS monitoring alert level mapping to Flashduty:
 | Critical      | Critical  | Critical
 
 </div>
-`, b = `---
+`,TencentCm:`---
 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"
@@ -2453,7 +2453,7 @@ Choose this option when you need to route alerts to different channels based on
 All metric alerts from Tencent Cloud Monitor correspond to "warning" severity level alerts in Flashduty.
 
 </div>
-`, w = `---
+`,TencentEb:`---
 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"
@@ -2545,7 +2545,7 @@ As shown below:
 All Tencent Cloud EventBridge events correspond to "warning" severity level alerts in Flashduty.
 
 </div>
-`, C = `---
+`,OceanBase:`---
 title: "OceanBase Alert Events"
 description: "Synchronize OceanBase alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-05-23T10:00:00+08:00"
@@ -2733,7 +2733,7 @@ OCP Alert Notification - Single Alert
 |Notice|Info|Info|
 
 </div>
-`, k = `---
+`,Graylog:`---
 title: "Graylog Alert Events"
 description: "Sync Graylog alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-06-18T10:00:00+08:00"
@@ -2828,7 +2828,7 @@ Choose this option when you need to route alerts to different channels based on
 |1|Info|Info|
 
 </div>
-`, I = `---
+`,Skywalking:`---
 title: "Skywalking Alert Events"
 description: "Sync Skywalking alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-06-20T10:00:00+08:00"
@@ -2927,7 +2927,7 @@ hooks:
 |Others or Empty|Info|Info|
 
 </div>
-`, S = `---
+`,Sentry:`---
 title: "Sentry Alert Events"
 description: "Sync Sentry alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -3033,7 +3033,7 @@ Sentry provides two types of alert mechanisms: Issue Alerts and Metric Alerts. W
 |resolved|Ok|Resolved|
 
 </div>
-`, _ = `---
+`,Jiankongbao:`---
 title: "Jiankongbao Alert Events"
 description: "Sync Jiankongbao alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10: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>
-`, A = `---
+`,AWSEventBridge:`---
 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 = `---
+`,Dynatrace:`---
 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 = `---
+`,HuaweiyunLTS:`---
 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 = `---
+`,GoogleCM:`---
 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"
@@ -3537,7 +3537,80 @@ Choose this option when you need to route alerts to different channels based on
 |No severity|Info|Info|
 
 </div>
-`, R = `---
+`,Zilliz:`---
+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"
+url: "https://docs.flashcat.cloud/en/flashduty/zilliz-integration-guide"
+---
+
+Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using 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 **Zilliz** 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 **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
+  5. Done
+    
+</details>
+</div>
+
+## In Zilliz
+---
+
+<div class="md-block">
+
+## I. Alert Push Configuration
+
+1. Log in to your \`Zilliz\` console, create or modify an \`Alert\` in \`Project Alerts\`
+2. In the \`Send to\` section of the \`Alert\` editing page, select \`Webhook\` and fill in the <span class='integration_url'>push URL</span> from your alert integration
+3. Check \`Alert Resolution Notification\`, select other options as needed
+4. Click \`Save\` or \`Create\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zilliz-1.png" />
+
+</dev>
+
+## II. Status Mapping
+
+<div class="md-block">
+
+| Zilliz    | Flashduty | Status   |
+| --------- | --------- | -------- |
+| CRITICAL  | Critical  | Critical |
+| WARNING   | Warning   | Warning  |
+
+</div>
+
+`,Splunk:`---
 title: "Splunk Alert Events"
 description: "Sync Splunk alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3612,7 +3685,7 @@ Choose this method when you need to route alerts to different channels based on
 <div class="md-block">
 Since Splunk alert events don't differentiate severity levels, all alert events pushed from Splunk to Flashduty will have a Warning status and won't include recovery events.
 </div>
-`, T = `---
+`,AppDynamics:`---
 title: "AppDynamics Alert Integration"
 description: "Sync AppDynamics alerts to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -3772,7 +3845,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 |INFO|Info|Info|
 
 </div>
-`, U = `---
+`,SolarWinds:`---
 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"
@@ -3875,7 +3948,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`, E = `---
+`,VolcEngineMetric:`---
 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 +4037,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`, D = `---
+`,VolcEngineEvent:`---
 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"
@@ -4051,7 +4124,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`, N = `---
+`,VolcEngineTLS:`---
 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"
@@ -4188,7 +4261,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 </div>
-`, P = `---
+`,OpManager:`---
 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"
@@ -4322,7 +4395,7 @@ Choose this method when you need to route alerts to different channels based on
 | Attention  | Info           | Info |
 
 </div>
-`, M = `---
+`,Meraki:`---
 title: "Meraki Alert Events"
 description: "Sync Meraki alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4394,7 +4467,7 @@ Choose this option when you need to route alerts to different channels based on
 | informational      | Info     | Info |
 
 </div>
-`, W = `---
+`,StateCloud:`---
 title: "StateCloud Alert Events"
 description: "Sync StateCloud alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4481,7 +4554,7 @@ Choose this option when you need to route alerts to different channels based on
 | North | Beijing2/Changchun/Harbin/North China/Inner Mongolia3/Qingdao/Shenyang3/Shijiazhuang/Taiyuan/Tianjin/Zhengzhou |
 
 </div>
-`, G = `---
+`,Guance:`---
 title: "Guance Alert Events"
 description: "Sync Guance alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4566,80 +4639,7 @@ Choose this option when you need to route alerts to different channels based on
 | Data Missing | Info | Info |
 
 </div>
-`, Y = `---
-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"
-url: "https://docs.flashcat.cloud/en/flashduty/zilliz-integration-guide"
----
-
-Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction.
-
-<div class="hide">
-
-## In Flashduty
----
-You can obtain an integration push URL through either of these two methods:
-
-### Using 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 **Zilliz** 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 **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
-  5. Done
-    
-</details>
-</div>
-
-## In Zilliz
----
-
-<div class="md-block">
-
-## I. Alert Push Configuration
-
-1. Log in to your \`Zilliz\` console, create or modify an \`Alert\` in \`Project Alerts\`
-2. In the \`Send to\` section of the \`Alert\` editing page, select \`Webhook\` and fill in the <span class='integration_url'>push URL</span> from your alert integration
-3. Check \`Alert Resolution Notification\`, select other options as needed
-4. Click \`Save\` or \`Create\` to complete the configuration
-
-<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zilliz-1.png" />
-
-</dev>
-
-## II. Status Mapping
-
-<div class="md-block">
-
-| Zilliz    | Flashduty | Status   |
-| --------- | --------- | -------- |
-| CRITICAL  | Critical  | Critical |
-| WARNING   | Warning   | Warning  |
-
-</div>
-
-`, q = `---
+`,CustomChange:`---
 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"
@@ -4696,7 +4696,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`, O = `---
+`,Jira:`---
 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"
@@ -4770,7 +4770,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`, j = `---
+`,Lark:`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -4905,7 +4905,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`, $ = `---
+    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,Dingtalk:`---
 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"
@@ -5061,7 +5061,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
-`, H = `---
+`,Wecom:`---
 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"
@@ -5140,7 +5140,7 @@ 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
-`, B = `---
+`,Slack:`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2024-05-11T10:00:00+08:00"
@@ -5194,7 +5194,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`, V = `---
+   - If the error persists, contact customer support`,MicrosoftTeams:`---
 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"
@@ -5289,7 +5289,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`, z = `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.
+`,AlertWebhook:`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>
 
@@ -5457,7 +5457,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.
+`,IncidentWebhook:`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>
 
@@ -5663,7 +5663,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`,CustomAction:`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
 
@@ -5910,7 +5910,7 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
 
 ### Update Status Page
 
-When an incident is confirmed to affect online services, trigger external status page updates to prompt`, J = `---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,Templates:`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -6513,59 +6513,4 @@ If custom content is not set, the system default template will be used for notif
 As shown below:
 <img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
 
-`;
-export {
-  c as AWSCW,
-  A as AWSEventBridge,
-  z as AlertWebhook,
-  r as AliyunARMS,
-  d as AliyunCm,
-  l as AliyunCmEvent,
-  c as AliyunSLS,
-  T as AppDynamics,
-  h as AzureMonitor,
-  u as BaiDuBCM,
-  Z as CustomAction,
-  e as CustomAlert,
-  q as CustomChange,
-  $ as Dingtalk,
-  L as Dynatrace,
-  n as Email,
-  x as GoogleCM,
-  i as Grafana,
-  k as Graylog,
-  G as Guance,
-  g as HuaWeiCES,
-  F as HuaweiyunLTS,
-  K as IncidentWebhook,
-  p as InfluxDB,
-  _ as Jiankongbao,
-  O as Jira,
-  j as Lark,
-  M as Meraki,
-  V as MicrosoftTeams,
-  t as N9e,
-  C as OceanBase,
-  P as OpManager,
-  m as OpenFalcon,
-  f as PagerDuty,
-  a as Prometheus,
-  S as Sentry,
-  I as Skywalking,
-  B as Slack,
-  U as SolarWinds,
-  R as Splunk,
-  W as StateCloud,
-  J as Templates,
-  y as TencentBK,
-  v as TencentCLS,
-  b as TencentCm,
-  w as TencentEb,
-  s as UptimeKuma,
-  D as VolcEngineEvent,
-  E as VolcEngineMetric,
-  N as VolcEngineTLS,
-  H as Wecom,
-  o as Zabbix,
-  Y as Zilliz
-};
+`};n.FlashDocsEn=u})(window);