flashduty-knowledge-base 1.3.1 → 1.3.3

package/dist/en.d.ts

@@ -60,7 +60,11 @@ declare const docs: {
     ElastAlert2: string;
     DingtalkAlert: string;
     FeishuAlert: string;
+    VolcEngineDetect: string;
     Link: string;
     ServiceNowSync: string;
+    Monit: string;
+    Rum: string;
+    Cloudflare: string;
 };
 export default docs;

package/dist/esm/en.js

@@ -309,8 +309,7 @@ attachment_stripped = true
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
-
+Currently, all alerts pushed to Flashduty through the email integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
 `,a=`---
 title: "Nightingale/Flashcat Integration"
 description: "Push alert events from Nightingale (n9e) or Flashcat to Flashduty via webhook. When an alert is triggered, send a trigger event to Flashduty; when an alert recovers, send a recovery event to Flashduty"
@@ -3267,7 +3266,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"
@@ -3374,7 +3373,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`,L=`---
+`,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"
@@ -3487,7 +3486,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,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"
@@ -3813,7 +3812,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 |INFO|Info|Info|
 
 </div>
-`,D=`---
+`,U=`---
 title: "SolarWinds Alert Events"
 description: "Sync SolarWinds alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3916,7 +3915,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,U=`---
+`,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"
@@ -4005,7 +4004,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,N=`---
+`,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"
@@ -4092,7 +4091,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,E=`---
+`,N=`---
 title: "Volcengine Log Service (TLS) Alert Events"
 description: "Sync Volcengine Log Service (TLS) alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4229,7 +4228,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 </div>
-`,P=`---
+`,M=`---
 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"
@@ -4363,7 +4362,7 @@ Choose this method when you need to route alerts to different channels based on
 | Attention  | Info           | Info |
 
 </div>
-`,M=`---
+`,P=`---
 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"
@@ -4874,7 +4873,7 @@ Choose this method when you need to route alerts to different channels based on
 
 </div>
 
-`,Y=`---
+`,H=`---
 title: "Keep Alert Integration Guide"
 description: "Push alert events to Flashduty through Keep's Provider to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -4955,7 +4954,7 @@ Field|Required|Type|Definition
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/keep-2.png" />
 
-`,H=`---
+`,Y=`---
 title: "ElastAlert2 Alert Integration Guide"
 description: "Push alert events to Flashduty through ElastAlert2's Provider to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -5157,9 +5156,8 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
-
-`,B=`---
+Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+`,V=`---
 title: "Feishu Alert Integration"
 description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
 date: "2025-05-19T10:00:00+08:00"
@@ -5240,9 +5238,201 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through Feishu Alert integration are set to Warning severity.
+Currently, all alerts pushed to Flashduty through the Feishu(lark) integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+`,B=`---
+title: "Volcengine Cloud-Detect Alert Events"
+description: "Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/volcengine-tls-integration-guide"
+---
 
