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

package/dist/esm/en.js

@@ -1,4 +1,4 @@
-"use strict";var o=Object.defineProperty;var r=Object.getOwnPropertyDescriptor;var l=Object.getOwnPropertyNames;var d=Object.prototype.hasOwnProperty;var c=(n,e)=>{for(var a in e)o(n,a,{get:e[a],enumerable:!0})},h=(n,e,a,i)=>{if(e&&typeof e=="object"||typeof e=="function")for(let t of l(e))!d.call(n,t)&&t!==a&&o(n,t,{get:()=>e[t],enumerable:!(i=r(e,t))||i.enumerable});return n};var u=n=>h(o({},"__esModule",{value:!0}),n);var ue={};c(ue,{default:()=>he});module.exports=u(ue);const g=`---
+"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> `,p=`---
+</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.
 
-`,m=`---
+`,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>
 
-`,f=`---
+`,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:
 
 
 
-`,y=`---
+`,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>
-`,v=`---
+`,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>`,b=`---
+</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>`,w=`---
+</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>
-`,C=`---
+`,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>`,k=`---
+</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>
-`,s=`---
+`,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>
-`,I=`---
+`,u=`---
 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>
-`,S=`---
+`,g=`---
 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>
-`,A=`---
+`,p=`---
 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>
-`,_=`Sync Influxdata alert events to Flashduty via webhook to achieve automated alert noise reduction.
+`,m=`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>
-`,L=`---
+`,f=`---
 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=`---
+`,y=`---
 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>
-`,x=`---
+`,v=`---
 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>
-`,R=`---
+`,b=`---
 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>
-`,T=`---
+`,w=`---
 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>
-`,U=`---
+`,C=`---
 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>
-`,E=`---
+`,k=`---
 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>
-`,D=`---
+`,I=`---
 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>
-`,N=`---
+`,S=`---
 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>
-`,P=`---
+`,A=`---
 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>
-`,M=`---
+`,_=`---
 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>
-`,W=`---
+`,L=`---
 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>
 
-`,G=`---
+`,F=`---
 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>
-`,Y=`---
+`,x=`---
 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>
-`,q=`---
+`,R=`---
 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,7 @@ Choose this option when you need to route alerts to different channels based on
 |No severity|Info|Info|
 
 </div>
-`,O=`---
+`,T=`---
 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 +3612,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>
-`,j=`---
+`,U=`---
 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 +3772,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 |INFO|Info|Info|
 
 </div>
-`,$=`---
+`,E=`---
 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 +3875,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,H=`---
+`,D=`---
 title: "Volcengine Cloud Monitor Alert Events"
 description: "Sync Volcengine Cloud Monitor alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3964,7 +3964,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,B=`---
+`,N=`---
 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 +4051,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,V=`---
+`,P=`---
 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 +4188,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 </div>
-`,z=`---
+`,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"
@@ -4322,7 +4322,7 @@ Choose this method when you need to route alerts to different channels based on
 | Attention  | Info           | Info |
 
 </div>
-`,K=`---
+`,W=`---
 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 +4394,7 @@ Choose this option when you need to route alerts to different channels based on
 | informational      | Info     | Info |
 
 </div>
-`,Z=`---
+`,G=`---
 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 +4481,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>
-`,J=`---
+`,Y=`---
 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,7 +4566,7 @@ Choose this option when you need to route alerts to different channels based on
 | Data Missing | Info | Info |
 
 </div>
-`,Q=`---
+`,q=`---
 title: "Zilliz Alert Events"
 description: "Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4639,7 +4639,7 @@ Choose this method when you need to route alerts to different channels based on
 
 </div>
 
-`,X=`---
+`,O=`---
 title: "Custom Change Event Integration Guide"
 description: "Push change events from your own systems to Flashduty using standard protocols. Most incidents are caused by changes, and the correlation between changes and alerts helps quickly identify incident causes."
 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>
 
-`,ee=`---
+`,j=`---
 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>
-`,ne=`---
+`,$=`---
 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`,te=`---
