Skip to content

Commit 3351d02

Browse files
pijiang3pijiang3
committed
add jdcloud docs
1 parent d4c2b25 commit 3351d02

3 files changed

Lines changed: 226 additions & 0 deletions

File tree

‎docs.json‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -218,6 +218,7 @@
218218
"zh/on-call/integration/alert-integration/alert-sources/monit",
219219
"zh/on-call/integration/alert-integration/alert-sources/harbor",
220220
"zh/on-call/integration/alert-integration/alert-sources/ucloud-cloudwatch",
221+
"zh/on-call/integration/alert-integration/alert-sources/jdcloud",
221222
"zh/on-call/integration/alert-integration/alert-sources/volcengine-rtc",
222223
"zh/on-call/integration/alert-integration/alert-sources/nagios",
223224
"zh/on-call/integration/alert-integration/alert-sources/label-mapping-api"
@@ -641,6 +642,7 @@
641642
"en/on-call/integration/alert-integration/alert-sources/monit",
642643
"en/on-call/integration/alert-integration/alert-sources/harbor",
643644
"en/on-call/integration/alert-integration/alert-sources/ucloud-cloudwatch",
645+
"en/on-call/integration/alert-integration/alert-sources/jdcloud",
644646
"en/on-call/integration/alert-integration/alert-sources/volcengine-rtc",
645647
"en/on-call/integration/alert-integration/alert-sources/nagios",
646648
"en/on-call/integration/alert-integration/alert-sources/label-mapping-api"

‎en/on-call/integration/alert-integration/alert-sources/jdcloud.mdx‎

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
---
2+
title: "JD Cloud monitoring integration"
3+
description: "Sync JD Cloud monitoring alert events to Flashduty On-call via webhook for automated alert noise reduction"
4+
keywords: ["alert integration", "JD Cloud monitoring integration", "monitoring alerts", "data ingestion"]
5+
---
6+
7+
<div className="hide">
8+
9+
## In Flashduty On-call
10+
---
11+
You can obtain an integration push URL through either of these two methods:
12+
13+
### Using private integration
14+
15+
Choose this method when you don't need to route alert events to different channels — it's simpler.
16+
17+
<AccordionGroup>
18+
<Accordion title="Expand">
19+
20+
1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
21+
2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
22+
3. Choose **JD Cloud Monitoring** integration and click **Save** to generate a card
23+
4. Click the generated card to view the **Push URL**, copy it for later use
24+
25+
</Accordion>
26+
</AccordionGroup>
27+
28+
### Using shared integration
29+
30+
Choose this method when you need to route alerts to different channels based on the alert event payload.
31+
32+
<AccordionGroup>
33+
<Accordion title="Expand">
34+
35+
1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
36+
2. Select **JD Cloud Monitoring** integration:
37+
- **Integration Name**: Define a name for this integration
38+
3. Configure the default route and select the corresponding channel (after creation, go to `Route` to configure more routing rules)
39+
4. Click **Save** and copy the newly generated **Push URL** for later use
40+
41+
</Accordion>
42+
</AccordionGroup>
43+
</div>
44+
45+
## In JD Cloud
46+
---
47+
48+
<Steps>
49+
<Step title="Create notification template">
50+
51+
1. Log in to the JD Cloud console, search for **Monitoring**, and enter the corresponding console
52+
2. In the left menu, select **Alarm Management → Notice Templates**, and create or edit a notification template
53+
3. Check **Alert Callback** and enter the integration push URL in the `URL` field
54+
4. Enter the following template content in the `POST` input box:
55+
56+
```json
57+
{
58+
"resource_id": "${resourceId}",
59+
"request_id": "${requestId}",
60+
"metric": "${metric}",
61+
"current_value": "${currentValue}",
62+
"times": "${times}",
63+
"tags": "${tags}",
64+
"alert_time": "${alertTime}",
65+
"region": "${region}",
66+
"threshold": "${threshold}",
67+
"service_code": "${serviceCode}",
68+
"as_group_id": "${asGroupId}",
69+
"unhealthy_instance": "${unhealthyInstance}",
70+
"rule_policy_id": "${rulePolicyId}",
71+
"service_code_en": "${serviceCodeEN}",
72+
"service_code_cn": "${serviceCodeCN}",
73+
"level": "${level}",
74+
"resource_name": "${resourceName}",
75+
"ip_address": "${ipAddress}",
76+
"status": "${status}"
77+
}
78+
```
79+
80+
5. Configure other options as needed and click **Save**
81+
82+
</Step>
83+
84+
<Step title="Configure alert rules">
85+
86+
1. In the left menu, select **Alarm Management → Alarm Rules**, and create or edit an alert rule
87+
2. In the **Notification Policy** section, select **Use Template** and choose the template created in the previous step
88+
3. Configure other options as needed and click **Save**
89+
90+
</Step>
91+
92+
<Step title="Verify integration">
93+
94+
Go back to the Flashduty console integration list page. If the latest event time is displayed, the configuration is successful and events are being received.
95+
96+
</Step>
97+
</Steps>
98+
99+
## Severity mapping
100+
---
101+
<div className="md-block">
102+
103+
JD Cloud Monitoring to Flashduty severity mapping:
104+
105+
| JD Cloud Monitoring | Flashduty | Status |
106+
| :--- | :--- | :--- |
107+
| Critical | Critical | Critical |
108+
| Major | Warning | Warning |
109+
| General | Info | Info |
110+
111+
</div>

