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

package/dist/en.d.ts

@@ -54,5 +54,6 @@ declare const docs: {
     Templates: string;
     HuaweiyunAPM: string;
     JiraSync: string;
+    ZStack: string;
 };
 export default docs;

package/dist/esm/en.js

@@ -3772,7 +3772,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"
@@ -3875,7 +3875,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"
@@ -4746,6 +4746,94 @@ When you need to route alerts to different channels based on alert payload infor
 </div>
 
 `,j=`---
+title: "zstack integration"
+description: "Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction."
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/zstack-integration-guide"
+---
+
+Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **ZStack** integration and click **Save** to generate a card
+  4. Click the generated card to view the **push URL**, copy it for later use, and you're done
+
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **ZStack** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Click **Save** and copy the newly generated **push URL** for later use
+  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  5. Done
+    
+</details>
+</div>
+
+
+## In ZStack
+---
+
+<div class="md-block">
+
+## 一、Create Notification Object
+
+### Step 1: Create Notification Object
+1. Login to your \`ZStack\` console, find \`Cloud Monitoring\` in the \`Platform O&M\` menu
+2. Click \`Endpoint\`, click \`Create Endpoint\` or edit the existing endpoint
+3. In the edit page, Name it \`Flashduty\`, select \`Webhook\` type, and fill in the <span class='integration_url'>push URL</span> of the alert integration
+4. Click \`Send Test Message\`, if the message is sent successfully, it means the configuration is successful
+5. Click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/zstack-1.png" />
+
+### Step 2: Use Notification Object in Alert Policy
+
+1. Login to your \`ZStack\` console, find \`Cloud Monitoring\` in the \`Platform O&M\` menu
+2. Click \`Alarm\`, click \`Create Resource Alarm\` or \`Create Event Alarm\`, or edit the existing alarm object
+3. In the edit page, select the created \`Flashduty\` Endpoint (\`Resource Alarm\` is recommended to open the recovery notification)
+4. Configure other settings as needed, and click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/zstack-2.png" />
+
+
+
+</dev>
+
+## 二、Status Mapping
+
+<div class="md-block">
+
+| ZStack |  Flashduty | Status |
+| ---------- | -------- | ---- |
+| Emergent  | Critical | Critical |
+| Major   | Warning  | Warning |
+| Info     | Info     | Info |
+
+</div>
+
+`,O=`---
 title: "Custom Change Event Integration Guide"
 description: "Push change events from your own systems to Flashduty using standard protocols. Most incidents are caused by changes, and the correlation between changes and alerts helps quickly identify incident causes."
 date: "2024-05-11T10:00:00+08:00"
@@ -4802,7 +4890,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,O=`---
+`,H=`---
 title: "Jira Issue Events"
 description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
 date: "2024-05-11T10:00:00+08:00"
@@ -4876,7 +4964,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,H=`---
+`,$=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5011,7 +5099,7 @@ Once published, you can access the application via mobile/PC client. First-time
     |Group Bot Webhook|Maximum 100 calls/minute|
     |Sending messages to the same user or group|Maximum 5 calls/second|
 
-    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,$=`---
+    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,B=`---
 title: "Dingtalk Integration"
 description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
 date: "2024-05-11T10:00:00+08:00"
@@ -5167,7 +5255,7 @@ After the application is released, you can access it via mobile/PC client. First
 |Enterprise|5,500,000|60|1st of each month|
 
 **Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
-`,B=`---
+`,z=`---
 title: "WeCom Integration"
 description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
 date: "2024-05-11T10:00:00+08:00"
@@ -5246,7 +5334,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
-`,z=`---
+`,V=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2024-05-11T10:00:00+08:00"
@@ -5300,7 +5388,7 @@ Integrate with Slack to receive and respond to alerts within Slack.
 
 8. **Slack App shows Other questions error**
    - Try again, as this might be an unrecorded issue
-   - If the error persists, contact customer support`,V=`---
+   - If the error persists, contact customer support`,J=`---
 title: "Microsoft Teams Integration"
 description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
 date: "2024-05-11T10:00:00+08:00"
@@ -5395,7 +5483,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`,J=`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>
 
@@ -5563,7 +5651,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.
+`,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>
 
