flashduty-knowledge-base 1.2.3-beta.1 → 1.2.3
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 +0 -1
- package/dist/esm/en.js +15 -120
- package/dist/esm/zh.js +10 -118
- package/dist/iife/en.js +0 -105
- package/dist/iife/zh.js +0 -108
- package/dist/zh.d.ts +0 -1
- 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
|
+
`,i=`---
|
|
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
|
+
`,o=`---
|
|
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
|
+
`,_=`---
|
|
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
|
+
`,L=`---
|
|
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,111 +4640,6 @@ 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
|
-
1. Log in to your Huawei Cloud console, search for \`SMN\` (Simple Message Notification) service and enter the corresponding product console
|
|
4697
|
-
2. Select \`Topic Management=>Topics\` from the left navigation bar
|
|
4698
|
-
3. Click \`Create Topic\`, enter \`FlashDuty\` in the topic name field and click confirm
|
|
4699
|
-
|
|
4700
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-1.png" />
|
|
4701
|
-
|
|
4702
|
-
4. Back in the topic list, click \`Add Subscription\` in the newly created FlashDuty topic
|
|
4703
|
-
|
|
4704
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-2.png" />
|
|
4705
|
-
|
|
4706
|
-
5. In the edit page, select \`HTTPS\` for protocol, enter the **integration push URL** for subscription endpoint and click confirm
|
|
4707
|
-
|
|
4708
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-3.png" />
|
|
4709
|
-
|
|
4710
|
-
6. After adding, check if the subscription status shows **Confirmed** in the subscription list
|
|
4711
|
-
|
|
4712
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-4.png" />
|
|
4713
|
-
|
|
4714
|
-
### Configure Application Monitoring Alerts
|
|
4715
|
-
|
|
4716
|
-
#### Step 1: Add Notification Configuration
|
|
4717
|
-
1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
|
|
4718
|
-
2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
|
|
4719
|
-
3. Click \`Confirm\` to complete the configuration
|
|
4720
|
-
|
|
4721
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
|
|
4722
|
-
|
|
4723
|
-
#### Step 2: Create Alert Policy
|
|
4724
|
-
1. Under \`Application Monitoring=>Metrics\`, select your application and click the \`Settings\` button
|
|
4725
|
-
2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
|
|
4726
|
-
3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
|
|
4727
|
-
4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
|
|
4728
|
-
5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
|
|
4729
|
-
6. Click \`Confirm\` to complete the configuration
|
|
4730
|
-
|
|
4731
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
|
|
4732
|
-
|
|
4733
|
-
**Note:** The current integration configuration only supports application monitoring alerts, and does not fully support front-end monitoring, link tracking, and App monitoring alerts.
|
|
4734
|
-
</div>
|
|
4735
|
-
|
|
4736
|
-
## II. Status Mapping
|
|
4737
|
-
|
|
4738
|
-
<div class="md-block">
|
|
4739
|
-
|
|
4740
|
-
| Huawei Cloud APM | Flashduty | Severity |
|
|
4741
|
-
| ---------- | -------- | ---- |
|
|
4742
|
-
| CRITICAL | Critical | Critical |
|
|
4743
|
-
| COMMON | Info | Info |
|
|
4744
|
-
|
|
4745
|
-
</div>
|
|
4746
|
-
|
|
4747
|
-
`,O=`---
|
|
4748
4643
|
title: "Custom Change Event Integration Guide"
|
|
4749
4644
|
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."
|
|
4750
4645
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4801,7 +4696,7 @@ Labels are descriptions of events. You should enrich label content as much as po
|
|
|
4801
4696
|
|
|
4802
4697
|
</details>
|
|
4803
4698
|
|
|
4804
|
-
`,
|
|
4699
|
+
`,O=`---
|
|
4805
4700
|
title: "Jira Issue Events"
|
|
4806
4701
|
description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
|
|
4807
4702
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4875,7 +4770,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
|
|
|
4875
4770
|
Please contact Flashduty if you wish to modify this mapping.
|
|
4876
4771
|
|
|
4877
4772
|
</div>
|
|
4878
|
-
|
|
4773
|
+
`,j=`---
|
|
4879
4774
|
title: Contributing to our documentation — Meilisearch documentation
|
|
4880
4775
|
description: The Meilisearch documentation is open-source. Learn how to help make it even better.
|
|
4881
4776
|
sidebarDepth: 3
|
|
@@ -5010,7 +4905,7 @@ Once published, you can access the application via mobile/PC client. First-time
|
|
|
5010
4905
|
|Group Bot Webhook|Maximum 100 calls/minute|
|
|
5011
4906
|
|Sending messages to the same user or group|Maximum 5 calls/second|
|
|
5012
4907
|
|
|
5013
|
-
**Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably
|
|
4908
|
+
**Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,$=`---
|
|
5014
4909
|
title: "Dingtalk Integration"
|
|
5015
4910
|
description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
|
|
5016
4911
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5166,7 +5061,7 @@ After the application is released, you can access it via mobile/PC client. First
|
|
|
5166
5061
|
|Enterprise|5,500,000|60|1st of each month|
|
|
5167
5062
|
|
|
5168
5063
|
**Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
|
|
5169
|
-
`,
|
|
5064
|
+
`,H=`---
|
|
5170
5065
|
title: "WeCom Integration"
|
|
5171
5066
|
description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
|
|
5172
5067
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5245,7 +5140,7 @@ Integrate WeCom third-party application to receive and respond to alerts within
|
|
|
5245
5140
|
7. **Incident notification fails with \`WeCom License Not Activated\`?**
|
|
5246
5141
|
|
|
5247
5142
|
- Contact Flashduty customer service or dedicated support for license purchase and activation
|
|
5248
|
-
`,
|
|
5143
|
+
`,B=`---
|
|
5249
5144
|
title: "Slack Integration"
|
|
5250
5145
|
description: "Integrate with Slack to receive and respond to alerts within Slack"
|
|
5251
5146
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5299,7 +5194,7 @@ Integrate with Slack to receive and respond to alerts within Slack.
|
|
|
5299
5194
|
|
|
5300
5195
|
8. **Slack App shows Other questions error**
|
|
5301
5196
|
- Try again, as this might be an unrecorded issue
|
|
5302
|
-
- If the error persists, contact customer support`,
|
|
5197
|
+
- If the error persists, contact customer support`,V=`---
|
|
5303
5198
|
title: "Microsoft Teams Integration"
|
|
5304
5199
|
description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
|
|
5305
5200
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5394,7 +5289,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
|
|
|
5394
5289
|
Currently not supported
|
|
5395
5290
|
</details>
|
|
5396
5291
|
|
|
5397
|
-
`,
|
|
5292
|
+
`,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.
|
|
5398
5293
|
|
|
5399
5294
|
<span id="EventTypes"></span>
|
|
5400
5295
|
|
|
@@ -5562,7 +5457,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
|
|
|
5562
5457
|
4. **Trusted IP whitelist for push sources?**
|
|
5563
5458
|
- {ip_whitelist}
|
|
5564
5459
|
- May be updated in the future, please check periodically
|
|
5565
|
-
`,
|
|
5460
|
+
`,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.
|
|
5566
5461
|
|
|
5567
5462
|
<span id="EventTypes"></span>
|
|
5568
5463
|
|
|
@@ -5768,7 +5663,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
|
|
|
5768
5663
|
|
|
5769
5664
|
4. **Trusted IP whitelist for push sources?**
|
|
5770
5665
|
- {ip_whitelist}
|
|
5771
|
-
- May be updated in the future, please check periodically`,
|
|
5666
|
+
- 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.
|
|
5772
5667
|
|
|
5773
5668
|
## I. Creating Actions
|
|
5774
5669
|
|
|
@@ -6015,7 +5910,7 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
|
|
|
6015
5910
|
|
|
6016
5911
|
### Update Status Page
|
|
6017
5912
|
|
|
6018
|
-
When an incident is confirmed to affect online services, trigger external status page updates to prompt`,
|
|
5913
|
+
When an incident is confirmed to affect online services, trigger external status page updates to prompt`,J=`---
|
|
6019
5914
|
title: "Configure Notification Templates"
|
|
6020
5915
|
description: "Customize notification content through template configuration"
|
|
6021
5916
|
date: "2024-05-10T10:00:00+08:00"
|
|
@@ -6618,4 +6513,4 @@ If custom content is not set, the system default template will be used for notif
|
|
|
6618
6513
|
As shown below:
|
|
6619
6514
|
<img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
|
|
6620
6515
|
|
|
6621
|
-
`,
|
|
6516
|
+
`,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;
|
package/dist/esm/zh.js
CHANGED
|
@@ -4904,114 +4904,6 @@ 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=`---
|
|
5015
4907
|
title: "自定义变更事件集成指引"
|
|
5016
4908
|
description: "通过标准协议推送自有系统变更事件到 Flashduty,大部分故障由变更导致,变更和告警事件联动有助于快速定位故障原因。"
|
|
5017
4909
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5068,7 +4960,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议,对
|
|
|
5068
4960
|
|
|
5069
4961
|
</details>
|
|
5070
4962
|
|
|
5071
|
-
`,
|
|
4963
|
+
`,O=`---
|
|
5072
4964
|
title: "Jira 事件集成指引"
|
|
5073
4965
|
description: "通过 webhook 的方式同步 Jira Issue 事件到 Flashduty,实现变更事件收集。"
|
|
5074
4966
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5142,7 +5034,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息,并按照下边
|
|
|
5142
5034
|
如您希望变更此映射关系,请联系 Flashduty。
|
|
5143
5035
|
|
|
5144
5036
|
</div>
|
|
5145
|
-
`,
|
|
5037
|
+
`,q=`---
|
|
5146
5038
|
title: Contributing to our documentation — Meilisearch documentation
|
|
5147
5039
|
description: The Meilisearch documentation is open-source. Learn how to help make it even better.
|
|
5148
5040
|
sidebarDepth: 3
|
|
@@ -5259,7 +5151,7 @@ sidebarDepth: 3
|
|
|
5259
5151
|
|
|
5260
5152
|
<img alt="drawing" width="800" src="https://download.flashcat.cloud/feishu-self-app-invite-to-chat.jpeg" />
|
|
5261
5153
|
<img src="https://download.flashcat.cloud/feishu-self-app-notify-rule.png" alt="drawing" width="800"/>
|
|
5262
|
-
`,
|
|
5154
|
+
`,B=`---
|
|
5263
5155
|
title: "钉钉集成"
|
|
5264
5156
|
description: "通过集成钉钉自建应用,实现在钉钉端内接收和响应告警的能力"
|
|
5265
5157
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5410,7 +5302,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
|
|
|
5410
5302
|
|
|
5411
5303
|
<img src="https://download.flashcat.cloud/dingtalk-self-app-notify-rule.png" alt="drawing" width="800"/>
|
|
5412
5304
|
|
|
5413
|
-
`,
|
|
5305
|
+
`,G=`---
|
|
5414
5306
|
title: "企业微信集成"
|
|
5415
5307
|
description: "通过集成企业微信第三方应用,实现在企业微信端内接收和响应告警的能力"
|
|
5416
5308
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5490,7 +5382,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
|
|
|
5490
5382
|
7. **故障通知失败,提示\`未开通企微许可\`?**
|
|
5491
5383
|
|
|
5492
5384
|
- 联系 Flashduty 客服或专属支持,为您购买开通
|
|
5493
|
-
`,
|
|
5385
|
+
`,V=`---
|
|
5494
5386
|
title: "Slack 集成"
|
|
5495
5387
|
description: "通过集成Slack第三方应用,实现在Slack内接收和响应告警的能力"
|
|
5496
5388
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -5639,7 +5531,7 @@ Microsoft Teams 集成现处于 Beta 阶段,在关联前您需要先完成以
|
|
|
5639
5531
|
暂不支持
|
|
5640
5532
|
</details>
|
|
5641
5533
|
|
|
5642
|
-
`,
|
|
5534
|
+
`,K=`配置告警 Webhook,当告警发生特定操作(如触发、关闭)时,系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息,您可以与自研工具进行集成。
|
|
5643
5535
|
|
|
5644
5536
|
<span id="EventTypes"></span>
|
|
5645
5537
|
|
|
@@ -5807,7 +5699,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
|
|
|
5807
5699
|
4. **推送来源可信 IP 白名单?**
|
|
5808
5700
|
- {ip_whitelist}
|
|
5809
5701
|
- 未来可能会更新,请定期查验
|
|
5810
|
-
`,
|
|
5702
|
+
`,J=`配置故障 Webhook,当故障发生特定操作(如触发、关闭)时,系统通过 HTTP 回调您配置的地址。回调内容将包含故障最新关键信息,您可以与自研工具进行集成。
|
|
5811
5703
|
|
|
5812
5704
|
<span id="EventTypes"></span>
|
|
5813
5705
|
|
|
@@ -6014,7 +5906,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
|
|
|
6014
5906
|
|
|
6015
5907
|
4. **推送来源可信 IP 白名单?**
|
|
6016
5908
|
- {ip_whitelist}
|
|
6017
|
-
- 未来可能会更新,请定期查验`,
|
|
5909
|
+
- 未来可能会更新,请定期查验`,X=`配置故障 自定义操作,允许您在故障排查期间,快速调用外部接口,实现故障自愈、信息丰富等任何自定义操作。
|
|
6018
5910
|
|
|
6019
5911
|
## 一、创建操作
|
|
6020
5912
|
|
|
@@ -6273,7 +6165,7 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
|
|
|
6273
6165
|
|
|
6274
6166
|
2. **推送来源可信 IP 白名单?**
|
|
6275
6167
|
- {ip_whitelist}
|
|
6276
|
-
- 未来可能会更新,请定期查验`,
|
|
6168
|
+
- 未来可能会更新,请定期查验`,Q=`---
|
|
6277
6169
|
title: "配置通知模版"
|
|
6278
6170
|
description: "通过自定义配置模版,可以实现个性化通知内容的需求"
|
|
6279
6171
|
date: "2024-05-10T10:00:00+08:00"
|
|
@@ -7103,4 +6995,4 @@ CloseTime | int64 | 否 | 关闭时间,EndTime 为告警恢复时间,CloseTi
|
|
|
7103
6995
|
<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
|
|
7104
6996
|
|
|
7105
6997
|
|
|
7106
|
-
`,
|
|
6998
|
+
`,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;
|
package/dist/iife/en.js
CHANGED
|
@@ -6513,109 +6513,4 @@ 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
|
-
1. Log in to your Huawei Cloud console, search for \`SMN\` (Simple Message Notification) service and enter the corresponding product console
|
|
6571
|
-
2. Select \`Topic Management=>Topics\` from the left navigation bar
|
|
6572
|
-
3. Click \`Create Topic\`, enter \`FlashDuty\` in the topic name field and click confirm
|
|
6573
|
-
|
|
6574
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-1.png" />
|
|
6575
|
-
|
|
6576
|
-
4. Back in the topic list, click \`Add Subscription\` in the newly created FlashDuty topic
|
|
6577
|
-
|
|
6578
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-2.png" />
|
|
6579
|
-
|
|
6580
|
-
5. In the edit page, select \`HTTPS\` for protocol, enter the **integration push URL** for subscription endpoint and click confirm
|
|
6581
|
-
|
|
6582
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-3.png" />
|
|
6583
|
-
|
|
6584
|
-
6. After adding, check if the subscription status shows **Confirmed** in the subscription list
|
|
6585
|
-
|
|
6586
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/huawei-lts-4.png" />
|
|
6587
|
-
|
|
6588
|
-
### Configure Application Monitoring Alerts
|
|
6589
|
-
|
|
6590
|
-
#### Step 1: Add Notification Configuration
|
|
6591
|
-
1. Log in to your \`Huawei Cloud APM\` console, under \`Application Monitoring=>Metrics\`, click \`Notification\`
|
|
6592
|
-
2. Select the corresponding region, click \`Add\`, and select the created \`FlashDuty\` topic
|
|
6593
|
-
3. Click \`Confirm\` to complete the configuration
|
|
6594
|
-
|
|
6595
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-1.png" />
|
|
6596
|
-
|
|
6597
|
-
#### Step 2: Create Alert Policy
|
|
6598
|
-
1. Under \`Application Monitoring=>Metrics\`, select your application and click the \`Settings\` button
|
|
6599
|
-
2. Select \`Alarm Policy\`, click \`Add Custom Alarm Policy\` or edit an existing alarm policy
|
|
6600
|
-
3. In the \`Alarm Policy\` edit page, configure alert metrics and conditions according to your business needs
|
|
6601
|
-
4. In \`Notification Content\`, when referencing variables, it's recommended to use K:V format for easier alert parsing, such as host:\${hostInfo}
|
|
6602
|
-
5. In \`Notification Object\`, select the created \`FlashDuty\` notification channel
|
|
6603
|
-
6. Click \`Confirm\` to complete the configuration
|
|
6604
|
-
|
|
6605
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/hw/hw-apm-2.png" />
|
|
6606
|
-
|
|
6607
|
-
**Note:** The current integration configuration only supports application monitoring alerts, and does not fully support front-end monitoring, link tracking, and App monitoring alerts.
|
|
6608
|
-
</div>
|
|
6609
|
-
|
|
6610
|
-
## II. Status Mapping
|
|
6611
|
-
|
|
6612
|
-
<div class="md-block">
|
|
6613
|
-
|
|
6614
|
-
| Huawei Cloud APM | Flashduty | Severity |
|
|
6615
|
-
| ---------- | -------- | ---- |
|
|
6616
|
-
| CRITICAL | Critical | Critical |
|
|
6617
|
-
| COMMON | Info | Info |
|
|
6618
|
-
|
|
6619
|
-
</div>
|
|
6620
|
-
|
|
6621
6516
|
`};n.FlashDocsEn=u})(window);
|
package/dist/iife/zh.js
CHANGED
|
@@ -6995,112 +6995,4 @@ 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
|
-
|
|
7106
6998
|
`};n.FlashDocsZh=t})(window);
|
package/dist/zh.d.ts
CHANGED