flashduty-knowledge-base 1.2.3 → 1.2.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/en.d.ts +1 -0
- package/dist/esm/en.js +121 -15
- package/dist/esm/zh.js +118 -10
- package/dist/iife/en.js +106 -0
- package/dist/iife/zh.js +108 -0
- package/dist/zh.d.ts +1 -0
- package/package.json +1 -1
package/dist/en.d.ts
CHANGED
package/dist/esm/en.js
CHANGED
|
@@ -469,7 +469,7 @@ Nightingale/Flashcat to Flashduty alert severity mapping:
|
|
|
469
469
|
|
|
470
470
|
</details>
|
|
471
471
|
|
|
472
|
-
`,
|
|
472
|
+
`,o=`---
|
|
473
473
|
title: "Prometheus Integration Guide"
|
|
474
474
|
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."
|
|
475
475
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -651,7 +651,7 @@ Prometheus to Flashduty severity mapping:
|
|
|
651
651
|
|
|
652
652
|
|
|
653
653
|
|
|
654
|
-
`,
|
|
654
|
+
`,i=`---
|
|
655
655
|
title: "Grafana Integration"
|
|
656
656
|
description: "Sync Grafana alert events to Flashduty via webhook to achieve automated alert noise reduction."
|
|
657
657
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -3124,7 +3124,7 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
3124
3124
|
|2|Info|Info|
|
|
3125
3125
|
|
|
3126
3126
|
</div>
|
|
3127
|
-
`,
|
|
3127
|
+
`,L=`---
|
|
3128
3128
|
title: "AWS EventBridge Alert Events"
|
|
3129
3129
|
description: "Sync AWS EventBridge alert events to Flashduty via webhook for automated alert noise reduction"
|
|
3130
3130
|
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
|
|
|
3226
3226
|
|
|
3227
3227
|
</div>
|
|
3228
3228
|
|
|
3229
|
-
`,
|
|
3229
|
+
`,_=`---
|
|
3230
3230
|
title: "Dynatrace Alert Events"
|
|
3231
3231
|
description: "Sync Dynatrace alert events to Flashduty via webhook to achieve automated alert noise reduction."
|
|
3232
3232
|
date: "2024-08-20T10:00:00+08:00"
|
|
@@ -4640,6 +4640,112 @@ Choose this method when you need to route alerts to different channels based on
|
|
|
4640
4640
|
</div>
|
|
4641
4641
|
|
|
4642
4642
|
`,q=`---
|
|
4643
|
+
title: "Huawei Cloud APM Alerts"
|
|
4644
|
+
description: "Sync Huawei Cloud APM alerts to Flashduty through webhook to achieve automatic alert noise reduction"
|
|
4645
|
+
date: "2024-07-05T10:00:00+08:00"
|
|
4646
|
+
url: "https://docs.flashcat.cloud/en/flashduty/huawei-apm-integration-guide"
|
|
4647
|
+
---
|
|
4648
|
+
|
|
4649
|
+
Sync Huawei Cloud APM alerts to Flashduty through webhook, to achieve automatic noise reduction of alerts.
|
|
4650
|
+
|
|
4651
|
+
<div class="hide">
|
|
4652
|
+
|
|
4653
|
+
## In Flashduty
|
|
4654
|
+
---
|
|
4655
|
+
You can get an integration push URL through the following 2 methods, choose one of them.
|
|
4656
|
+
|
|
4657
|
+
### Use dedicated integration
|
|
4658
|
+
|
|
4659
|
+
When you don't need to route alerts to different channels, choose this method, it's simpler.
|
|
4660
|
+
|
|
4661
|
+
<details>
|
|
4662
|
+
<summary>Expand</summary>
|
|
4663
|
+
|
|
4664
|
+
1. Go to Flashduty console, select **Channels**, enter the details page of a channel
|
|
4665
|
+
2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
|
|
4666
|
+
3. Select **Huawei Cloud APM** integration, click **Save** to generate a card
|
|
4667
|
+
4. Click the generated card to view the **push URL**, copy it for later use. Done.
|
|
4668
|
+
|
|
4669
|
+
</details>
|
|
4670
|
+
|
|
4671
|
+
### Use shared integration
|
|
4672
|
+
|
|
4673
|
+
When you need to route alerts to different channels based on alert payload information, this method is preferred.
|
|
4674
|
+
|
|
4675
|
+
<details>
|
|
4676
|
+
<summary>Expand</summary>
|
|
4677
|
+
|
|
4678
|
+
1. Go to Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
|
|
4679
|
+
2. Select **Huawei Cloud APM** integration:
|
|
4680
|
+
- **Integration Name**: Define a name for the current integration
|
|
4681
|
+
3. Click **Save** and copy the newly generated **push URL** for later use
|
|
4682
|
+
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
|
|
4683
|
+
5. Done.
|
|
4684
|
+
|
|
4685
|
+
</details>
|
|
4686
|
+
</div>
|
|
4687
|
+
|
|
4688
|
+
## In Huawei Cloud
|
|
4689
|
+
---
|
|
4690
|
+
|
|
4691
|
+
<div class="md-block">
|
|
4692
|
+
|
|
4693
|
+
## I. Huawei Cloud APM Alert Push Configuration
|
|
4694
|
+
|
|
4695
|
+
### Create FlashDuty Alert Channel
|
|
4696
|
+
|
|
4697
|
+
1. Log in to your Huawei Cloud Console, search for \`SMN\` (Simple Message Notification) service and enter its console
|
|
4698
|
+
2. Select \`Topic Management=>Topics\` from the left navigation bar
|
|
4699
|
+
3. Click \`Create Topic\`, enter \`FlashDuty\` as the topic name in the edit page and confirm
|
|
4700
|
+
|
|
4701
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-1.png" alt="drawing" width="500"/>
|
|
4702
|
+
|
|
4703
|
+
4. Return to the topic list and click \`Add Subscription\` in the newly created FlashDuty topic
|
|
4704
|
+
|
|
4705
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-2.png" alt="drawing" width="500"/>
|
|
4706
|
+
|
|
4707
|
+
5. In the edit page, select \`HTTPS\` as the protocol, enter the **push URL** as the subscription endpoint and confirm
|
|
4708
|
+
|
|
4709
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-3.png" alt="drawing" width="500"/>
|
|
4710
|
+
|
|
4711
|
+
6. After adding, check if the subscription status shows **Confirmed** in the subscription list
|
|
4712
|
+
|
|
4713
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-4.png" alt="drawing" width="500"/>
|
|
4714
|
+
|
|
4715
|
+
### Configure Application Monitoring Alerts
|
|
4716
|
+
|
|
4717
|
+
#### Step 1: Add Notification Configuration
|
|
4718
|
+
1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
|
|
4719
|
+
2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
|
|
4720
|
+
3. Click \`Confirm\` to complete the configuration
|
|
4721
|
+
|
|
4722
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
|
|
4723
|
+
|
|
4724
|
+
#### Step 2: Create Alert Policy
|
|
4725
|
+
1. Under \`Application Monitoring=>Metrics\`, select your application and click the \`Settings\` button
|
|
4726
|
+
2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
|
|
4727
|
+
3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
|
|
4728
|
+
4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
|
|
4729
|
+
5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
|
|
4730
|
+
6. Click \`Confirm\` to complete the configuration
|
|
4731
|
+
|
|
4732
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
|
|
4733
|
+
|
|
4734
|
+
**Note:** The current integration configuration only supports application monitoring alerts, and does not fully support front-end monitoring, link tracking, and App monitoring alerts.
|
|
4735
|
+
</div>
|
|
4736
|
+
|
|
4737
|
+
## II. Status Mapping
|
|
4738
|
+
|
|
4739
|
+
<div class="md-block">
|
|
4740
|
+
|
|
4741
|
+
| Huawei Cloud APM | Flashduty | Severity |
|
|
4742
|
+
| ---------- | -------- | ---- |
|
|
4743
|
+
| CRITICAL | Critical | Critical |
|
|
4744
|
+
| COMMON | Info | Info |
|
|
4745
|
+
|
|
4746
|
+
</div>
|
|
4747
|
+
|
|
4748
|
+
`,O=`---
|
|
4643
4749
|
title: "Custom Change Event Integration Guide"
|
|
4644
4750
|
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."
|
|
4645
4751
|
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
|
|
|
4696
4802
|
|
|
4697
4803
|
</details>
|
|
4698
4804
|
|
|
4699
|
-
`,
|
|
4805
|
+
`,j=`---
|
|
4700
4806
|
title: "Jira Issue Events"
|
|
4701
4807
|
description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
|
|
4702
4808
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4770,7 +4876,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
|
|
|
4770
4876
|
Please contact Flashduty if you wish to modify this mapping.
|
|
4771
4877
|
|
|
4772
4878
|
</div>
|
|
4773
|
-
|
|
4879
|
+
`,$=`---
|
|
4774
4880
|
title: Contributing to our documentation — Meilisearch documentation
|
|
4775
4881
|
description: The Meilisearch documentation is open-source. Learn how to help make it even better.
|
|
4776
4882
|
sidebarDepth: 3
|
|
@@ -4905,7 +5011,7 @@ Once published, you can access the application via mobile/PC client. First-time
|
|
|
4905
5011
|
|Group Bot Webhook|Maximum 100 calls/minute|
|
|
4906
5012
|
|Sending messages to the same user or group|Maximum 5 calls/second|
|
|
4907
5013
|
|
|
4908
|
-
**Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably
|
|
5014
|
+
**Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,H=`---
|
|
4909
5015
|
title: "Dingtalk Integration"
|
|
4910
5016
|
description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
|
|
4911
5017
|
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
|
|
|
5061
5167
|
|Enterprise|5,500,000|60|1st of each month|
|
|
5062
5168
|
|
|
5063
5169
|
**Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
|
|
5064
|
-
`,
|
|
5170
|
+
`,B=`---
|
|
5065
5171
|
title: "WeCom Integration"
|
|
5066
5172
|
description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
|
|
5067
5173
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5140,7 +5246,7 @@ Integrate WeCom third-party application to receive and respond to alerts within
|
|
|
5140
5246
|
7. **Incident notification fails with \`WeCom License Not Activated\`?**
|
|
5141
5247
|
|
|
5142
5248
|
- Contact Flashduty customer service or dedicated support for license purchase and activation
|
|
5143
|
-
`,
|
|
5249
|
+
`,V=`---
|
|
5144
5250
|
title: "Slack Integration"
|
|
5145
5251
|
description: "Integrate with Slack to receive and respond to alerts within Slack"
|
|
5146
5252
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5194,7 +5300,7 @@ Integrate with Slack to receive and respond to alerts within Slack.
|
|
|
5194
5300
|
|
|
5195
5301
|
8. **Slack App shows Other questions error**
|
|
5196
5302
|
- Try again, as this might be an unrecorded issue
|
|
5197
|
-
- If the error persists, contact customer support`,
|
|
5303
|
+
- If the error persists, contact customer support`,z=`---
|
|
5198
5304
|
title: "Microsoft Teams Integration"
|
|
5199
5305
|
description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
|
|
5200
5306
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5289,7 +5395,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
|
|
|
5289
5395
|
Currently not supported
|
|
5290
5396
|
</details>
|
|
5291
5397
|
|
|
5292
|
-
`,
|
|
5398
|
+
`,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.
|
|
5293
5399
|
|
|
5294
5400
|
<span id="EventTypes"></span>
|
|
5295
5401
|
|
|
@@ -5457,7 +5563,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
|
|
|
5457
5563
|
4. **Trusted IP whitelist for push sources?**
|
|
5458
5564
|
- {ip_whitelist}
|
|
5459
5565
|
- May be updated in the future, please check periodically
|
|
5460
|
-
`,
|
|
5566
|
+
`,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.
|
|
5461
5567
|
|
|
5462
5568
|
<span id="EventTypes"></span>
|
|
5463
5569
|
|
|
@@ -5663,7 +5769,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
|
|
|
5663
5769
|
|
|
5664
5770
|
4. **Trusted IP whitelist for push sources?**
|
|
5665
5771
|
- {ip_whitelist}
|
|
5666
|
-
- May be updated in the future, please check periodically`,
|
|
5772
|
+
- May be updated in the future, please check periodically`,J=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
|
|
5667
5773
|
|
|
5668
5774
|
## I. Creating Actions
|
|
5669
5775
|
|
|
@@ -5910,7 +6016,7 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
|
|
|
5910
6016
|
|
|
5911
6017
|
### Update Status Page
|
|
5912
6018
|
|
|
5913
|
-
When an incident is confirmed to affect online services, trigger external status page updates to prompt`,
|
|
6019
|
+
When an incident is confirmed to affect online services, trigger external status page updates to prompt`,Q=`---
|
|
5914
6020
|
title: "Configure Notification Templates"
|
|
5915
6021
|
description: "Customize notification content through template configuration"
|
|
5916
6022
|
date: "2024-05-10T10:00:00+08:00"
|
|
@@ -6513,4 +6619,4 @@ If custom content is not set, the system default template will be used for notif
|
|
|
6513
6619
|
As shown below:
|
|
6514
6620
|
<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
|
|
6515
6621
|
|
|
6516
|
-
`,
|
|
6622
|
+
`,X={CustomAlert:n,Email:t,N9e:a,Prometheus:o,Grafana:i,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:_,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:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:V,MicrosoftTeams:z,AlertWebhook:K,IncidentWebhook:Z,CustomAction:J,Templates:Q,HuaweiyunAPM:q};module.exports=X;
|
package/dist/esm/zh.js
CHANGED
|
@@ -4904,6 +4904,114 @@ url: "https://docs.flashcat.cloud/zh/flashduty/zilliz-integration-guide"
|
|
|
4904
4904
|
</div>
|
|
4905
4905
|
|
|
4906
4906
|
`,H=`---
|
|
4907
|
+
title: "华为云 APM 告警事件"
|
|
4908
|
+
description: "通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty,实现告警事件自动化降噪处理"
|
|
4909
|
+
date: "2024-07-05T10:00:00+08:00"
|
|
4910
|
+
url: "https://docs.flashcat.cloud/zh/flashduty/huawei-apm-integration-guide"
|
|
4911
|
+
---
|
|
4912
|
+
|
|
4913
|
+
通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty,实现告警事件自动化降噪处理。
|
|
4914
|
+
|
|
4915
|
+
<div class="hide">
|
|
4916
|
+
|
|
4917
|
+
## 在 Flashduty
|
|
4918
|
+
---
|
|
4919
|
+
您可通过以下2种方式,获取一个集成推送地址,任选其一即可。
|
|
4920
|
+
|
|
4921
|
+
### 使用专属集成
|
|
4922
|
+
|
|
4923
|
+
当您不需要将告警事件路由到不同的协作空间,优先选择此方式,更简单。
|
|
4924
|
+
|
|
4925
|
+
<details>
|
|
4926
|
+
<summary>展开</summary>
|
|
4927
|
+
|
|
4928
|
+
1. 进入 Flashduty 控制台,选择 **协作空间**,进入某个空间的详情页面
|
|
4929
|
+
2. 选择 **集成数据** tab,点击 **添加一个集成**,进入添加集成页面
|
|
4930
|
+
3. 选择 **华为云 APM** 集成,点击 **保存**,生成卡片。
|
|
4931
|
+
4. 点击生成的卡片,可以查看到 **推送地址**,复制备用,完成。
|
|
4932
|
+
|
|
4933
|
+
|
|
4934
|
+
</details>
|
|
4935
|
+
|
|
4936
|
+
### 使用共享集成
|
|
4937
|
+
|
|
4938
|
+
当您需要根据告警事件的 Payload 信息,将告警路由到不同的协作空间,优先选择此方式。
|
|
4939
|
+
|
|
4940
|
+
<details>
|
|
4941
|
+
<summary>展开</summary>
|
|
4942
|
+
|
|
4943
|
+
1. 进入 Flashduty 控制台,选择 **集成中心=>告警事件**,进入集成选择页面。
|
|
4944
|
+
2. 选择 **华为云 APM** 集成:
|
|
4945
|
+
- **集成名称**:为当前集成定义一个名称。
|
|
4946
|
+
3. 点击 **保存** 后,复制当前页面的新生成的 **推送地址** 备用。
|
|
4947
|
+
4. 点击 **创建路由**,为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间,也可以直接设置默认协作空间作为兜底,后续再按需调整。
|
|
4948
|
+
5. 完成。
|
|
4949
|
+
|
|
4950
|
+
</details>
|
|
4951
|
+
</div>
|
|
4952
|
+
|
|
4953
|
+
## 在华为云 APM
|
|
4954
|
+
---
|
|
4955
|
+
|
|
4956
|
+
<div class="md-block">
|
|
4957
|
+
|
|
4958
|
+
|
|
4959
|
+
## 一、华为云 APM 告警推送配置
|
|
4960
|
+
|
|
4961
|
+
### 创建 FlashDuty 告警通道
|
|
4962
|
+
1. 登录您的华为云控制台,检索 \`SMN\` 消息通知服务产品,并进入对应产品控制台。
|
|
4963
|
+
2. 在左侧导航栏选择 \`主题管理=>主题\`。
|
|
4964
|
+
3. 点击 \`创建主题\`,在编辑页面中的主题名称处输入 \`FlashDuty\` 并点击确认。
|
|
4965
|
+
|
|
4966
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-1.png" />
|
|
4967
|
+
|
|
4968
|
+
4. 回到主题列表后,在刚创建的 FlashDuty 主题中点击 \`添加订阅\`。
|
|
4969
|
+
|
|
4970
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-2.png" />
|
|
4971
|
+
|
|
4972
|
+
5. 在编辑页面中,协议选择 \`HTTPS\`,订阅终端填写 **集成推送地址** 并点击确认。
|
|
4973
|
+
|
|
4974
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-3.png" />
|
|
4975
|
+
|
|
4976
|
+
6. 添加完成后,可以在订阅列表中查看已添加的订阅状态是否为 **已确认**。
|
|
4977
|
+
|
|
4978
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-4.png" />
|
|
4979
|
+
|
|
4980
|
+
### 配置应用监控告警
|
|
4981
|
+
|
|
4982
|
+
#### 步骤1:添加通知配置
|
|
4983
|
+
1. 登录您的 \`华为云 APM\` 控制台,在 \`应用监控=>指标\` 中,点击 \`通知配置\`。
|
|
4984
|
+
2. 选择对应的区域后,点击 \`新增\`,在主题处选择已创建的 \`FlashDuty\` 主题。
|
|
4985
|
+
3. 点击 \`确认\` 完成配置。
|
|
4986
|
+
|
|
4987
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-1.png" />
|
|
4988
|
+
|
|
4989
|
+
#### 步骤2:创建告警策略
|
|
4990
|
+
1. 在 \`应用监控=>指标\` 中,选择您的应用并点击 \`设置\` 按钮。
|
|
4991
|
+
2. 选择 \`告警策略\`,点击 \`新增自定义告警策略\` 或编辑已有的告警策略。
|
|
4992
|
+
3. 在 \`告警策略\` 编辑页面中,告警指标、告警条件等请按业务需要进行配置。
|
|
4993
|
+
4. \`告警内容\` 中在引用变量时,建议以K:V的格式进行配置,便于后续告警事件的解析,比如 host:\${hostInfo}。
|
|
4994
|
+
5. \`通知对象\` 中选择已创建的 \`FlashDuty\` 通知渠道。
|
|
4995
|
+
6. 点击 \`确认\` 完成配置。
|
|
4996
|
+
|
|
4997
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-2.png" />
|
|
4998
|
+
|
|
4999
|
+
**注意:** 当前集成配置仅支持应用监控告警,还未完全兼容前端监控、链路追踪、App监控告警。
|
|
5000
|
+
</div>
|
|
5001
|
+
|
|
5002
|
+
## 二、状态对照
|
|
5003
|
+
|
|
5004
|
+
<div class="md-block">
|
|
5005
|
+
|
|
5006
|
+
| 华为云 APM | Flashduty | 状态 |
|
|
5007
|
+
| ---------- | -------- | ---- |
|
|
5008
|
+
| 严重告警 | Critical | 严重 |
|
|
5009
|
+
| 轻微告警 | Info | 提醒 |
|
|
5010
|
+
|
|
5011
|
+
|
|
5012
|
+
</div>
|
|
5013
|
+
|
|
5014
|
+
`,O=`---
|
|
4907
5015
|
title: "自定义变更事件集成指引"
|
|
4908
5016
|
description: "通过标准协议推送自有系统变更事件到 Flashduty,大部分故障由变更导致,变更和告警事件联动有助于快速定位故障原因。"
|
|
4909
5017
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4960,7 +5068,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议,对
|
|
|
4960
5068
|
|
|
4961
5069
|
</details>
|
|
4962
5070
|
|
|
4963
|
-
`,
|
|
5071
|
+
`,q=`---
|
|
4964
5072
|
title: "Jira 事件集成指引"
|
|
4965
5073
|
description: "通过 webhook 的方式同步 Jira Issue 事件到 Flashduty,实现变更事件收集。"
|
|
4966
5074
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5034,7 +5142,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息,并按照下边
|
|
|
5034
5142
|
如您希望变更此映射关系,请联系 Flashduty。
|
|
5035
5143
|
|
|
5036
5144
|
</div>
|
|
5037
|
-
`,
|
|
5145
|
+
`,B=`---
|
|
5038
5146
|
title: Contributing to our documentation — Meilisearch documentation
|
|
5039
5147
|
description: The Meilisearch documentation is open-source. Learn how to help make it even better.
|
|
5040
5148
|
sidebarDepth: 3
|
|
@@ -5151,7 +5259,7 @@ sidebarDepth: 3
|
|
|
5151
5259
|
|
|
5152
5260
|
<img alt="drawing" width="800" src="https://download.flashcat.cloud/feishu-self-app-invite-to-chat.jpeg" />
|
|
5153
5261
|
<img src="https://download.flashcat.cloud/feishu-self-app-notify-rule.png" alt="drawing" width="800"/>
|
|
5154
|
-
`,
|
|
5262
|
+
`,G=`---
|
|
5155
5263
|
title: "钉钉集成"
|
|
5156
5264
|
description: "通过集成钉钉自建应用,实现在钉钉端内接收和响应告警的能力"
|
|
5157
5265
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5302,7 +5410,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
|
|
|
5302
5410
|
|
|
5303
5411
|
<img src="https://download.flashcat.cloud/dingtalk-self-app-notify-rule.png" alt="drawing" width="800"/>
|
|
5304
5412
|
|
|
5305
|
-
`,
|
|
5413
|
+
`,V=`---
|
|
5306
5414
|
title: "企业微信集成"
|
|
5307
5415
|
description: "通过集成企业微信第三方应用,实现在企业微信端内接收和响应告警的能力"
|
|
5308
5416
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5382,7 +5490,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
|
|
|
5382
5490
|
7. **故障通知失败,提示\`未开通企微许可\`?**
|
|
5383
5491
|
|
|
5384
5492
|
- 联系 Flashduty 客服或专属支持,为您购买开通
|
|
5385
|
-
`,
|
|
5493
|
+
`,K=`---
|
|
5386
5494
|
title: "Slack 集成"
|
|
5387
5495
|
description: "通过集成Slack第三方应用,实现在Slack内接收和响应告警的能力"
|
|
5388
5496
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5531,7 +5639,7 @@ Microsoft Teams 集成现处于 Beta 阶段,在关联前您需要先完成以
|
|
|
5531
5639
|
暂不支持
|
|
5532
5640
|
</details>
|
|
5533
5641
|
|
|
5534
|
-
`,
|
|
5642
|
+
`,J=`配置告警 Webhook,当告警发生特定操作(如触发、关闭)时,系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息,您可以与自研工具进行集成。
|
|
5535
5643
|
|
|
5536
5644
|
<span id="EventTypes"></span>
|
|
5537
5645
|
|
|
@@ -5699,7 +5807,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
|
|
|
5699
5807
|
4. **推送来源可信 IP 白名单?**
|
|
5700
5808
|
- {ip_whitelist}
|
|
5701
5809
|
- 未来可能会更新,请定期查验
|
|
5702
|
-
`,
|
|
5810
|
+
`,X=`配置故障 Webhook,当故障发生特定操作(如触发、关闭)时,系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息,您可以与自研工具进行集成。
|
|
5703
5811
|
|
|
5704
5812
|
<span id="EventTypes"></span>
|
|
5705
5813
|
|
|
@@ -5906,7 +6014,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
|
|
|
5906
6014
|
|
|
5907
6015
|
4. **推送来源可信 IP 白名单?**
|
|
5908
6016
|
- {ip_whitelist}
|
|
5909
|
-
- 未来可能会更新,请定期查验`,
|
|
6017
|
+
- 未来可能会更新,请定期查验`,Q=`配置故障 自定义操作,允许您在故障排查期间,快速调用外部接口,实现故障自愈、信息丰富等任何自定义操作。
|
|
5910
6018
|
|
|
5911
6019
|
## 一、创建操作
|
|
5912
6020
|
|
|
@@ -6165,7 +6273,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
|
|
|
6165
6273
|
|
|
6166
6274
|
2. **推送来源可信 IP 白名单?**
|
|
6167
6275
|
- {ip_whitelist}
|
|
6168
|
-
- 未来可能会更新,请定期查验`,
|
|
6276
|
+
- 未来可能会更新,请定期查验`,Y=`---
|
|
6169
6277
|
title: "配置通知模版"
|
|
6170
6278
|
description: "通过自定义配置模版,可以实现个性化通知内容的需求"
|
|
6171
6279
|
date: "2024-05-10T10:00:00+08:00"
|
|
@@ -6995,4 +7103,4 @@ CloseTime | int64 | 否 | 关闭时间,EndTime 为告警恢复时间,CloseTi
|
|
|
6995
7103
|
<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
|
|
6996
7104
|
|
|
6997
7105
|
|
|
6998
|
-
`,
|
|
7106
|
+
`,nn={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:O,Jira:q,Lark:B,Dingtalk:G,Wecom:V,Slack:K,MicrosoftTeams:Z,AlertWebhook:J,IncidentWebhook:X,CustomAction:Q,Templates:Y,HuaweiyunAPM:H};module.exports=nn;
|
package/dist/iife/en.js
CHANGED
|
@@ -6513,4 +6513,110 @@ If custom content is not set, the system default template will be used for notif
|
|
|
6513
6513
|
As shown below:
|
|
6514
6514
|
<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
|
|
6515
6515
|
|
|
6516
|
+
`,HuaweiyunAPM:`---
|
|
6517
|
+
title: "Huawei Cloud APM Alerts"
|
|
6518
|
+
description: "Sync Huawei Cloud APM alerts to Flashduty through webhook to achieve automatic alert noise reduction"
|
|
6519
|
+
date: "2024-07-05T10:00:00+08:00"
|
|
6520
|
+
url: "https://docs.flashcat.cloud/en/flashduty/huawei-apm-integration-guide"
|
|
6521
|
+
---
|
|
6522
|
+
|
|
6523
|
+
Sync Huawei Cloud APM alerts to Flashduty through webhook, to achieve automatic noise reduction of alerts.
|
|
6524
|
+
|
|
6525
|
+
<div class="hide">
|
|
6526
|
+
|
|
6527
|
+
## In Flashduty
|
|
6528
|
+
---
|
|
6529
|
+
You can get an integration push URL through the following 2 methods, choose one of them.
|
|
6530
|
+
|
|
6531
|
+
### Use dedicated integration
|
|
6532
|
+
|
|
6533
|
+
When you don't need to route alerts to different channels, choose this method, it's simpler.
|
|
6534
|
+
|
|
6535
|
+
<details>
|
|
6536
|
+
<summary>Expand</summary>
|
|
6537
|
+
|
|
6538
|
+
1. Go to Flashduty console, select **Channels**, enter the details page of a channel
|
|
6539
|
+
2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
|
|
6540
|
+
3. Select **Huawei Cloud APM** integration, click **Save** to generate a card
|
|
6541
|
+
4. Click the generated card to view the **push URL**, copy it for later use. Done.
|
|
6542
|
+
|
|
6543
|
+
</details>
|
|
6544
|
+
|
|
6545
|
+
### Use shared integration
|
|
6546
|
+
|
|
6547
|
+
When you need to route alerts to different channels based on alert payload information, this method is preferred.
|
|
6548
|
+
|
|
6549
|
+
<details>
|
|
6550
|
+
<summary>Expand</summary>
|
|
6551
|
+
|
|
6552
|
+
1. Go to Flashduty console, select **Integration Center=>Alerts** to enter the integration selection page
|
|
6553
|
+
2. Select **Huawei Cloud APM** integration:
|
|
6554
|
+
- **Integration Name**: Define a name for the current integration
|
|
6555
|
+
3. Click **Save** and copy the newly generated **push URL** for later use
|
|
6556
|
+
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
|
|
6557
|
+
5. Done.
|
|
6558
|
+
|
|
6559
|
+
</details>
|
|
6560
|
+
</div>
|
|
6561
|
+
|
|
6562
|
+
## In Huawei Cloud
|
|
6563
|
+
---
|
|
6564
|
+
|
|
6565
|
+
<div class="md-block">
|
|
6566
|
+
|
|
6567
|
+
## I. Huawei Cloud APM Alert Push Configuration
|
|
6568
|
+
|
|
6569
|
+
### Create FlashDuty Alert Channel
|
|
6570
|
+
|
|
6571
|
+
1. Log in to your Huawei Cloud Console, search for \`SMN\` (Simple Message Notification) service and enter its console
|
|
6572
|
+
2. Select \`Topic Management=>Topics\` from the left navigation bar
|
|
6573
|
+
3. Click \`Create Topic\`, enter \`FlashDuty\` as the topic name in the edit page and confirm
|
|
6574
|
+
|
|
6575
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-1.png" alt="drawing" width="500"/>
|
|
6576
|
+
|
|
6577
|
+
4. Return to the topic list and click \`Add Subscription\` in the newly created FlashDuty topic
|
|
6578
|
+
|
|
6579
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-2.png" alt="drawing" width="500"/>
|
|
6580
|
+
|
|
6581
|
+
5. In the edit page, select \`HTTPS\` as the protocol, enter the **push URL** as the subscription endpoint and confirm
|
|
6582
|
+
|
|
6583
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-3.png" alt="drawing" width="500"/>
|
|
6584
|
+
|
|
6585
|
+
6. After adding, check if the subscription status shows **Confirmed** in the subscription list
|
|
6586
|
+
|
|
6587
|
+
<img src="https://download.flashcat.cloud/flashduty/doc/en/hw/lts-4.png" alt="drawing" width="500"/>
|
|
6588
|
+
|
|
6589
|
+
### Configure Application Monitoring Alerts
|
|
6590
|
+
|
|
6591
|
+
#### Step 1: Add Notification Configuration
|
|
6592
|
+
1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
|
|
6593
|
+
2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
|
|
6594
|
+
3. Click \`Confirm\` to complete the configuration
|
|
6595
|
+
|
|
6596
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
|
|
6597
|
+
|
|
6598
|
+
#### Step 2: Create Alert Policy
|
|
6599
|
+
1. Under \`Application Monitoring=>Metrics\`, select your application and click the \`Settings\` button
|
|
6600
|
+
2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
|
|
6601
|
+
3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
|
|
6602
|
+
4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
|
|
6603
|
+
5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
|
|
6604
|
+
6. Click \`Confirm\` to complete the configuration
|
|
6605
|
+
|
|
6606
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
|
|
6607
|
+
|
|
6608
|
+
**Note:** The current integration configuration only supports application monitoring alerts, and does not fully support front-end monitoring, link tracking, and App monitoring alerts.
|
|
6609
|
+
</div>
|
|
6610
|
+
|
|
6611
|
+
## II. Status Mapping
|
|
6612
|
+
|
|
6613
|
+
<div class="md-block">
|
|
6614
|
+
|
|
6615
|
+
| Huawei Cloud APM | Flashduty | Severity |
|
|
6616
|
+
| ---------- | -------- | ---- |
|
|
6617
|
+
| CRITICAL | Critical | Critical |
|
|
6618
|
+
| COMMON | Info | Info |
|
|
6619
|
+
|
|
6620
|
+
</div>
|
|
6621
|
+
|
|
6516
6622
|
`};n.FlashDocsEn=u})(window);
|
package/dist/iife/zh.js
CHANGED
|
@@ -6995,4 +6995,112 @@ CloseTime | int64 | 否 | 关闭时间,EndTime 为告警恢复时间,CloseTi
|
|
|
6995
6995
|
<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
|
|
6996
6996
|
|
|
6997
6997
|
|
|
6998
|
+
`,HuaweiyunAPM:`---
|
|
6999
|
+
title: "华为云 APM 告警事件"
|
|
7000
|
+
description: "通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty,实现告警事件自动化降噪处理"
|
|
7001
|
+
date: "2024-07-05T10:00:00+08:00"
|
|
7002
|
+
url: "https://docs.flashcat.cloud/zh/flashduty/huawei-apm-integration-guide"
|
|
7003
|
+
---
|
|
7004
|
+
|
|
7005
|
+
通过 webhook 的方式同步华为云 APM 告警事件到 Flashduty,实现告警事件自动化降噪处理。
|
|
7006
|
+
|
|
7007
|
+
<div class="hide">
|
|
7008
|
+
|
|
7009
|
+
## 在 Flashduty
|
|
7010
|
+
---
|
|
7011
|
+
您可通过以下2种方式,获取一个集成推送地址,任选其一即可。
|
|
7012
|
+
|
|
7013
|
+
### 使用专属集成
|
|
7014
|
+
|
|
7015
|
+
当您不需要将告警事件路由到不同的协作空间,优先选择此方式,更简单。
|
|
7016
|
+
|
|
7017
|
+
<details>
|
|
7018
|
+
<summary>展开</summary>
|
|
7019
|
+
|
|
7020
|
+
1. 进入 Flashduty 控制台,选择 **协作空间**,进入某个空间的详情页面
|
|
7021
|
+
2. 选择 **集成数据** tab,点击 **添加一个集成**,进入添加集成页面
|
|
7022
|
+
3. 选择 **华为云 APM** 集成,点击 **保存**,生成卡片。
|
|
7023
|
+
4. 点击生成的卡片,可以查看到 **推送地址**,复制备用,完成。
|
|
7024
|
+
|
|
7025
|
+
|
|
7026
|
+
</details>
|
|
7027
|
+
|
|
7028
|
+
### 使用共享集成
|
|
7029
|
+
|
|
7030
|
+
当您需要根据告警事件的 Payload 信息,将告警路由到不同的协作空间,优先选择此方式。
|
|
7031
|
+
|
|
7032
|
+
<details>
|
|
7033
|
+
<summary>展开</summary>
|
|
7034
|
+
|
|
7035
|
+
1. 进入 Flashduty 控制台,选择 **集成中心=>告警事件**,进入集成选择页面。
|
|
7036
|
+
2. 选择 **华为云 APM** 集成:
|
|
7037
|
+
- **集成名称**:为当前集成定义一个名称。
|
|
7038
|
+
3. 点击 **保存** 后,复制当前页面的新生成的 **推送地址** 备用。
|
|
7039
|
+
4. 点击 **创建路由**,为集成配置路由规则。您可以按条件匹配不同的告警到不同的协作空间,也可以直接设置默认协作空间作为兜底,后续再按需调整。
|
|
7040
|
+
5. 完成。
|
|
7041
|
+
|
|
7042
|
+
</details>
|
|
7043
|
+
</div>
|
|
7044
|
+
|
|
7045
|
+
## 在华为云 APM
|
|
7046
|
+
---
|
|
7047
|
+
|
|
7048
|
+
<div class="md-block">
|
|
7049
|
+
|
|
7050
|
+
|
|
7051
|
+
## 一、华为云 APM 告警推送配置
|
|
7052
|
+
|
|
7053
|
+
### 创建 FlashDuty 告警通道
|
|
7054
|
+
1. 登录您的华为云控制台,检索 \`SMN\` 消息通知服务产品,并进入对应产品控制台。
|
|
7055
|
+
2. 在左侧导航栏选择 \`主题管理=>主题\`。
|
|
7056
|
+
3. 点击 \`创建主题\`,在编辑页面中的主题名称处输入 \`FlashDuty\` 并点击确认。
|
|
7057
|
+
|
|
7058
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-1.png" />
|
|
7059
|
+
|
|
7060
|
+
4. 回到主题列表后,在刚创建的 FlashDuty 主题中点击 \`添加订阅\`。
|
|
7061
|
+
|
|
7062
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-2.png" />
|
|
7063
|
+
|
|
7064
|
+
5. 在编辑页面中,协议选择 \`HTTPS\`,订阅终端填写 **集成推送地址** 并点击确认。
|
|
7065
|
+
|
|
7066
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-3.png" />
|
|
7067
|
+
|
|
7068
|
+
6. 添加完成后,可以在订阅列表中查看已添加的订阅状态是否为 **已确认**。
|
|
7069
|
+
|
|
7070
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-4.png" />
|
|
7071
|
+
|
|
7072
|
+
### 配置应用监控告警
|
|
7073
|
+
|
|
7074
|
+
#### 步骤1:添加通知配置
|
|
7075
|
+
1. 登录您的 \`华为云 APM\` 控制台,在 \`应用监控=>指标\` 中,点击 \`通知配置\`。
|
|
7076
|
+
2. 选择对应的区域后,点击 \`新增\`,在主题处选择已创建的 \`FlashDuty\` 主题。
|
|
7077
|
+
3. 点击 \`确认\` 完成配置。
|
|
7078
|
+
|
|
7079
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-1.png" />
|
|
7080
|
+
|
|
7081
|
+
#### 步骤2:创建告警策略
|
|
7082
|
+
1. 在 \`应用监控=>指标\` 中,选择您的应用并点击 \`设置\` 按钮。
|
|
7083
|
+
2. 选择 \`告警策略\`,点击 \`新增自定义告警策略\` 或编辑已有的告警策略。
|
|
7084
|
+
3. 在 \`告警策略\` 编辑页面中,告警指标、告警条件等请按业务需要进行配置。
|
|
7085
|
+
4. \`告警内容\` 中在引用变量时,建议以K:V的格式进行配置,便于后续告警事件的解析,比如 host:\${hostInfo}。
|
|
7086
|
+
5. \`通知对象\` 中选择已创建的 \`FlashDuty\` 通知渠道。
|
|
7087
|
+
6. 点击 \`确认\` 完成配置。
|
|
7088
|
+
|
|
7089
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/hw/hw-apm-2.png" />
|
|
7090
|
+
|
|
7091
|
+
**注意:** 当前集成配置仅支持应用监控告警,还未完全兼容前端监控、链路追踪、App监控告警。
|
|
7092
|
+
</div>
|
|
7093
|
+
|
|
7094
|
+
## 二、状态对照
|
|
7095
|
+
|
|
7096
|
+
<div class="md-block">
|
|
7097
|
+
|
|
7098
|
+
| 华为云 APM | Flashduty | 状态 |
|
|
7099
|
+
| ---------- | -------- | ---- |
|
|
7100
|
+
| 严重告警 | Critical | 严重 |
|
|
7101
|
+
| 轻微告警 | Info | 提醒 |
|
|
7102
|
+
|
|
7103
|
+
|
|
7104
|
+
</div>
|
|
7105
|
+
|
|
6998
7106
|
`};n.FlashDocsZh=t})(window);
|
package/dist/zh.d.ts
CHANGED