chore: merge main into feat/alert-batch7

api-reference/on-call.openapi.en.json

@@ -30374,13 +30374,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "link": {
@@ -30468,13 +30469,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "start_time": {

api-reference/on-call.openapi.zh.json

@@ -30374,13 +30374,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "link": {
@@ -30468,13 +30469,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "start_time": {

api-reference/openapi.en.json

@@ -1320,6 +1320,10 @@
             "description": "Alert description.",
             "type": "string"
           },
+          "detail_url": {
+            "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.",
+            "type": "string"
+          },
           "end_time": {
             "description": "Unix timestamp (seconds) when the alert recovered. 0 if still active.",
             "format": "int64",
@@ -1541,6 +1545,10 @@
             "description": "Alert description.",
             "type": "string"
           },
+          "detail_url": {
+            "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.",
+            "type": "string"
+          },
           "end_time": {
             "description": "Resolution time, Unix epoch seconds. 0 if still active.",
             "format": "int64",
@@ -4494,13 +4502,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },
@@ -4576,13 +4585,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },

api-reference/openapi.legacy.zh.json

@@ -28938,7 +28938,8 @@
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "start_time": {
@@ -29007,7 +29008,8 @@
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "description": "变更状态"
           },

api-reference/openapi.zh.json

@@ -1320,6 +1320,10 @@
             "description": "告警描述。",
             "type": "string"
           },
+          "detail_url": {
+            "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。",
+            "type": "string"
+          },
           "end_time": {
             "description": "告警恢复的 Unix 时间戳（秒），仍活跃时为 0。",
             "format": "int64",
@@ -1541,6 +1545,10 @@
             "description": "告警描述。",
             "type": "string"
           },
+          "detail_url": {
+            "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。",
+            "type": "string"
+          },
           "end_time": {
             "description": "恢复时间，Unix 时间戳（秒）。活跃时为 0。",
             "format": "int64",
@@ -4494,13 +4502,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },
@@ -4576,13 +4585,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },

docs.json