+    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,H=`---
 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
-`,ae=`---
+`,B=`---
 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
-`,oe=`---
+`,V=`---
 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`,ie=`---
+   - If the error persists, contact customer support`,z=`---
 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>
 
-`,se=`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.
+`,K=`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
-`,re=`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.
+`,Z=`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`,le=`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`,J=`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`,de=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,Q=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -6513,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">
 
-`,ce={CustomAlert:g,Email:p,N9e:m,Prometheus:f,Grafana:y,Zabbix:v,UptimeKuma:b,AliyunARMS:w,AliyunCmEvent:C,AliyunCm:k,AliyunSLS:s,AWSCW:s,AzureMonitor:I,BaiDuBCM:S,HuaWeiCES:A,InfluxDB:_,OpenFalcon:L,PagerDuty:F,TencentBK:x,TencentCLS:R,TencentCm:T,TencentEb:U,OceanBase:E,Graylog:D,Skywalking:N,Sentry:P,Jiankongbao:M,AWSEventBridge:W,Dynatrace:G,HuaweiyunLTS:Y,GoogleCM:q,Zilliz:Q,Splunk:O,AppDynamics:j,SolarWinds:$,VolcEngineMetric:H,VolcEngineEvent:B,VolcEngineTLS:V,OpManager:z,Meraki:K,StateCloud:Z,Guance:J,CustomChange:X,Jira:ee,Lark:ne,Dingtalk:te,Wecom:ae,Slack:oe,MicrosoftTeams:ie,AlertWebhook:se,IncidentWebhook:re,CustomAction:le,Templates:de};global.FlashDocsEn=ce;var he=zhDocs;
+`,n={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:u,BaiDuBCM:g,HuaWeiCES:p,InfluxDB:m,OpenFalcon:f,PagerDuty:y,TencentBK:v,TencentCLS:b,TencentCm:w,TencentEb:C,OceanBase:k,Graylog:I,Skywalking:S,Sentry:A,Jiankongbao:_,AWSEventBridge:L,Dynatrace:F,HuaweiyunLTS:x,GoogleCM:R,Zilliz:q,Splunk:T,AppDynamics:U,SolarWinds:E,VolcEngineMetric:D,VolcEngineEvent:N,VolcEngineTLS:P,OpManager:M,Meraki:W,StateCloud:G,Guance:Y,CustomChange:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:V,MicrosoftTeams:z,AlertWebhook:K,IncidentWebhook:Z,CustomAction:J,Templates:Q};global.FlashDocsEn=n;module.exports=n;

package/dist/esm/zh.js

@@ -1,4 +1,4 @@
-"use strict";var i=Object.defineProperty;var d=Object.getOwnPropertyDescriptor;var o=Object.getOwnPropertyNames;var r=Object.prototype.hasOwnProperty;var c=(t,n)=>{for(var a in n)i(t,a,{get:n[a],enumerable:!0})},u=(t,n,a,s)=>{if(n&&typeof n=="object"||typeof n=="function")for(let e of o(n))!r.call(t,e)&&e!==a&&i(t,e,{get:()=>n[e],enumerable:!(s=d(n,e))||s.enumerable});return t};var h=t=>u(i({},"__esModule",{value:!0}),t);var pn={};c(pn,{default:()=>mn});module.exports=h(pn);const m=`---
+"use strict";const t=`---
 title: "标准告警事件集成指引"
 description: "通过标准协议推送自有系统告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-05-11T10:00:00+08:00"
