diff --git a/docs.json b/docs.json index 4f44b4f..e07475b 100644 --- a/docs.json +++ b/docs.json @@ -189,6 +189,7 @@ "zh/on-call/integration/alert-integration/alert-sources/aliyun-cm-event", "zh/on-call/integration/alert-integration/alert-sources/aliyun-cm-metrics", "zh/on-call/integration/alert-integration/alert-sources/aliyun-sls", + "zh/on-call/integration/alert-integration/alert-sources/aliyun-prometheus", "zh/on-call/integration/alert-integration/alert-sources/aws-cloudwatch", "zh/on-call/integration/alert-integration/alert-sources/aws-eventbridge", "zh/on-call/integration/alert-integration/alert-sources/tencent-cls", @@ -619,6 +620,7 @@ "en/on-call/integration/alert-integration/alert-sources/aliyun-cm-event", "en/on-call/integration/alert-integration/alert-sources/aliyun-cm-metrics", "en/on-call/integration/alert-integration/alert-sources/aliyun-sls", + "en/on-call/integration/alert-integration/alert-sources/aliyun-prometheus", "en/on-call/integration/alert-integration/alert-sources/aws-cloudwatch", "en/on-call/integration/alert-integration/alert-sources/aws-eventbridge", "en/on-call/integration/alert-integration/alert-sources/tencent-cls", diff --git a/en/on-call/integration/alert-integration/alert-sources/aliyun-prometheus.mdx b/en/on-call/integration/alert-integration/alert-sources/aliyun-prometheus.mdx new file mode 100644 index 0000000..cc18fcb --- /dev/null +++ b/en/on-call/integration/alert-integration/alert-sources/aliyun-prometheus.mdx @@ -0,0 +1,87 @@ +--- +title: "Aliyun Prometheus monitoring integration" +description: "Sync Alibaba Cloud Prometheus monitoring alert events to Flashduty On-call via webhook for automated alert noise reduction" +keywords: ["alert integration", "Aliyun Prometheus monitoring integration", "monitoring alerts", "data ingestion"] +--- + +
+ +## In Flashduty On-call +--- +You can obtain an integration push URL through either of these two methods: + +### Using private integration + +Choose this method when you don't need to route alert events to different channels — it's simpler. + + + + + 1. Go to the Flashduty console, select **Channel**, and enter a channel's details page + 2. Select the **Integrations** tab, click **Add Integration** to enter the integration page + 3. Choose **Aliyun Prometheus Monitoring** integration and click **Save** to generate a card + 4. Click the generated card to view the **Push URL**, copy it for later use + + + + +### Using shared integration + +Choose this method when you need to route alerts to different channels based on the alert event payload. + + + + + 1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page + 2. Select **Aliyun Prometheus Monitoring** integration: + - **Integration Name**: Define a name for this integration + 3. Configure the default route and select the corresponding channel (after creation, go to `Route` to configure more routing rules) + 4. Click **Save** and copy the newly generated **Push URL** for later use + + + + +
+ +## In Alibaba Cloud +--- + + + + +1. Log in to the Alibaba Cloud console, search for **Prometheus Monitoring**, and enter the corresponding console +2. In the left menu, select **Alert Management → Notification Policies**, and create or edit a notification policy +3. Add a **Webhook** type notification target and enter the integration push URL +4. Click **Confirm** to save + + + + + +1. In the left menu, select **Alert Management → Alert Rules**, and create or edit an alert rule +2. Bind the notification policy created in the previous step +3. Configure other options as needed and click **Save** + + + + + +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. + + + + +## Severity mapping +--- +
+ +Aliyun Prometheus Monitoring to Flashduty severity mapping: + +| Aliyun Prometheus Monitoring | Flashduty | Status | +| ------------ | -------- | ---- | +| CRITICAL | Critical | Critical | +| ERROR | Critical | Critical | +| WARNING | Warning | Warning | +| INFO | Info | Info | + +
diff --git a/zh/on-call/integration/alert-integration/alert-sources/aliyun-prometheus.mdx b/zh/on-call/integration/alert-integration/alert-sources/aliyun-prometheus.mdx new file mode 100644 index 0000000..43bb59e --- /dev/null +++ b/zh/on-call/integration/alert-integration/alert-sources/aliyun-prometheus.mdx @@ -0,0 +1,89 @@ +--- +title: "阿里云 Prometheus 监控集成" +description: "通过 webhook 的方式同步阿里云 Prometheus 监控告警事件到 Flashduty On-call，实现告警事件自动化降噪处理" +keywords: ["告警集成", "阿里云 Prometheus 监控集成", "监控告警", "数据接入"] +--- + +
+ +## 在 Flashduty On-call +--- +您可通过以下2种方式，获取一个集成推送地址，任选其一即可。 + +### 使用专属集成 + +当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。 + + + + + 1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面 + 2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面 + 3. 选择 **阿里云 Prometheus 监控** 集成，点击 **保存**，生成卡片。 + 4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。 + + + + + +### 使用共享集成 + +当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。 + + + + + 1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。 + 2. 选择 **阿里云 Prometheus 监控** 集成： + - **集成名称**：为当前集成定义一个名称。 + 3. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 `路由` 进行更多路由规则的配置）。 + 4. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。 + 5. 完成。 + + + + +
+ +## 在阿里云 +--- + + + + +1. 登录阿里云控制台，检索 **Prometheus 监控** 产品，进入对应控制台 +2. 在左侧菜单选择 **告警管理 → 通知策略**，创建或编辑通知策略 +3. 在通知对象中添加 **Webhook** 类型的通知对象，将集成的推送地址填入 URL 中 +4. 点击 **确认** 按钮，提交更新 + + + + + +1. 在左侧菜单选择 **告警管理 → 告警规则**，创建或编辑告警规则 +2. 在规则配置中绑定上一步创建的通知策略 +3. 其他选项按需配置，点击 **保存** 完成 + + + + + +回到 Flashduty 控制台集成列表页面，如果展示了最新事件时间，说明配置成功且收到事件。 + + + + +## 状态对照 +--- +
+ +阿里云 Prometheus 监控到 Flashduty 告警等级映射关系： + +| 阿里云 Prometheus 监控 | Flashduty | 状态 | +| ------------ | -------- | ---- | +| CRITICAL | Critical | 严重 | +| ERROR | Critical | 严重 | +| WARNING | Warning | 警告 | +| INFO | Info | 提醒 | + +