From 36eba3b4d8e2c54f102ea60d06a20eafc1a9b66f Mon Sep 17 00:00:00 2001 From: Flashduty AI-SRE Date: Wed, 30 Sep 2026 16:07:33 +0000 Subject: [PATCH 1/2] =?UTF-8?q?docs(api):=20daily=20audit=202026-09-30=20?= =?UTF-8?q?=E2=80=94=20alert=20detail=5Furl=20into=20the=20rendered=20on-c?= =?UTF-8?q?all=20spec,=20RUM=20issue-detail=20team=5Fid=20semantics?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two changes, both derived from the source repos at origin/main. B. on-call AlertItem / AlertInfo gain `detail_url`. fc-event structs/alert.go:74-78 — `DetailUrl string `json:"detail_url,omitempty"``, filled at read time, empty when the deployment has no console base. The consolidated specs got the field on 2026-09-29 (4b9015a4) but the per-module split files — the ones Mintlify renders — never did, so POST /alert/info documented no detail_url on the docs site. A. POST /rum/issue/info documents that `team_id` is the application's current team. fc-rum cmd/server/controller/issue/info.go:221 `item.TeamID = application.TeamID` (PR #230, merge a190844, 2026-09-29). Issue rows keep the team recorded at creation (logic/transfer.go:55), which is what list and export still report. --- api-reference/on-call.openapi.en.json | 8 ++++++++ api-reference/on-call.openapi.zh.json | 8 ++++++++ api-reference/openapi.en.json | 2 +- api-reference/openapi.zh.json | 2 +- api-reference/rum.openapi.en.json | 2 +- api-reference/rum.openapi.zh.json | 2 +- 6 files changed, 20 insertions(+), 4 deletions(-) diff --git a/api-reference/on-call.openapi.en.json b/api-reference/on-call.openapi.en.json index 53f4b9b57..e69b7b74d 100644 --- a/api-reference/on-call.openapi.en.json +++ b/api-reference/on-call.openapi.en.json @@ -18334,6 +18334,10 @@ }, "description": "Attached images." }, + "detail_url": { + "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.", + "type": "string" + }, "data_source_name": { "type": "string", "description": "Deprecated. Use `integration_name`." @@ -18516,6 +18520,10 @@ }, "description": "Images attached to the alert." }, + "detail_url": { + "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.", + "type": "string" + }, "data_source_name": { "type": "string", "description": "Deprecated: use `integration_name` instead.", diff --git a/api-reference/on-call.openapi.zh.json b/api-reference/on-call.openapi.zh.json index 6ffe7dad0..7e941b5b7 100644 --- a/api-reference/on-call.openapi.zh.json +++ b/api-reference/on-call.openapi.zh.json @@ -18334,6 +18334,10 @@ }, "description": "附加图片。" }, + "detail_url": { + "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。", + "type": "string" + }, "data_source_name": { "type": "string", "description": "已废弃，请使用 `integration_name`。" @@ -18516,6 +18520,10 @@ }, "description": "告警附加的图片。" }, + "detail_url": { + "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。", + "type": "string" + }, "data_source_name": { "type": "string", "description": "已废弃：请使用 `integration_name`。", diff --git a/api-reference/openapi.en.json b/api-reference/openapi.en.json index 5c2bdd216..a82f00f92 100644 --- a/api-reference/openapi.en.json +++ b/api-reference/openapi.en.json @@ -48845,7 +48845,7 @@ "RUM/Issues" ], "x-mint": { - "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |", + "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |\n\n## Usage\n\n- `team_id` is the owning application's **current** team; `POST /rum/issue/list` and `POST /rum/issue/export` report the team recorded when the issue was first seen, which differs once the application moves to another team.", "href": "/en/api-reference/rum/issues/rum-issue-read-info", "metadata": { "sidebarTitle": "Get issue detail" diff --git a/api-reference/openapi.zh.json b/api-reference/openapi.zh.json index afedef7f7..dc7e1eab9 100644 --- a/api-reference/openapi.zh.json +++ b/api-reference/openapi.zh.json @@ -48845,7 +48845,7 @@ "RUM/RUM 问题跟踪" ], "x-mint": { - "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |", + "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |\n\n## 使用说明\n\n- `team_id` 为所属应用**当前**的团队；`POST /rum/issue/list` 与 `POST /rum/issue/export` 返回 Issue 首次出现时记录的团队，应用转移到其他团队后两者不同。", "href": "/zh/api-reference/rum/issues/rum-issue-read-info", "metadata": { "sidebarTitle": "查看 Issue 详情" diff --git a/api-reference/rum.openapi.en.json b/api-reference/rum.openapi.en.json index 61dd9d3bb..c5cd0e90c 100644 --- a/api-reference/rum.openapi.en.json +++ b/api-reference/rum.openapi.en.json @@ -6454,7 +6454,7 @@ "RUM/Issues" ], "x-mint": { - "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |", + "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |\n\n## Usage\n\n- `team_id` is the owning application's **current** team; `POST /rum/issue/list` and `POST /rum/issue/export` report the team recorded when the issue was first seen, which differs once the application moves to another team.", "href": "/en/api-reference/rum/issues/rum-issue-read-info", "metadata": { "sidebarTitle": "Get issue detail" diff --git a/api-reference/rum.openapi.zh.json b/api-reference/rum.openapi.zh.json index 213c06766..99c4e32f0 100644 --- a/api-reference/rum.openapi.zh.json +++ b/api-reference/rum.openapi.zh.json @@ -6454,7 +6454,7 @@ "RUM/RUM 问题跟踪" ], "x-mint": { - "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |", + "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |\n\n## 使用说明\n\n- `team_id` 为所属应用**当前**的团队；`POST /rum/issue/list` 与 `POST /rum/issue/export` 返回 Issue 首次出现时记录的团队，应用转移到其他团队后两者不同。", "href": "/zh/api-reference/rum/issues/rum-issue-read-info", "metadata": { "sidebarTitle": "查看 Issue 详情" From 59229aaceadcadca2c85902ea9bdb7f2e5200846 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Mon, 5 Oct 2026 19:55:50 -0700 Subject: [PATCH 2/2] docs(api): reconcile RumIssueItem.team_id wording with the info operation's current-team semantics --- api-reference/openapi.en.json | 2 +- api-reference/openapi.zh.json | 2 +- api-reference/rum.openapi.en.json | 2 +- api-reference/rum.openapi.zh.json | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/api-reference/openapi.en.json b/api-reference/openapi.en.json index 06df8fa59..e8a1e9fa7 100644 --- a/api-reference/openapi.en.json +++ b/api-reference/openapi.en.json @@ -21147,7 +21147,7 @@ "type": "object" }, "team_id": { - "description": "ID of the team owning this issue, copied from the owning application's `team_id` at issue creation.", + "description": "ID of the team owning this issue. For `POST /rum/issue/info` this is the owning application's current `team_id`; `POST /rum/issue/list` and `POST /rum/issue/export` report the team recorded when the issue was first seen, which differs once the application moves to another team.", "format": "int64", "type": "integer" }, diff --git a/api-reference/openapi.zh.json b/api-reference/openapi.zh.json index 823cb42e3..98146c41b 100644 --- a/api-reference/openapi.zh.json +++ b/api-reference/openapi.zh.json @@ -21147,7 +21147,7 @@ "type": "object" }, "team_id": { - "description": "Issue 所属团队的 ID，创建 Issue 时取自所属应用的 `team_id`。", + "description": "Issue 所属团队的 ID。`POST /rum/issue/info` 返回所属应用当前的 `team_id`；`POST /rum/issue/list` 与 `POST /rum/issue/export` 返回 Issue 首次出现时记录的团队，应用转移到其他团队后两者不同。", "format": "int64", "type": "integer" }, diff --git a/api-reference/rum.openapi.en.json b/api-reference/rum.openapi.en.json index c5cd0e90c..dae47c66f 100644 --- a/api-reference/rum.openapi.en.json +++ b/api-reference/rum.openapi.en.json @@ -2298,7 +2298,7 @@ "type": "object" }, "team_id": { - "description": "ID of the team owning this issue, copied from the owning application's `team_id` at issue creation.", + "description": "ID of the team owning this issue. For `POST /rum/issue/info` this is the owning application's current `team_id`; `POST /rum/issue/list` and `POST /rum/issue/export` report the team recorded when the issue was first seen, which differs once the application moves to another team.", "format": "int64", "type": "integer" }, diff --git a/api-reference/rum.openapi.zh.json b/api-reference/rum.openapi.zh.json index 3d752ad00..4df9ba0b9 100644 --- a/api-reference/rum.openapi.zh.json +++ b/api-reference/rum.openapi.zh.json @@ -2298,7 +2298,7 @@ "type": "object" }, "team_id": { - "description": "Issue 所属团队的 ID，创建 Issue 时取自所属应用的 `team_id`。", + "description": "Issue 所属团队的 ID。`POST /rum/issue/info` 返回所属应用当前的 `team_id`；`POST /rum/issue/list` 与 `POST /rum/issue/export` 返回 Issue 首次出现时记录的团队，应用转移到其他团队后两者不同。", "format": "int64", "type": "integer" },