-`,V=`---
+Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Volcengine Detect** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Volcengine Detect** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+## In Volcengine
+---
+
+<div class="md-block">
+
+## 一、Create Notification Object
+
+### Step 1: Create Notification Object
+1. Login to your \`Volcengine\` console, find \`Alert Manager\` in the \`Notify Object\` menu
+2. Click \`System Integration\`, click \`Create System Integration\` or edit the existing endpoint
+3. In the edit page, enter Flashduty as the name and fill in the <span class='integration_url'>push URL</span> for the alert integration in the URL field.
+5. Click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/volcengine-1.png" />
+
+### Step 2: Use Notification Object in Alert Policy
+1. Login to your \`Volcengine\` console, find \`Alert Manager\` in the \`Alert Policy\` menu
+2. Click \`Create Alert Policy\` or edit the existing alert policy
+3. In the edit page, select the created \`Flashduty\` Endpoint
+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/zh/fd/volcengine-2.png" />
+
+</dev>
+
+## 二、Status Mapping
+
+<div class="md-block">
+
+| Detect |  Flashduty | Status |
+| ---------- | -------- | ---- |
+| P0  | Critical | Critical|
+| P2   | Warning  |  Warning|
+
+</div>
+
+`,z=`---
+title: "Monit Alert Integration"
+description: "Flashduty Monit alert integration, Monit service reports alerts through this integration"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/monit-alert-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+
+When you enable the Monit service, the system will automatically create this integration for you. This integration is used to collect alert events generated by the Monit service.
+
+:::tips
+You cannot modify or delete this integration. However, you can manage the label enrichment, alert pipeline, and routing rules under the integration.
+:::
+
+## How to Enable Monit Alerts
+
+Go to the \`Monit\` - \`Alert Rules\` - \`Rule Details\` page to configure monitoring metrics and threshold conditions, and enable alerts. You can choose to deliver alerts to multiple channels. Alert notification rules follow the escalation rules under the channel, and you can set responders for the team to assign to responders when alerts occur.
+
+![2025-08-19-20-35-45](https://docs-cdn.flashcat.cloud/images/png/59c9d2566db9a0482fb2eabb729ea739.png)
+
+In some cases, you may want to route alerts generated by the same alert rule to different channels based on conditions. In this case, you can choose to deliver alerts directly to the integration rather than to the channels, and set routing rules under the current integration.
+`,K=`---
+title: "RUM Alert Integration"
+description: "Flashduty RUM alert integration, RUM service reports alerts through this integration"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/rum-alert-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+
+When you enable the RUM service, the system will automatically create this integration for you. This integration is used to collect alert events generated by the RUM service.
+
+:::tips
+You cannot modify or delete this integration. However, you can manage the label enrichment, alert pipeline, and routing rules under the integration.
+:::
+
+## How to Enable RUM Alerts
+
+Go to the \`RUM\` - \`Application Details\` - \`Alert Settings\` page to enable alerts. You can choose to deliver alerts to multiple channels. Alert notification rules follow the escalation rules under the channel, and you can set responders for the team to assign to responders when alerts occur.
+
+![2025-08-20-10-16-14](https://docs-cdn.flashcat.cloud/images/png/b6ad24809a2ee8f0b3c0b38988b46030.png)
+
+For more information, please refer to [RUM Issue Alerting](https://docs.flashcat.cloud/en/flashduty/rum/issue-alerting?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+`,J=`---
+title: "Cloudflare Alert Events"
+description: "Sync Cloudflaret 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/Cloudflare-integration-guide"
+---
+
+Sync Cloudflare alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Cloudflare** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Cloudflare** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+
+## In Cloudflare
+---
+
+<div class="md-block">
+
+## 一、Create Notification Object
+1. Log in to the \`Cloudflare dashboard\` and select your account.
+2. Go to \`Notifications\` > \`Destinations\`.
+3. In the \`Webhooks\` card, select Create.
+4. In the edit page, enter Flashduty as the name and fill in the <span class='integration_url'>push URL</span> for the alert integration in the URL field.
+5. Select \`Save and Test\` to finish setting up your webhook.
+
+After configuring the Webhook channel, you can use it in notification policies.
+
+</dev>
+
+## 二、Status Mapping
+
+<div class="md-block">
+
+Currently, all alerts pushed to Flashduty through the Cloudflare integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+
+</div>
+
+`,Z=`---
 title: "Custom Change Event Integration Guide"
 description: "Push change events from your own systems to Flashduty using standard protocols. Most incidents are caused by changes, and the correlation between changes and alerts helps quickly identify incident causes."
 date: "2025-05-19T10:00:00+08:00"
@@ -5270,7 +5460,7 @@ Flashduty has already adapted webhook protocols for several commonly used ticket
 ## Implementation Protocol
 --- 
 
-Please refer to the [Developer Documentation](https://developer.flashcat.cloud/en/flashduty/event-api/change-event) to complete the protocol development.
+Please refer to the [Developer Documentation](https://developer-en.flashcat.cloud/en/flashduty/event-api/change-event) to complete the protocol development.
 
 ## Best Practices
 ---
@@ -5299,7 +5489,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,z=`---
+`,Q=`---
 title: "Jira Issue Events"
 description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
 date: "2025-05-19T10:00:00+08:00"
@@ -5373,7 +5563,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,K=`---
+`,X=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5508,7 +5698,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`,J=`---
+    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,ee=`---
 title: "Dingtalk Integration"
 description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
 date: "2025-05-19T10:00:00+08:00"
@@ -5664,7 +5854,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
-`,Z=`---
+`,ne=`---
 title: "WeCom Integration"
 description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
 date: "2025-05-19T10:00:00+08:00"
@@ -5743,7 +5933,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
-`,Q=`---
+`,te=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2025-05-19T10:00:00+08:00"
@@ -5797,7 +5987,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`,X=`---
+   - If the error persists, contact customer support`,ae=`---
 title: "Microsoft Teams Integration"
 description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
 date: "2025-05-19T10:00:00+08:00"
