flashduty-knowledge-base 1.0.5 → 1.0.7

package/dist/en.cjs

@@ -3287,7 +3287,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`,x=`---
+`,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"
@@ -3400,7 +3400,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,F=`---
+`,x=`---
 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"
@@ -4521,6 +4521,79 @@ Choose this option when you need to route alerts to different channels based on
 
 </div>
 `,Y=`---
+title: "Zilliz Alert Events"
+description: "Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/zilliz-integration-guide"
+---
+
+Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **Zilliz** integration and click **Save** to generate a card
+  4. Click the generated card to view the **push URL**, copy it for later use, and you're done
+
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Zilliz** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Click **Save** and copy the newly generated **push URL** for later use
+  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  5. Done
+    
+</details>
+</div>
+
+## In Zilliz
+---
+
+<div class="md-block">
+
+## I. Alert Push Configuration
+
+1. Log in to your \`Zilliz\` console, create or modify an \`Alert\` in \`Project Alerts\`
+2. In the \`Send to\` section of the \`Alert\` editing page, select \`Webhook\` and fill in the <span class='integration_url'>push URL</span> from your alert integration
+3. Check \`Alert Resolution Notification\`, select other options as needed
+4. Click \`Save\` or \`Create\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zilliz-1.png" />
+
+</dev>
+
+## II. Status Mapping
+
+<div class="md-block">
+
+| Zilliz    | Flashduty | Status   |
+| --------- | --------- | -------- |
+| CRITICAL  | Critical  | Critical |
+| WARNING   | Warning   | Warning  |
+
+</div>
+
+`,q=`---
 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"
@@ -4577,7 +4650,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,q=`---
+`,O=`---
 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"
@@ -4651,7 +4724,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,O=`---
+`,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
@@ -4942,7 +5015,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
-`,j=`---
+`,H=`---
 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"
@@ -5021,7 +5094,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
-`,H=`---
+`,B=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2024-05-11T10:00:00+08:00"
@@ -5075,7 +5148,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`,B=`---
+   - If the error persists, contact customer support`,V=`---
 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"
@@ -5170,7 +5243,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`,V=`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.
+`,z=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -5338,7 +5411,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
-`,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.
+`,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.
 
 <span id="EventTypes"></span>
 
@@ -5544,7 +5617,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`,K=`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`,Z=`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
 
@@ -6394,4 +6467,4 @@ If custom content is not set, the system default template will be used for notif
 As shown below:
 <img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
 
-`;exports.AWSCW=e;exports.AWSEventBridge=A;exports.AlertWebhook=V;exports.AliyunARMS=l;exports.AliyunCm=c;exports.AliyunCmEvent=d;exports.AliyunSLS=e;exports.AppDynamics=T;exports.AzureMonitor=h;exports.BaiDuBCM=u;exports.CustomAction=K;exports.CustomAlert=n;exports.CustomChange=Y;exports.Dingtalk=$;exports.Dynatrace=L;exports.Email=t;exports.GoogleCM=F;exports.Grafana=i;exports.Graylog=k;exports.Guance=G;exports.HuaWeiCES=g;exports.HuaweiyunLTS=x;exports.IncidentWebhook=z;exports.InfluxDB=p;exports.Jiankongbao=_;exports.Jira=q;exports.Lark=O;exports.Meraki=M;exports.MicrosoftTeams=B;exports.N9e=a;exports.OceanBase=C;exports.OpManager=N;exports.OpenFalcon=m;exports.PagerDuty=f;exports.Prometheus=o;exports.Sentry=S;exports.Skywalking=I;exports.Slack=H;exports.SolarWinds=U;exports.Splunk=R;exports.StateCloud=W;exports.Templates=J;exports.TencentBK=y;exports.TencentCLS=v;exports.TencentCm=b;exports.TencentEb=w;exports.UptimeKuma=r;exports.VolcEngineEvent=D;exports.VolcEngineMetric=E;exports.VolcEngineTLS=P;exports.Wecom=j;exports.Zabbix=s;
+`;exports.AWSCW=e;exports.AWSEventBridge=A;exports.AlertWebhook=z;exports.AliyunARMS=l;exports.AliyunCm=c;exports.AliyunCmEvent=d;exports.AliyunSLS=e;exports.AppDynamics=T;exports.AzureMonitor=h;exports.BaiDuBCM=u;exports.CustomAction=Z;exports.CustomAlert=n;exports.CustomChange=q;exports.Dingtalk=$;exports.Dynatrace=L;exports.Email=t;exports.GoogleCM=x;exports.Grafana=i;exports.Graylog=k;exports.Guance=G;exports.HuaWeiCES=g;exports.HuaweiyunLTS=F;exports.IncidentWebhook=K;exports.InfluxDB=p;exports.Jiankongbao=_;exports.Jira=O;exports.Lark=j;exports.Meraki=M;exports.MicrosoftTeams=V;exports.N9e=a;exports.OceanBase=C;exports.OpManager=N;exports.OpenFalcon=m;exports.PagerDuty=f;exports.Prometheus=o;exports.Sentry=S;exports.Skywalking=I;exports.Slack=B;exports.SolarWinds=U;exports.Splunk=R;exports.StateCloud=W;exports.Templates=J;exports.TencentBK=y;exports.TencentCLS=v;exports.TencentCm=b;exports.TencentEb=w;exports.UptimeKuma=r;exports.VolcEngineEvent=D;exports.VolcEngineMetric=E;exports.VolcEngineTLS=P;exports.Wecom=H;exports.Zabbix=s;exports.Zilliz=Y;