@@ -219,7 +219,7 @@ curl -X POST '{api_host}/event/push/alert/standard?integration_key={integration_
   更多内容请参考 [告警降噪](https://docs.flashcat.cloud/zh/flashduty/what-is-noise-reduction)。
 </details>
 
-`,p=`---
+`,e=`---
 title: "邮件Email集成"
 description: "在 Flashduty 生成唯一的邮件地址，通过邮件的方式将告警的发生与恢复同步到 Flashduty"
 date: "2024-05-11T10:00:00+08:00"
@@ -320,7 +320,7 @@ attachment_stripped = true
 
 当前邮件集成推送到 Flashduty 的告警等级均为Warning。
 
-`,g=`---
+`,a=`---
 title: "夜莺/FlahCat集成"
 description: "通过 webhook 的方式将夜莺（Nightingale / n9e）或 Flashcat 告警事件推送到 Flashduty。当告警触发时，向 Flashduty 发送触发事件，当告警恢复时，向 Flashduty 发送恢复事件"
 date: "2024-05-11T10:00:00+08:00"
@@ -477,7 +477,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/nightingale-integration-guide"
     
 </details>
 
-`,y=`---
+`,i=`---
 title: "Prometheus告警集成"
 description: "通过 webhook 的方式将 Prometheus 告警事件通过 AlertManager 推送到 Flashduty。当告警触发时，向 Flashduty 发送触发事件，当告警恢复时，向 Flashduty 发送恢复事件。"
 date: "2024-05-11T10:00:00+08:00"
@@ -661,7 +661,7 @@ Promtheus 到 Flashduty 告警等级映射关系：
 
 
 
-`,f=`---
+`,s=`---
 title: "Grafana集成"
 description: "通过 webhook 的方式同步 Grafana 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-05-11T10:00:00+08:00"
@@ -776,7 +776,7 @@ Grafana Alerting 到 Flashduty 告警等级映射关系：
 | ok               | Ok       | 恢复 |
 
 </div>
-`,b=`---
+`,l=`---
 title: "Zabbix集成"
 description: "通过 webhook 的方式同步 Zabbix 告警事件到 Flashduty（支持 Zabbix 3.x ~ 6.x 版本，不同版本配置有差异），实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1138,7 +1138,7 @@ Zabbix 到快猫星云告警等级映射关系：
 | Not classified | Info     | 提醒 |
 
 </div>
-`,v=`---
+`,d=`---
 title: "Uptime Kuma 集成"
 description: "通过 webhook 的方式同步 Uptime Kuma 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1222,7 +1222,7 @@ Uptime Kuma 到 Flashduty 告警等级映射关系：
 | Warning     | Warning  | 警告 |
 | Info     | Info     | 提醒 |
 
-</div>`,w=`---
+</div>`,o=`---
 title: "阿里云 ARMS 集成"
 description: "通过 webhook 的方式同步阿里云 ARMS 监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1309,7 +1309,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aliyun-arms-integration-guide"
 | P4     | Info     | 提醒 |
 
 </div>
-`,_=`---
+`,r=`---
 title: "阿里云监控 CM 事件集成"
 description: "通过 webhook 的方式同步阿里云云监控事件中心告警到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1398,7 +1398,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aliyun-cm-event-integration-guide
 | INFO         | Info     | 提醒 |
 
 </div>
-`,k=`---
+`,c=`---
 title: "阿里云监控 CM 指标集成"
 description: "通过 webhook 的方式同步阿里云云监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1498,7 +1498,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aliyun-cm-metric-integration-guid
 | NODATA       | Info     | 提醒 |
 
 </div>
-`,F=`---
+`,u=`---
 title: "阿里云 SLS集成"
 description: "通过 webhook 的方式同步阿里云日志服务 SLS 监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1626,7 +1626,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aliyun-sls-integration-guide"
 | 2               | Info     | 提醒 |
 
 </div>
-`,x=`---
+`,h=`---
 title: "AWS CloudWatch集成"
 description: "通过 webhook 的方式同步 AWS CloudWatch 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1706,7 +1706,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aws-cloudwatch-integration-guide"
 CloudWatch 监控所有指标告警均对应到 Flashduty “警告（warning）”级别告警。
 
 </div>
-`,T=`---
+`,m=`---
 title: "Azure Monitor集成"
 description: "通过 webhook 的方式同步 Azure Monitor 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1794,7 +1794,7 @@ Azure Monitor 到 Flashduty 告警等级映射关系：
 | Sev4     | Info     | 提醒 |
 
 </div>
-`,L=`---
+`,p=`---
 title: "百度云BCM监控集成"
 description: "通过 webhook 的方式同步百度云 BCM 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1870,7 +1870,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/baidu-bcm-integration-guide"
 | 通知 | Info     | 提醒 |
 
 </div>
-`,A=`---
+`,g=`---
 title: "华为云监控 CES集成"
 description: 通过 webhook 的方式同步华为云监控 CES 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -1959,7 +1959,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/huawei-ces-integration-guide"
 | 提示 | Info     | 提醒 |
 
 </div>
-`,S=`---
+`,y=`---
 title: "Influxdata 集成"
 description: "通过 webhook 的方式同步 Influxdata 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2065,7 +2065,7 @@ Influxdata 告警事件到快猫星云告警等级映射关系：
 | unknow     | Info     | 提醒 |
 
 </div>
-`,C=`---
+`,f=`---
 title: "Open Falcon集成"
 description: "通过 webhook 的方式同步 Open-Falcon 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2151,7 +2151,7 @@ Open-Falcon 到 Flashduty 告警等级映射关系：
 | 6           | Info     | 提醒 |
 
 </div>
-`,I=`---
+`,b=`---
 title: "PagerDuty集成"
 description: "可以通过 PagerDuty 协议推送告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2315,7 +2315,7 @@ pagerduty_v2_payload_source: mysql.host.name
 4. 步骤 4：重启 ElastAlert，等待告警触发
 
 </div>
-`,D=`---
+`,v=`---
 title: "蓝鲸智云集成"
 description: "通过 webhook 的方式同步蓝鲸智云监控事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2414,7 +2414,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/tencent-bk-integration-guide"
 | 提醒     | Info     | 提醒 |
 
 </div>
-`,P=`---
+`,w=`---
 title: "腾讯云日志服务CLS集成"
 description: "通过 webhook 的方式同步腾讯云日志服务 CLS 监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2560,7 +2560,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/tencent-cls-integration-guide"
 | Critical      |  Critical | 紧急
 
 </div>
-`,M=`---
+`,_=`---
 title: "腾讯云监控 CM集成"
 description: "通过 webhook 的方式同步腾讯云监控 CM 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2634,7 +2634,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/tencent-cm-integration-guide"
 腾讯云监控所有指标告警均对应到 Flashduty “警告（warning）”级别告警。
 
 </div>
-`,N=`---
+`,k=`---
 title: "腾讯云EventBridge"
 description: "通过 webhook 的方式同步腾讯云事件总线 EB 事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-11T10:00:00+08:00"
@@ -2727,7 +2727,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/tencent-event-bridge-integration-
 腾讯云事件总线所有事件均对应到 Flashduty “警告（warning）”级别告警。
 
 </div>
-`,$=`---
+`,F=`---
 title: "OceanBase 告警事件"
 description: "通过 webhook 的方式同步OceanBase告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-05-23T10:00:00+08:00"
@@ -2941,7 +2941,7 @@ OCP告警通知-单条告警
 |提醒|Info|提醒|
 
 </div>
-`,E=`---
+`,x=`---
 title: "Graylog 告警事件"
 description: "通过 webhook 的方式同步Graylog告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-06-18T10:00:00+08:00"
@@ -3038,7 +3038,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/graylog-integration-guide"
 |1|Info|提醒|
 
 </div>
-`,R=`---
+`,T=`---
 title: "Skywalking 告警事件"
 description: "通过 webhook 的方式同步 Skywalking 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-06-20T10:00:00+08:00"
@@ -3140,7 +3140,7 @@ hooks:
 
 
 </div>
-`,W=`---
+`,L=`---
 title: "Sentry 告警事件"
 description: "通过 webhook 的方式同步 Sentry 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -3251,7 +3251,7 @@ Sentry 提供了两类告警机制：Issue Alerts 和 Metric Alerts。Issue Aler
 |resolved|Ok|恢复|
 
 </div>
-`,z=`---
+`,A=`---
 title: "监控宝告警事件"
 description: "通过 webhook 的方式同步监控宝告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -3346,7 +3346,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/jiankongbao-integration-guide"
 |2|Info|提醒|
 
 </div>
-`,j=`---
+`,S=`---
 title: "AWS EventBridge 告警事件"
 description: "通过 webhook 的方式同步 AWS EventBridge 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -3451,7 +3451,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aws-eventbridge-integration-guide
 
 </div>
 
-`,U=`---
+`,C=`---
 title: "Dynatrace 告警事件"
 description: "通过 webhook 的方式同步 Dynatrace 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-08-20T10:00:00+08:00"
@@ -3565,7 +3565,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dynatrace-integration-guide"
 |CUSTOM_ALERT|Info|提醒|
 
 </div>
-`,H=`---
+`,I=`---
 title: "华为云日志服务 LTS 告警事件"
 description: "通过 webhook 的方式同步华为云日志服务 LTS 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-08-20T10:00:00+08:00"
@@ -3681,7 +3681,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/huaweilts-integration-guide"
 |Info|Info|提醒|
 
 </div>
-`,O=`---
+`,D=`---
 title: "GoogleCloudMonitoring 告警事件"
 description: "通过 webhook 的方式同步 GoogleCloudMonitoring 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -3775,7 +3775,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/gcpcm-integration-guide"
 |No severity|Info|提醒|
 
 </div>
-`,q=`---
+`,P=`---
 title: "Splunk 告警事件"
 description: "通过 webhook 的方式同步 Splunk 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -3852,7 +3852,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/splunk-integration-guide"
 <div class="md-block">
 由于 Splunk 的告警事件没有区分严重程度，所以 Splunk 推送到 Flashduty的所有告警事件状态都为 Warning 且没有恢复事件。
 </div>
-`,B=`---
+`,M=`---
 title: "AppDynamics 告警事件"
 description: "通过 webhook 的方式同步 AppDynamics 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4019,7 +4019,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/appdynamics-integration-guide"
 |INFO|Info|提醒|
 
 </div>
-`,G=`---
+`,N=`---
 title: "SolarWinds 告警事件"
 description: "通过 webhook 的方式同步 SolarWinds 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -4124,7 +4124,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/solarwinds-integration-guide"
 |Info|Info|提醒|
 
 </div>
-`,V=`---
+`,$=`---
 title: "火山引擎云监控告警事件"
 description: "通过 webhook 的方式同步火山引擎云监控告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -4215,7 +4215,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-metric-integration-gui
 |通知|Info|提醒|
 
 </div>
-`,Z=`---
+`,E=`---
 title: "火山引擎云监控事件中心告警事件"
 description: "通过 webhook 的方式同步火山引擎云监控事件中心告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4304,7 +4304,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-event-integration-guid
 |通知|Info|提醒|
 
 </div>
-`,K=`---
+`,R=`---
 title: "火山引擎日志服务 TLS 告警事件"
 description: "通过 webhook 的方式同步火山引擎日志服务 TLS 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4441,7 +4441,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-tls-integration-guide"
 |通知|Info|提醒|
 
 </div>
-`,J=`---
+`,W=`---
 title: "Opmanager 告警事件"
 description: "通过 webhook 的方式同步 Opmanager 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4576,7 +4576,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/opmanager-integration-guide"
 | Attention      | Info     | 提醒 |
 
 </div>
-`,X=`---
+`,z=`---
 title: "Meraki 告警事件"
 description: "通过 webhook 的方式同步 Meraki 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4652,7 +4652,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/meraki-integration-guide"
 | informational      | Info     | 提醒 |
 
 </div>
-`,Q=`---
+`,j=`---
 title: "天翼云告警事件"
 description: "通过 webhook 的方式同步天翼云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4740,7 +4740,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 
 </div>
-`,Y=`---
+`,U=`---
 title: "观测云告警事件"
 description: "通过 webhook 的方式同步观测云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4828,7 +4828,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
 | 数据断档     | Info     | 提醒 |
 
 </div>
-`,nn=`---
+`,H=`---
 title: "zilliz 告警事件"
 description: "通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4903,7 +4903,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/zilliz-integration-guide"
 
 </div>
 
-`,tn=`---
+`,O=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2024-05-11T10:00:00+08:00"
@@ -4960,7 +4960,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`,en=`---
+`,q=`---
 title: ""
 description: ""
 date: "2024-05-11T10:00:00+08:00"
@@ -5034,7 +5034,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`,an=`---
+`,B=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5151,7 +5151,7 @@ sidebarDepth: 3
 
 <img alt="drawing" width="800" src="https://download.flashcat.cloud/feishu-self-app-invite-to-chat.jpeg" />
 <img src="https://download.flashcat.cloud/feishu-self-app-notify-rule.png" alt="drawing" width="800"/>
-`,sn=`---
+`,G=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5302,7 +5302,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
 
 <img src="https://download.flashcat.cloud/dingtalk-self-app-notify-rule.png" alt="drawing" width="800"/>
 
-`,ln=`---
+`,V=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5382,7 +5382,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`,dn=`---
+`,Z=`---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5436,7 +5436,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 8. **Slack App 内 Other questions，报错**
    - 重新操作，遇到了还没被记录的问题
-   - 重试后仍然报错，联系客服`,on=`---
+   - 重试后仍然报错，联系客服`,K=`---
 title: "Microsoft Teams集成"
 description: "通过集成 Microsoft Teams 第三方应用，实现在 Microsoft Teams 内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5531,7 +5531,7 @@ Microsoft Teams 集成现处于 Beta 阶段，在关联前您需要先完成以
 暂不支持
 </details>
 
-`,rn=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
+`,J=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5699,7 +5699,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`,cn=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`,X=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5906,7 +5906,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,un=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,Q=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6165,7 +6165,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,hn=`---
+   - 未来可能会更新，请定期查验`,Y=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -6995,4 +6995,4 @@ CloseTime | int64 | 否 | 关闭时间，EndTime 为告警恢复时间，CloseTi
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
 
-`,l={CustomAlert:m,Email:p,N9e:g,Prometheus:y,Grafana:f,Zabbix:b,UptimeKuma:v,AliyunARMS:w,AliyunCmEvent:_,AliyunCm:k,AliyunSLS:F,AWSCW:x,AzureMonitor:T,BaiDuBCM:L,HuaWeiCES:A,InfluxDB:S,OpenFalcon:C,PagerDuty:I,TencentBK:D,TencentCLS:P,TencentCm:M,TencentEb:N,OceanBase:$,Graylog:E,Skywalking:R,Sentry:W,Jiankongbao:z,AWSEventBridge:j,Dynatrace:U,HuaweiyunLTS:H,GoogleCM:O,Splunk:q,AppDynamics:B,SolarWinds:G,VolcEngineMetric:V,VolcEngineEvent:Z,VolcEngineTLS:K,OpManager:J,Meraki:X,Zilliz:nn,StateCloud:Q,Guance:Y,CustomChange:tn,Jira:en,Lark:an,Dingtalk:sn,Wecom:ln,Slack:dn,MicrosoftTeams:on,AlertWebhook:rn,IncidentWebhook:cn,CustomAction:un,Templates:hn};global.FlashDocsZh=l;var mn=l;
+`,n={CustomAlert:t,Email:e,N9e:a,Prometheus:i,Grafana:s,Zabbix:l,UptimeKuma:d,AliyunARMS:o,AliyunCmEvent:r,AliyunCm:c,AliyunSLS:u,AWSCW:h,AzureMonitor:m,BaiDuBCM:p,HuaWeiCES:g,InfluxDB:y,OpenFalcon:f,PagerDuty:b,TencentBK:v,TencentCLS:w,TencentCm:_,TencentEb:k,OceanBase:F,Graylog:x,Skywalking:T,Sentry:L,Jiankongbao:A,AWSEventBridge:S,Dynatrace:C,HuaweiyunLTS:I,GoogleCM:D,Splunk:P,AppDynamics:M,SolarWinds:N,VolcEngineMetric:$,VolcEngineEvent:E,VolcEngineTLS:R,OpManager:W,Meraki:z,Zilliz:H,StateCloud:j,Guance:U,CustomChange:O,Jira:q,Lark:B,Dingtalk:G,Wecom:V,Slack:Z,MicrosoftTeams:K,AlertWebhook:J,IncidentWebhook:X,CustomAction:Q,Templates:Y};global.FlashDocsZh=n;module.exports=n;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.2.0-beta.1",
+  "version": "1.2.0-beta.2",
   "description": "flashduty knowledge base",
   "type": "module",
   "scripts": {