@@ -5925,7 +6115,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`,ee=`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.
+`,ie=`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>
 
@@ -6093,7 +6283,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
-`,ne=`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.
+`,oe=`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>
 
@@ -6193,7 +6383,7 @@ acknowledged_at | int64| No | Acknowledgment time
 |      fields       |  map[string]interface{}  |  No   | Custom field key-value pairs, Key is string, Value can be any type depending on field type |
 |      creator      |  [Person](#Person)  |  No   | Creator information, exists only for manually created incidents |
 |       closer      |  [Person](#Person)  |  No   | Closer information, exists only for manually closed incidents |
-|    responders     | [][Responder](#Responder) |  No   | List of responder information |
+|    responders     | [][Responder](#Responder) |  No   | List of responder information, only exists after the incident is assigned. For i_new events, this value may be empty |
 |     alert_cnt     |        int64        |  No   | Number of associated alerts |
 |     channel_id     |        int64        |  No   | Channel ID, 0 means not belonging to any channel |
 |     channel_name   |        string        |  No   | Channel name |
@@ -6300,7 +6490,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`,te=`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`,se=`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
 
@@ -6547,7 +6737,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`,ae=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,re=`---
 title: "Jira Sync"
 description: "Sync incidents with Jira issues through Jira Sync Webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -6629,7 +6819,7 @@ In the Integration Center, select **Webhook**, choose **Jira Sync** integration,
 
 - Flashduty syncs information according to default field mappings and your custom field configurations. If your Jira issue type has required fields without mapping relationships, Jira issue creation may fail.
 - Jira issue details are accessed using project KEY + number format. If you modify the project KEY, saved issue URLs in Flashduty may become inaccessible, so please modify project KEYs with caution.
-`,ie=`---
+`,le=`---
 title: "ServiceNow Sync"
 description: "Sync incidents with ServiceNow Incidents through ServiceNow sync webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -6913,7 +7103,7 @@ Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
 | Low        | Info      |       |
 | Medium     | Warning   |       |
 | High       | Critical  |       |
-`,oe=`---
+`,de=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -8033,7 +8223,7 @@ As shown in the image below:
 
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
-</div>`,se=`---
+</div>`,ce=`---
 title: "Link Integration"
 description: "Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information"
 date: "2025-05-19T10:00:00+08:00"
@@ -8090,4 +8280,4 @@ https://cmdb.com/vm?sn=VM123456
 1. When referenced content does not exist, Link integration will still generate the corresponding link but will not be able to retrieve the value
 2. Each channel can bind up to three Link integrations
 3. Pay attention to reference syntax; improper variable reference formatting will result in failure to retrieve corresponding values
-`,re={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:u,BaiDuBCM:h,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:_,HuaweiyunLTS:L,GoogleCM:F,Zilliz:G,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:N,VolcEngineTLS:E,OpManager:P,Meraki:M,StateCloud:W,Guance:q,CustomChange:V,Jira:z,Lark:K,Dingtalk:J,Wecom:Z,Slack:Q,MicrosoftTeams:X,AlertWebhook:ee,IncidentWebhook:ne,CustomAction:te,Templates:oe,HuaweiyunAPM:O,JiraSync:ae,ZStack:j,Keep:Y,ElastAlert2:H,DingtalkAlert:$,FeishuAlert:B,Link:se,ServiceNowSync:ie};module.exports=re;
+`,ue={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:u,BaiDuBCM:h,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:F,GoogleCM:_,Zilliz:G,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:D,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:M,Meraki:P,StateCloud:W,Guance:q,CustomChange:Z,Jira:Q,Lark:X,Dingtalk:ee,Wecom:ne,Slack:te,MicrosoftTeams:ae,AlertWebhook:ie,IncidentWebhook:oe,CustomAction:se,Templates:de,HuaweiyunAPM:O,JiraSync:re,ZStack:j,Keep:H,ElastAlert2:Y,DingtalkAlert:$,FeishuAlert:V,VolcEngineDetect:B,Link:ce,ServiceNowSync:le,Monit:z,Rum:K,Cloudflare:J};module.exports=ue;