@@ -5770,7 +5858,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
-   - May be updated in the future, please check periodically`,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`,Q=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
 
 ## I. Creating Actions
 
@@ -6017,7 +6105,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`,Q=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,X=`---
 title: "Jira Sync"
 description: "Sync incidents with Jira issues through Jira Sync Webhook."
 date: "2024-05-11T10:00:00+08:00"
@@ -6099,7 +6187,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.
-`,X=`---
+`,ee=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -7096,4 +7184,4 @@ 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>`,ee={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:L,HuaweiyunLTS:_,GoogleCM:F,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:j,Jira:O,Lark:H,Dingtalk:$,Wecom:B,Slack:z,MicrosoftTeams:V,AlertWebhook:J,IncidentWebhook:K,CustomAction:Z,Templates:X,HuaweiyunAPM:q,JiraSync:Q};module.exports=ee;
+</div>`,ne={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:L,HuaweiyunLTS:_,GoogleCM:F,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:D,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:H,Lark:$,Dingtalk:B,Wecom:z,Slack:V,MicrosoftTeams:J,AlertWebhook:K,IncidentWebhook:Z,CustomAction:Q,Templates:ee,HuaweiyunAPM:q,JiraSync:X,ZStack:j};module.exports=ne;

package/dist/esm/zh.js

@@ -3251,7 +3251,7 @@ Sentry 提供了两类告警机制：Issue Alerts 和 Metric Alerts。Issue Aler
 |resolved|Ok|恢复|
 
 </div>
-`,A=`---
+`,S=`---
 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>
-`,C=`---
+`,A=`---
 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>
 
-`,S=`---
+`,C=`---
 title: "Dynatrace 告警事件"
 description: "通过 webhook 的方式同步 Dynatrace 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-08-20T10:00:00+08:00"
@@ -4441,7 +4441,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-tls-integration-guide"
 |通知|Info|提醒|
 
 </div>
-`,R=`---
+`,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>
-`,W=`---
+`,R=`---
 title: "Meraki 告警事件"
 description: "通过 webhook 的方式同步 Meraki 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -5012,6 +5012,95 @@ url: "https://docs.flashcat.cloud/zh/flashduty/huawei-apm-integration-guide"
 </div>
 
 `,O=`---
+title: "zstack 告警事件"
+description: "通过 webhook 的方式同步 zstack 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/zstack-integration-guide"
+---
+
+通过 webhook 的方式同步 ZStack 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **ZStack** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **ZStack** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  4. 点击 **创建路由**，为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间，也可以直接设置默认协作空间作为兜底，后续再按需调整。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在 ZStack
+---
+
+<div class="md-block">
+
+## 一、告警推送配置
+
+### 步骤1：创建通知对象
+
+1. 登录您的 \`ZStack\` 控制台，在 \`平台运维\` 菜单中，找到 \`云平台监控\`。
+2. 点击左侧的 \`通知对象\`，点击\`创建通知对象\`或编辑已有的通知对象。
+3. 在编辑页面中，名称填写 \`Flashduty\` ，类型选择 \`Webhook\`，\`地址\` 处填写告警集成的<span class='integration_url'>推送地址</span>。
+4. 点击 \`发送测试消息\`，如果消息发送成功，则说明配置成功。
+5. 点击 \`确定\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zstack-1.png" />
+
+### 步骤2：在告警策略中使用通知对象
+
+1. 登录您的 \`ZStack\` 控制台，在 \`平台运维\` 菜单中，找到 \`云平台监控\`。
+2. 点击左侧的 \`报警器\`，点击\`创建资源报警器\` 或 \`创建事件报警器\`，或编辑已有的报警器。
+3. 在编辑页面中，\`通知对象\` 处选择创建的 \`Flashduty\` 通知对象（资源报警器建议打开恢复通知）。
+4. 其他按需配置即可，点击 \`确定\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zstack-2.png" />
+
+
+
+</dev>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| ZStack |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| 紧急  | Critical | 严重 |
+| 严重   | Warning  | 警告 |
+| 提示   | Info     | 信息 |
+
+</div>
+
+`,q=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2024-05-11T10:00:00+08:00"
@@ -5068,7 +5157,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`,q=`---
+`,B=`---
 title: "Jira 事件集成指引"
 description: "通过 webhook 的方式同步 Jira Issue 事件到 Flashduty，实现变更事件收集。"
 date: "2024-05-11T10:00:00+08:00"
