chore: merge main into feat/alert-batch6

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

@@ -1825,7 +1825,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"
                     ]
                   },
                   {
@@ -3274,7 +3284,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/cfengine.mdx

@@ -60,16 +60,16 @@ The script does not parse the parameter file. It sends every `KEY='VALUE'` line
 <Step title="Upload the script">
 
 1. Log in to Mission Portal, click **Settings** in the top right, and open **Custom notification scripts**
-2. Click **Add script**, upload `flashduty_custom_action.sh`, and enter a name (for example `Flashduty`) and a description
+2. Click **Add a script**, upload `flashduty_custom_action.sh`, and enter a name (for example `Flashduty`) and a description
 3. Click **Save**
 
 </Step>
 
 <Step title="Associate the script with alerts">
 
-On the **Dashboard**, create an alert or edit an existing one, select the `Flashduty` script uploaded in the previous step in the notification settings, and save. One script can be associated with many alerts; associate it with every alert that should reach Flashduty.
+On the **Dashboard**, create an alert or edit an existing one, tick **Custom action** in the notification settings, tick the `Flashduty` script uploaded in the previous step, and save. One script can be associated with many alerts; associate it with every alert that should reach Flashduty.
 
-To keep notifying while an alert stays triggered, choose a reminder interval in the alert's **Remind me** setting. Reminders also run the script, and Flashduty merges them into the existing alert.
+To keep notifying while an alert stays triggered, choose a reminder interval after ticking **Set reminders** in the alert. Reminders also run the script, and Flashduty merges them into the existing alert.
 
 </Step>
 

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

@@ -54,7 +54,9 @@ One integration can follow several status pages. Alerts from different pages are
 
 <Step title="Verify">
 
-Instatus has no button that sends a test notification. To verify:
+Saving the subscriber sends a validation delivery right away (the **RUN** button next to the Webhook URL field sends another). Flashduty recognizes it and answers with success, no alert.
+
+To verify with a real incident instead:
 
 1. In Instatus, go to **Incidents** and click **Add incident**. Set the status to **Investigating**, select an affected component, set it to **Major outage**, then save and notify subscribers. Flashduty shows an incident alert and a component alert, both Critical
 2. Add an update to that incident with the status **Resolved**, set the component back to **Operational**, and notify subscribers. Both alerts recover
@@ -79,7 +81,8 @@ Instatus sends one JSON payload each time an incident is added or updated, a com
 | `incident.id` | Incident ID | Alert Key, label `incident_id` |
 | `incident.name` | Incident name | Alert title |
 | `incident.status` | Incident status | Alert status, label `incident_status` |
-| `incident.impact` | Incident impact | Alert severity, label `impact` |
+| `incident.impact` | Incident impact | Label `impact`, informational only: on an incident created through the Instatus dashboard this carries the same word as `status` (e.g. `Investigating`), not an outage severity |
+| `incident.affected_components[].status` | Status of each affected component | Alert severity — the worst one across all affected components; used as a fallback only when there are none |
 | `incident.url` | Incident link | Label `incident_url` |
 | `incident.incident_updates` | Incident updates | The body of the latest update is the alert description, truncated above 8 KB |
 
@@ -122,15 +125,17 @@ Renaming an incident or component, or changing the impact, does not change the A
 
 **Instatus incidents**
 
-The alert severity comes from the impact (`impact`, which takes the same values as component status), and the alert status from the incident status (`status`):
+The alert severity is the worst status across the incident's `affected_components` (same values as component status, only differently cased and spaced, e.g. `Major outage`), and the alert status comes from the incident status (`status`):
 
-| Instatus `impact` | Flashduty severity |
+| Instatus `affected_components[].status` | Flashduty severity |
 | :--- | :--- |
-| `MAJOROUTAGE` | Critical |
-| `PARTIALOUTAGE` | Warning |
-| `DEGRADEDPERFORMANCE`, `OPERATIONAL` | Info |
+| `Major outage` | Critical |
+| `Partial outage` | Warning |
+| `Degraded performance`, `Operational` | Info |
 | Empty or any other value | Warning |
 
+An incident with no affected component falls back to the same mapping applied to `impact` instead — but on a dashboard-created incident, `impact` is usually just the `status` wording (e.g. `Investigating`), which matches none of these values and lands on Warning.
+
 | Instatus `status` | Flashduty status |
 | :--- | :--- |
 | `INVESTIGATING`, `IDENTIFIED`, `MONITORING` | Trigger or update the alert |