flashduty-knowledge-base 1.0.3 → 1.0.5
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.cjs +19 -6
- package/dist/en.js +19 -6
- package/dist/zh.cjs +18 -5
- package/dist/zh.js +18 -5
- package/package.json +1 -1
package/dist/en.cjs
CHANGED
|
@@ -4357,6 +4357,9 @@ url: "https://docs.flashcat.cloud/en/flashduty/statecloud-integration-guide"
|
|
|
4357
4357
|
|
|
4358
4358
|
Sync StateCloud monitoring alert events to Flashduty via webhook for automated alert noise reduction.
|
|
4359
4359
|
|
|
4360
|
+
For resource monitoring events from StateCloud [secondary nodes](#secondary-nodes), please use Huawei Cloud integration. Refer to [Huawei Cloud Alert Integration Guide](https://docs.flashcat.cloud/en/flashduty/huawei-ces-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
|
|
4361
|
+
|
|
4362
|
+
|
|
4360
4363
|
<div class="hide">
|
|
4361
4364
|
|
|
4362
4365
|
## In Flashduty
|
|
@@ -4407,7 +4410,7 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4407
4410
|
4. In the alarm rule editing page, fill in the integration <span class='integration_url' >push URL</span> under \`Alert Callback\` and click test
|
|
4408
4411
|
5. After successful testing, click \`Save\`
|
|
4409
4412
|
|
|
4410
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/
|
|
4413
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/state-1.png" />
|
|
4411
4414
|
|
|
4412
4415
|
</dev>
|
|
4413
4416
|
|
|
@@ -4421,12 +4424,22 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4421
4424
|
| Warning | Warning | warning |
|
|
4422
4425
|
| Normal | Info | info |
|
|
4423
4426
|
|
|
4427
|
+
## III. StateCloud Secondary Node List<span id="secondary-nodes"></span>
|
|
4428
|
+
|
|
4429
|
+
| Region | Cities |
|
|
4430
|
+
| ---------- | -------- |
|
|
4431
|
+
| East China | Hangzhou/Nanchang/Shanghai4/Suzhou/Wuhu |
|
|
4432
|
+
| South China | Changsha2/Fuzhou1/Guangzhou4/Haikou/Nanning/Wuhan2 |
|
|
4433
|
+
| Northwest | Lanzhou/Urumqi/Xi'an2/Xining/Zhongwei |
|
|
4434
|
+
| Southwest | Chengdu3/Chongqing/Guizhou1/Kunming |
|
|
4435
|
+
| North | Beijing2/Changchun/Harbin/North China/Inner Mongolia3/Qingdao/Shenyang3/Shijiazhuang/Taiyuan/Tianjin/Zhengzhou |
|
|
4436
|
+
|
|
4424
4437
|
</div>
|
|
4425
4438
|
`,G=`---
|
|
4426
4439
|
title: "Guance Alert Events"
|
|
4427
4440
|
description: "Sync Guance alert events to Flashduty via webhook for automated alert noise reduction"
|
|
4428
4441
|
date: "2024-07-05T10:00:00+08:00"
|
|
4429
|
-
url: "https://docs.flashcat.cloud/en/flashduty/
|
|
4442
|
+
url: "https://docs.flashcat.cloud/en/flashduty/guance-integration-guide"
|
|
4430
4443
|
---
|
|
4431
4444
|
|
|
4432
4445
|
Sync Guance monitoring alert events to Flashduty via webhook for automated alert noise reduction.
|
|
@@ -4490,7 +4503,7 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4490
4503
|
3. In the notification configuration section of the alert strategies editing page, select \`severity\` and choose \`FlashDuty\` created in Step 1 as the \`Notification Tragets\`
|
|
4491
4504
|
4. Configure other options as needed and click \`Save\` to complete
|
|
4492
4505
|
|
|
4493
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/
|
|
4506
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/guance-2.png" />
|
|
4494
4507
|
|
|
4495
4508
|
</dev>
|
|
4496
4509
|
|
|
@@ -4500,11 +4513,11 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4500
4513
|
|
|
4501
4514
|
| Guance | Flashduty | Status |
|
|
4502
4515
|
| ---------- | -------- | ---- |
|
|
4503
|
-
|
|
|
4504
|
-
|
|
|
4516
|
+
| Critical | Critical | Critical |
|
|
4517
|
+
| Error | Warning | Warning |
|
|
4505
4518
|
| Warning | Warning | Warning |
|
|
4506
4519
|
| Info | Info | Info |
|
|
4507
|
-
| Data
|
|
4520
|
+
| Data Missing | Info | Info |
|
|
4508
4521
|
|
|
4509
4522
|
</div>
|
|
4510
4523
|
`,Y=`---
|
package/dist/en.js
CHANGED
|
@@ -4357,6 +4357,9 @@ url: "https://docs.flashcat.cloud/en/flashduty/statecloud-integration-guide"
|
|
|
4357
4357
|
|
|
4358
4358
|
Sync StateCloud monitoring alert events to Flashduty via webhook for automated alert noise reduction.
|
|
4359
4359
|
|
|
4360
|
+
For resource monitoring events from StateCloud [secondary nodes](#secondary-nodes), please use Huawei Cloud integration. Refer to [Huawei Cloud Alert Integration Guide](https://docs.flashcat.cloud/en/flashduty/huawei-ces-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
|
|
4361
|
+
|
|
4362
|
+
|
|
4360
4363
|
<div class="hide">
|
|
4361
4364
|
|
|
4362
4365
|
## In Flashduty
|
|
@@ -4407,7 +4410,7 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4407
4410
|
4. In the alarm rule editing page, fill in the integration <span class='integration_url' >push URL</span> under \`Alert Callback\` and click test
|
|
4408
4411
|
5. After successful testing, click \`Save\`
|
|
4409
4412
|
|
|
4410
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/
|
|
4413
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/state-1.png" />
|
|
4411
4414
|
|
|
4412
4415
|
</dev>
|
|
4413
4416
|
|
|
@@ -4421,12 +4424,22 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4421
4424
|
| Warning | Warning | warning |
|
|
4422
4425
|
| Normal | Info | info |
|
|
4423
4426
|
|
|
4427
|
+
## III. StateCloud Secondary Node List<span id="secondary-nodes"></span>
|
|
4428
|
+
|
|
4429
|
+
| Region | Cities |
|
|
4430
|
+
| ---------- | -------- |
|
|
4431
|
+
| East China | Hangzhou/Nanchang/Shanghai4/Suzhou/Wuhu |
|
|
4432
|
+
| South China | Changsha2/Fuzhou1/Guangzhou4/Haikou/Nanning/Wuhan2 |
|
|
4433
|
+
| Northwest | Lanzhou/Urumqi/Xi'an2/Xining/Zhongwei |
|
|
4434
|
+
| Southwest | Chengdu3/Chongqing/Guizhou1/Kunming |
|
|
4435
|
+
| North | Beijing2/Changchun/Harbin/North China/Inner Mongolia3/Qingdao/Shenyang3/Shijiazhuang/Taiyuan/Tianjin/Zhengzhou |
|
|
4436
|
+
|
|
4424
4437
|
</div>
|
|
4425
4438
|
`, G = `---
|
|
4426
4439
|
title: "Guance Alert Events"
|
|
4427
4440
|
description: "Sync Guance alert events to Flashduty via webhook for automated alert noise reduction"
|
|
4428
4441
|
date: "2024-07-05T10:00:00+08:00"
|
|
4429
|
-
url: "https://docs.flashcat.cloud/en/flashduty/
|
|
4442
|
+
url: "https://docs.flashcat.cloud/en/flashduty/guance-integration-guide"
|
|
4430
4443
|
---
|
|
4431
4444
|
|
|
4432
4445
|
Sync Guance monitoring alert events to Flashduty via webhook for automated alert noise reduction.
|
|
@@ -4490,7 +4503,7 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4490
4503
|
3. In the notification configuration section of the alert strategies editing page, select \`severity\` and choose \`FlashDuty\` created in Step 1 as the \`Notification Tragets\`
|
|
4491
4504
|
4. Configure other options as needed and click \`Save\` to complete
|
|
4492
4505
|
|
|
4493
|
-
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/
|
|
4506
|
+
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/guance-2.png" />
|
|
4494
4507
|
|
|
4495
4508
|
</dev>
|
|
4496
4509
|
|
|
@@ -4500,11 +4513,11 @@ Choose this option when you need to route alerts to different channels based on
|
|
|
4500
4513
|
|
|
4501
4514
|
| Guance | Flashduty | Status |
|
|
4502
4515
|
| ---------- | -------- | ---- |
|
|
4503
|
-
|
|
|
4504
|
-
|
|
|
4516
|
+
| Critical | Critical | Critical |
|
|
4517
|
+
| Error | Warning | Warning |
|
|
4505
4518
|
| Warning | Warning | Warning |
|
|
4506
4519
|
| Info | Info | Info |
|
|
4507
|
-
| Data
|
|
4520
|
+
| Data Missing | Info | Info |
|
|
4508
4521
|
|
|
4509
4522
|
</div>
|
|
4510
4523
|
`, Y = `---
|
package/dist/zh.cjs
CHANGED
|
@@ -4637,6 +4637,8 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
|
|
|
4637
4637
|
|
|
4638
4638
|
通过 webhook 的方式同步天翼云监控告警事件到 Flashduty,实现告警事件自动化降噪处理。
|
|
4639
4639
|
|
|
4640
|
+
天翼云[二级节点](#二级节点)的资源监控事件推送,请使用华为云集成,请参考 [华为云告警集成指引](https://docs.flashcat.cloud/zh/flashduty/huawei-ces-integration-guide)。
|
|
4641
|
+
|
|
4640
4642
|
<div class="hide">
|
|
4641
4643
|
|
|
4642
4644
|
## 在 Flashduty
|
|
@@ -4702,12 +4704,23 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
|
|
|
4702
4704
|
| 警示 | Warning | 警告 |
|
|
4703
4705
|
| 普通 | Info | 提醒 |
|
|
4704
4706
|
|
|
4707
|
+
## 三、天翼云二级节点列表<span id="二级节点"></span>
|
|
4708
|
+
|
|
4709
|
+
| 地区 | 城市 |
|
|
4710
|
+
| ---------- | -------- |
|
|
4711
|
+
| 华东 | 杭州/南昌/上海4/苏州/芜湖 |
|
|
4712
|
+
| 华南 | 长沙2/福州1/广州4/海口/南宁/武汉2 |
|
|
4713
|
+
| 西北 | 兰州/乌鲁木齐/西安2/西宁/中卫 |
|
|
4714
|
+
| 西南 | 成都3/重庆/贵州1/昆明 |
|
|
4715
|
+
| 北方 | 北京2/长春/哈尔滨/华北/内蒙3/青岛/沈阳3/石家庄/太原/天津/郑州 |
|
|
4716
|
+
|
|
4717
|
+
|
|
4705
4718
|
</div>
|
|
4706
4719
|
`,U=`---
|
|
4707
4720
|
title: "观测云告警事件"
|
|
4708
4721
|
description: "通过 webhook 的方式同步观测云告警事件到 Flashduty,实现告警事件自动化降噪处理"
|
|
4709
4722
|
date: "2024-07-05T10:00:00+08:00"
|
|
4710
|
-
url: "https://docs.flashcat.cloud/zh/flashduty/
|
|
4723
|
+
url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
|
|
4711
4724
|
---
|
|
4712
4725
|
|
|
4713
4726
|
通过 webhook 的方式同步观测云监控告警事件到 Flashduty,实现告警事件自动化降噪处理。
|
|
@@ -4791,7 +4804,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
|
|
|
4791
4804
|
| 数据断档 | Info | 提醒 |
|
|
4792
4805
|
|
|
4793
4806
|
</div>
|
|
4794
|
-
`,
|
|
4807
|
+
`,z=`---
|
|
4795
4808
|
title: "自定义变更事件集成指引"
|
|
4796
4809
|
description: "通过标准协议推送自有系统变更事件到 Flashduty,大部分故障由变更导致,变更和告警事件联动有助于快速定位故障原因。"
|
|
4797
4810
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4848,7 +4861,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议,对
|
|
|
4848
4861
|
|
|
4849
4862
|
</details>
|
|
4850
4863
|
|
|
4851
|
-
`,
|
|
4864
|
+
`,H=`---
|
|
4852
4865
|
title: ""
|
|
4853
4866
|
description: ""
|
|
4854
4867
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4922,7 +4935,7 @@ Flashduty 默认提取 webhook payload 中 status.name 信息,并按照下边
|
|
|
4922
4935
|
如您希望变更此映射关系,请联系 Flashduty。
|
|
4923
4936
|
|
|
4924
4937
|
</div>
|
|
4925
|
-
`,
|
|
4938
|
+
`,O=`---
|
|
4926
4939
|
title: Contributing to our documentation — Meilisearch documentation
|
|
4927
4940
|
description: The Meilisearch documentation is open-source. Learn how to help make it even better.
|
|
4928
4941
|
sidebarDepth: 3
|
|
@@ -6883,4 +6896,4 @@ CloseTime | int64 | 否 | 关闭时间,EndTime 为告警恢复时间,CloseTi
|
|
|
6883
6896
|
<img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
|
|
6884
6897
|
|
|
6885
6898
|
|
|
6886
|
-
`;exports.AWSCW=u;exports.AWSEventBridge=S;exports.AlertWebhook=K;exports.AliyunARMS=d;exports.AliyunCm=r;exports.AliyunCmEvent=o;exports.AliyunSLS=c;exports.AppDynamics=P;exports.AzureMonitor=h;exports.BaiDuBCM=m;exports.CustomAction=J;exports.CustomAlert=n;exports.CustomChange=
|
|
6899
|
+
`;exports.AWSCW=u;exports.AWSEventBridge=S;exports.AlertWebhook=K;exports.AliyunARMS=d;exports.AliyunCm=r;exports.AliyunCmEvent=o;exports.AliyunSLS=c;exports.AppDynamics=P;exports.AzureMonitor=h;exports.BaiDuBCM=m;exports.CustomAction=J;exports.CustomAlert=n;exports.CustomChange=z;exports.Dingtalk=q;exports.Dynatrace=A;exports.Email=t;exports.GoogleCM=I;exports.Grafana=i;exports.Graylog=x;exports.Guance=U;exports.HuaWeiCES=p;exports.HuaweiyunLTS=C;exports.IncidentWebhook=Z;exports.InfluxDB=g;exports.Jiankongbao=L;exports.Jira=H;exports.Lark=O;exports.Meraki=R;exports.MicrosoftTeams=V;exports.N9e=e;exports.OceanBase=k;exports.OpManager=W;exports.OpenFalcon=y;exports.PagerDuty=_;exports.Prometheus=a;exports.Sentry=T;exports.Skywalking=F;exports.Slack=G;exports.SolarWinds=M;exports.Splunk=D;exports.StateCloud=j;exports.Templates=X;exports.TencentBK=f;exports.TencentCLS=b;exports.TencentCm=v;exports.TencentEb=w;exports.UptimeKuma=l;exports.VolcEngineEvent=E;exports.VolcEngineMetric=$;exports.VolcEngineTLS=N;exports.Wecom=B;exports.Zabbix=s;
|
package/dist/zh.js
CHANGED
|
@@ -4637,6 +4637,8 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
|
|
|
4637
4637
|
|
|
4638
4638
|
通过 webhook 的方式同步天翼云监控告警事件到 Flashduty,实现告警事件自动化降噪处理。
|
|
4639
4639
|
|
|
4640
|
+
天翼云[二级节点](#二级节点)的资源监控事件推送,请使用华为云集成,请参考 [华为云告警集成指引](https://docs.flashcat.cloud/zh/flashduty/huawei-ces-integration-guide)。
|
|
4641
|
+
|
|
4640
4642
|
<div class="hide">
|
|
4641
4643
|
|
|
4642
4644
|
## 在 Flashduty
|
|
@@ -4702,12 +4704,23 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
|
|
|
4702
4704
|
| 警示 | Warning | 警告 |
|
|
4703
4705
|
| 普通 | Info | 提醒 |
|
|
4704
4706
|
|
|
4707
|
+
## 三、天翼云二级节点列表<span id="二级节点"></span>
|
|
4708
|
+
|
|
4709
|
+
| 地区 | 城市 |
|
|
4710
|
+
| ---------- | -------- |
|
|
4711
|
+
| 华东 | 杭州/南昌/上海4/苏州/芜湖 |
|
|
4712
|
+
| 华南 | 长沙2/福州1/广州4/海口/南宁/武汉2 |
|
|
4713
|
+
| 西北 | 兰州/乌鲁木齐/西安2/西宁/中卫 |
|
|
4714
|
+
| 西南 | 成都3/重庆/贵州1/昆明 |
|
|
4715
|
+
| 北方 | 北京2/长春/哈尔滨/华北/内蒙3/青岛/沈阳3/石家庄/太原/天津/郑州 |
|
|
4716
|
+
|
|
4717
|
+
|
|
4705
4718
|
</div>
|
|
4706
4719
|
`, U = `---
|
|
4707
4720
|
title: "观测云告警事件"
|
|
4708
4721
|
description: "通过 webhook 的方式同步观测云告警事件到 Flashduty,实现告警事件自动化降噪处理"
|
|
4709
4722
|
date: "2024-07-05T10:00:00+08:00"
|
|
4710
|
-
url: "https://docs.flashcat.cloud/zh/flashduty/
|
|
4723
|
+
url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
|
|
4711
4724
|
---
|
|
4712
4725
|
|
|
4713
4726
|
通过 webhook 的方式同步观测云监控告警事件到 Flashduty,实现告警事件自动化降噪处理。
|
|
@@ -4791,7 +4804,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
|
|
|
4791
4804
|
| 数据断档 | Info | 提醒 |
|
|
4792
4805
|
|
|
4793
4806
|
</div>
|
|
4794
|
-
`,
|
|
4807
|
+
`, z = `---
|
|
4795
4808
|
title: "自定义变更事件集成指引"
|
|
4796
4809
|
description: "通过标准协议推送自有系统变更事件到 Flashduty,大部分故障由变更导致,变更和告警事件联动有助于快速定位故障原因。"
|
|
4797
4810
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -4848,7 +4861,7 @@ Flashduty 已经适配部分常用工单、部署系统的 webhook 协议,对
|
|
|
4848
4861
|
|
|
4849
4862
|
</details>
|
|
4850
4863
|
|
|
4851
|
-
`,
|
|
4864
|
+
`, H = `---
|
|
4852
4865
|
title: ""
|
|
4853
4866
|
description: ""
|
|
4854
4867
|
date: "2024-05-11T10:00:00+08:00"
|
|
@@ -6897,7 +6910,7 @@ export {
|
|
|
6897
6910
|
m as BaiDuBCM,
|
|
6898
6911
|
J as CustomAction,
|
|
6899
6912
|
n as CustomAlert,
|
|
6900
|
-
|
|
6913
|
+
z as CustomChange,
|
|
6901
6914
|
q as Dingtalk,
|
|
6902
6915
|
A as Dynatrace,
|
|
6903
6916
|
t as Email,
|
|
@@ -6910,7 +6923,7 @@ export {
|
|
|
6910
6923
|
Z as IncidentWebhook,
|
|
6911
6924
|
g as InfluxDB,
|
|
6912
6925
|
L as Jiankongbao,
|
|
6913
|
-
|
|
6926
|
+
H as Jira,
|
|
6914
6927
|
O as Lark,
|
|
6915
6928
|
R as Meraki,
|
|
6916
6929
|
V as MicrosoftTeams,
|