@@ -5142,7 +5231,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`,B=`---
+`,J=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5279,7 +5368,7 @@ sidebarDepth: 3
     |给同一个用户或同一个群发消息|最高频率 5 次/秒|
 
     **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
-`,J=`---
+`,G=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5439,7 +5528,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
 |专属版|550万次|60|     每月1日          |
 
 **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
-`,G=`---
+`,V=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5519,7 +5608,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`,V=`---
+`,Z=`---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5668,7 +5757,7 @@ Microsoft Teams 集成现处于 Beta 阶段，在关联前您需要先完成以
 暂不支持
 </details>
 
-`,Z=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
+`,X=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5836,7 +5925,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`,X=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`,Y=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -6044,7 +6133,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,Y=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,Q=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6303,7 +6392,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,Q=`---
+   - 未来可能会更新，请定期查验`,nn=`---
 title: "Jira 同步"
 description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
 date: "2024-05-11T10:00:00+08:00"
@@ -6388,7 +6477,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
 
 - Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
 - Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
-`,nn=`---
+`,tn=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -7392,4 +7481,4 @@ msg_type 必填，值为 post
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
 </div>
-`,tn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:C,Dynatrace:S,HuaweiyunLTS:I,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:$,OpManager:R,Meraki:W,Zilliz:U,StateCloud:z,Guance:j,CustomChange:O,Jira:q,Lark:B,Dingtalk:J,Wecom:G,Slack:V,MicrosoftTeams:K,AlertWebhook:Z,IncidentWebhook:X,CustomAction:Y,Templates:nn,HuaweiyunAPM:H,JiraSync:Q};module.exports=tn;
+`,en={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:S,AWSEventBridge:A,Dynatrace:C,HuaweiyunLTS:I,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:$,OpManager:W,Meraki:R,Zilliz:U,StateCloud:z,Guance:j,CustomChange:q,Jira:B,Lark:J,Dingtalk:G,Wecom:V,Slack:Z,MicrosoftTeams:K,AlertWebhook:X,IncidentWebhook:Y,CustomAction:Q,Templates:tn,HuaweiyunAPM:H,JiraSync:nn,ZStack:O};module.exports=en;

package/dist/iife/en.js

@@ -7096,4 +7096,92 @@ 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.
+`,ZStack:`---
+title: "zstack integration"
+description: "Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction."
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/zstack-integration-guide"
+---
+
+Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **ZStack** integration and click **Save** to generate a card
+  4. Click the generated card to view the **push URL**, copy it for later use, and you're done
+
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **ZStack** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Click **Save** and copy the newly generated **push URL** for later use
+  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  5. Done
+    
+</details>
+</div>
+
+
+## In ZStack
+---
+
+<div class="md-block">
+
+## 一、Create Notification Object
+
+### Step 1: Create Notification Object
+1. Login to your \`ZStack\` console, find \`Cloud Monitoring\` in the \`Platform O&M\` menu
+2. Click \`Endpoint\`, click \`Create Endpoint\` or edit the existing endpoint
+3. In the edit page, Name it \`Flashduty\`, select \`Webhook\` type, and fill in the <span class='integration_url'>push URL</span> of the alert integration
+4. Click \`Send Test Message\`, if the message is sent successfully, it means the configuration is successful
+5. Click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/zstack-1.png" />
+
+### Step 2: Use Notification Object in Alert Policy
+
+1. Login to your \`ZStack\` console, find \`Cloud Monitoring\` in the \`Platform O&M\` menu
+2. Click \`Alarm\`, click \`Create Resource Alarm\` or \`Create Event Alarm\`, or edit the existing alarm object
+3. In the edit page, select the created \`Flashduty\` Endpoint (\`Resource Alarm\` is recommended to open the recovery notification)
+4. Configure other settings as needed, and click \`OK\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/zstack-2.png" />
+
+
+
+</dev>
+
+## 二、Status Mapping
+
+<div class="md-block">
+
+| ZStack |  Flashduty | Status |
+| ---------- | -------- | ---- |
+| Emergent  | Critical | Critical |
+| Major   | Warning  | Warning |
+| Info     | Info     | Info |
+
+</div>
+
 `};n.FlashDocsEn=u})(window);

