diff --git a/en/ai-sre/agents.mdx b/en/ai-sre/agents.mdx index 8c8c612d..ef88b567 100644 --- a/en/ai-sre/agents.mdx +++ b/en/ai-sre/agents.mdx @@ -20,7 +20,7 @@ sidebarTitle: Agent Delegation doesn't make you wait. After AI SRE delegates a task to a remote agent, the conversation continues immediately. You can keep working or delegate several tasks at once. When the remote agent finishes, its result appears in the conversation as a new message. -Each A2A delegation appears in the conversation stream as one line: a robot icon, "Dispatched" plus the remote agent name, and the task intent. On the right it shows the run status and usage metrics such as tool call count, tokens, and elapsed time. The run status is one of: initializing, in progress, awaiting input, awaiting authorization, completed, failed (including orphaned), interrupted, or killed. Click the line to view the full delegation trace in the right-hand panel; the `A2A` badge sits in that panel's title, not on the line. +Each A2A delegation appears in the conversation stream as one line: a robot icon, "Dispatched" plus the remote agent name, and the task intent. On the right it shows the run status and usage metrics such as tool call count, tokens, and elapsed time. The run status is one of: initializing, in progress, awaiting input, awaiting authorization, completed, failed (including orphaned), interrupted, or killed. Click the line to view the full delegation trace in the right-hand panel; the `A2A` badge sits in that panel's title, not on the line. A delegation running on a BYOC Runner survives a dropped connection or an AI SRE instance restart (another instance takes it over), while a delegation on a cloud environment ends with its instance — so the interrupted and failed (including orphaned) statuses mostly appear on cloud environments. **The instructions decide whether AI SRE picks this agent.** Before delegating, AI SRE sees only one `name: summary` line per agent and uses it to decide. The summary comes from the `summary:` line at the top of the instructions. The body is delivered in full only on the first delegation, so it can be long and detailed. See [Writing Instructions](#writing-instructions). diff --git a/en/ai-sre/artifacts.mdx b/en/ai-sre/artifacts.mdx index 3179ed85..8c7d045f 100644 --- a/en/ai-sre/artifacts.mdx +++ b/en/ai-sre/artifacts.mdx @@ -37,8 +37,8 @@ Entry point: **AI SRE → Artifacts** in the left navigation. | Form | What you see | |---|---| | Multi-file page | One HTML page can bundle its styles, scripts, and images and is shown as-is on the artifact detail page. A single publish allows up to 255 files (including the entry page) and 64 MiB in total. A page, text, data, or code file can be up to 16 MiB each; images, video, audio, PDF, and archives up to 15 MiB each | -| Canvas | Several pages laid out on one canvas that you can pan and zoom (2%–400%); select a board to view it full window. Suited to reviewing several interface designs side by side | -| Slides | Each page is a fixed 1920×1080. Turn pages with the arrow keys or Space, and select **Present** for full screen | +| Canvas | Several pages laid out on one canvas that you can pan and zoom (2%–400%); select a board to view it full window, where ←/→ or the **Previous** / **Next** buttons step through every board in the canvas and Esc or **Close** exits. Suited to reviewing several interface designs side by side | +| Slides | Each page is a fixed 1920×1080. Turn pages with the arrow keys, PageUp / PageDown, Home / End, or Space (Shift + Space goes back), and swipe left or right on a touch screen; select **Present** for full screen, where clicking the left or right half of the screen turns the page and the page number shows at the bottom | | Table | `.csv` / `.tsv` files display as a table with a fixed header row. Up to 1000 rows and 200 columns are shown, within 20000 cells in total, so a wide table shows fewer rows | | Video & audio | `.mp4` `.webm` `.mov` and `.mp3` `.m4a` `.wav` play in the browser's built-in player | @@ -56,7 +56,7 @@ You can't upload files to the artifact gallery directly. The agent produces and - **Paging**: 12 / 24 / 48 per page, 24 by default. - **Shareable URL**: the page URL keeps the scope, search term, sorting, and page. Copy it to share or bookmark the filtered list. When you return from a detail page, you land where you were. -Each card shows a content thumbnail, a type icon, the title, the edited time, and the scope. It also shows whether a public link is on and whether the artifact is pinned. The thumbnail is a static preview for HTML, Markdown, images, and plain text, and an empty frame for PDFs and other types. Hover over the edited time to see the exact time. +Each card shows a content thumbnail, a type icon, the title, the edited time, and the scope. It also shows whether a public link is on and whether the artifact is pinned. The thumbnail is a static preview for HTML, Markdown, images, plain text, tables (the header and first few rows), video (the first frame), and canvases / slide decks (their first board or first slide); only PDFs and audio show an empty frame. Hover over the edited time to see the exact time. ### Pinning @@ -133,10 +133,6 @@ Visitors see a read-only page marked "Content is user-generated and unverified." | Update snapshot | Appears only when the artifact's content has changed since the snapshot was taken (an "Artifact content has changed — update the snapshot to sync the latest content" notice). Clicking it overwrites the snapshot with the latest content; **the link itself stays the same** | | Revoke public link | Turns off public access; the link stops working immediately | - -Artifacts larger than **16 MiB** can't generate a public link — you'll see a notice that the artifact exceeds the size limit. You can still share it using "Account only" mode. - - ## Update a published artifact Publishing the same file again does **not** silently overwrite a published artifact. When the agent updates an artifact, it names the artifact and the version it is based on. If someone changed the artifact in the meantime, the agent reads the current content and merges before retrying, instead of overwriting it. The link and artifact ID stay the same after an update. diff --git a/en/ai-sre/automations.mdx b/en/ai-sre/automations.mdx index d1202be8..0ae6315f 100644 --- a/en/ai-sre/automations.mdx +++ b/en/ai-sre/automations.mdx @@ -222,7 +222,7 @@ In that analysis's chat, a merge appears as one process line: `Joined this analy Two platform limits are fixed and not configurable: - **One analysis takes in at most 20 incidents.** Once it is full it stops receiving similar incidents, and later ones start a new run, which carries on absorbing. -- **A finished run can only be joined within 10 minutes of finishing.** A run still `running` or `retrying` is always joinable. A run that finished well (`succeeded` / `partial`) stays joinable for 10 minutes after it completed, and after that a similar incident starts a new run. Failed, skipped, and abandoned runs are never joined. +- **A finished run can only be joined within 60 minutes of finishing.** A run still `running` or `retrying` is always joinable. A run that finished well (`succeeded` / `partial`) stays joinable for 60 minutes after it completed, and after that a similar incident starts a new run. Failed, skipped, and abandoned runs are never joined. The similarity comparison requires the account's AIOps capability and a Pro or higher subscription. If AIOps is off or the edition doesn't qualify, no comparison runs, and every incident starts its own run. diff --git a/en/ai-sre/environments.mdx b/en/ai-sre/environments.mdx index 15911913..88d5141a 100644 --- a/en/ai-sre/environments.mdx +++ b/en/ai-sre/environments.mdx @@ -420,7 +420,7 @@ When troubleshooting Runner issues, start with the **Status** and **Last heartbe - Offline means the Runner connected before, but AI SRE has not received a heartbeat for about 90 seconds. Check whether the systemd service or process is running, whether the machine is sleeping or offline, and whether outbound traffic to AI SRE is blocked by a firewall. After process and network recovery, the Runner reconnects automatically. + Offline means the Runner connected before, but AI SRE has not received a heartbeat for about 90 seconds. Check whether the systemd service or process is running, whether the machine is sleeping or offline, and whether outbound traffic to AI SRE is blocked by a firewall. After process and network recovery, the Runner reconnects automatically; any A2A delegation still in progress then carries on (the Runner retains and replays what it has already produced) rather than failing or rerunning the whole round. Pending means this Environment has never connected successfully. Confirm that the install command completed, the Token belongs to this Environment, and the `URL` is reachable from the target machine. If you configured permissions, also confirm that the file exists and the YAML parses. diff --git a/en/ai-sre/sessions.mdx b/en/ai-sre/sessions.mdx index 57027fa4..bd25fe01 100644 --- a/en/ai-sre/sessions.mdx +++ b/en/ai-sre/sessions.mdx @@ -216,6 +216,8 @@ Click a file the agent produced to preview it on the right: | Code | Syntax highlighting and line numbers | | Markdown / HTML | Rendered view, with a **Source** toggle | | Images, PDF | Shown directly | +| Table (`.csv` / `.tsv`) | Shown as a table with a fixed header row. Up to 1000 rows and 200 columns are shown, within 20000 cells in total, so a wide table shows fewer rows | +| Video & audio (`.mp4` `.webm` `.mov` / `.mp3` `.m4a` `.wav`) | Play in the browser's built-in player; if a file can't be played, you're asked to download it | | Skill package (`.skill`) | File tree and contents; download it or **Save Skill** to your account | Previews support **Copy** and **Download**. All artifacts can also be managed on the **Artifacts** page in the left navigation — see Artifacts. diff --git a/en/on-call/channel/create-edit.mdx b/en/on-call/channel/create-edit.mdx index 9b8ed0d3..7851230a 100644 --- a/en/on-call/channel/create-edit.mdx +++ b/en/on-call/channel/create-edit.mdx @@ -124,7 +124,7 @@ Configure rules in **Configuration** → **Integrate Data** → **Drop Rules** t - Click **Add Drop Rule**. + Click **New rule** in the upper-right corner of the page. The drop rule list is a table: click any row to expand it and view that rule's drop conditions, and columns such as **Last modified** can be shown or hidden from the **View** menu. Enter a **Rule Name** (required) and **Description** (optional). diff --git a/en/on-call/channel/escalation-rule.mdx b/en/on-call/channel/escalation-rule.mdx index be1d0c65..5cc2adfc 100644 --- a/en/on-call/channel/escalation-rule.mdx +++ b/en/on-call/channel/escalation-rule.mdx @@ -9,7 +9,7 @@ Escalation rules determine **when**, **through which channels**, **to whom**, an An escalation rule contains six core elements. The system matches rules from top to bottom, **stopping after the first successful match**. -You can enable or disable individual escalation rules. Flashduty skips disabled rules during matching, so they trigger no notifications. You can also copy an escalation rule to the current channel or another channel to quickly reuse existing configurations; see [Copy an Escalation Rule](#copy-an-escalation-rule). +You can enable or disable individual escalation rules. Flashduty skips disabled rules during matching, so they trigger no notifications. You can also copy an escalation rule to the current channel or another channel to quickly reuse existing configurations; see [Copy an Escalation Rule](#copy-an-escalation-rule). **Edit**, **Copy**, **Enable**/**Disable**, and **Delete** all live in the **More actions** (⋯) menu at the end of each row: an enabled rule offers **Disable**, and only after it is disabled does the menu offer **Enable** and **Delete**. **Disable** and **Delete** both ask you to confirm first. ### 1. Trigger conditions @@ -22,6 +22,8 @@ Determines which incidents trigger the current rule. - **Specific Time Period**: for example, only active on weekdays (Monday-Friday 9:00-18:00) - **Service Calendar**: Reference a predefined [Service Calendar](/en/on-call/configuration/service-calendar), for example, only active on "Trading Days", automatically excluding holidays +The status dot before each rule name in the list shows whether that rule is participating in matching right now: green **Enabled**, gray **Disabled**, and yellow **Outside active hours**. Yellow means the rule itself is enabled but currently falls outside its effective time, so it is skipped for now; it turns green again automatically once the effective time begins, and you don't need to enable it manually. + **Incident Filter**: Controls which incidents the rule matches. - **Off (Default)**: All incidents may match this rule @@ -136,7 +138,7 @@ The minimum escalation timeout is 1 minute. ## Copy an escalation rule -Click the **Copy** icon on an escalation rule card to set the new rule's name, target channel and description: +In the escalation rule list, click the **More actions** (⋯) icon at the end of a row and select **Copy** to set the new rule's name, target channel and description: | Field | Description | | :--- | :--- | diff --git a/en/on-call/channel/noise-reduction.mdx b/en/on-call/channel/noise-reduction.mdx index fb033b14..489915b7 100644 --- a/en/on-call/channel/noise-reduction.mdx +++ b/en/on-call/channel/noise-reduction.mdx @@ -348,7 +348,7 @@ When you create a quick silence, the drawer lists the labels Flashduty excluded ### Copy a silence rule -Click the **Copy** icon on a silence rule card (not available for rules created by **Quick Silence**) to set the new rule's name, description and target channel: +Silence rules are listed in a table; click a row to expand it and see the rule's details. In that list, open **More actions** (⋯) on the target rule and choose **Copy** (not offered for rules created by **Quick Silence**) to set the new rule's name, description and target channel: | Configuration | Description | | :--- | :--- | diff --git a/en/on-call/integration/alert-integration/routing-rules.mdx b/en/on-call/integration/alert-integration/routing-rules.mdx index 81365612..c4176b93 100644 --- a/en/on-call/integration/alert-integration/routing-rules.mdx +++ b/en/on-call/integration/alert-integration/routing-rules.mdx @@ -36,7 +36,7 @@ For the complete syntax and examples, see [Configure filter conditions](/en/on-c | Mode | Description | Use Case | | :--- | :--- | :--- | | **Standard Routing** | Manually select target channel | Alert-to-channel mapping is fixed | -| **Name Mapping** | Map specified label value to channel name, auto-deliver | Alerts already carry business identifier and channel name matches label value | +| **Name Mapping** | Map specified label value to channel name, auto-deliver; separate multiple names in the label value with commas | Alerts already carry business identifier and channel name matches label value | When using name mapping mode, if corresponding channel doesn't exist, delivers to default route or discards. @@ -111,6 +111,8 @@ You can perform the following actions: **Result**: Alerts with `Labels.team=payment` auto-deliver to channel named `payment`. +**Multiple channels**: You can separate multiple channel names in the label value with commas; empty and duplicate items are ignored. For example, alerts with `Labels.team=payment,order` deliver to both the `payment` and `order` channels. At most 100 names are resolved in a single lookup, and names beyond that are treated as unmatched. + Name mapping mode @@ -137,7 +139,7 @@ Confirm reported alerts can hit configured routing rules. We recommend configuri -No. The default route is independent of flow control: it only takes effect when no rule actually delivers the alert to any channel. As long as a matched rule delivers the alert to at least one channel (whether flow control is set to 'Continue' or 'Stop'), the default route will not be triggered. Note that if a name mapping rule matches but the mapped channel does not exist (so nothing is actually delivered), the default route will still be triggered. +No. The default route is independent of flow control: it only takes effect when no rule actually delivers the alert to any channel. As long as a matched rule delivers the alert to at least one channel (whether flow control is set to 'Continue' or 'Stop'), the default route will not be triggered. There are two exceptions: if a name mapping rule matches but the mapped channel does not exist (so nothing is actually delivered), the default route will still be triggered; and if the label value of a name mapping rule lists multiple channel names and some of them have no matching channel (or more than 100 names are truncated), the default route is delivered alongside the channels that rule already matched. diff --git a/en/on-call/statuspage/subscriptions.mdx b/en/on-call/statuspage/subscriptions.mdx index a90cb63c..b064b63b 100644 --- a/en/on-call/statuspage/subscriptions.mdx +++ b/en/on-call/statuspage/subscriptions.mdx @@ -38,7 +38,7 @@ When a visitor enters an email address on a public status page, the system sends -If the visitor changes their subscription scope before confirming, the system updates the pending subscription content without sending a new confirmation email. +When a pending subscription already exists for the same email address, submitting the form again neither changes the scope awaiting confirmation nor sends another confirmation email — the scope chosen on the first submission is what takes effect. To change it, resubmit after the confirmation email expires (5 minutes). A confirmed subscriber who changes scope must resubmit the form and click the link in the new confirmation email: their existing subscription stays as it is until they confirm, and the new scope replaces it once confirmed. Alternatively, they can use the manage token in any notification email to update it directly. ### IM subscription (internal status pages) diff --git a/en/platform/permission-design.mdx b/en/platform/permission-design.mdx index fa20a080..64fd2f3a 100644 --- a/en/platform/permission-design.mdx +++ b/en/platform/permission-design.mdx @@ -182,8 +182,9 @@ In addition to preset roles, you can create custom roles for more granular permi - System preset roles (Admin, Responder, Viewer) cannot be modified or deleted - Custom roles support editing, copying, enabling/disabling, and deletion +- Disabling a custom role revokes what it granted immediately: both API authorization and the visibility of buttons and menus in the console stop granting it. The role's member bindings are kept, so re-enabling it restores its permissions - You can't delete a custom role that any saved SSO configuration (SAML2.0 / OIDC / CAS) uses as its **default role**. Force delete doesn't help, because it only removes member bindings. First deselect it as the default role in that SSO configuration. This applies even when SSO or role sync is off -- A member can hold multiple roles simultaneously; their effective permissions are the union of all assigned roles +- A member can hold multiple roles simultaneously; their effective permissions are the union of the permissions of all their **enabled** roles - When you [invite a member through the Open API](/en/api-reference/platform/members/member-invite) or SSO creates a member automatically without a role, the member gets **Viewer** by default diff --git a/zh/ai-sre/agents.mdx b/zh/ai-sre/agents.mdx index f5f70565..d83e5e2f 100644 --- a/zh/ai-sre/agents.mdx +++ b/zh/ai-sre/agents.mdx @@ -20,7 +20,7 @@ sidebarTitle: Agent 委派后无需等待：AI SRE 把任务交给远端 Agent 后会立即继续当前对话，您可以继续工作或同时委派多个任务；远端完成后，其结果作为一条新消息出现在对话中。 -每次 A2A 委派在对话流里以一行呈现：机器人图标 + “已派发〈远端 Agent 名〉”文案 + 本次任务意图，右侧显示运行状态（初始化 / 进行中 / 等待输入 / 等待授权 / 完成 / 失败（含孤儿任务）/ 中断 / 已终止）以及工具调用数、Token、耗时等用量；点击这一行可在右侧面板里查看该次委派的完整过程，`A2A` 徽标标在该面板标题上，不在对话流这一行上。 +每次 A2A 委派在对话流里以一行呈现：机器人图标 + “已派发〈远端 Agent 名〉”文案 + 本次任务意图，右侧显示运行状态（初始化 / 进行中 / 等待输入 / 等待授权 / 完成 / 失败（含孤儿任务）/ 中断 / 已终止）以及工具调用数、Token、耗时等用量；点击这一行可在右侧面板里查看该次委派的完整过程，`A2A` 徽标标在该面板标题上，不在对话流这一行上。在 BYOC Runner 上执行的委派遇到连接中断或 AI SRE 实例重启也会接着跑（由另一实例接管），只有云端环境上的委派随实例一起中断，因此「中断」与「失败（含孤儿任务）」主要出现在云端环境。 **调用说明决定 AI SRE 会不会选中这个 Agent。** 委派前，AI SRE 只看到清单里的一行 `名称：简介`（简介取自调用说明开头的 `summary:`），据此判断要不要派给它；正文只在首次委派时完整送达，可以写长写细。写法见[调用说明的写法](#调用说明的写法)。 diff --git a/zh/ai-sre/artifacts.mdx b/zh/ai-sre/artifacts.mdx index 29abaae8..2b545d90 100644 --- a/zh/ai-sre/artifacts.mdx +++ b/zh/ai-sre/artifacts.mdx @@ -37,8 +37,8 @@ sidebarTitle: 产物 | 形态 | 您看到的效果 | |---|---| | 多文件网页 | 一个 HTML 页面可带样式、脚本和图片，在产物详情页里按原样展示。单次发布最多 255 个文件（含入口页），总大小不超过 64 MiB；单个页面、文本、数据或代码文件不超过 16 MiB，图片、视频、音频、PDF 和压缩包每个不超过 15 MiB | -| 画布 | 多个页面平铺在一张画布上，可拖动、缩放（2%–400%），点击某个画板全屏查看。适合并排评审多个界面设计 | -| 幻灯片 | 每页固定 1920×1080，用方向键或空格翻页，点击 **全屏演示** 进入演示 | +| 画布 | 多个页面平铺在一张画布上，可拖动、缩放（2%–400%），点击某个画板全屏查看；全屏后可用 ←/→ 键或 **上一个** / **下一个** 按钮逐个浏览画布里的所有画板，按 Esc 或 **关闭** 退出。适合并排评审多个界面设计 | +| 幻灯片 | 每页固定 1920×1080，用方向键、PageUp / PageDown、Home / End 或空格翻页（Shift + 空格回上一页），触摸左右滑动也可翻页；点击 **全屏演示** 进入演示，演示时点击画面左半或右半区翻页，底部显示页码 | | 表格 | `.csv` / `.tsv` 以表格显示，表头固定。最多显示 1000 行、200 列，且总计不超过 20000 个单元格，列多时显示的行数相应减少 | | 视频与音频 | `.mp4` `.webm` `.mov` 和 `.mp3` `.m4a` `.wav` 用浏览器自带播放器播放 | @@ -56,7 +56,7 @@ sidebarTitle: 产物 - **分页**：每页 12 / 24 / 48 条，默认 24 条。 - **地址可分享**：范围、搜索词、排序和页码都记录在页面地址中，复制地址即可分享或收藏筛选后的列表；从详情页返回时也会回到原来的位置。 -卡片展示内容缩略图（HTML、Markdown、图片和纯文本有静态预览，PDF 等显示空框）、类型图标、标题、编辑时间（悬停可看精确时刻）、作用域，以及是否已开启公开链接、是否已置顶。 +卡片展示内容缩略图（HTML、Markdown、图片、纯文本、表格、视频和画布 / 幻灯片有静态预览：表格显示表头与前几行，视频显示首帧，画布与幻灯片显示第一个画板或第一张幻灯片；PDF 与音频显示空框）、类型图标、标题、编辑时间（悬停可看精确时刻）、作用域，以及是否已开启公开链接、是否已置顶。 ### 置顶 @@ -133,10 +133,6 @@ sidebarTitle: 产物 | 更新快照 | 仅当检测到产物内容已更新时出现（提示“识别到产物内容有更新，可更新快照以同步最新内容”）。点击后用最新内容覆盖快照，**链接保持不变** | | 撤销公开链接 | 关闭公开访问，链接立即失效 | - -超过 **16 MiB** 的产物无法生成公开链接，会提示该产物体积超限。此时仍可使用“仅账户内”模式分享。 - - ## 更新已发布产物 再次发布同一个文件**不会**静默覆盖已发布的产物。Agent 更新产物时会指明要更新哪个产物及其基于的版本；如果产物在此期间被别人改过，Agent 会先读取当前内容、合并后再重试，而不是直接覆盖。更新后产物链接与 ID 不变。 diff --git a/zh/ai-sre/automations.mdx b/zh/ai-sre/automations.mdx index cfcc3f07..288826ec 100644 --- a/zh/ai-sre/automations.mdx +++ b/zh/ai-sre/automations.mdx @@ -220,7 +220,7 @@ curl -X POST 'https://<触发地址>' \ 两条平台限制是固定的，不可配置： - **一次分析最多并入 20 个故障**。达到上限的那次分析不再接收相似故障，后来的相似故障另起一次运行，由新运行继续接收并入。 -- **已结束的运行只在结束后 10 分钟内可被并入**。仍在运行（`running` / `retrying`）的运行随时可被并入；成功或部分成功结束（`succeeded` / `partial`）的运行在结束后 10 分钟内仍可被并入，此后到达的相似故障另起一次运行。失败、跳过、放弃的运行不再被并入。 +- **已结束的运行只在结束后 60 分钟内可被并入**。仍在运行（`running` / `retrying`）的运行随时可被并入；成功或部分成功结束（`succeeded` / `partial`）的运行在结束后 60 分钟内仍可被并入，此后到达的相似故障另起一次运行。失败、跳过、放弃的运行不再被并入。 相似度比较依赖账户的 AIOps 能力与专业版及以上订阅：平台关闭 AIOps、或账户版本不满足时，比较不会执行，每个故障各自拉起一次运行。 diff --git a/zh/ai-sre/environments.mdx b/zh/ai-sre/environments.mdx index a17195ee..e811c9fe 100644 --- a/zh/ai-sre/environments.mdx +++ b/zh/ai-sre/environments.mdx @@ -420,7 +420,7 @@ permission: - 离线说明 Runner 曾连接过，但 AI SRE 在约 90 秒内没有收到心跳。请检查 systemd 服务或进程是否在运行、机器是否休眠或断网、到 AI SRE 的出网是否被防火墙阻断。恢复进程和网络后，Runner 会自动重连。 + 离线说明 Runner 曾连接过，但 AI SRE 在约 90 秒内没有收到心跳。请检查 systemd 服务或进程是否在运行、机器是否休眠或断网、到 AI SRE 的出网是否被防火墙阻断。恢复进程和网络后，Runner 会自动重连；重连后，此前正在进行中的 A2A 委派会接着跑（Runner 保留并重放已产出的内容），不会整轮失败或重跑。 等待中说明这个环境从未成功连接过。请确认安装命令完整执行、Token 属于这个环境、`URL` 从目标机器可达。如果使用了权限配置，也要确认配置文件存在且 YAML 可解析。 diff --git a/zh/ai-sre/sessions.mdx b/zh/ai-sre/sessions.mdx index 3cad6225..f2700c5f 100644 --- a/zh/ai-sre/sessions.mdx +++ b/zh/ai-sre/sessions.mdx @@ -216,6 +216,8 @@ Agent 委派子任务时，对话中会出现一行子任务引用，显示名 | 代码 | 语法高亮与行号 | | Markdown / HTML | 渲染视图，可切换 **源码** | | 图片、PDF | 直接显示 | +| 表格（`.csv` / `.tsv`） | 以表格显示，表头固定；最多显示 1000 行、200 列，且总计不超过 20000 个单元格，列多时显示的行数相应减少 | +| 视频与音频（`.mp4` `.webm` `.mov` / `.mp3` `.m4a` `.wav`） | 浏览器自带播放器，可直接播放；无法播放时提示下载后查看 | | Skill 压缩包（`.skill`） | 文件树与内容，可以下载或 **保存 Skill** 到账户 | 预览支持 **复制** 和 **下载**。所有产物也可以在左侧导航的 **产物** 页统一管理，见 产物。 diff --git a/zh/on-call/channel/create-edit.mdx b/zh/on-call/channel/create-edit.mdx index 462a41d1..7e20ff12 100644 --- a/zh/on-call/channel/create-edit.mdx +++ b/zh/on-call/channel/create-edit.mdx @@ -125,7 +125,7 @@ keywords: ["协作空间", "创建管理", "业务隔离", "团队协作", "告 - 点击 **添加排除规则**。 + 点击页面右上角的 **新增规则**。排除规则列表以表格展示，点击任意一行即可展开查看该规则的排除条件；**上次修改** 等列可在 **视图** 菜单中显示或隐藏。 输入 **规则名称**（必填）和 **描述**（可选）。 diff --git a/zh/on-call/channel/escalation-rule.mdx b/zh/on-call/channel/escalation-rule.mdx index bc164fd6..d839b808 100644 --- a/zh/on-call/channel/escalation-rule.mdx +++ b/zh/on-call/channel/escalation-rule.mdx @@ -10,7 +10,7 @@ keywords: ["分派策略", "告警分派", "升级规则", "值班通知", "多 一条分派策略包含六个核心要素，系统按从上到下的顺序匹配策略，**匹配成功后停止匹配后续策略**。 -您可以对每条分派策略进行启用或禁用操作。禁用的策略在匹配时会被跳过，不会触发通知。此外，您还可以将分派策略复制到当前协作空间或其他协作空间，快速复用已有配置，详见[复制分派策略](#复制分派策略)。 +您可以对每条分派策略进行启用或禁用操作。禁用的策略在匹配时会被跳过，不会触发通知。此外，您还可以将分派策略复制到当前协作空间或其他协作空间，快速复用已有配置，详见[复制分派策略](#复制分派策略)。**编辑**、**复制**、**启用**/**停用**、**删除** 都在列表每行末尾的 **更多操作**（⋯）菜单里：策略启用时菜单提供 **停用**，停用后才提供 **启用** 与 **删除**；**停用** 与 **删除** 都会先弹出确认框。 ### 1. 触发条件 @@ -23,6 +23,8 @@ keywords: ["分派策略", "告警分派", "升级规则", "值班通知", "多 - **特定时间段**：如仅工作日（周一至周五 9:00-18:00）生效 - **服务日历**：引用预定义的 [服务日历](/zh/on-call/configuration/service-calendar)，如仅「交易日」生效，自动排除节假日 +列表里策略名称前的状态点反映策略此刻是否参与匹配：绿色 **启用中**、灰色 **停用中**、黄色 **当前不在生效时间**。黄色表示策略本身是启用的，只是此刻落在生效时间之外、因此暂不参与匹配；进入生效时间后会自动变回绿色，无需手动启用。 + **故障筛选**：控制策略匹配哪些故障。 - **关闭（默认）**：所有故障均可能命中该策略 @@ -137,7 +139,7 @@ keywords: ["分派策略", "告警分派", "升级规则", "值班通知", "多 ## 复制分派策略 -在分派策略卡片上点击 **复制** 图标，可以设置新策略的名称、目标协作空间和描述： +在分派策略列表的某一行，点击行末尾的 **更多操作**（⋯）图标，选择 **复制**，可以设置新策略的名称、目标协作空间和描述： | 字段 | 说明 | | :--- | :--- | diff --git a/zh/on-call/channel/noise-reduction.mdx b/zh/on-call/channel/noise-reduction.mdx index 926e86b7..41612af2 100644 --- a/zh/on-call/channel/noise-reduction.mdx +++ b/zh/on-call/channel/noise-reduction.mdx @@ -349,7 +349,7 @@ keywords: ["告警降噪", "告警聚合", "静默策略", "抑制策略", "噪 ### 复制静默策略 -在静默策略卡片上点击 **复制** 图标（**快速静默** 生成的规则不支持），可以设置新规则的名称、描述和目标协作空间： +静默策略以表格列出，点击某一行可展开查看规则详情。在列表中点击目标规则右侧的 **更多操作**（⋯）→ **复制**（**快速静默** 生成的规则没有这一项），可以设置新规则的名称、描述和目标协作空间： | 配置项 | 说明 | | :--- | :--- | diff --git a/zh/on-call/integration/alert-integration/routing-rules.mdx b/zh/on-call/integration/alert-integration/routing-rules.mdx index dd1b767b..1371d1de 100644 --- a/zh/on-call/integration/alert-integration/routing-rules.mdx +++ b/zh/on-call/integration/alert-integration/routing-rules.mdx @@ -37,7 +37,7 @@ keywords: ["路由规则", "告警路由", "分发策略", "协作空间", "分 | 模式 | 说明 | 适用场景 | | :--- | :--- | :--- | | **标准路由** | 手动选择目标协作空间 | 告警与空间对应关系固定 | -| **名称映射** | 将指定标签的值映射为协作空间名称，自动投递 | 告警已携带业务标识且空间名与标签值一致 | +| **名称映射** | 将指定标签的值映射为协作空间名称，自动投递；标签值可用英文逗号分隔写多个名称 | 告警已携带业务标识且空间名与标签值一致 | 使用名称映射模式时，如对应空间不存在，则投递至默认路由或丢弃。 @@ -112,6 +112,8 @@ keywords: ["路由规则", "告警路由", "分发策略", "协作空间", "分 **效果**：`Labels.team=payment` 的告警自动投递到名为 `payment` 的协作空间。 +**多个空间**：标签值可以用英文逗号分隔写入多个协作空间名称，空项与重复项会被忽略。例如 `Labels.team=payment,order` 的告警会同时投递到名为 `payment` 和 `order` 的协作空间。单次最多解析 100 个名称，超出的名称按未匹配处理。 + 名称映射模式 @@ -138,7 +140,7 @@ keywords: ["路由规则", "告警路由", "分发策略", "协作空间", "分 -不会。默认路由与流程控制无关，仅在没有任何规则实际投递到协作空间时才生效：只要某条规则命中并实际投递了协作空间（无论流程控制选择「继续」还是「停止」），默认路由都不会再触发。需要注意，名称映射模式的规则即使命中，如果映射到的协作空间不存在、未能实际投递，默认路由仍会触发。 +不会。默认路由与流程控制无关，仅在没有任何规则实际投递到协作空间时才生效：只要某条规则命中并实际投递了协作空间（无论流程控制选择「继续」还是「停止」），默认路由都不会再触发。需要注意两种例外：名称映射模式的规则即使命中，如果映射到的协作空间不存在、未能实际投递，默认路由仍会触发；名称映射的标签值写了多个协作空间名称，而其中部分名称找不到对应协作空间（或超过 100 个名称被截断）时，默认路由会与这条规则已匹配到的协作空间一起投递。 diff --git a/zh/on-call/statuspage/subscriptions.mdx b/zh/on-call/statuspage/subscriptions.mdx index 3985182d..3333e8b3 100644 --- a/zh/on-call/statuspage/subscriptions.mdx +++ b/zh/on-call/statuspage/subscriptions.mdx @@ -38,7 +38,7 @@ Flashduty 状态页允许用户主动订阅服务状态更新。当状态页中 -如果访客在确认前修改了订阅范围，系统会更新待确认的订阅内容，不会重新发送确认邮件。 +同一邮箱已有待确认的订阅时，访客再次提交表单既不会改写这次待确认的订阅范围，也不会重新发送确认邮件——最终生效的是首次提交时选择的范围。如需修改，请等确认邮件过期（5 分钟）后重新提交。已完成确认的订阅者修改订阅范围需要重新提交表单并点击新邮件中的确认链接，确认之前原有订阅保持不变，确认后新的范围会替换原有订阅；也可以直接使用通知邮件中的管理令牌自助修改。 ### IM 订阅（内部状态页） diff --git a/zh/platform/permission-design.mdx b/zh/platform/permission-design.mdx index b2f97999..0f06085d 100644 --- a/zh/platform/permission-design.mdx +++ b/zh/platform/permission-design.mdx @@ -182,8 +182,9 @@ Flashduty 的权限点分为两类： - 系统预置角色（Admin、Responder、Viewer）不可修改或删除 - 自定义角色支持编辑、复制、启用/禁用和删除操作 +- 禁用自定义角色会立即收回它授予的权限，接口鉴权和页面按钮、菜单的可见性随之失效；角色与成员的绑定会保留，重新启用后权限恢复 - 被任一 SSO 配置（SAML2.0 / OIDC / CAS）选为**默认角色**的自定义角色不能删除，强制删除也不行（强制删除只解除成员绑定）。请先在对应的单点登录配置中取消该默认角色；即使 SSO 或角色同步已关闭，也需要先取消 -- 一个成员可以同时拥有多个角色，其权限为所有角色权限的并集 +- 一个成员可以同时拥有多个角色，其权限为所有**已启用**角色权限的并集 - 通过 [Open API 邀请新成员](/zh/api-reference/platform/members/member-invite)或 SSO 自动创建成员时未指定角色，默认授予 **Viewer**