Skip to content

Commit e9878fe

Browse files
author
niuweili
committed
Merge branch 'test' of github.com:flashcatcloud/knowledge-base into test
2 parents f9f5cb4 + 17ccb4f commit e9878fe

6 files changed

Lines changed: 215 additions & 19 deletions

File tree

‎flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.22 OceanBase Integration.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ OCP Alert Notification - Single Alert
180180
|OceanBase|Flashduty|Status|
181181
|---|---|---|
182182
|Down|Critical|Critical|
183-
|Critical|Warning|Critical|
183+
|Critical|Critical|Critical|
184184
|Warning|Warning|Warning|
185185
|Caution|Info|Info|
186186
|Notice|Info|Info|

‎flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.58 JD Cloud Monitoring Integration.md‎

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
title: "JD Cloud Monitoring Alert Events"
3+
description: "Sync JD Cloud monitoring alert events to Flashduty via webhook for automated alert noise reduction"
4+
date: "2025-05-19T10:00:00+08:00"
5+
url: "https://docs.flashcat.cloud/en/flashduty/jdcloud-integration-guide"
6+
---
7+
8+
Sync JD Cloud monitoring alert events to Flashduty via webhook for automated alert noise reduction.
9+
10+
<div class="hide">
11+
12+
## In Flashduty
13+
---
14+
You can obtain an integration push URL through either of these two methods:
15+
16+
### Using Private Integration
17+
18+
Choose this method when you don't need to route alert events to different channels - it's simpler.
19+
20+
<details>
21+
<summary>Expand</summary>
22+
23+
1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
24+
2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
25+
3. Choose **JD Cloud Monitoring** integration and click **Save** to generate a card
26+
4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
27+
28+
</details>
29+
30+
### Using Shared Integration
31+
32+
Choose this method when you need to route alerts to different channels based on the alert event payload.
33+
34+
<details>
35+
<summary>Expand</summary>
36+
37+
1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
38+
2. Select **JD Cloud Monitoring** integration:
39+
- **Integration Name**: Define a name for this integration
40+
3. Configure the default route and select the corresponding channel (after the integration is created, you can go to `Route` to configure more routing rules)
41+
4. Click **Save** and copy the newly generated **push URL** for later use
42+
5. Done
43+
44+
</details>
45+
46+
</div>
47+
48+
## In JD Cloud
49+
---
50+
51+
### Step 1: Create Notification Template
52+
1. Login to your JD Cloud console, search for `Monitoring` product, and enter the corresponding product console.
53+
2. In the left menu, select `Alarm Management->Notice Templates`, and create or edit a notification template.
54+
3. Check `Alert Callback` on the template page, and enter the <span class='integration_url'>push URL</span> for the alert integration in the `URL` field.
55+
4. Enter the following template content in the `POST` input box.
56+
```
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.
81+
6. Click `Save` to complete the configuration.
82+
83+
### Step 2: Configure Alert Rules
84+
1. Login to your JD Cloud console, search for `Monitoring` product, and enter the corresponding product console.
85+
2. In the left menu, select `Alarm Management->Alarm Rules`, and create or edit an alert rule.
86+
3. In the **Notification Policy** section of the rule configuration page, select `Use Template` and choose the template created in **Step 1**.
87+
4. Configure other options as needed.
88+
5. Click `Save` to complete the configuration.
89+
90+
## Severity Mapping
91+
---
92+
<div class="md-block">
93+
94+
JD Cloud Monitoring to Flashduty severity mapping:
95+
96+
| JD Cloud Monitoring | Flashduty | Status |
97+
| ------------------- | --------- | -------- |
98+
| Critical | Critical | Critical |
99+
| Major | Warning | Warning |
100+
| General | Info | Info |
101+
102+
</div>

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.22 OceanBase 告警事件集成指引.md‎

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -191,22 +191,7 @@ OCP告警通知-单条告警
191191
|OceanBase| Flashduty|状态|
192192
|---|---|---|
193193
|停服|Critical|严重|
194-
|严重|Warning|严重|
195-
|警告|Warning|警告|
196-
|注意|Info|提醒|
197-
|提醒|Info|提醒|
198-
199-
</div>
200-
201-
202-
## 状态对照
203-
---
204-
<div class="md-block">
205-
206-
|OceanBase| Flashduty|状态|
207-
|---|---|---|
208-
|停服|Critical|严重|
209-
|严重|Warning|严重|
194+
|严重|Critical|严重|
210195
|警告|Warning|警告|
211196
|注意|Info|提醒|
212197
|提醒|Info|提醒|

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.58 京东云监控告警集成指引.md‎

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

‎src/en.ts‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,7 @@ import Harbor from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integr
5656
import VolcEngineRTC from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.55 Volcengine RTC Integration.md?raw";
5757
import UcloudCloudWatch from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.56 Ucloud CloudWatch Integration.md?raw";
5858
import Nagios from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.57 Nagios Integration.md?raw";
59+
import JDCloudMonitor from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.58 JD Cloud Monitoring Integration.md?raw";
5960
/** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
6061

6162
/** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -166,6 +167,7 @@ const docs = {
166167
LabelMappingAPI,
167168
VolcEngineRTC,
168169
UcloudCloudWatch,
169-
Nagios
170+
Nagios,
171+
JDCloudMonitor
170172
};
171173
export default docs;

‎src/zh.ts‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,7 @@ import Harbor from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/
5656
import VolcEngineRTC from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.55 火山引擎 RTC 告警集成指引.md?raw";
5757
import UcloudCloudWatch from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.56 Ucloud CloudWatch 告警集成指引.md?raw";
5858
import Nagios from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.57 Nagios 告警集成指引.md?raw";
59+
import JDCloudMonitor from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.58 京东云监控告警集成指引.md?raw";
5960
/** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
6061

6162
/** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -164,6 +165,7 @@ const docs = {
164165
LabelMappingAPI,
165166
VolcEngineRTC,
166167
UcloudCloudWatch,
167-
Nagios
168+
Nagios,
169+
JDCloudMonitor
168170
};
169171
export default docs;

0 commit comments

Comments
 (0)