Skip to content

Commit ff315d3

Browse files
authored
Merge pull request #926 from flashcatcloud/feat/alert-batch21-test2
docs: sync Kener test-button wording to test
2 parents 9d376e0 + ff0b1d2 commit ff315d3

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

  • en/on-call/integration/alert-integration/alert-sources
  • zh/on-call/integration/alert-integration/alert-sources

‎en/on-call/integration/alert-integration/alert-sources/kener.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Kener renders the template without JSON escaping. The built-in default template
7979

8080
<Step title="Verify">
8181

82-
1. Use the test button on the trigger page. Flashduty receives an Info alert titled `Kener test notification`. The test request is a fixed body built into Kener whose status is randomly `TRIGGERED` or `RESOLVED`; either way it creates only this separate Info alert, which never recovers, so close it manually in Flashduty after verifying. Flashduty recognizes the test request by `alert_incident_id` and the two threshold fields of the template above
82+
1. Use the test button on the trigger page and confirm that Kener reports the request as sent. The test request is a fixed body built into Kener (alert ID `1`, severity `WARNING`, status randomly `TRIGGERED` or `RESOLVED`), and Flashduty handles it like any other alert: `TRIGGERED` creates or updates a Warning alert with Alert Key `1`, and `RESOLVED` recovers that alert, or creates nothing when no such alert is open. If the alert is still open after verifying, close it manually in Flashduty
8383
2. Make a monitored service fail and confirm that an active alert appears in Flashduty once the failure threshold is reached
8484
3. Restore the service and confirm that the alert recovers once the success threshold is reached
8585

‎zh/on-call/integration/alert-integration/alert-sources/kener.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Kener 渲染模板时不做 JSON 转义。内置默认模板包含 `alert_messag
7979

8080
<Step title="验证">
8181

82-
1. 在触发器页面点击测试按钮,Flashduty 会收到一条标题为 `Kener test notification` 的 Info 告警。测试请求是 Kener 内置的固定内容,状态随机为 `TRIGGERED` 或 `RESOLVED`,两种都只创建这条独立的 Info 告警,不会恢复,验证后请在 Flashduty 中手动关闭。测试请求需要上面模板中的 `alert_incident_id` 和两个阈值字段才能被识别
82+
1. 在触发器页面点击测试按钮,确认 Kener 显示发送成功。测试请求是 Kener 内置的固定内容(告警 ID 为 `1`,严重程度 `WARNING`,状态随机为 `TRIGGERED` 或 `RESOLVED`),Flashduty 按普通告警处理:`TRIGGERED` 时会创建或更新 Alert Key 为 `1` 的 Warning 告警,`RESOLVED` 时会恢复这条告警,没有打开的告警时不产生新告警。验证后若该告警仍未恢复,请在 Flashduty 中手动关闭
8383
2. 让被监控的服务失败,达到失败阈值后确认 Flashduty 出现活动告警
8484
3. 服务恢复并达到成功阈值后,确认该告警自动恢复
8585

0 commit comments

Comments
 (0)