flashduty-knowledge-base 1.2.3 → 1.2.4-beta.2

package/dist/en.d.ts

@@ -52,5 +52,7 @@ declare const docs: {
     IncidentWebhook: string;
     CustomAction: string;
     Templates: string;
+    HuaweiyunAPM: string;
+    JiraSync: string;
 };
 export default docs;

package/dist/esm/en.js

@@ -3124,7 +3124,7 @@ Choose this option when you need to route alerts to different channels based on
 |2|Info|Info|
 
 </div>
-`,_=`---
+`,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>
 
-`,L=`---
+`,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>
-`,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"
@@ -4051,7 +4051,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,N=`---
+`,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>
-`,P=`---
+`,N=`---
 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"
@@ -4640,6 +4640,112 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 `,q=`---
+title: "Huawei Cloud APM Alerts"
+description: "Sync Huawei Cloud APM alerts to Flashduty through webhook to achieve automatic alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/huawei-apm-integration-guide"
+---
+
+Sync Huawei Cloud APM alerts to Flashduty through webhook, to achieve automatic noise reduction of alerts.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can get an integration push URL through the following 2 methods, choose one of them.
+
+### Use dedicated integration
+
+When you don't need to route alerts to different channels, choose this method, it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to Flashduty console, select **Channels**, enter the details page of a channel
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Select **Huawei Cloud APM** integration, click **Save** to generate a card
+  4. Click the generated card to view the **push URL**, copy it for later use. Done.
+    
+</details>
+
+### Use shared integration
+
+When you need to route alerts to different channels based on alert payload information, this method is preferred.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
+  2. Select **Huawei Cloud APM** integration:
+        - **Integration Name**: Define a name for the current 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 Huawei Cloud
+---
+
+<div class="md-block">
+
+## I. Huawei Cloud APM Alert Push Configuration
+
+### Create FlashDuty Alert Channel
+
+1. Log in to your Huawei Cloud Console, search for \`SMN\` (Simple Message Notification) service and enter its console
+2. Select \`Topic Management=>Topics\` from the left navigation bar
+3. Click \`Create Topic\`, enter \`FlashDuty\` as the topic name in the edit page and confirm
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-1.png" alt="drawing" width="500"/>
+
+4. Return to the topic list and click \`Add Subscription\` in the newly created FlashDuty topic
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-2.png" alt="drawing" width="500"/>
+
+5. In the edit page, select \`HTTPS\` as the protocol, enter the **push URL** as the subscription endpoint and confirm
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-3.png" alt="drawing" width="500"/>
+
+6. After adding, check if the subscription status shows **Confirmed** in the subscription list
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-4.png" alt="drawing" width="500"/>
+
+### Configure Application Monitoring Alerts
+
+#### Step 1: Add Notification Configuration
+1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
+2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
+3. Click \`Confirm\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
+
+#### Step 2: Create Alert Policy
+1. Under \`Application Monitoring=>Metrics\`, select your application and click the \`Settings\` button
+2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
+3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
+4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
+5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
+6. Click \`Confirm\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
+
+**Note:** The current integration configuration only supports application monitoring alerts, and does not fully support front-end monitoring, link tracking, and App monitoring alerts.
+</div>
+
+## II. Status Mapping
+
+<div class="md-block">
+
+| Huawei Cloud APM | Flashduty | Severity |
+| ---------- | -------- | ---- |
+| CRITICAL | Critical | Critical |
+| COMMON | 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"
@@ -4696,7 +4802,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,O=`---
+`,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 +4876,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,j=`---
+`,$=`---
 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 +5011,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`,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 +5167,7 @@ After the application is released, you can access it via mobile/PC client. First
 |Enterprise|5,500,000|60|1st of each month|
 
 **Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
-`,H=`---
+`,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 +5246,7 @@ Integrate WeCom third-party application to receive and respond to alerts within
 7. **Incident notification fails with \`WeCom License Not Activated\`?**
 
    - Contact Flashduty customer service or dedicated support for license purchase and activation
-`,B=`---
+`,z=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2024-05-11T10:00:00+08:00"
@@ -5289,7 +5395,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`,z=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
+`,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.
 
 <span id="EventTypes"></span>
 
@@ -5910,7 +6016,89 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
 
 ### Update Status Page
 