@@ -1814,7 +1814,17 @@
                   {
                     "group": "变更集成",
                     "pages": [
-                      "zh/on-call/integration/change-integration/custom-event"
+                      "zh/on-call/integration/change-integration/custom-event",
+                      "zh/on-call/integration/change-integration/github",
+                      "zh/on-call/integration/change-integration/gitlab",
+                      "zh/on-call/integration/change-integration/hcp-terraform",
+                      "zh/on-call/integration/change-integration/argocd",
+                      "zh/on-call/integration/change-integration/netlify",
+                      "zh/on-call/integration/change-integration/vercel",
+                      "zh/on-call/integration/change-integration/jfrog-artifactory",
+                      "zh/on-call/integration/change-integration/buildkite",
+                      "zh/on-call/integration/change-integration/launchdarkly",
+                      "zh/on-call/integration/change-integration/jenkins"
                     ]
                   },
                   {
@@ -3252,7 +3262,17 @@
                   {
                     "group": "Change Integration",
                     "pages": [
-                      "en/on-call/integration/change-integration/custom-event"
+                      "en/on-call/integration/change-integration/custom-event",
+                      "en/on-call/integration/change-integration/github",
+                      "en/on-call/integration/change-integration/gitlab",
+                      "en/on-call/integration/change-integration/hcp-terraform",
+                      "en/on-call/integration/change-integration/argocd",
+                      "en/on-call/integration/change-integration/netlify",
+                      "en/on-call/integration/change-integration/vercel",
+                      "en/on-call/integration/change-integration/jfrog-artifactory",
+                      "en/on-call/integration/change-integration/buildkite",
+                      "en/on-call/integration/change-integration/launchdarkly",
+                      "en/on-call/integration/change-integration/jenkins"
                     ]
                   },
                   {

en/developer/cli.mdx

@@ -842,8 +842,8 @@ The following commands support `--fields` with `json` or `toon` output. Supply c
 
 | Command | Structured output when `--fields` is omitted | Limit |
 | --- | --- | --- |
-| `flashduty incident list` | `incident_id`, `title`, `incident_severity`, `progress`, `start_time`, `channel_id` | 16 KiB |
-| `flashduty incident similar <id>` | `incident_id`, `title`, `incident_severity`, `progress`, `start_time`, `close_time`, `ack_time`, `alert_cnt`, `root_cause`, `score` | 16 KiB |
+| `flashduty incident list` | `incident_id`, `num`, `title`, `incident_severity`, `progress`, `start_time`, `channel_id`, `detail_url` | 16 KiB |
+| `flashduty incident similar <id>` | `incident_id`, `num`, `title`, `incident_severity`, `progress`, `start_time`, `close_time`, `ack_time`, `alert_cnt`, `root_cause`, `score`, `detail_url` | 16 KiB |
 | `flashduty incident detail <id>` | Returns full detail when `--fields` is omitted; otherwise returns only the selected fields | 8 KiB for projections only |
 | `flashduty alert-event list` | `event_id`, `alert_id`, `event_severity`, `event_status`, `event_time`, `title` | 16 KiB |
 | `flashduty channel escalate-rule-list <channel-id>` | `rule_id`, `rule_name`, `status`, `priority`, `filters` | 16 KiB |

en/on-call/incident/search-view-incident.mdx

@@ -277,7 +277,7 @@ The change event list displays the following information:
 
 | Column | Description |
 | :--- | :--- |
-| **Status** | Current status of the change event, including Planned, Ready, Processing, Canceled, Done |
+| **Status** | Current status of the change event, including Planned, Ready, Processing, Canceled, Done, Failed |
 | **Change Key** | Unique identifier of the change event |
 | **Title** | Brief description of the change event |
 | **Description** | Detailed information about the change event |

en/on-call/integration/alert-integration/alert-sources/argocd.mdx

@@ -148,7 +148,7 @@ kubectl exec -n argocd deploy/argocd-notifications-controller -- \
   /usr/local/bin/argocd admin notifications template notify flashduty-health <app-name> --recipient flashduty
 ```
 
-No error output means Flashduty accepted the request. When the application is `Healthy`, this is a recovery message and creates no alert; in an intermediate state such as `Progressing`, Flashduty ignores it.
+The command prints debug logs of the request and response, including the full push URL with its `integration_key`, so do not paste the output anywhere public. A `200 OK` status on the `Received response:` line means Flashduty accepted the request. When the application is `Healthy`, this is a recovery message and creates no alert; in an intermediate state such as `Progressing`, Flashduty ignores it.
 
 </Step>
 

en/on-call/integration/alert-integration/alert-sources/kentik.mdx

@@ -37,8 +37,8 @@ Creating a notification channel requires the Administrator role in Kentik; Membe
 <Steps>
 <Step title="Create a Custom Webhook notification channel">
 
-1. Log in to the Kentik Portal and go to **Settings** → **Notifications**
-2. Click **Add Notification Channel** and set **Type** to **Custom Webhook**. Do not choose the **JSON** type: Flashduty parses the output of the template below
+1. Log in to the Kentik Portal and go to **Settings** → **Notification Channels**
+2. Click **Add Notification Channel** and set **Type** to **Webhook** (listed as Custom Webhook). Do not choose the **JSON** type: Flashduty parses the output of the template below
 3. Fill in the fields as follows:
 
 | Field | Value |
@@ -47,7 +47,7 @@ Creating a notification channel requires the Administrator role in Kentik; Membe
 | **Status** | On |
 | **URL** | The full Flashduty integration push URL, including `integration_key` |
 | **Custom Headers** | Leave empty |
-| **Custom Template** | Paste the template below without renaming any field |
+| **Custom Template** | Click **Go to Notification Template Setup** and paste the template below into **TEMPLATE** on the **Template & Preview** tab, without renaming any field |
 | **Uglify JSON** | Keep the default |
 
 ```go-template
@@ -75,7 +75,7 @@ Creating a notification channel requires the Administrator role in Kentik; Membe
 }
 ```
 
-4. Click **Add Notification Channel** to save
+4. Click **Save**
 
 </Step>
 
@@ -102,6 +102,7 @@ Do not use this channel for mitigation methods or Insights notifications: these
 Flashduty uses the Kentik alert ID (`AlarmID`, shown as **Alert ID** in Kentik) as the Alert Key. Every state-change notification of one Kentik alert, from Active to Cleared, carries the same alert ID, so they merge into one alert, and the clear notification closes it.
 
 - **Alerts per key**: an alert policy raises a separate alert for each key (one set of values of the policy dimensions) that matches the conditions. Each alert has its own ID, so each is a separate Flashduty alert that recovers on its own
+- **Synthetics alerts per agent**: a Synthetics test raises a separate alert, with its own ID, for each test agent. A new failure after an alert clears gets a new alert ID and becomes a new Flashduty alert
 - Changes to the description, severity, metric values, or times do not change the Alert Key. Events without `AlarmID` are rejected
 - When one notification carries several events, each event maps to its own alert. A notification with no events is accepted but creates no alert
 
@@ -150,6 +151,6 @@ The alert title is the Kentik event description (`Description`), such as `Alarm
 - **`AlarmID is required`**: the channel is used for mitigation or Insights notifications, or the template was changed. Use the channel only for alert policies and Synthetics tests
 - **The alert does not recover**: confirm that the alert is Cleared in Kentik. For policies with **Acknowledgement Required** on, the alert must be acknowledged in Kentik before it can clear (see [Kentik threshold policy settings](https://kb.kentik.com/v1/docs/threshold-policy-settings))
 - **One policy creates several alerts**: the policy alerts on each set of dimension values separately; this is expected
-- **Test notifications**: the content of the Kentik **Test** / **Test Notification Channels** buttons is defined by Kentik. If it carries an alert ID, Flashduty handles it as a regular alert; close that alert manually in Flashduty
+- **Test notifications**: **Send Test Notification** on the **Template & Preview** tab sends mock data whose event description starts with `[TEST]`; Flashduty accepts it and creates no alert. If you first load a real alert with **Enter Alert ID**, the test carries that alert's real state, and Flashduty handles it as a real notification
 
 For field details, see [Kentik notification channels](https://kb.kentik.com/docs/notification-channel) and the [Kentik Custom Webhook templating reference](https://github.com/kentik/custom-notification-templates/blob/main/docs/TEMPLATING_REFERENCE.md).