npm - flashduty-knowledge-base - Versions diffs - 1.1.0 → 1.2.0-beta.1 - Mend

flashduty-knowledge-base 1.1.0 → 1.2.0-beta.1

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

Files changed (5) hide show

package/dist/{en.js → esm/en.js} +171 -180
package/dist/{zh.cjs → esm/zh.js} +115 -91
package/dist/{en.cjs → iife/en.js} +242 -196
package/dist/{zh.js → iife/zh.js} +189 -220
package/package.json +11 -3

package/dist/{en.cjs → iife/en.js} RENAMED Viewed

@@ -1,115 +1,131 @@
-"use strict";Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const n=`---
-title: "Standard Alert Integration Guide"
-description: "Push alerts from your own system to Flashduty using standard protocols to achieve automated alert noise reduction."
-date: "2024-05-11T10:00:00+08:00"
+(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"
 url: "https://docs.flashcat.cloud/en/flashduty/custom-alert-integration-guide"
 ---
-Push alerts from your own system to Flashduty using standard protocols to achieve automated alert noise reduction.
+Push alert events from your own system to Flashduty through standard protocols to achieve automated alert noise reduction.
 :::tips
-Flashduty has already adapted webhook protocols for most common alert systems. For these systems, you should first use their corresponding integrations for simplicity. This integration provides a standard HTTP interface that requires development adaptation. The advantage is that you can push any alerts you want to handle through on-call.
+Flashduty has already adapted webhook protocols for most common alert systems. For these systems, you should first use the corresponding integration for simplicity. This integration provides a standard HTTP interface that requires your development for adaptation. The advantage is that you can push any alert events you want to handle through on-call.
 :::
-<div class="hide">
 ## Steps
 ---
 ### In Flashduty
-You can obtain a push URL through either of these two methods:
+You can obtain an integration push URL through either of the following two methods:
-#### Using Private Integration
+#### Using Dedicated Integration
-Choose this method when you don't need to route alerts to different channels. This is the simpler option.
+When you don't need to route alert events to different collaboration spaces, this method is preferred as it's simpler.
 <details>
   <summary>Expand</summary>
-  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
-  2. Select the **Integration** tab, click **Add Integration**, and enter the integration page
-  3. Choose **Standard Alert** 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
+  1. Enter the Flashduty console, select **Collaboration Space**, and enter the details page of a space
+  2. Select the **Integrations** tab, click **Add Integration**, and enter the add integration page
+  3. Select **Standard Alert Event** integration, 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 payload information.
+When you need to route alert events to different collaboration spaces based on the alert event's Payload information, this method is preferred.
 <details>
   <summary>Expand</summary>
-  1. Go to the Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
-  2. Select **Standard Alert** 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
+  1. Enter the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
+  2. Select **Standard Alert Event** integration:
+        - **Integration Name**: Define a name for the current integration
+  3. Click **Save** and copy the newly generated **Push URL** on the current page for later use
+  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different collaboration spaces based on conditions, or set a default collaboration space as a fallback, and adjust as needed later
   5. Complete
 </details>
-</div>
 ## I. Request Description
+---
 ### Request Method
+<div class="md-block">
 POST, Content-Type:"application/json"
+</div>
 ### Request Parameters:
-QueryString must include the integration_key parameter for access control.
+<div class="md-block">
+#### Headers:
+Field|Required|Type|Description
+:-:|:-:|:-:|:---
+| Content-Type | Yes | string | Fixed value: \`application/json\`
-JsonBody parameters are as follows:
+#### Query Strings:
+Field|Required|Type|Description
+:-:|:-:|:-:|:---
+| integration_key | Yes | string | Integration key for access control. Obtained after adding integration.
-|     Field     | Required |  Type  | Description                                                                                                                                                                                                                                    |
-| :----------: | :------: | :----: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| event_status |   Yes    | string | Alert event status, enumerated values: Critical, Warning, Info, Ok                                                                                                                                                                               |
-|  alert_key   |   Yes    | string | Event grouping basis, different alert events are grouped into one alert based on this field and time window                                                                                                                                      |
-|  title_rule  |    No    | string | Alert title generation rule, in the form of \`$a::b::$c\`, substrings are separated by \`::\`; each substring can be a fixed string or a variable prefixed with \`$\`. Variable content will be extracted from the labels parameter, error if not found. By default, the system will generate rules by extracting service, cluster, resource, and check tags from the labels field |
-| description  |    No    | string | Alert description, no more than 2048 characters                                                                                                                                                                                                  |
-|    labels    |    No    |  map   | Alert label collection, key is the label name, value is the label value. Labels are event descriptions, crucial for subsequent correlation and noise reduction. 1. Label keys and values are case-sensitive strings. 2. Label keys should not exceed 128 characters. 3. Maximum 50 labels allowed. \`Label content reference\` [Best Practices](#Best-Practices) |
+#### Payload:
+Field|Required|Type|Description
+:-:|:-:|:-:|:---
+| title_rule | Yes | string | Alert title, no more than \`512\` characters, will be truncated if exceeded.<br><br>Supports dynamic title generation based on alert content, see [Customizing Incidents](https://docs.flashcat.cloud/en/flashduty/customize-incident-attrs) for generation rules.
+| event_status | Yes | string | Alert status.<br><br>Enumerated values (case-sensitive): *Critical*, *Warning*, *Info*, *Ok*.<br><br>When specified as Ok, it means automatic recovery of the alert.
+| alert_key | No | string | Alert identifier, used to update or automatically recover existing alerts.<br><br>You can customize this value, but it cannot exceed \`255\` characters. You can also rely on system auto-generation, this value will be returned in the response.<br><br>If you're reporting a recovery event, this value must exist.
+| description | No | string | Alert description, no more than \`2048\` characters, will be truncated if exceeded.
+| labels | No | map | Alert label collection, key is the label name, value is the label value:<br><br>1. Both key and value of labels are string type, case-sensitive.<br>2. Label key should not exceed \`128\` characters, following Prometheus label naming conventions. Value should not exceed \`2048\` characters, will be truncated if exceeded.<br>3. Maximum of \`50\` labels. See \`Label Content Reference\` in [Best Practices](#best-practices).<br><br>Example: "resource": "171.26.23.22", "check": "api latency > 500ms"
 </div>
 ### Response
-<div class="md-block">
-Body:
-Parameter|Required|Type|Description
-----------|---|---|---
-request_id|Yes|string|Request trace id for issue tracking
+Field Name|Required|Type|Description
+:-:|:-:|:-:|:---
+request_id|Yes|string|Request ID for trace tracking
 error|No|[Error](#Error)|Error description, returned only when an error occurs
+data|No|[Data](#Data)|Report information
+<span id="Data"></span>
+Data:
+| Field Name | Required | Type | Description |
+:-:|:-:|:-:|:---
+| alert_key | No | string | Alert identifier, can be used to report recovery events. If you specified an alert_key when reporting the event, this value remains unchanged. Otherwise, it's automatically generated by the system. |
 <span id="Error"></span>
 Error:
-| Parameter | Optional | Type   | Description     |
-| --------- | -------- | ------ | --------------- |
-| code      | Yes      | string | Error code      |
-| message   | Yes      | string | Error message   |
+| Field Name | Required | Type | Description |
+:-:|:-:|:-:|:---
+| code | Yes | string | Error code, see [Code](#Code) for enumerated values |
+| message | No | string | Error description |
 <span id="Code"></span>
 Code:
-| Error Code           | HTTP Status | Description                                        |
-| -------------------- | ----------- | -------------------------------------------------- |
-| InvalidParameter     | 400         | Parameter error                                    |
-| InvalidContentType   | 400         | Content-Type not supported                         |
-| MethodNotAllowed     | 400         | HTTP method not supported                          |
-| Unauthorized         | 401         | Login authentication failed                        |
-| AccessDenied         | 403         | Permission authentication failed                   |
-| RequestTooFrequently | 429         | Request too frequent                               |
-| RouteNotFound        | 404         | Request Method+Path not matched                    |
-| ResourceNotFound     | 400         | Account resource not purchased, proceed to billing |
-| InternalError        | 500         | Internal or unknown error                          |
-</div>
+| Error Code | HTTP Status | Description |
+| :-:|:-:| ------------------ |
+| InvalidParameter | 400 | Parameter error |
+| InvalidContentType | 400 | Content-Type not supported |
+| MethodNotAllowed | 400 | HTTP Method not supported |
+| Unauthorized | 401 | Login authentication failed |
+| AccessDenied | 403 | Permission authentication failed |
+| RequestTooFrequently | 429 | Request too frequent |
+| RouteNotFound | 404 | Request Method+Path not matched |
+| ResourceNotFound | 400 | Account hasn't purchased resources, please go to the cost center to place an order |
+| NoLicense | 400 | Account has insufficient subscription licenses, please upgrade or purchase subscription in the cost center |
+| InternalError | 500 | Internal or unknown error |
-### Request Example
+### II. Request Example
+---
 Request:
@@ -118,9 +134,7 @@ curl -X POST '{api_host}/event/push/alert/standard?integration_key={integration_
 -H 'Content-Type: application/json' \\
 -d '{
     "event_status": "Warning",
-    "alert_key": "asdfjl1234asdf2s",
-    "description": "cpu idle low than 20%",
-    "title_rule": "$cluster::$resource::$check",
+    "title_rule": "cpu idle low than 20%",
     "labels": {
         "service": "engine",
         "cluster":"nj",
@@ -131,15 +145,18 @@ curl -X POST '{api_host}/event/push/alert/standard?integration_key={integration_
 }' -v
 \`\`\`
-Successful response:
+Successful Response:
 \`\`\`
 {
-    "request_id": "0ace00116215ab4ca0ec5244b8fc54b0"
+    "request_id": "0ace00116215ab4ca0ec5244b8fc54b0",
+    "data": {
+        "alert_key": "9qJ798NJoXS4UMVB5SHsNj"
+    }
 }
 \`\`\`
-Failed response:
+Failed Response:
 \`\`\`
 {
@@ -151,20 +168,49 @@ Failed response:
 }
 \`\`\`
-<span id="Best-Practices"></span>
-## II. Best Practices
+## III. Best Practices <span id="best-practices"></span>
+---
-1. Send events to Flashcat Cloud when alert status changes or labels are updated
+1. Send events to Flashduty when alert status changes
 2. When an alert recovers, send an event with status Ok to close the alert. Otherwise, the alert will remain open. If your alert system doesn't have recovery events, we recommend manually sending recovery events
-3. Labels are event descriptions. You should enrich label content as much as possible (specified when sending or generated through enrichment rules), such as:
-   - Alert source information: host, cluster, check, or metric
-   - Alert ownership information: team, owner
-   - Alert category information: class (api, db, net)
-   - Alert details link for jumping to the alert system
-4. alert_key is used to group different alert events into one alert. For example, when a host's cpu.idle drops below threshold, escalates, and recovers, you should send 3 events with the same alert_key, which will be grouped into one alert
-5. title_rule is used to generate alert display titles. It's recommended to include the source system alert name (commonly defined as rule_name or check) and add cluster, host, and other information as auxiliary reminders
-`,t=`---
+3. Labels are event descriptions, and label content should be as rich as possible (specified when sending, or generated through enrichment rules), such as:
+   - Alert source, like host, cluster, check, or metric
+   - Alert ownership information, like team, owner
+   - Alert category information, like class (api, db, net)
+## IV. FAQ
+---
+<details>
+  <summary>Why haven't I received alerts in Flashduty?</summary>
+  #### In Flashduty
+  1. Check if the integration shows **Latest Event Time**? If not, it means Flashduty hasn't received the push, prioritize checking your system.
+  2. If you're using **Shared Integration**, first confirm if you've configured **Routing Rules**. Without routing rules, the system will directly reject new pushes as there's no collaboration space to handle your alerts. In this case, simply configure routing rules to your desired space.
+  #### In Your System
+  1. Confirm that your request URL exactly matches the URL in the integration details.
+  2. Confirm that your service can access the external domain api.flashcat.cloud. If not, you need to enable external network access for the server or specifically for Flashduty's domain.
+  3. Print Flashduty service's response to check for clear information.
+  If you still can't find the root cause after these steps, please contact us with the **request_id** from the request response.
+</details>
+<details>
+  <summary>Why was the push request successful but no new alerts or incidents were generated?</summary>
+  Flashduty uses a 2-layer noise reduction mechanism:
+  1. First, it checks for duplicate alert events. If your pushed event is identical to a previously pushed event, the new event will be discarded.
+  2. If the new event's status and description match the status, title, and description of the last event of its corresponding alert, the new event will be discarded while updating the alert's attributes.
+  3. The new event might be discarded due to matching exclusion, discard, suppression, or silence rules.
+  4. When a new event triggers a new alert, the system enters the second layer of noise reduction check, determining if the new alert can be merged into an active incident. If possible, it will only merge into the existing incident without generating a new one.
+  For more information, please refer to [Alert Noise Reduction](https://docs.flashcat.cloud/en/flashduty/what-is-noise-reduction).
+</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"
@@ -265,7 +311,7 @@ attachment_stripped = true
 Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
-`,a=`---
+`,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"
@@ -423,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"
@@ -605,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"
@@ -718,7 +764,7 @@ The system extracts the \`severity\`, \`priority\`, and \`level\` labels from al
 | ok               | Ok       | Resolved |
 </div>
-`,s=`---
+`,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"
@@ -1024,7 +1070,7 @@ Zabbix to Flashduty alert severity mapping:
 | Information    | Info           | Info     |
 | Not classified | Info           | Info     |