package/dist/iife/zh.js

@@ -7392,4 +7392,93 @@ url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
 
 - Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
 - Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
+`,ZStack:`---
+title: "zstack 告警事件"
+description: "通过 webhook 的方式同步 zstack 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/zstack-integration-guide"
+---
+
+通过 webhook 的方式同步 ZStack 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **ZStack** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **ZStack** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  4. 点击 **创建路由**，为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间，也可以直接设置默认协作空间作为兜底，后续再按需调整。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在 ZStack
+---
+
+<div class="md-block">
+
+## 一、告警推送配置
+
+### 步骤1：创建通知对象
+
+1. 登录您的 \`ZStack\` 控制台，在 \`平台运维\` 菜单中，找到 \`云平台监控\`。
+2. 点击左侧的 \`通知对象\`，点击\`创建通知对象\`或编辑已有的通知对象。
+3. 在编辑页面中，名称填写 \`Flashduty\` ，类型选择 \`Webhook\`，\`地址\` 处填写告警集成的<span class='integration_url'>推送地址</span>。
+4. 点击 \`发送测试消息\`，如果消息发送成功，则说明配置成功。
+5. 点击 \`确定\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zstack-1.png" />
+
+### 步骤2：在告警策略中使用通知对象
+
+1. 登录您的 \`ZStack\` 控制台，在 \`平台运维\` 菜单中，找到 \`云平台监控\`。
+2. 点击左侧的 \`报警器\`，点击\`创建资源报警器\` 或 \`创建事件报警器\`，或编辑已有的报警器。
+3. 在编辑页面中，\`通知对象\` 处选择创建的 \`Flashduty\` 通知对象（资源报警器建议打开恢复通知）。
+4. 其他按需配置即可，点击 \`确定\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zstack-2.png" />
+
+
+
+</dev>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| ZStack |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| 紧急  | Critical | 严重 |
+| 严重   | Warning  | 警告 |
+| 提示   | Info     | 信息 |
+
+</div>
+
 `};n.FlashDocsZh=t})(window);

package/dist/zh.d.ts

@@ -54,5 +54,6 @@ declare const docs: {
     Templates: string;
     HuaweiyunAPM: string;
     JiraSync: string;
+    ZStack: string;
 };
 export default docs;

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.2.5-beta.1",
+  "version": "1.2.5-beta.2",
   "description": "flashduty knowledge base",
   "type": "module",
   "scripts": {
     "build": "tsc && npm run build:iife && npm run build:esm",
     "build:iife": "rm -rf dist/iife && vite build --mode iife",
     "build:esm": "rm -rf dist/esm && vite build --mode esm",
-    "prepublishOnly": "npm run build && node scripts/upload.mjs",
+    "prepublishOnly": "npm run build",
     "upload": "npm run build:iife && node scripts/upload.mjs"
   },
   "exports": {