Skip to content

docs(on-call): correct alert status mappings #331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pijiang3 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(on-call): correct alert status mappings #331

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions en/on-call/integration/alert-integration/alert-sources/guance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,12 +72,12 @@ Choose this option when you need to route alerts to different channels based on

<div class="md-block">

| Guance | Flashduty | Status |
| ---------- | -------- | ---- |
| Critical | Critical | Critical |
| Error | Warning | Warning |
| Warning | Warning | Warning |
| Info | Info | Info |
| Data Missing | Info | Info |
| Guance `df_status` | Flashduty | Status |
| --- | --- | --- |
| `critical`, `fatal` | Critical | Critical |
| `error`, `warning` | Warning | Warning |
| `info`, `nodata` | Info | Info |
| Other values | Info | Info |
| `ok` | Info | Resolved (OK) |

</div>
17 changes: 16 additions & 1 deletion en/on-call/integration/alert-integration/alert-sources/tencent-cm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,21 @@ Choose this option when you need to route alerts to different channels based on
---
<div class="md-block">

All metric alerts from Tencent Cloud Monitor correspond to "warning" severity level alerts in Flashduty.
When `alarmLevel` is present, Flashduty maps the alert severity as follows:

| Tencent Cloud Monitor `alarmLevel` | Flashduty | Status |
| --- | --- | --- |
| `Remind` | Info | Info |
| `Warn` | Warning | Warning |
| `Serious` | Critical | Critical |

When `alarmLevel` is missing or unrecognized, Flashduty uses the default severity for the alert type:

| Tencent Cloud Monitor `alarmType` | Flashduty | Status |
| --- | --- | --- |
| `metric` | Warning | Warning |
| `event`, `prometheus`, and other types | Critical | Critical |

Recovery is evaluated independently: an `event` alert is resolved (OK) when `recoverTime` is not `0`; all other alert types are resolved (OK) when `alarmStatus` is `0`.

</div>
14 changes: 7 additions & 7 deletions zh/on-call/integration/alert-integration/alert-sources/guance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,12 +76,12 @@ keywords: ["告警集成", "观测云告警事件", "监控告警", "数据接

<div className="md-block">

| 观测云 | Flashduty | 状态 |
| ---------- | -------- | ---- |
| 紧急 | Critical | 严重 |
| 重要 | Warning | 警告 |
| 警告 | Warning | 警告 |
| 信息 | Info | 提醒 |
| 数据断档 | Info | 提醒 |
| 观测云 `df_status` | Flashduty | 状态 |
| --- | --- | --- |
| `critical`、`fatal` | Critical | 严重 |
| `error`、`warning` | Warning | 警告 |
| `info`、`nodata` | Info | 提醒 |
| 其他值 | Info | 提醒 |
| `ok` | Info | 已恢复（OK） |

</div>
17 changes: 16 additions & 1 deletion zh/on-call/integration/alert-integration/alert-sources/tencent-cm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,21 @@ keywords: ["告警集成", "腾讯云监控 CM集成", "监控告警", "数据
---
<div className="md-block">

腾讯云监控所有指标告警均对应到 Flashduty “警告（warning）”级别告警。
`alarmLevel` 存在时，按以下规则映射到 Flashduty 告警级别：

| 腾讯云监控 `alarmLevel` | Flashduty | 状态 |
| --- | --- | --- |
| `Remind` | Info | 提醒 |
| `Warn` | Warning | 警告 |
| `Serious` | Critical | 严重 |

未提供或未识别 `alarmLevel` 时，使用告警类型的默认级别：

| 腾讯云监控 `alarmType` | Flashduty | 状态 |
| --- | --- | --- |
| `metric` | Warning | 警告 |
| `event`、`prometheus` 及其他类型 | Critical | 严重 |

恢复状态单独判断：`event` 类型的 `recoverTime` 不为 `0` 时映射为已恢复（OK）；其他类型的 `alarmStatus` 为 `0` 时映射为已恢复（OK）。

</div>