-When an incident is confirmed to affect online services, trigger external status page updates to prompt`,J=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,Q=`---
+title: "Jira Sync"
+description: "Sync incidents with Jira issues through Jira Sync Webhook."
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jira-sync"
+---
+
+Through Jira Sync Webhook, you can associate and synchronize Flashduty incidents with Jira Issues, enabling integration between Flashduty and Jira.
+
+## Prerequisites
+- This integration is compatible with Jira Cloud, as well as versions 7.x and 8.x of Jira Server and Jira Data Center.
+- Currently, only one-way synchronization of incident information and status to Jira is supported. Information in Jira will not sync back to Flashduty.
+- For Jira Cloud, use an API Token in the password field during authorization configuration; for Jira Server or Data Center, use your Jira account password.
+
+## Getting API Token in Jira Cloud （Jira Server and Data Center please skip）
+
+- After logging into Jira Cloud, click your profile picture in the top right corner and select **Manage Account**.
+- On the **Manage Account** page, select the **Security** tab.
+- On the **Security** page, click **Create and manage API tokens**.
+- In the **Create and manage API tokens** dialog, enter an API token name and select an expiration time.
+- Click **Create** to generate the API token.
+- Copy the API token value and paste it into the API token field in Flashduty's authorization configuration.
+
+## Configuring Integration in Flashduty
+
+### 1. Create and Authenticate Jira Integration
+<div class="hide">
+
+In the Integration Center, select **Webhook**, choose **Jira Sync** integration, and fill in the following authentication information.
+
+</div>
+
+- **Jira Platform Type**: Choose based on your version. For Data Center version, select Self-hosted (Server).
+- **Service URL**: For Cloud version, enter your actual access URL, e.g., https://your-domain.atlassian.net. For Server version, enter your service access URL, e.g., https://your-jira-server-url.com.
+- **Username**: Your Jira account name. For Cloud version, enter your email; for Server version, enter your Jira username.
+- **API Token/Password**: Your Jira account credentials. For Cloud version, enter API Token; for Server version, enter your Jira account password.
+- After completion, click **Next** to proceed with configuration.
+
+**About Permissions**: Ensure your Jira account has permissions to access relevant projects, issue types, and create issues. Using an administrator account is recommended.
+
+### 2. Jira Integration Configuration
+
+- **Integration Name**: Define a name for this integration.
+- **Trigger Mode**:
+    - Automatic: Configure conditions for Flashduty to automatically sync qualifying incidents to Jira.
+    - Manual: Manually trigger Jira sync from the incident details page's more actions menu (integration name serves as trigger name).
+- **Project ID**: Select the target Jira project for synchronization.
+- **Issue Type**: Select the target Jira issue type.
+- **Channel**: Select the channel where this integration will be active. Only incidents within this channel can sync to Jira.
+- **Severity Mapping**: If the selected issue type doesn't support priority fields, this mapping cannot be configured.
+- **Custom Field Mapping**: Choose to sync certain or all incident labels and custom field content to Jira fields (text type fields only).
+
+### 3. About Updates
+
+- For incidents with existing Jira issues, updates to severity or status will automatically update in Jira, but Jira updates won't sync back to Flashduty.
+- Comments sync to Jira, but Jira comments won't sync back to Flashduty.
+- Updates to incident title, description, labels, or other fields won't update in Jira.
+
+### 4. Flashduty to Jira Mapping
+
+#### Field Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Summary | Title |
+| Description | Description |
+| Priority | Severity |
+| Reporter | Integration configured user |
+| Comments | Comments |
+
+#### Status Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Todo | Pending |
+| In Progress | In Progress |
+| Done | Resolved |
+
+### 5. Important Notes
+
+- 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=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -6513,4 +6701,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">
 
-`,Q={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:_,Dynatrace:L,HuaweiyunLTS:F,GoogleCM:x,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:E,VolcEngineEvent:D,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:q,Jira:O,Lark:j,Dingtalk:$,Wecom:H,Slack:B,MicrosoftTeams:V,AlertWebhook:z,IncidentWebhook:K,CustomAction:Z,Templates:J};module.exports=Q;
+`,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:L,Dynatrace:F,HuaweiyunLTS:_,GoogleCM:x,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:E,VolcEngineEvent:D,VolcEngineTLS:P,OpManager:N,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:z,MicrosoftTeams:V,AlertWebhook:J,IncidentWebhook:K,CustomAction:Z,Templates:X,HuaweiyunAPM:q,JiraSync:Q};module.exports=ee;

package/dist/esm/zh.js

@@ -4215,7 +4215,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-metric-integration-gui
 |通知|Info|提醒|
 
 </div>
-`,$=`---
+`,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>
-`,E=`---
+`,$=`---
 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>
-`,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"
@@ -4904,6 +4904,114 @@ url: "https://docs.flashcat.cloud/zh/flashduty/zilliz-integration-guide"
 </div>
 
 `,H=`---