-</dv>`,r=`---
+</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"
@@ -1110,7 +1156,7 @@ Uptime Kuma to Flashduty alert severity mapping:
 | Warning     | Warning  | Warning |
 | Info     | Info     | Info |
-</div>`,l=`---
+</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"
@@ -1196,7 +1242,7 @@ Alibaba Cloud ARMS monitoring to Flashduty alert severity mapping:
 | P4     | Info     | Info |
 </div>
-`,d=`---
+`,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"
@@ -1283,7 +1329,7 @@ Alibaba Cloud Monitor event alert to Flashduty severity level mapping:
 | WARNING              | Warning   | Warning |
 | INFO                 | Info      | Info |
-</div>`,c=`---
+</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"
@@ -1508,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"
@@ -1587,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"
@@ -1662,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"
@@ -1751,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">
@@ -1848,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"
@@ -1932,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"
@@ -2094,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"
@@ -2192,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"
@@ -2334,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"
@@ -2407,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"
@@ -2499,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"
@@ -2687,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"
@@ -2782,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"
@@ -2881,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"
@@ -2987,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"
@@ -3078,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"
@@ -3180,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"
@@ -3287,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"
@@ -3400,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"
@@ -3491,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"
@@ -3566,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"
@@ -3726,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"
@@ -3829,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"
@@ -3918,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"
@@ -4005,7 +4124,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 </div>
-`,P=`---
+`,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"
@@ -4142,7 +4261,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 </div>
-`,N=`---
+`,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"
@@ -4276,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"
@@ -4348,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"
@@ -4435,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"
@@ -4520,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"
@@ -4650,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"
@@ -4724,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
@@ -4859,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"
@@ -5015,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"
@@ -5094,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"
@@ -5148,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"
@@ -5243,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>
@@ -5411,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>
@@ -5617,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
@@ -5864,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"
@@ -6467,4 +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">
-`;exports.AWSCW=e;exports.AWSEventBridge=A;exports.AlertWebhook=z;exports.AliyunARMS=l;exports.AliyunCm=c;exports.AliyunCmEvent=d;exports.AliyunSLS=e;exports.AppDynamics=T;exports.AzureMonitor=h;exports.BaiDuBCM=u;exports.CustomAction=Z;exports.CustomAlert=n;exports.CustomChange=q;exports.Dingtalk=$;exports.Dynatrace=L;exports.Email=t;exports.GoogleCM=x;exports.Grafana=i;exports.Graylog=k;exports.Guance=G;exports.HuaWeiCES=g;exports.HuaweiyunLTS=F;exports.IncidentWebhook=K;exports.InfluxDB=p;exports.Jiankongbao=_;exports.Jira=O;exports.Lark=j;exports.Meraki=M;exports.MicrosoftTeams=V;exports.N9e=a;exports.OceanBase=C;exports.OpManager=N;exports.OpenFalcon=m;exports.PagerDuty=f;exports.Prometheus=o;exports.Sentry=S;exports.Skywalking=I;exports.Slack=B;exports.SolarWinds=U;exports.Splunk=R;exports.StateCloud=W;exports.Templates=J;exports.TencentBK=y;exports.TencentCLS=v;exports.TencentCm=b;exports.TencentEb=w;exports.UptimeKuma=r;exports.VolcEngineEvent=D;exports.VolcEngineMetric=E;exports.VolcEngineTLS=P;exports.Wecom=H;exports.Zabbix=s;exports.Zilliz=Y;
+`};n.FlashDocsEn=u})(window);