‎zh/on-call/integration/alert-integration/alert-sources/jdcloud.mdx‎

Lines changed: 113 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,113 @@
1+
---
2+
title: "京东云监控集成"
3+
description: "通过 webhook 的方式同步京东云监控告警事件到 Flashduty On-call，实现告警事件自动化降噪处理"
4+
keywords: ["告警集成", "京东云监控集成", "监控告警", "数据接入"]
5+
---
6+
7+
<div className="hide">
8+
9+
## 在 Flashduty On-call
10+
---
11+
您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
12+
13+
### 使用专属集成
14+
15+
当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
16+
17+
<AccordionGroup>
18+
<Accordion title="展开">
19+
20+
1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
21+
2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
22+
3. 选择 **京东云监控** 集成，点击 **保存**，生成卡片。
23+
4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
24+
25+
26+
</Accordion>
27+
</AccordionGroup>
28+
29+
### 使用共享集成
30+
31+
当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
32+
33+
<AccordionGroup>
34+
<Accordion title="展开">
35+
36+
1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
37+
2. 选择 **京东云监控** 集成：
38+
- **集成名称**：为当前集成定义一个名称。
39+
3. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 `路由` 进行更多路由规则的配置）。
40+
4. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
41+
5. 完成。
42+
43+
</Accordion>
44+
</AccordionGroup>
45+
</div>
46+
47+
## 在京东云
48+
---
49+
50+
<Steps>
51+
<Step title="创建通知模版">
52+
53+
1. 登录京东云控制台，检索 **云监控** 产品，进入对应控制台
54+
2. 在左侧菜单选择 **告警管理 → 通知模版**，创建或编辑通知模版
55+
3. 勾选 **告警回调**，在 `URL` 中输入集成的推送地址
56+
4. 在 `POST` 编辑框中输入以下模版内容：
57+
58+
```json
59+
{
60+
"resource_id": "${resourceId}",
61+
"request_id": "${requestId}",
62+
"metric": "${metric}",
63+
"current_value": "${currentValue}",
64+
"times": "${times}",
65+
"tags": "${tags}",
66+
"alert_time": "${alertTime}",
67+
"region": "${region}",
68+
"threshold": "${threshold}",
69+
"service_code": "${serviceCode}",
70+
"as_group_id": "${asGroupId}",
71+
"unhealthy_instance": "${unhealthyInstance}",
72+
"rule_policy_id": "${rulePolicyId}",
73+
"service_code_en": "${serviceCodeEN}",
74+
"service_code_cn": "${serviceCodeCN}",
75+
"level": "${level}",
76+
"resource_name": "${resourceName}",
77+
"ip_address": "${ipAddress}",
78+
"status": "${status}"
79+
}
80+
```
81+
82+
5. 其他选项按需配置，点击 **保存** 完成
83+
84+
</Step>
85+
86+
<Step title="配置告警规则">
87+
88+
1. 在左侧菜单选择 **告警管理 → 全部告警规则**，创建或编辑告警规则
89+
2. 在规则配置页面的 **通知策略** 处，选择 **使用模版** 并选择上一步创建的模版
90+
3. 其他选项按需配置，点击 **保存** 完成
91+
92+
</Step>
93+
94+
<Step title="验证集成">
95+
96+
回到 Flashduty 控制台集成列表页面，如果展示了最新事件时间，说明配置成功且收到事件。
97+
98+
</Step>
99+
</Steps>
100+
101+
## 状态对照
102+
---
103+
<div className="md-block">
104+
105+
京东云监控到 Flashduty 告警等级映射关系：
106+
107+
| 京东云监控 | Flashduty | 状态 |
108+
| :--- | :--- | :--- |
109+
| 紧急 | Critical | 严重 |
110+
| 严重 | Warning | 警告 |
111+
| 一般 | Info | 提醒 |
112+
113+
</div>

0 commit comments

Comments
 (0)