+title: "华为云 APM 告警事件"
+description: "通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/huawei-apm-integration-guide"
+---
+
+通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **华为云 APM** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **华为云 APM** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  4. 点击 **创建路由**，为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间，也可以直接设置默认协作空间作为兜底，后续再按需调整。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在华为云 APM
+---
+
+<div class="md-block">
+
+
+## 一、华为云 APM 告警推送配置
+
+### 创建 FlashDuty 告警通道
+1. 登录您的华为云控制台，检索 \`SMN\` 消息通知服务产品，并进入对应产品控制台。
+2. 在左侧导航栏选择 \`主题管理=>主题\`。
+3. 点击 \`创建主题\`，在编辑页面中的主题名称处输入 \`FlashDuty\` 并点击确认。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-1.png" />
+
+4. 回到主题列表后，在刚创建的 FlashDuty 主题中点击 \`添加订阅\`。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-2.png" />
+
+5. 在编辑页面中，协议选择 \`HTTPS\`，订阅终端填写 **集成推送地址** 并点击确认。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-3.png" />
+
+6. 添加完成后，可以在订阅列表中查看已添加的订阅状态是否为 **已确认**。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-4.png" />
+
+### 配置应用监控告警
+
+#### 步骤1：添加通知配置
+1. 登录您的 \`华为云 APM\` 控制台，在 \`应用监控=>指标\` 中，点击 \`通知配置\`。
+2. 选择对应的区域后，点击 \`新增\`，在主题处选择已创建的 \`FlashDuty\` 主题。
+3. 点击 \`确认\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-1.png" />
+
+#### 步骤2：创建告警策略
+1. 在 \`应用监控=>指标\` 中，选择您的应用并点击 \`设置\` 按钮。
+2. 选择 \`告警策略\`，点击 \`新增自定义告警策略\` 或编辑已有的告警策略。
+3. 在 \`告警策略\` 编辑页面中，告警指标、告警条件等请按业务需要进行配置。
+4. \`告警内容\` 中在引用变量时，建议以K:V的格式进行配置，便于后续告警事件的解析，比如 host:\${hostInfo}。
+5. \`通知对象\` 中选择已创建的 \`FlashDuty\` 通知渠道。
+6. 点击 \`确认\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-2.png" />
+
+**注意：** 当前集成配置仅支持应用监控告警，还未完全兼容前端监控、链路追踪、App监控告警。
+</div>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| 华为云 APM |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| 严重告警   | Critical | 严重 |
+| 轻微告警   | Info  | 提醒 |
+
+
+</div>
+
+`,O=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2024-05-11T10:00:00+08:00"
@@ -4960,7 +5068,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议，对
     
 </details>
 
-`,O=`---
+`,q=`---
 title: "Jira 事件集成指引"
 description: "通过 webhook 的方式同步 Jira Issue 事件到 Flashduty，实现变更事件收集。"
 date: "2024-05-11T10:00:00+08:00"
@@ -5034,7 +5142,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息，并按照下边
 如您希望变更此映射关系，请联系 Flashduty。
 
 </div>
-`,q=`---
+`,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
@@ -5144,14 +5252,34 @@ sidebarDepth: 3
     - 确保账户已经完成关联，前往 飞书 > 工作台 > 搜索应用名称 > 打开应用，完成一次登录并关联（飞书< - >Flashduty）账号。如果已经登录过，尝试点击右上角菜单，切换账户，重新登录来绑定账号
     - 确保已购买足够的 license，已使用 license 情况，可以在控制台 > 费用中心查看
 
-2. **分派策略飞书群聊列表为空**？
+3. **分派策略飞书群聊列表为空**？
 
     - 前往 飞书，选择群聊会话，添加已创建的Flashduty机器人，如下图所示：
     - 回到分派策略配置页面，刷新后重新选择群聊列表
 
 <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"/>
-`,B=`---
+
+4. **飞书自建应用 API 限制：** [飞书文档说明](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit)
+
+    **调用量限制：**
+
+    |     飞书版本     | 调用总量/月 | 刷新时间  |                       
+    | :----------: | :--: | :----: |
+    |基础免费版|10,000 次|每个自然月的 1 号|
+    |其他版本|不限制|-|        
+
+    **频控限制：**
+
+    |    场景     | 限制 |                   
+    | :----------: | :--: | 
+    |所有接口|每个应用最高频率 50 次/秒|
+    |发消息接口|每个应用最高频率 1000 次/分钟|
+    |群机器人 Webhook|最高频率 100 次/分钟|
+    |给同一个用户或同一个群发消息|最高频率 5 次/秒|
+
+    **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
+`,J=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5302,6 +5430,15 @@ 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"/>
 
