Skip to content

Commit 2394582

Browse files
niuweiliniuweili
authored
Merge pull request #74 from flashcatcloud/f-cloudflare-dev
F cloudflare dev
2 parents d0ee526 + cfb5c24 commit 2394582

11 files changed

Lines changed: 153 additions & 11 deletions

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,5 +97,4 @@ attachment_stripped = true
9797
## Severity Mapping
9898
---
9999

100-
Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
101-
100+
Currently, all alerts pushed to Flashduty through the email integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,5 +79,4 @@ By default, the system always creates new alerts for each message, but you can s
7979
## Severity Mapping
8080
---
8181

82-
Currently, all alerts pushed to Flashduty through email integration are set to Warning severity.
83-
82+
Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).

‎flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.47 Feishu(Lark)Alert Integration.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,5 +79,4 @@ By default, the system always creates new alerts for each message, but you can s
7979
## Severity Mapping
8080
---
8181

82-
Currently, all alerts pushed to Flashduty through Feishu Alert integration are set to Warning severity.
83-
82+
Currently, all alerts pushed to Flashduty through the Feishu(lark) integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Choose this method when you need to route alerts to different channels based on
5454
### Step 1: Create Notification Object
5555
1. Login to your `Volcengine` console, find `Alert Manager` in the `Notify Object` menu
5656
2. Click `System Integration`, click `Create System Integration` or edit the existing endpoint
57-
3. 在编辑页面中，名称填写 `Flashduty` ，`回调 URL` 处填写告警集成的<span class='integration_url'>推送地址</span>。
57+
3. In the edit page, enter Flashduty as the name and fill in the <span class='integration_url'>push URL</span> for the alert integration in the URL field.
5858
5. Click `OK` to complete the configuration
5959

6060
<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/zh/fd/volcengine-1.png" />

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

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: "Cloudflare Alert Events"
3+
description: "Sync Cloudflaret 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/Cloudflare-integration-guide"
6+
---
7+
8+
Sync Cloudflare 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 **Cloudflare** 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 **Cloudflare** 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+
48+
## In Cloudflare
49+
---
50+
51+
<div class="md-block">
52+
53+
## 一、Create Notification Object
54+
1. Log in to the `Cloudflare dashboard` and select your account.
55+
2. Go to `Notifications` > `Destinations`.
56+
3. In the `Webhooks` card, select Create.
57+
4. In the edit page, enter Flashduty as the name and fill in the <span class='integration_url'>push URL</span> for the alert integration in the URL field.
58+
5. Select `Save and Test` to finish setting up your webhook.
59+
60+
After configuring the Webhook channel, you can use it in notification policies.
61+
62+
</dev>
63+
64+
## 二、Status Mapping
65+
66+
<div class="md-block">
67+
68+
Currently, all alerts pushed to Flashduty through the Cloudflare integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
69+
70+
</div>
71+

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.1 邮件 Email 集成指引.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,5 +97,5 @@ attachment_stripped = true
9797
## 严重程度映射关系
9898
---
9999

100-
当前邮件集成推送到 Flashduty 的告警等级均为Warning。
100+
当前邮件集成推送到 Flashduty 的告警等级均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
101101

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.46 钉钉告警集成指引.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,5 +79,5 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-alert-integration-guide"
7979
## 严重程度映射关系
8080
---
8181

82-
当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning。
82+
当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
8383

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.47 飞书 Lark 告警集成指引.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,5 +79,5 @@ url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
7979
## 严重程度映射关系
8080
---
8181

82-
当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning。
82+
当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
8383

‎flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.51 Cloudflare 集成指引.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: "Cloudflare 告警事件"
3+
description: "通过 webhook 的方式同步 Cloudflare 告警事件到 Flashduty，实现告警事件自动化降噪处理"
4+
date: "2024-07-05T10:00:00+08:00"
5+
url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-detect-integration-guide"
6+
---
7+
8+
通过 webhook 的方式同步 Cloudflare 告警事件到 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. 选择 **Cloudflare** 集成，点击 **保存**，生成卡片。
26+
4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
27+
28+
29+
</details>
30+
31+
### 使用共享集成
32+
33+
当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
34+
35+
<details>
36+
<summary>展开</summary>
37+
38+
1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
39+
2. 选择 **Cloudflare** 集成：
40+
- **集成名称**：为当前集成定义一个名称。
41+
3. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 `路由` 进行更多路由规则的配置）。
42+
4. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
43+
5. 完成。
44+
45+
</details>
46+
</div>
47+
48+
## 在 Cloudflare
49+
---
50+
51+
<div class="md-block">
52+
53+
## 一、告警推送配置
54+
55+
1. 登录您的 `Cloudflare` 控制台，转到 `通知` 菜单中，。
56+
2. 在`Webhooks` 中点击创建。
57+
3. 在编辑页面中，名称填写 `Flashduty` ，`URL` 处填写告警集成的<span class='integration_url'>推送地址</span>。
58+
4. 点击 `保存和测试` 完成配置。
59+
60+
配置 Webhook 通道后，即可在通知策略中使用。
61+
</dev>
62+
63+
## 二、状态对照
64+
65+
<div class="md-block">
66+
67+
当前 Cloudflare 集成推送到 Flashduty 的告警等级均为 Warning，但您可以通过[告警处理 Pipeline](https://docs.flashcat.cloud/zh/flashduty/alert-pipelines) 来自定义严重程度。
68+
69+
</div>
70+

‎src/en.ts‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@ import FeishuAlert from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts i
5050
import VolcEngineDetect from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.48 Volcengine Detect Integration.md?raw";
5151
import Monit from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.49 Monit Alert Integration.md?raw";
5252
import Rum from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.50 RUM Alert Integration.md?raw";
53+
import Cloudflare from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.51 Cloudflare Integration.md?raw";
5354
/** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
5455

5556
/** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -147,6 +148,7 @@ const docs = {
147148
Link,
148149
ServiceNowSync,
149150
Monit,
150-
Rum
151+
Rum,
152+
Cloudflare
151153
};
152154
export default docs;

0 commit comments

Comments
 (0)