Skip to content

Commit 32a3abd

Browse files
pijiang3pijiang3
committed
add alert integration
1 parent 3126a8a commit 32a3abd

6 files changed

Lines changed: 301 additions & 2 deletions

File tree

‎flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.54 Volcengine RTC Integration.md‎

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
title: "Volcengine RTC Alert Events"
3+
description: "Sync Volcengine RTC alert events to Flashduty via webhook for automated alert noise reduction"
4+
date: "2024-07-05T10:00:00+08:00"
5+
url: "https://docs.flashcat.cloud/en/flashduty/volcengine-rtc-integration-guide"
6+
---
7+
8+
Sync Volcengine RTC 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 **Volcengine RTC** 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 **Volcengine RTC** 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+
</div>
46+
47+
## In Volcengine
48+
---
49+
50+
### Configure Alert Rules
51+
52+
1. Login to your `Volcengine` console, find `RTC`, and enter the corresponding product console.
53+
2. In the left menu, select `Monitor->Alert Notifications`, and go to the `Alert Rules` page.
54+
3. Create or edit an alert rule, check `Alert Callback` on the rule page and fill in the <span class='integration_url'>push URL</span> for the alert integration.
55+
4. Configure other options as needed.
56+
5. Click `Confirm` to complete the configuration.
57+
58+
![2026-02-04-17-11-27](https://docs-cdn.flashcat.cloud/images/png/f3a0d7b4943bd21b37fa34831ba120ff.png)
59+
60+
## Status Mapping
61+
62+
|Volcengine RTC|Flashduty|Status|
63+
|---|---|---|
64+
|Critical|Critical|Critical|
65+
|Warning|Warning|Warning|
66+
|Notice|Info|Info|
67+
68+
69+
You can customize the severity through [Alert Processing Pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).

‎flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.55 Ucloud CloudWatch Integration.md‎

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
title: "Ucloud CloudWatch Alert Events"
3+
description: "Sync Ucloud CloudWatch alert events to Flashduty via webhook for automated alert noise reduction"
4+
date: "2024-07-05T10:00:00+08:00"
5+
url: "https://docs.flashcat.cloud/en/flashduty/ucloud-cloudwatch-integration-guide"
6+
---
7+
8+
Sync Ucloud CloudWatch 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 **Ucloud CloudWatch** 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 **Ucloud CloudWatch** 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+
</div>
46+
47+
## In Ucloud
48+
---
49+
50+
### Step 1: Configure Notice Template
51+
52+
1. Login to your Ucloud console, search for `CloudWatch` product, and enter the corresponding product console.
53+
2. In the menu, select `Notice Management`, and go to the `Contact Template` page.
54+
3. Create or edit a notification template, check `Webhook` on the template page.
55+
4. Select `English` for **Callback Language**, and enter the <span class='integration_url'>push URL</span> for the alert integration in the input box.
56+
5. Enter `Flashduty` or another name for the template name.
57+
6. Configure other options as needed.
58+
7. Click `Submit` to complete the configuration.
59+
60+
![2026-02-05-14-16-00](https://docs-cdn.flashcat.cloud/images/png/9e6ee0943b6f3ee6b942229bd456cf75.png)
61+
62+
### Step 2: Configure Alert Policy
63+
1. Login to your Ucloud console, search for `CloudWatch` product, and enter the corresponding product console.
64+
2. In the menu, select `Alarm Management`, and go to the `Alarm Policy` page.
65+
3. Create or edit an alert policy, find the **Notification Settings** on the policy configuration page, and select the notification template created in **Step 1**.
66+
4. Configure other options as needed.
67+
5. Click `Submit` to complete the configuration.
68+
69+
70+
## Severity Mapping
71+
---
72+
Currently, all Ucloud CloudWatch alert events pushed to Flashduty have a severity of Warning. You can customize the severity through [Alert Processing Pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.54 火山引擎 RTC 告警集成指引.md‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
---
2+
title: "火山引擎 RTC 告警集成"
3+
description: "通过 webhook 的方式同步火山引擎 RTC 的告警事件到 Flashduty，实现告警事件自动化降噪处理"
4+
date: "2025-05-19T10:00:00+08:00"
5+
url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-rtc-integration-guide"
6+
---
7+
8+
通过 webhook 的方式同步火山引擎 RTC 的告警事件到 Flashduty，实现告警事件自动化降噪处理。
9+
10+
<div class="hide">
11+
12+
## 在 Flashduty
13+
---
14+
15+
### 创建火山引擎 RTC 告警集成
16+
17+
您可通过以下2种方式，获取一个企微机器人告警集成地址，任选其一即可。
18+
19+
#### 使用专属集成
20+
21+
当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
22+
23+
<details>
24+
<summary>展开</summary>
25+
26+
1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
27+
2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
28+
3. 选择 **火山引擎 RTC** 集成，点击 **保存**，生成卡片。
29+
4. 点击生成的卡片，可以查看到 **火山引擎 RTC 告警集成地址**，复制备用，完成。
30+
31+
</details>
32+
33+
#### 使用共享集成
34+
35+
当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
36+
37+
<details>
38+
<summary>展开</summary>
39+
40+
1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
41+
2. 选择 **火山引擎 RTC** 集成：
42+
- **集成名称**：为当前集成定义一个名称。
43+
- **推送模式**：选择企微告警在何种情况下触发或恢复告警。
44+
3. 复制当前页面的 **火山引擎 RTC 告警集成地址** 备用。
45+
4. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 `路由` 进行更多路由规则的配置）。
46+
5. 完成。
47+
48+
</details>
49+
50+
## 在火山引擎
51+
---
52+
</div>
53+
54+
55+
### 配置告警规则
56+
57+
1. 登录您的火山引擎控制台，检索 `实时音视频` 产品，并进入对应产品控制台。
58+
2. 在左侧菜单中选择 `监控台->告警通知`，并转到 `告警规则` 页面。
59+
3. 创建或编辑告警规则，在规则页面中勾选 `告警回调` 并输入告警集成的<span class='integration_url'>推送地址</span>。
60+
4. 其他选项按需配置。
61+
5. 点击 `确定` 完成配置。
62+
63+
![2026-02-04-17-11-27](https://docs-cdn.flashcat.cloud/images/png/f3a0d7b4943bd21b37fa34831ba120ff.png)
64+
65+
## 严重程度映射关系
66+
---
67+
|火山引擎RTC| Flashduty|状态|
68+
|---|---|---|
69+
|严重|Critical|严重|
70+
|警告|Warning|警告|
71+
|通知|Info|提醒|
72+
73+
您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.55 Ucloud Cloud Watch告警集成指引.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
title: "Ucloud CloudWatch 告警集成"
3+
description: "通过 webhook 的方式同步 Ucloud CloudWatch 的告警事件到 Flashduty，实现告警事件自动化降噪处理"
4+
date: "2025-05-19T10:00:00+08:00"
5+
url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-rtc-integration-guide"
6+
---
7+
8+
通过 webhook 的方式同步 Ucloud CloudWatch 的告警事件到 Flashduty，实现告警事件自动化降噪处理。
9+
10+
<div class="hide">
11+
12+
## 在 Flashduty
13+
---
14+
15+
### 创建 Ucloud CloudWatch 告警集成
16+
17+
您可通过以下2种方式，获取一个企微机器人告警集成地址，任选其一即可。
18+
19+
#### 使用专属集成
20+
21+
当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
22+
23+
<details>
24+
<summary>展开</summary>
25+
26+
1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
27+
2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
28+
3. 选择 **Ucloud CloudWatch** 集成，点击 **保存**，生成卡片。
29+
4. 点击生成的卡片，可以查看到 **火山引擎 RTC 告警集成地址**，复制备用，完成。
30+
31+
</details>
32+
33+
#### 使用共享集成
34+
35+
当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
36+
37+
<details>
38+
<summary>展开</summary>
39+
40+
1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
41+
2. 选择 **Ucloud CloudWatch** 集成：
42+
- **集成名称**：为当前集成定义一个名称。
43+
- **推送模式**：选择企微告警在何种情况下触发或恢复告警。
44+
3. 复制当前页面的 **Ucloud CloudWatch 告警集成地址** 备用。
45+
4. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 `路由` 进行更多路由规则的配置）。
46+
5. 完成。
47+
48+
</details>
49+
50+
## 在 Ucloud
51+
---
52+
</div>
53+
54+
55+
### 步骤1：配置通知模版
56+
57+
1. 登录您的 Ucloud 控制台，检索 `CloudWatch` 产品，并进入对应产品控制台。
58+
2. 在菜单中选择 `通知管理`，并转到 `通知模版` 页面。
59+
3. 创建或编辑通知模版，在模版页面中勾选 `接口回调`。
60+
4. **回调语言**选择 `英文`，输入框中输入告警集成的<span class='integration_url'>推送地址</span>。
61+
5. 模版名称输入 `Flashduty` 或其他。
62+
6. 其他选项按需配置。
63+
7. 点击 `提交` 完成配置。
64+
65+
![2026-02-05-14-01-38](https://docs-cdn.flashcat.cloud/images/png/fe2879b5a85faf90935d8d65b45638d3.png)
66+
67+
### 步骤2：配置告警策略
68+
1. 登录您的 Ucloud 控制台，检索 `CloudWatch` 产品，并进入对应产品控制台。
69+
2. 在菜单中选择 `告警管理`，并转到 `告警策略` 页面。
70+
3. 新建或编辑告警策略，找到策略配置页面的**通知设置**，选择**步骤1** 创建的通知模版。
71+
4. 其他选项按需配置。
72+
5. 点击 `提交` 完成配置。
73+
74+
75+
## 严重程度映射关系
76+
---
77+
当前 Ucloud CloudWatch 告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/on-call/integration/alert-integration/alert-pipelines) 来自定义严重程度。

‎src/en.ts‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,8 @@ import Rum from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integrati
5353
import Cloudflare from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.51 Cloudflare Integration.md?raw";
5454
import WecomAlert from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.52 WecomAlert Integration.md?raw";
5555
import Harbor from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.53 Harbor Alert Integration.md?raw";
56+
import VolcEngineRTC from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.54 Volcengine RTC Integration.md?raw";
57+
import UcloudCloudWatch from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.55 Ucloud CloudWatch Integration.md?raw";
5658
/** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
5759

5860
/** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -155,6 +157,8 @@ const docs = {
155157
Cloudflare,
156158
WecomAlert,
157159
ServiceDeskPlusSync,
158-
Harbor
160+
Harbor,
161+
VolcEngineRTC,
162+
UcloudCloudWatch
159163
};
160164
export default docs;

‎src/zh.ts‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,8 @@ import Rum from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1
5353
import Cloudflare from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.51 Cloudflare 集成指引.md?raw";
5454
import WecomAlert from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.52 企微告警集成指引.md?raw";
5555
import Harbor from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.53 Harbor 告警集成指引.md?raw";
56+
import VolcEngineRTC from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.54 火山引擎 RTC 告警集成指引.md?raw";
57+
import UcloudCloudWatch from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.55 Ucloud CloudWatch 告警集成指引.md?raw";
5658
/** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
5759

5860
/** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -153,6 +155,8 @@ const docs = {
153155
Cloudflare,
154156
WecomAlert,
155157
ServiceDeskPlusSync,
156-
Harbor
158+
Harbor,
159+
VolcEngineRTC,
160+
UcloudCloudWatch
157161
};
158162
export default docs;

0 commit comments

Comments
 (0)