+4. **钉钉自建应用 API 调用量：** [钉钉文档说明](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI)
+
+|     钉钉版本     | 调用总量/月 | QPS| 刷新时间  |                       
+| :----------: | :--: | :----: | :----:|
+|标准版|10,000 次|20|每月1日|
+|专业版|50万次|40|     每月1日          |
+|专属版|550万次|60|     每月1日          |
+
+**注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
 `,G=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
@@ -5436,7 +5573,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/slack-integration-guide"
 
 8. **Slack App 内 Other questions，报错**
    - 重新操作，遇到了还没被记录的问题
-   - 重试后仍然报错，联系客服`,Z=`---
+   - 重试后仍然报错，联系客服`,K=`---
 title: "Microsoft Teams集成"
 description: "通过集成 Microsoft Teams 第三方应用，实现在 Microsoft Teams 内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5531,7 +5668,7 @@ Microsoft Teams 集成现处于 Beta 阶段，在关联前您需要先完成以
 暂不支持
 </details>
 
-`,K=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
+`,Z=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5699,7 +5836,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验
-`,J=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
+`,X=`配置故障 Webhook，当故障发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5906,7 +6043,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,X=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,Y=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6166,6 +6303,91 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
    - 未来可能会更新，请定期查验`,Q=`---
+title: "Jira 同步"
+description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
+---
+
+通过 Jira 同步 Webhook，将 Flashduty 的故障与 Jira Issue 进行关联同步，实现 Flashduty 与 Jira 的联动。
+
+## 前提说明
+- 该集成兼容 Jira Cloud 以及 Jira Server 和 Jira Data Center 的 7.x 和 8.x 版本。
+- 目前仅支持将故障相关信息或状态单向同步到 Jira 中，Jira 中的信息不会同步到 Flashduty 中。
+- 对于 Jira Cloud，请在授权配置的密码处填写 API Token；而对于Jira Server 或 Data Center，则使用您的 Jira 账户登录密码即可。
+
+## 在 Jira Cloud 中获取 API Token （Jira Server 和 Data Center 请跳过）
+
+- 登录 Jira Cloud 后，点击右上角头像，选择 **管理账户**。
+- 在 **管理账户** 页面中，选择 **安全性** 选项卡。
+- 在 **安全性** 页面中，点击 **创建并管理 API 令牌** 按钮。
+- 在 **创建并管理 API 令牌** 弹窗中，填写 API token 名称，并选择过期时间。
+- 点击 **创建** 按钮，创建 API token。
+- 创建完成后，复制 API token 值，并粘贴到 Flashduty 授权配置中的 API 令牌处。
+
+## 在 Flashduty 中配置集成
+
+### 1. 创建并认证 Jira 集成
+<div class="hide">
+
+在集成中心，选择 **Webhook** ，选择 **Jira 同步** 集成，并填写以下认证信息。
+
+</div>
+
+- **Jira 平台类型**：根据您使用的版本进行选择，如果是 Data Center 版本的请选择私有化（Server） 即可。
+- **服务地址**：Cloud 版本请填写您的实际访问地址，例如： https://your-domain.atlassian.net，Server 版本请填写您的服务访问地址，例如： https://your-jira-server-url.com。
+- **用户名**：您的 Jira 账户名，Cloud 版本请填写您的邮箱，Server 版本请填写您的 Jira 账户名。
+- **API令牌/密码**：您的 Jira 账户密码，Cloud 版本请填写 API Token，Server 版本请填写您的 Jira 账户密码。
+- 填写完成后，点击 **下一步** 按钮，进行相关配置。
+
+**关于权限**：请确保您的 Jira 账户拥有获取相关项目、事务类型以及创建 Issue 等权限，建议使用管理员账户。
+
+### 2. Jira 集成配置
+
+- **集成名称**：为当前集成定义一个名称。
+- **触发模式**：
+    - 自动触发：需要配置相应的条件，Flashduty 会自动将符合条件的故障同步到 Jira 中。
+    - 手动触发：需要在故障详情页的更多操作中手动触发 Jira 同步（该集成配置的名称为触发器名称）。
+- **项目 ID**：选择需要同步至 Jira 的项目。
+- **事务类型**：选择需要同步至 Jira 的事务类型。
+- **协作空间**：选择该集成生效的协作空间，只有该协作空间内的故障才可以同步至 Jira 中。
+- **严重程度映射**：如果选择的事务类型不支持优先级字段，则无法配置该映射关系。
+- **自定义字段映射**：可以选择将故障的某些标签或所有标签以及自定义字段内容同步至 Jira 的字段中（仅支持文本类型的字段）。
+
+### 3. 关于更新
+
+- 已经创建 Issue 的故障，如果您更新了故障的严重程度、状态，Jira 中会自动更新，但 Jira 中的更新不会同步到 Flashduty 中。
+- 评论信息会同步到 Jira 中，但 Jira 中更新的内容不会同步到 Flashduty 中。
+- 更新故障中的标题、描述、标签等字段的信息，Jira 中不会更新。
+
+
+### 4. Flashduty 与 Jira 的映射关系
+
+#### 字段映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  摘要  | 标题 | 
+| 描述   | 描述  | 
+| 优先级 | 严重程度 | 
+| 报告人 | 集成配置的用户 | 
+| 评论 | 评论 | 
+
+
+#### 状态映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  Todo  | 待处理 | 
+|  In Progress  | 处理中 | 
+|  Done  | 已解决 | 
+
+
+### 5. 注意事项
+
+- Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
+- Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
+`,nn=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -6995,4 +7217,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"/>
 
 
-`,Y={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:L,AWSEventBridge:A,Dynatrace:S,HuaweiyunLTS:C,GoogleCM:I,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:$,VolcEngineTLS:E,OpManager:R,Meraki:W,Zilliz:U,StateCloud:z,Guance:j,CustomChange:H,Jira:O,Lark:q,Dingtalk:B,Wecom:G,Slack:V,MicrosoftTeams:Z,AlertWebhook:K,IncidentWebhook:J,CustomAction:X,Templates:Q};module.exports=Y;
+`,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:L,AWSEventBridge:A,Dynatrace:S,HuaweiyunLTS:C,GoogleCM:I,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:$,OpManager:W,Meraki:R,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;

package/dist/iife/en.js

@@ -311,7 +311,7 @@ attachment_stripped = true
 
 Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
 
-`,o=`---
+`,i=`---
 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>
 
-`,i=`---
+`,o=`---
 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"
@@ -1554,7 +1554,7 @@ Alibaba Cloud SLS monitoring to Flashduty alert severity mapping:
 | 2                | Info      | Info |
 
 </div>
-`,u={CustomAlert:t,Email:a,N9e:o,Prometheus:i,Grafana:s,Zabbix:r,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:c,AliyunCm:h,AliyunSLS:e,AWSCW:e,AzureMonitor:`---
+`,u={CustomAlert:t,Email:a,N9e:i,Prometheus:o,Grafana:s,Zabbix:r,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:c,AliyunCm:h,AliyunSLS:e,AWSCW:e,AzureMonitor:`---
 title: "AWS CloudWatch Integration"
 description: "Sync AWS CloudWatch alert events to Flashduty via webhook to achieve automated alert noise reduction"
 date: "2024-05-11T10:00:00+08:00"
@@ -6513,4 +6513,192 @@ 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">
 
+`,HuaweiyunAPM:`---
+title: "Huawei Cloud APM Alerts"
+description: "Sync Huawei Cloud APM alerts to Flashduty through webhook to achieve automatic alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/huawei-apm-integration-guide"
+---
+
+Sync Huawei Cloud APM alerts to Flashduty through webhook, to achieve automatic noise reduction of alerts.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can get an integration push URL through the following 2 methods, choose one of them.
+
+### Use dedicated integration
+
+When you don't need to route alerts to different channels, choose this method, it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to Flashduty console, select **Channels**, enter the details page of a channel
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Select **Huawei Cloud APM** integration, click **Save** to generate a card
+  4. Click the generated card to view the **push URL**, copy it for later use. Done.
+    
+</details>
+
+### Use shared integration
+
+When you need to route alerts to different channels based on alert payload information, this method is preferred.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
+  2. Select **Huawei Cloud APM** integration:
+        - **Integration Name**: Define a name for the current 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 Huawei Cloud
+---
+
+<div class="md-block">
+
+## I. Huawei Cloud APM Alert Push Configuration
+
+### Create FlashDuty Alert Channel
+
+1. Log in to your Huawei Cloud Console, search for \`SMN\` (Simple Message Notification) service and enter its console
+2. Select \`Topic Management=>Topics\` from the left navigation bar
+3. Click \`Create Topic\`, enter \`FlashDuty\` as the topic name in the edit page and confirm
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-1.png" alt="drawing" width="500"/>
+
+4. Return to the topic list and click \`Add Subscription\` in the newly created FlashDuty topic
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-2.png" alt="drawing" width="500"/>
+
+5. In the edit page, select \`HTTPS\` as the protocol, enter the **push URL** as the subscription endpoint and confirm
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-3.png" alt="drawing" width="500"/>
+
+6. After adding, check if the subscription status shows **Confirmed** in the subscription list
+
+<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-4.png" alt="drawing" width="500"/>
+
+### Configure Application Monitoring Alerts
+
+#### Step 1: Add Notification Configuration
+1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
+2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
+3. Click \`Confirm\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
+
+#### Step 2: Create Alert Policy
+1. Under \`Application Monitoring=>Metrics\`, select your application and click the \`Settings\` button
+2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
+3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
+4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
+5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
+6. Click \`Confirm\` to complete the configuration
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
+
+**Note:** The current integration configuration only supports application monitoring alerts, and does not fully support front-end monitoring, link tracking, and App monitoring alerts.
+</div>
+
+## II. Status Mapping
+
+<div class="md-block">
+
+| Huawei Cloud APM | Flashduty | Severity |
+| ---------- | -------- | ---- |
+| CRITICAL | Critical | Critical |
+| COMMON | Info | Info |
+
+</div>
+
+`,JiraSync:`---
+title: "Jira Sync"
+description: "Sync incidents with Jira issues through Jira Sync Webhook."
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jira-sync"
+---
+
+Through Jira Sync Webhook, you can associate and synchronize Flashduty incidents with Jira Issues, enabling integration between Flashduty and Jira.
+
+## Prerequisites
+- This integration is compatible with Jira Cloud, as well as versions 7.x and 8.x of Jira Server and Jira Data Center.
+- Currently, only one-way synchronization of incident information and status to Jira is supported. Information in Jira will not sync back to Flashduty.
+- For Jira Cloud, use an API Token in the password field during authorization configuration; for Jira Server or Data Center, use your Jira account password.
+
+## Getting API Token in Jira Cloud （Jira Server and Data Center please skip）
+
+- After logging into Jira Cloud, click your profile picture in the top right corner and select **Manage Account**.
+- On the **Manage Account** page, select the **Security** tab.
+- On the **Security** page, click **Create and manage API tokens**.
+- In the **Create and manage API tokens** dialog, enter an API token name and select an expiration time.
+- Click **Create** to generate the API token.
+- Copy the API token value and paste it into the API token field in Flashduty's authorization configuration.
+
+## Configuring Integration in Flashduty
+
+### 1. Create and Authenticate Jira Integration
+<div class="hide">
+
+In the Integration Center, select **Webhook**, choose **Jira Sync** integration, and fill in the following authentication information.
+
+</div>
+
+- **Jira Platform Type**: Choose based on your version. For Data Center version, select Self-hosted (Server).
+- **Service URL**: For Cloud version, enter your actual access URL, e.g., https://your-domain.atlassian.net. For Server version, enter your service access URL, e.g., https://your-jira-server-url.com.
+- **Username**: Your Jira account name. For Cloud version, enter your email; for Server version, enter your Jira username.
+- **API Token/Password**: Your Jira account credentials. For Cloud version, enter API Token; for Server version, enter your Jira account password.
+- After completion, click **Next** to proceed with configuration.
+
+**About Permissions**: Ensure your Jira account has permissions to access relevant projects, issue types, and create issues. Using an administrator account is recommended.
+
+### 2. Jira Integration Configuration
+
+- **Integration Name**: Define a name for this integration.
+- **Trigger Mode**:
+    - Automatic: Configure conditions for Flashduty to automatically sync qualifying incidents to Jira.
+    - Manual: Manually trigger Jira sync from the incident details page's more actions menu (integration name serves as trigger name).
+- **Project ID**: Select the target Jira project for synchronization.
+- **Issue Type**: Select the target Jira issue type.
+- **Channel**: Select the channel where this integration will be active. Only incidents within this channel can sync to Jira.
+- **Severity Mapping**: If the selected issue type doesn't support priority fields, this mapping cannot be configured.
+- **Custom Field Mapping**: Choose to sync certain or all incident labels and custom field content to Jira fields (text type fields only).
+
+### 3. About Updates
+
+- For incidents with existing Jira issues, updates to severity or status will automatically update in Jira, but Jira updates won't sync back to Flashduty.
+- Comments sync to Jira, but Jira comments won't sync back to Flashduty.
+- Updates to incident title, description, labels, or other fields won't update in Jira.
+
+### 4. Flashduty to Jira Mapping
+
+#### Field Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Summary | Title |
+| Description | Description |
+| Priority | Severity |
+| Reporter | Integration configured user |
+| Comments | Comments |
+
+#### Status Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Todo | Pending |
+| In Progress | In Progress |
+| Done | Resolved |
+
+### 5. Important Notes
+
+- 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.
 `};n.FlashDocsEn=u})(window);

