Merge pull request #13 from flashcatcloud/doc-review/2026-03-17

ysyneu · web-flow · commit cc3827cd59f5 · 2026-03-17T11:07:19.000+08:00
fix: correct on-call docs inaccuracies found by doc-review
diff --git a/en/on-call/advanced/reference-variables.mdx b/en/on-call/advanced/reference-variables.mdx
@@ -48,14 +48,18 @@ Use `[TPL]` as prefix and `${}` to reference variables. Variable content is extr
 
 ### Reference via Golang Template Syntax
 
-Use `[TPL]` as prefix and `{{}}` to reference variables (can reference both labels and attributes); if extraction fails, `<no value>` is used as a placeholder.
+Use `[TPL]` as prefix and `{{}}` to reference variables (can reference both labels and attributes); if extraction fails, returns an empty string for missing labels.
 
 | Rule | Variable Values | Generated Content |
 | --- | --- | --- |
 | `[TPL]{{.Labels.resource}} / {{.Labels.check}}` | `{"resource": "127.0.0.1", "check": "cpu idle low"}` | 127.0.0.1 / cpu idle low |
-| `[TPL]{{.Labels.resource}} / {{.Labels.check}}` | `{"resource": "127.0.0.1"}` | 127.0.0.1 / `<no value>` |
+| `[TPL]{{.Labels.resource}} / {{.Labels.check}}` | `{"resource": "127.0.0.1"}` | 127.0.0.1 /  |
 | `[TPL]{{.EventSeverity}} / Host Down` | `{"EventSeverity": "Warning"}` | Warning / Host Down |
 
+<Note>
+`${}` syntax and `{{}}` syntax behave differently when a label is missing: `${}` returns `<no value>`, while `{{}}` returns an empty string.
+</Note>
+
 #### Supported Attributes
 
 | Field | Type | Description |
diff --git a/en/on-call/analytics/insights.mdx b/en/on-call/analytics/insights.mdx
@@ -33,7 +33,7 @@ When customizing filter conditions, the system remembers your selections. Even a
 | Team | Select team names to query, supports multiple selection. Dashboard data updates based on selected teams |
 | Channel | Select channel names to query, supports multiple selection. Dashboard data updates based on selected channels |
 | Severity | Select severity levels to query, supports multiple selection. Dashboard data updates based on selected severity levels |
-| Time Range | Select time range to query. Supports this week, last two weeks, this month, last month, and custom time ranges, but only up to the last **180 days** of data |
+| Time Range | Select time range to query. Supports this week, last two weeks, this month, last month, and custom time ranges, but only up to the last **1 year** of data |
 | Data Interval | Supports day, week, and month dimensions. Defaults to hourly queries, but when time range exceeds 31 days, daily preview is not available |
 | Sorting | Team, channel, and individual dimension dashboards support ascending and descending order. Defaults to showing TOP 10 data; expand to show more |
 
@@ -124,7 +124,7 @@ Export incident list data in CSV format. Supports exporting incident list, team,
 
 <AccordionGroup>
 <Accordion title="How can I query older data?">