package/dist/en.js

@@ -3287,7 +3287,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`, x = `---
+`, 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"
@@ -3400,7 +3400,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`, F = `---
+`, x = `---
 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"
@@ -4521,6 +4521,79 @@ Choose this option when you need to route alerts to different channels based on
 
 </div>
 `, Y = `---
+title: "Zilliz Alert Events"
+description: "Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/zilliz-integration-guide"
+---
+
+Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **Zilliz** integration and click **Save** to generate a card
+  4. Click the generated card to view the **push URL**, copy it for later use, and you're done
+
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Zilliz** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Click **Save** and copy the newly generated **push URL** for later use
+  4. Click **Create Route** to configure routing rules for the integration. You can match different alerts to different channels based on conditions, or set a default channel as a fallback and adjust as needed later
+  5. Done
+    
+</details>
+</div>
+
+## In Zilliz
+---
+
+<div class="md-block">
+
+## I. Alert Push Configuration
+
+1. Log in to your \`Zilliz\` console, create or modify an \`Alert\` in \`Project Alerts\`
+2. In the \`Send to\` section of the \`Alert\` editing page, select \`Webhook\` and fill in the <span class='integration_url'>push URL</span> from your alert integration
+3. Check \`Alert Resolution Notification\`, select other options as needed
+4. Click \`Save\` or \`Create\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zilliz-1.png" />
+
+</dev>
+
+## II. Status Mapping
+
+<div class="md-block">
+
+| Zilliz    | Flashduty | Status   |
+| --------- | --------- | -------- |
+| CRITICAL  | Critical  | Critical |
+| WARNING   | Warning   | Warning  |
+
+</div>
+
+`, q = `---
 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"
@@ -4577,7 +4650,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`, q = `---
+`, O = `---
 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"
@@ -4651,7 +4724,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`, O = `---
+`, $ = `---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -4786,7 +4859,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`, j = `---
 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"
@@ -4942,7 +5015,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
-`, j = `---
+`, H = `---
 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"
@@ -5021,7 +5094,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
-`, H = `---
+`, B = `---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2024-05-11T10:00:00+08:00"
@@ -5075,7 +5148,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`, B = `---
+   - If the error persists, contact customer support`, V = `---
 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"
@@ -5170,7 +5243,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`, V = `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.
+`, z = `Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -5338,7 +5411,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
-`, 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.
+`, 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.
 
 <span id="EventTypes"></span>
 
@@ -5544,7 +5617,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`, K = `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`, Z = `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
 
@@ -6398,7 +6471,7 @@ As shown below:
 export {
   c as AWSCW,
   A as AWSEventBridge,
-  V as AlertWebhook,
+  z as AlertWebhook,
   r as AliyunARMS,
   d as AliyunCm,
   l as AliyunCmEvent,
@@ -6406,25 +6479,25 @@ export {
   T as AppDynamics,
   h as AzureMonitor,
   u as BaiDuBCM,
-  K as CustomAction,
+  Z as CustomAction,
   e as CustomAlert,
-  Y as CustomChange,
-  $ as Dingtalk,
+  q as CustomChange,
+  j as Dingtalk,
   L as Dynatrace,
   n as Email,
-  F as GoogleCM,
+  x as GoogleCM,
   o as Grafana,
   k as Graylog,
   G as Guance,
   g as HuaWeiCES,
-  x as HuaweiyunLTS,
-  z as IncidentWebhook,
+  F as HuaweiyunLTS,
+  K as IncidentWebhook,
   p as InfluxDB,
   _ as Jiankongbao,
-  q as Jira,
-  O as Lark,
+  O as Jira,
+  $ as Lark,
   M as Meraki,
-  B as MicrosoftTeams,
+  V as MicrosoftTeams,
   t as N9e,
   C as OceanBase,
   N as OpManager,
@@ -6433,7 +6506,7 @@ export {
   a as Prometheus,
   S as Sentry,
   I as Skywalking,
-  H as Slack,
+  B as Slack,
   U as SolarWinds,
   R as Splunk,
   W as StateCloud,
@@ -6446,6 +6519,7 @@ export {
   D as VolcEngineEvent,
   E as VolcEngineMetric,
   P as VolcEngineTLS,
-  j as Wecom,
-  i as Zabbix
+  H as Wecom,
+  i as Zabbix,
+  Y as Zilliz
 };

package/dist/zh.cjs

@@ -2917,7 +2917,7 @@ OCP告警通知-单条告警
 |提醒|Info|提醒|
 
 </div>
-`,x=`---
+`,F=`---
 title: "Graylog 告警事件"
 description: "通过 webhook 的方式同步Graylog告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-06-18T10:00:00+08:00"
@@ -3014,7 +3014,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/graylog-integration-guide"
 |1|Info|提醒|
 
 </div>
-`,F=`---
+`,x=`---
 title: "Skywalking 告警事件"
 description: "通过 webhook 的方式同步 Skywalking 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-06-20T10:00:00+08:00"
@@ -4628,7 +4628,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/meraki-integration-guide"
 | informational      | Info     | 提醒 |
 
 </div>
-`,j=`---
+`,z=`---
 title: "天翼云告警事件"
 description: "通过 webhook 的方式同步天翼云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4716,7 +4716,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 
 </div>
-`,U=`---
+`,j=`---
 title: "观测云告警事件"
 description: "通过 webhook 的方式同步观测云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4804,7 +4804,82 @@ url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
 | 数据断档     | Info     | 提醒 |
 
 </div>
-`,z=`---
+`,U=`---
+title: "zilliz 告警事件"
+description: "通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/zilliz-integration-guide"
+---
+
+通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **zilliz** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **zilliz** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  4. 点击 **创建路由**，为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间，也可以直接设置默认协作空间作为兜底，后续再按需调整。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在 zilliz
+---
+
+<div class="md-block">
+
+## 一、告警推送配置
+
+1. 登录您的 \`zilliz\` 控制台，在 \`Project Alerts\` 中，创建或修改 \`Alert\`。
+2. 在 \`Alert\` 编辑页面中的 \`Send to\` 部分，选择 \`Webhook\`，Webhook URL 填写告警集成的 <span class='integration_url' >推送地址</span>。
+3. 选中 \`Alert Resolution Notification\`，其他按需选择。
+4. 点击 \`Save\` 或 \`Create\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zilliz-1.png" />
+
+</dev>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| 观测云 |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| CRITICAL   | Critical | 严重 |
+| WARNING   | Warning  | 警告 |
+
+
+</div>
+
+`,H=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2024-05-11T10:00:00+08:00"
@@ -4861,7 +4936,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`,H=`---
+`,O=`---
 title: ""
 description: ""
 date: "2024-05-11T10:00:00+08:00"