package/dist/iife/zh.js

@@ -5144,13 +5144,33 @@ sidebarDepth: 3
     - 确保账户已经完成关联，前往 飞书 > 工作台 > 搜索应用名称 > 打开应用，完成一次登录并关联（飞书< - >Flashduty）账号。如果已经登录过，尝试点击右上角菜单，切换账户，重新登录来绑定账号
     - 确保已购买足够的 license，已使用 license 情况，可以在控制台 > 费用中心查看
 
-2. **分派策略飞书群聊列表为空**？
+3. **分派策略飞书群聊列表为空**？
 
     - 前往 飞书，选择群聊会话，添加已创建的Flashduty机器人，如下图所示：
     - 回到分派策略配置页面，刷新后重新选择群聊列表
 
 <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"/>
+
+4. **飞书自建应用 API 限制：** [飞书文档说明](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit)
+
+    **调用量限制：**
+
+    |     飞书版本     | 调用总量/月 | 刷新时间  |                       
+    | :----------: | :--: | :----: |
+    |基础免费版|10,000 次|每个自然月的 1 号|
+    |其他版本|不限制|-|        
+
+    **频控限制：**
+
+    |    场景     | 限制 |                   
+    | :----------: | :--: | 
+    |所有接口|每个应用最高频率 50 次/秒|
+    |发消息接口|每个应用最高频率 1000 次/分钟|
+    |群机器人 Webhook|最高频率 100 次/分钟|
+    |给同一个用户或同一个群发消息|最高频率 5 次/秒|
+
+    **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
 `,Dingtalk:`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