-Currently, insights only supports querying the last 180 days of data. For older data, use the [API Query](https://developer.flashcat.cloud/api-213441443).
+Currently, insights only supports querying the last 1 year (depending on your plan's data retention period) of data. For older data, use the [API Query](https://developer.flashcat.cloud/api-213441443).
 </Accordion>
 
 <Accordion title="Why can't I view data at daily granularity when the time range exceeds 31 days?">
diff --git a/en/on-call/channel/noise-reduction.mdx b/en/on-call/channel/noise-reduction.mdx
@@ -233,10 +233,10 @@ Quickly create temporary silence rules based on existing incidents.
 
 **Operation Path**: Incident Details → More Actions → **Quick Silence**
 
-- Rule name defaults to incident ID + title
+- Rule name defaults to "Quick Silence - #short-ID", with the incident title included in the description
 - Effective scope is the incident's channel (cannot be changed)
 - Default effective for 24 hours, automatically deleted after expiration
-- Conditions default to exact match of incident labels
+- Conditions default to severity and filtered label matching (automatically excluding numeric, overly long, and special labels)
 
 <Frame caption="Quick Silence Configuration">
   ![Quick Silence](https://docs-cdn.flashcat.cloud/images/png/e80c2632d9065b28499edfa5a81a8505.png)
diff --git a/en/on-call/configuration/custom-fields.mdx b/en/on-call/configuration/custom-fields.mdx
@@ -72,8 +72,8 @@ Click **Create Custom Field**, enter the following information:
 | Type | Description |
 | :--- | :--- |
 | **Text** | Plain text input, max 500 characters |
-| **Single-select** | Dropdown with single selection, max 10 options, each up to 200 characters |
-| **Multi-select** | Dropdown with multiple selection, max 10 options, each up to 200 characters |
+| **Single-select** | Dropdown with single selection, max 20 options, each up to 200 characters |
+| **Multi-select** | Dropdown with multiple selection, max 20 options, each up to 200 characters |
 | **Checkbox** | Checkbox toggle |
 </Step>
 <Step title="Complete Creation">
diff --git a/en/on-call/configuration/templates.mdx b/en/on-call/configuration/templates.mdx
@@ -116,10 +116,10 @@ Complete variable list for incident objects:
 <Accordion title="Assignment - Assignment Configuration">
 | Field | Type | Required | Description |
 | :--- | :--- | :---: | :--- |
-| PersonIDs | []string | | Person ID list, only exists when assigned by person |
+| PersonIDs | []int64 | | Person ID list, only exists when assigned by person |
 | EscalateRuleID | string | | Escalation rule ID |
 | EscalateRuleName | string | | Escalation rule name |
-| LayerIdx | string | | Assignment level, starts from 0 |
+| LayerIdx | int | | Assignment level, starts from 0 |
 | Type | string | ✓ | Assignment type: assign / reassign / escalate / reopen |
 </Accordion>
 
@@ -140,10 +140,9 @@ Complete variable list for incident objects:
 | Description | string | ✓ | Alert description, may be empty |
 | AlertSeverity | string | ✓ | Severity: Critical / Warning / Info |
 | AlertStatus | string | ✓ | Alert status: Critical / Warning / Info / Ok |
-| Progress | string | ✓ | Processing progress: Triggered / Processing / Closed |
 | StartTime | int64 | ✓ | Trigger time, Unix timestamp in seconds |
+| LastTime | int64 | | Latest event time, Unix timestamp in seconds |
 | EndTime | int64 | | Recovery time, Unix timestamp in seconds |
-| CloseTime | int64 | | Close time, Unix timestamp in seconds |
 | Labels | map | | Label KV |
 </Accordion>
 </AccordionGroup>
diff --git a/en/on-call/incident/handle-update-incident.mdx b/en/on-call/incident/handle-update-incident.mdx
@@ -95,7 +95,7 @@ You can view each person's assignment time and acknowledgment time in the consol
 
 ## Snooze
 
-After acknowledging an incident, responders may need time to investigate and handle it. **Snooze** can temporarily stop the incident from escalating per the expected escalation rule. After acknowledging, you can set a snooze duration like 2 hours, 4 hours, or a custom expiration time within 24 hours.
+After acknowledging an incident, responders may need time to investigate and handle it. **Snooze** can temporarily stop the incident from escalating per the expected escalation rule. After acknowledging, you can set a snooze duration such as 2 hours, 4 hours, 12 hours, or a custom expiration time within 24 hours.
 
 <Warning>
 If you've snoozed and the snooze time has passed but you still haven't resolved the incident, the system automatically reverts the incident to **Triggered** status and re-initiates assignment notifications.
diff --git a/en/on-call/incident/outlier-incidents.mdx b/en/on-call/incident/outlier-incidents.mdx
@@ -64,7 +64,7 @@ When enabled, incident lists and notification content will include an "Outlier"
 
 <AccordionGroup>
 <Accordion title="Does outlier incident detection need to be enabled separately?">
-No setup or enabling needed. By default, all Professional subscription and above versions trigger outlier incident detection.
+Enabled by default for Pro and above plans, but can be disabled in the channel's basic settings. See the "Enable and disable" section above.
 </Accordion>
 </AccordionGroup>
 
diff --git a/en/on-call/integration/alert-integration/alert-pipelines.mdx b/en/on-call/integration/alert-integration/alert-pipelines.mdx
@@ -105,7 +105,7 @@ When rewriting titles or descriptions, you can use Go Template syntax to referen
 | `[TPL]{{.Labels.xxx}}` | Reference specific label | `[TPL]{{.Labels.host}}` |
 | `[TPL]{{.Title}}` | Reference current title | `[TPL][Forwarded] {{.Title}}` |
 | `[TPL]{{.Description}}` | Reference current description | `[TPL]Details: {{.Description}}` |
-| `[TPL]{{.Severity}}` | Reference current severity | `[TPL]Current Level: {{.Severity}}` |
+| `[TPL]{{.EventSeverity}}` | Reference current severity | `[TPL]Current Level: {{.EventSeverity}}` |
 
 <Tip>
 Before configuring Pipeline, we recommend observing raw alert data for a period to identify which fields (Labels) are stable and which need cleansing.
diff --git a/en/on-call/integration/alert-integration/label-enhancement.mdx b/en/on-call/integration/alert-integration/label-enhancement.mdx
@@ -179,8 +179,8 @@ Prepare a CSV format mapping table file to map resource type IDs in alerts to ac
 | Description | Service purpose description | Query asset info by host IP |
 | Request URL | API request address | `https://mapping-api.example.com/v1/enrich-event` |
 | Headers | HTTP request header configuration | `X-Auth-Token: your-token` |
-| Timeout | Request timeout in seconds | 1 |
-| Retry Count | Number of retries after failure | 1 |
+| Timeout | Request timeout, 1-3 seconds, default 2 seconds | 1 |
+| Retry Count | Retry count on failure, 0-1 times, default 0 times | 1 |
 
 <Tip>
 If the API uses HTTPS with an untrusted certificate, you can enable the `Skip Certificate Verification` option.
@@ -244,7 +244,6 @@ Flashduty will call your API via `POST` method with the following request body:
     "description": "CPU usage for instance '10.0.1.1:9100' is over 95%",
     "title": "High CPU Usage on instance 10.0.1.1:9100",
     "alert_key": "d41d8cd98f00b204e9800998ecf8427e",
-    "alert_id": "62d6c0f6b8f1b2b3c4d5e6f7",
     "event_severity": "Critical",
     "event_status": "Critical",
     "event_time": 1678886400,
diff --git a/en/on-call/integration/alert-integration/routing-rules.mdx b/en/on-call/integration/alert-integration/routing-rules.mdx
@@ -118,7 +118,7 @@ Confirm reported alerts can hit configured routing rules. We recommend configuri
 </Accordion>
 
 <Accordion title="When flow control is set to 'Stop', will default route still match?">
-Yes. Default route is a fallback rule not subject to flow control restrictions.
+No. The default route only takes effect when no routing rules match the alert. If any rule has already matched (regardless of whether flow control is set to 'continue' or 'stop'), the default route will not be triggered.
 </Accordion>
 </AccordionGroup>
 
diff --git a/zh/on-call/advanced/reference-variables.mdx b/zh/on-call/advanced/reference-variables.mdx
@@ -49,14 +49,18 @@ keywords: ["引用变量", "模板变量", "标签引用", "动态内容", "变
 
 ### 通过 Golang 模版语法引用
 
-以 `[TPL]` 作为前缀，使用 `{{}}` 来引用变量（可以引用标签和属性），提取不到使用 `<no value>` 替代。
+以 `[TPL]` 作为前缀，使用 `{{}}` 来引用变量（可以引用标签和属性），标签不存在时返回空字符串。
 
 | 规则 | 变量值 | 生成内容 |
 | --- | --- | --- |
 | `[TPL]{{.Labels.resource}} / {{.Labels.check}}` | `{"resource": "127.0.0.1", "check": "cpu idle low"}` | 127.0.0.1 / cpu idle low |
-| `[TPL]{{.Labels.resource}} / {{.Labels.check}}` | `{"resource": "127.0.0.1"}` | 127.0.0.1 / `<no value>` |
+| `[TPL]{{.Labels.resource}} / {{.Labels.check}}` | `{"resource": "127.0.0.1"}` | 127.0.0.1 / |
 | `[TPL]{{.EventSeverity}} / 主机宕机` | `{"EventSeverity": "Warning"}` | Warning / 主机宕机 |
 
+<Note>
+`${}` 语法和 `{{}}` 语法在标签不存在时的行为不同：`${}` 返回 `<no value>`，`{{}}` 返回空字符串。
+</Note>
+
 #### 支持引用的属性列表
 
 | 字段 | 类型 | 说明 |
diff --git a/zh/on-call/analytics/insights.mdx b/zh/on-call/analytics/insights.mdx
@@ -34,7 +34,7 @@ keywords: ["分析看板", "数据分析", "故障统计", "报表导出", "运
 | 团队 | 选择需要查询的团队名称，支持多选，选中后会按选中的团队更新仪表盘中的数据 |
 | 协作空间 | 选择需要查询的协作空间名称，支持多选，选中后会按选中的协作空间更新仪表盘中的数据 |
 | 严重程度 | 选择需要查询的严重程度，支持多选，选中后会按选中的严重程度更新仪表盘中的数据 |
-| 时间范围 | 选择需要查询的时间范围，支持按本周、最近两周、本月、上个月以及自定义时间的维度进行查询，但最多支持查询最近 **180 天** 的数据 |
+| 时间范围 | 选择需要查询的时间范围，支持按本周、最近两周、本月、上个月以及自定义时间的维度进行查询，但最多支持查询最近 **1 年** 的数据 |
 | 数据间隔 | 支持天、周、月的维度进行查询，默认按小时进行查询，但查询的时间范围大于 31 天时，无法以天的维度进行预览 |
 | 排序 | 团队、协作空间和个人维度的仪表盘可以选择倒排和正排，默认只显示 TOP 10 的数据，单独放大后可以展示更多 |
 
@@ -125,7 +125,7 @@ keywords: ["分析看板", "数据分析", "故障统计", "报表导出", "运
 
 <AccordionGroup>
 <Accordion title="想要查询更久的数据怎么办？">
-目前分析看板中仅支持查询最近 180 天的数据，如果需要查询更久的数据，可以通过 [API 查询](https://developer.flashcat.cloud/api-213441443)。
+目前分析看板中最多支持查询最近 1 年的数据（具体取决于您的订阅版本的数据保留周期），如果需要查询更久的数据，可以通过 [API 查询](https://developer.flashcat.cloud/api-213441443)。
 </Accordion>
 
 <Accordion title="为什么查询数据的时间范围超过 31 天后，不能以天的维度查看数据？">
diff --git a/zh/on-call/channel/noise-reduction.mdx b/zh/on-call/channel/noise-reduction.mdx
@@ -234,10 +234,10 @@ src="https://download.flashcat.cloud/flashduty/video/silence.mp4"
 
 **操作路径**：故障详情 → 更多操作 → **快速静默**
 
-- 规则名称默认为故障 ID + 标题
+- 规则名称默认为「快速静默 - #短标识」，描述中包含故障标题
 - 生效范围为故障所属协作空间（不可更改）
 - 默认生效 24 小时，到期后自动删除
-- 条件默认为故障标签的完全匹配
+- 条件默认为故障严重程度和筛选后的标签匹配（自动排除数值型、过长及特殊标签）
 
 <Frame caption="快速静默配置">
   ![快速静默](https://docs-cdn.flashcat.cloud/images/png/e80c2632d9065b28499edfa5a81a8505.png)
diff --git a/zh/on-call/configuration/custom-fields.mdx b/zh/on-call/configuration/custom-fields.mdx
@@ -73,8 +73,8 @@ keywords: ["自定义字段", "元数据", "故障属性", "业务信息", "字
 | 类型 | 说明 |
 | :--- | :--- |
 | **文本** | 纯文本输入框，最多 500 字符 |
-| **单选** | 单选下拉框，最多 10 个选项，每项不超过 200 字符 |
-| **多选** | 多选下拉框，最多 10 个选项，每项不超过 200 字符 |
+| **单选** | 单选下拉框，最多 20 个选项，每项不超过 200 字符 |
+| **多选** | 多选下拉框，最多 20 个选项，每项不超过 200 字符 |
 | **复选** | Checkbox 勾选框 |
 </Step>
 <Step title="完成创建">
diff --git a/zh/on-call/configuration/templates.mdx b/zh/on-call/configuration/templates.mdx
@@ -117,10 +117,10 @@ keywords: ["通知模板", "模板配置", "消息格式", "模板变量", "通
 <Accordion title="Assignment - 分派配置">
 | 字段 | 类型 | 必含 | 说明 |
 | :--- | :--- | :---: | :--- |
-| PersonIDs | []string | | 人员 ID 列表，仅当按人员分派时存在 |
+| PersonIDs | []int64 | | 人员 ID 列表，仅当按人员分派时存在 |
 | EscalateRuleID | string | | 分派策略 ID |
 | EscalateRuleName | string | | 分派策略名称 |
-| LayerIdx | string | | 分派环节，从 0 开始 |
+| LayerIdx | int | | 分派环节，从 0 开始 |
 | Type | string | ✓ | 分派类型：assign / reassign / escalate / reopen |
 </Accordion>
 
@@ -141,10 +141,9 @@ keywords: ["通知模板", "模板配置", "消息格式", "模板变量", "通
 | Description | string | ✓ | 告警描述，可能为空 |
 | AlertSeverity | string | ✓ | 严重程度：Critical / Warning / Info |
 | AlertStatus | string | ✓ | 告警状态：Critical / Warning / Info / Ok |
-| Progress | string | ✓ | 处理进度：Triggered / Processing / Closed |
 | StartTime | int64 | ✓ | 触发时间，Unix 秒时间戳 |
+| LastTime | int64 | | 最新事件时间，Unix 秒时间戳 |
 | EndTime | int64 | | 恢复时间，Unix 秒时间戳 |
-| CloseTime | int64 | | 关闭时间，Unix 秒时间戳 |
 | Labels | map | | 标签 KV |
 </Accordion>
 </AccordionGroup>
diff --git a/zh/on-call/incident/handle-update-incident.mdx b/zh/on-call/incident/handle-update-incident.mdx
@@ -96,7 +96,7 @@ Flashduty On-call 推送的语音告警，在语音播报结束时，会提醒
 
 ## 暂缓处理
 
-故障的处理人，在认领故障之后，可能需要一些时间来调查和处理故障，**暂缓** 操作可以暂时停止故障按照预期的分派策略进行升级。您可以在认领故障之后，设定一个暂缓时间，比如 2 小时、4 小时，或设定一个 24 小时以内的自定义到期时间。
+故障的处理人，在认领故障之后，可能需要一些时间来调查和处理故障，**暂缓** 操作可以暂时停止故障按照预期的分派策略进行升级。您可以在认领故障之后，设定一个暂缓时间，比如 2 小时、4 小时、12 小时，或设定一个 24 小时以内的自定义到期时间。
 
 <Warning>
 如果您已经操作了暂缓，并且暂缓时间已过，且您仍然没有完成故障的处理，这时系统会自动将故障回退为 **待处理** 状态，并重新发起分派通知。
diff --git a/zh/on-call/incident/outlier-incidents.mdx b/zh/on-call/incident/outlier-incidents.mdx
@@ -65,7 +65,7 @@ keywords: ["新奇故障", "异常检测", "AI识别", "故障分析", "智能
 
 <AccordionGroup>
 <Accordion title="新奇故障是否需要单独开启？">
-无需设置和开启，默认所有专业版及以上订阅版本，系统都会触发新奇故障识别。
+专业版及以上默认开启，但可以在协作空间的基础设置中关闭。详见上方「开启与关闭」章节。
 </Accordion>
 </AccordionGroup>
 
diff --git a/zh/on-call/integration/alert-integration/alert-pipelines.mdx b/zh/on-call/integration/alert-integration/alert-pipelines.mdx
@@ -106,7 +106,7 @@ Pipeline 中的抑制功能与协作空间的抑制规则**完全一致**，都
 | `[TPL]{{.Labels.xxx}}` | 引用特定标签 | `[TPL]{{.Labels.host}}` |
 | `[TPL]{{.Title}}` | 引用当前标题 | `[TPL][转发] {{.Title}}` |
 | `[TPL]{{.Description}}` | 引用当前描述 | `[TPL]详情: {{.Description}}` |
-| `[TPL]{{.Severity}}` | 引用当前等级 | `[TPL]当前级别: {{.Severity}}` |
+| `[TPL]{{.EventSeverity}}` | 引用当前等级 | `[TPL]当前级别: {{.EventSeverity}}` |
 
 <Tip>
 在配置 Pipeline 之前，建议先观察一段时间的原始告警数据，明确哪些字段（Labels）是稳定的，哪些是需要清洗的。
diff --git a/zh/on-call/integration/alert-integration/label-enhancement.mdx b/zh/on-call/integration/alert-integration/label-enhancement.mdx
@@ -179,8 +179,8 @@ keywords: ["标签增强", "自动标签", "数据提取", "字段映射", "告
 | 描述 | 服务用途说明 | 根据主机 IP 查询资产信息 |
 | 请求 URL | API 的请求地址 | `https://mapping-api.example.com/v1/enrich-event` |
 | 请求头 | HTTP 请求头配置 | `X-Auth-Token: your-token` |
-| 超时时间 | 请求超时时间（秒） | 1 |
-| 重试次数 | 请求失败后的重试次数 | 1 |
+| 超时时间 | 请求超时时间，1-3 秒，默认 2 秒 | 1 |
+| 重试次数 | 请求失败后的重试次数，0-1 次，默认 0 次 | 1 |
 
 <Tip>
 如果 API 使用 HTTPS 且证书不受信任，可开启 `跳过证书验证` 选项。
@@ -244,7 +244,6 @@ Flashduty 将通过 `POST` 方法调用您的 API，请求体包含以下内容
     "description": "CPU usage for instance '10.0.1.1:9100' is over 95%",
     "title": "High CPU Usage on instance 10.0.1.1:9100",
     "alert_key": "d41d8cd98f00b204e9800998ecf8427e",
-    "alert_id": "62d6c0f6b8f1b2b3c4d5e6f7",
     "event_severity": "Critical",
     "event_status": "Critical",
     "event_time": 1678886400,
diff --git a/zh/on-call/integration/alert-integration/routing-rules.mdx b/zh/on-call/integration/alert-integration/routing-rules.mdx
@@ -119,7 +119,7 @@ keywords: ["路由规则", "告警路由", "分发策略", "协作空间", "分
 </Accordion>
 
 <Accordion title="流程控制选择「停止」时，是否还会匹配默认路由？">
-会。默认路由是兜底规则，不受流程控制限制。
+不会。默认路由仅在所有路由规则均未命中时才生效。如果某条规则已命中（无论流程控制选择「继续」还是「停止」），默认路由都不会再触发。
 </Accordion>
 </AccordionGroup>
 