@@ -4935,7 +5010,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`,O=`---
+`,q=`---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5052,7 +5127,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"/>
-`,q=`---
+`,B=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5203,7 +5278,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"/>
 
-`,B=`---
+`,G=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5283,7 +5358,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`,G=`---
+`,V=`---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5337,7 +5412,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 8. **Slack App 内 Other questions，报错**
    - 重新操作，遇到了还没被记录的问题
-   - 重试后仍然报错，联系客服`,V=`---
+   - 重试后仍然报错，联系客服`,Z=`---
 title: "Microsoft Teams集成"
 description: "通过集成 Microsoft Teams 第三方应用，实现在 Microsoft Teams 内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5600,7 +5675,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`,Z=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`,J=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5807,7 +5882,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,J=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,X=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6066,7 +6141,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,X=`---
+   - 未来可能会更新，请定期查验`,Q=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -6896,4 +6971,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"/>
 
 
-`;exports.AWSCW=u;exports.AWSEventBridge=S;exports.AlertWebhook=K;exports.AliyunARMS=d;exports.AliyunCm=r;exports.AliyunCmEvent=o;exports.AliyunSLS=c;exports.AppDynamics=P;exports.AzureMonitor=h;exports.BaiDuBCM=m;exports.CustomAction=J;exports.CustomAlert=n;exports.CustomChange=z;exports.Dingtalk=q;exports.Dynatrace=A;exports.Email=t;exports.GoogleCM=I;exports.Grafana=i;exports.Graylog=x;exports.Guance=U;exports.HuaWeiCES=p;exports.HuaweiyunLTS=C;exports.IncidentWebhook=Z;exports.InfluxDB=g;exports.Jiankongbao=L;exports.Jira=H;exports.Lark=O;exports.Meraki=R;exports.MicrosoftTeams=V;exports.N9e=e;exports.OceanBase=k;exports.OpManager=W;exports.OpenFalcon=y;exports.PagerDuty=_;exports.Prometheus=a;exports.Sentry=T;exports.Skywalking=F;exports.Slack=G;exports.SolarWinds=M;exports.Splunk=D;exports.StateCloud=j;exports.Templates=X;exports.TencentBK=f;exports.TencentCLS=b;exports.TencentCm=v;exports.TencentEb=w;exports.UptimeKuma=l;exports.VolcEngineEvent=E;exports.VolcEngineMetric=$;exports.VolcEngineTLS=N;exports.Wecom=B;exports.Zabbix=s;
+`;exports.AWSCW=u;exports.AWSEventBridge=S;exports.AlertWebhook=K;exports.AliyunARMS=d;exports.AliyunCm=r;exports.AliyunCmEvent=o;exports.AliyunSLS=c;exports.AppDynamics=P;exports.AzureMonitor=h;exports.BaiDuBCM=m;exports.CustomAction=X;exports.CustomAlert=n;exports.CustomChange=H;exports.Dingtalk=B;exports.Dynatrace=A;exports.Email=t;exports.GoogleCM=I;exports.Grafana=i;exports.Graylog=F;exports.Guance=j;exports.HuaWeiCES=p;exports.HuaweiyunLTS=C;exports.IncidentWebhook=J;exports.InfluxDB=g;exports.Jiankongbao=L;exports.Jira=O;exports.Lark=q;exports.Meraki=R;exports.MicrosoftTeams=Z;exports.N9e=e;exports.OceanBase=k;exports.OpManager=W;exports.OpenFalcon=y;exports.PagerDuty=_;exports.Prometheus=a;exports.Sentry=T;exports.Skywalking=x;exports.Slack=V;exports.SolarWinds=M;exports.Splunk=D;exports.StateCloud=z;exports.Templates=Q;exports.TencentBK=f;exports.TencentCLS=b;exports.TencentCm=v;exports.TencentEb=w;exports.UptimeKuma=l;exports.VolcEngineEvent=E;exports.VolcEngineMetric=$;exports.VolcEngineTLS=N;exports.Wecom=G;exports.Zabbix=s;exports.Zilliz=U;

package/dist/zh.js

@@ -2917,7 +2917,7 @@ OCP告警通知-单条告警
 |提醒|Info|提醒|
 
 </div>
-`, x = `---
+`, F = `---
 title: "Graylog 告警事件"
 description: "通过 webhook 的方式同步Graylog告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-06-18T10:00:00+08:00"
@@ -3014,7 +3014,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/graylog-integration-guide"
 |1|Info|提醒|
 
 </div>
-`, F = `---
+`, x = `---
 title: "Skywalking 告警事件"
 description: "通过 webhook 的方式同步 Skywalking 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-06-20T10:00:00+08:00"
@@ -4628,7 +4628,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/meraki-integration-guide"
 | informational      | Info     | 提醒 |
 
 </div>
-`, j = `---
+`, z = `---
 title: "天翼云告警事件"
 description: "通过 webhook 的方式同步天翼云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4716,7 +4716,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 
 </div>
-`, U = `---
+`, j = `---
 title: "观测云告警事件"
 description: "通过 webhook 的方式同步观测云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4804,7 +4804,82 @@ url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
 | 数据断档     | Info     | 提醒 |
 
 </div>
-`, z = `---
+`, U = `---
+title: "zilliz 告警事件"
+description: "通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/zilliz-integration-guide"
+---
+
+通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **zilliz** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **zilliz** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  4. 点击 **创建路由**，为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间，也可以直接设置默认协作空间作为兜底，后续再按需调整。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在 zilliz
+---
+
+<div class="md-block">
+
+## 一、告警推送配置
+
+1. 登录您的 \`zilliz\` 控制台，在 \`Project Alerts\` 中，创建或修改 \`Alert\`。
+2. 在 \`Alert\` 编辑页面中的 \`Send to\` 部分，选择 \`Webhook\`，Webhook URL 填写告警集成的 <span class='integration_url' >推送地址</span>。
+3. 选中 \`Alert Resolution Notification\`，其他按需选择。
+4. 点击 \`Save\` 或 \`Create\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/zilliz-1.png" />
+
+</dev>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| 观测云 |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| CRITICAL   | Critical | 严重 |
+| WARNING   | Warning  | 警告 |
+
+
+</div>
+
+`, H = `---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2024-05-11T10:00:00+08:00"
@@ -4861,7 +4936,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`, H = `---
+`, O = `---
 title: ""
 description: ""
 date: "2024-05-11T10:00:00+08:00"
@@ -4935,7 +5010,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`, O = `---
+`, q = `---
 title: Contributing to our documentation — Meilisearch documentation
 description: The Meilisearch documentation is open-source. Learn how to help make it even better.
 sidebarDepth: 3
@@ -5052,7 +5127,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"/>
-`, q = `---
+`, B = `---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5203,7 +5278,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"/>
 
-`, B = `---
+`, G = `---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5283,7 +5358,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`, G = `---
+`, V = `---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5337,7 +5412,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 8. **Slack App 内 Other questions，报错**
    - 重新操作，遇到了还没被记录的问题
-   - 重试后仍然报错，联系客服`, V = `---
+   - 重试后仍然报错，联系客服`, Z = `---
 title: "Microsoft Teams集成"
 description: "通过集成 Microsoft Teams 第三方应用，实现在 Microsoft Teams 内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5600,7 +5675,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`, Z = `配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`, J = `配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5807,7 +5882,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`, J = `配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`, X = `配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6066,7 +6141,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`, X = `---
+   - 未来可能会更新，请定期查验`, Q = `---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -6908,25 +6983,25 @@ export {
   P as AppDynamics,
   h as AzureMonitor,
   m as BaiDuBCM,
-  J as CustomAction,
+  X as CustomAction,
   n as CustomAlert,
-  z as CustomChange,
-  q as Dingtalk,
+  H as CustomChange,
+  B as Dingtalk,
   A as Dynatrace,
   t as Email,
   I as GoogleCM,
   i as Grafana,
-  x as Graylog,
-  U as Guance,
+  F as Graylog,
+  j as Guance,
   p as HuaWeiCES,
   C as HuaweiyunLTS,
-  Z as IncidentWebhook,
+  J as IncidentWebhook,
   g as InfluxDB,
   L as Jiankongbao,
-  H as Jira,
-  O as Lark,
+  O as Jira,
+  q as Lark,
   R as Meraki,
-  V as MicrosoftTeams,
+  Z as MicrosoftTeams,
   e as N9e,
   k as OceanBase,
   W as OpManager,
@@ -6934,12 +7009,12 @@ export {
   _ as PagerDuty,
   a as Prometheus,
   T as Sentry,
-  F as Skywalking,
-  G as Slack,
+  x as Skywalking,
+  V as Slack,
   M as SolarWinds,
   D as Splunk,
-  j as StateCloud,
-  X as Templates,
+  z as StateCloud,
+  Q as Templates,
   f as TencentBK,
   b as TencentCLS,
   v as TencentCm,
@@ -6948,6 +7023,7 @@ export {
   E as VolcEngineEvent,
   $ as VolcEngineMetric,
   N as VolcEngineTLS,
-  B as Wecom,
-  s as Zabbix
+  G as Wecom,
+  s as Zabbix,
+  U as Zilliz
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "flashduty knowledge base",
   "type": "module",
   "scripts": {