@@ -5302,6 +5322,15 @@ 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"/>
 
+4. **钉钉自建应用 API 调用量：** [钉钉文档说明](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI)
+
+|     钉钉版本     | 调用总量/月 | QPS| 刷新时间  |                       
+| :----------: | :--: | :----: | :----:|
+|标准版|10,000 次|20|每月1日|
+|专业版|50万次|40|     每月1日          |
+|专属版|550万次|60|     每月1日          |
+
+**注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
 `,Wecom:`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
@@ -6995,4 +7024,197 @@ 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"/>
 
 
+`,HuaweiyunAPM:`---
+title: "华为云 APM 告警事件"
+description: "通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty，实现告警事件自动化降噪处理"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/huawei-apm-integration-guide"
+---
+
+通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty，实现告警事件自动化降噪处理。
+
+<div class="hide">
+
+## 在 Flashduty
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **华为云 APM** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+
+    
+</details>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<details>
+  <summary>展开</summary>
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **华为云 APM** 集成： 
+        - **集成名称**：为当前集成定义一个名称。
+  3. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  4. 点击 **创建路由**，为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间，也可以直接设置默认协作空间作为兜底，后续再按需调整。
+  5. 完成。
+    
+</details>
+</div>
+
+## 在华为云 APM
+---
+
+<div class="md-block">
+
+
+## 一、华为云 APM 告警推送配置
+
+### 创建 FlashDuty 告警通道
+1. 登录您的华为云控制台，检索 \`SMN\` 消息通知服务产品，并进入对应产品控制台。
+2. 在左侧导航栏选择 \`主题管理=>主题\`。
+3. 点击 \`创建主题\`，在编辑页面中的主题名称处输入 \`FlashDuty\` 并点击确认。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-1.png" />
+
+4. 回到主题列表后，在刚创建的 FlashDuty 主题中点击 \`添加订阅\`。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-2.png" />
+
+5. 在编辑页面中，协议选择 \`HTTPS\`，订阅终端填写 **集成推送地址** 并点击确认。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-3.png" />
+
+6. 添加完成后，可以在订阅列表中查看已添加的订阅状态是否为 **已确认**。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-4.png" />
+
+### 配置应用监控告警
+
+#### 步骤1：添加通知配置
+1. 登录您的 \`华为云 APM\` 控制台，在 \`应用监控=>指标\` 中，点击 \`通知配置\`。
+2. 选择对应的区域后，点击 \`新增\`，在主题处选择已创建的 \`FlashDuty\` 主题。
+3. 点击 \`确认\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-1.png" />
+
+#### 步骤2：创建告警策略
+1. 在 \`应用监控=>指标\` 中，选择您的应用并点击 \`设置\` 按钮。
+2. 选择 \`告警策略\`，点击 \`新增自定义告警策略\` 或编辑已有的告警策略。
+3. 在 \`告警策略\` 编辑页面中，告警指标、告警条件等请按业务需要进行配置。
+4. \`告警内容\` 中在引用变量时，建议以K:V的格式进行配置，便于后续告警事件的解析，比如 host:\${hostInfo}。
+5. \`通知对象\` 中选择已创建的 \`FlashDuty\` 通知渠道。
+6. 点击 \`确认\` 完成配置。
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-2.png" />
+
+**注意：** 当前集成配置仅支持应用监控告警，还未完全兼容前端监控、链路追踪、App监控告警。
+</div>
+
+## 二、状态对照
+
+<div class="md-block">
+
+| 华为云 APM |  Flashduty | 状态 |
+| ---------- | -------- | ---- |
+| 严重告警   | Critical | 严重 |
+| 轻微告警   | Info  | 提醒 |
+
+
+</div>
+
+`,JiraSync:`---
+title: "Jira 同步"
+description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
+---
+
+通过 Jira 同步 Webhook，将 Flashduty 的故障与 Jira Issue 进行关联同步，实现 Flashduty 与 Jira 的联动。
+
+## 前提说明
+- 该集成兼容 Jira Cloud 以及 Jira Server 和 Jira Data Center 的 7.x 和 8.x 版本。
+- 目前仅支持将故障相关信息或状态单向同步到 Jira 中，Jira 中的信息不会同步到 Flashduty 中。
+- 对于 Jira Cloud，请在授权配置的密码处填写 API Token；而对于Jira Server 或 Data Center，则使用您的 Jira 账户登录密码即可。
+
+## 在 Jira Cloud 中获取 API Token （Jira Server 和 Data Center 请跳过）
+
+- 登录 Jira Cloud 后，点击右上角头像，选择 **管理账户**。
+- 在 **管理账户** 页面中，选择 **安全性** 选项卡。
+- 在 **安全性** 页面中，点击 **创建并管理 API 令牌** 按钮。
+- 在 **创建并管理 API 令牌** 弹窗中，填写 API token 名称，并选择过期时间。
+- 点击 **创建** 按钮，创建 API token。
+- 创建完成后，复制 API token 值，并粘贴到 Flashduty 授权配置中的 API 令牌处。
+
+## 在 Flashduty 中配置集成
+
+### 1. 创建并认证 Jira 集成
+<div class="hide">
+
+在集成中心，选择 **Webhook** ，选择 **Jira 同步** 集成，并填写以下认证信息。
+
+</div>
+
+- **Jira 平台类型**：根据您使用的版本进行选择，如果是 Data Center 版本的请选择私有化（Server） 即可。
+- **服务地址**：Cloud 版本请填写您的实际访问地址，例如： https://your-domain.atlassian.net，Server 版本请填写您的服务访问地址，例如： https://your-jira-server-url.com。
+- **用户名**：您的 Jira 账户名，Cloud 版本请填写您的邮箱，Server 版本请填写您的 Jira 账户名。
+- **API令牌/密码**：您的 Jira 账户密码，Cloud 版本请填写 API Token，Server 版本请填写您的 Jira 账户密码。
+- 填写完成后，点击 **下一步** 按钮，进行相关配置。
+
+**关于权限**：请确保您的 Jira 账户拥有获取相关项目、事务类型以及创建 Issue 等权限，建议使用管理员账户。
+
+### 2. Jira 集成配置
+
+- **集成名称**：为当前集成定义一个名称。
+- **触发模式**：
+    - 自动触发：需要配置相应的条件，Flashduty 会自动将符合条件的故障同步到 Jira 中。
+    - 手动触发：需要在故障详情页的更多操作中手动触发 Jira 同步（该集成配置的名称为触发器名称）。
+- **项目 ID**：选择需要同步至 Jira 的项目。
+- **事务类型**：选择需要同步至 Jira 的事务类型。
+- **协作空间**：选择该集成生效的协作空间，只有该协作空间内的故障才可以同步至 Jira 中。
+- **严重程度映射**：如果选择的事务类型不支持优先级字段，则无法配置该映射关系。
+- **自定义字段映射**：可以选择将故障的某些标签或所有标签以及自定义字段内容同步至 Jira 的字段中（仅支持文本类型的字段）。
+
+### 3. 关于更新
+
+- 已经创建 Issue 的故障，如果您更新了故障的严重程度、状态，Jira 中会自动更新，但 Jira 中的更新不会同步到 Flashduty 中。
+- 评论信息会同步到 Jira 中，但 Jira 中更新的内容不会同步到 Flashduty 中。
+- 更新故障中的标题、描述、标签等字段的信息，Jira 中不会更新。
+
+
+### 4. Flashduty 与 Jira 的映射关系
+
+#### 字段映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  摘要  | 标题 | 
+| 描述   | 描述  | 
+| 优先级 | 严重程度 | 
+| 报告人 | 集成配置的用户 | 
+| 评论 | 评论 | 
+
+
+#### 状态映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  Todo  | 待处理 | 
+|  In Progress  | 处理中 | 
+|  Done  | 已解决 | 
+
+
+### 5. 注意事项
+
+- Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
+- Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
 `};n.FlashDocsZh=t})(window);

package/dist/zh.d.ts

@@ -52,5 +52,7 @@ declare const docs: {
     IncidentWebhook: string;
     CustomAction: string;
     Templates: string;
+    HuaweiyunAPM: string;
+    JiraSync: string;
 };
 export default docs;

package/package.json

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