Merge pull request #149 from flashcatcloud/doc-review/2026-07-08-031734

docs: sync doc-review drift fixes

Author: ysyneu

en/on-call/analytics/insights.mdx

@@ -107,7 +107,9 @@ All dimensions support downloading dashboards in PDF format for further data ana
 </Tab>
 
 <Tab title="Data Export">
-Export incident list data in CSV format. Supports exporting incident list, team, channel, and individual dimension data, but exported data may not match displayed fields.
+Export incident list, team, channel, and individual dimension data in CSV format. Before exporting, choose the fields you need in the popover. Incident list exports support labels, custom fields, raw assignment text, raw responder text, escalation rule, and other incident fields. Enable **Extract text content from HTML** to write incident descriptions as plain text in the CSV, which makes them easier to read in spreadsheet tools.
+
+When the page shows extended fields, CSV export can also include alert counts, active alert counts, alert events, owner, closer, snoozed until, ever muted, and outlier incident fields.
 
 <Frame>
 <img src="https://download.flashcat.cloud/flashduty/doc/zh/fd/insight-5.png" alt="Data Export Diagram" />
@@ -118,8 +120,8 @@ Export incident list data in CSV format. Supports exporting incident list, team,
 ### Export Limitations
 
 <Warning>
-- Incident list exports do not include Labels data. For more detailed data, we recommend querying via the [Incident List API](/en/api-reference/on-call/incidents/incident-list)
-- Maximum data list query and export is 10,000 records. For more data, we recommend exporting in time segments
+- For data that is more complete than CSV or easier to process programmatically, query the [Incident List API](/en/api-reference/on-call/incidents/incident-list)
+- List queries and CSV exports are limited to 10,000 records. For more data, export in smaller time ranges
 </Warning>
 
 ## Usage Statistics

en/on-call/integration/alert-integration/alert-sources/db-pull.mdx

@@ -67,7 +67,7 @@ When you need to route alert events to different channels based on the alert pay
 | :-: | :-: | :-: | :--- |
 | Query | Yes | - | A read-only SELECT statement (or a CTE starting with `WITH`). **DML/DDL keywords** (`INSERT`, `UPDATE`, `DELETE`, `DROP`, etc.) are **forbidden**. **Parameter placeholders** (`?`) are **forbidden**. **Row-limiting keywords** (`LIMIT`, `OFFSET`, `FETCH NEXT`, `SELECT TOP`) are **forbidden** — the system controls pagination automatically. The query output **must include** both cursor columns (`time_column` and `id_column`); validation fails at save time if they are missing. |
 | Timeout (seconds) | Yes | `5` | Maximum execution time for a single page query, range `1 ~ 10` seconds. Values above `10` are clamped to `10`. |
-| Polling Cycle (seconds) | Yes | - | Interval between successive polling cycles (seconds). |
+| Polling Cycle (seconds) | Yes | `60` | Interval between successive polling cycles, in seconds. The minimum value is `30`. |
 | Max Pages | Yes | `5` | Maximum pages fetched per polling cycle, range `1 ~ 10`. Values above `10` are clamped to `10`. Pagination stops when the cap is reached or a page returns fewer rows than `page_size`. |
 | Page Size | Yes | `500` | Maximum rows returned per page, range `1 ~ 1000`. Values above `1000` are clamped to `1000`. |
 
@@ -83,7 +83,7 @@ Flashduty uses **keyset pagination** to fetch new rows incrementally and avoid f
 | :-: | :-: | :--- |
 | Time Column (`time_column`) | Yes | The timestamp column used for ordering and pagination. The name must match `[a-zA-Z_][a-zA-Z0-9_]*` and must appear in the SELECT output. |
 | ID Column (`id_column`) | Yes | A unique-identifier column used together with the time column to break ties when multiple rows share the same timestamp (typically an auto-increment primary key or UUID). Same naming rules as `time_column`. |
-| Initial Time (`initial_time`) | No | The starting point for the very first fetch (or after a checkpoint reset), in `YYYY-MM-DD HH:MM:SS` format. If omitted, the system uses the time the integration was saved as the starting point — **rows that already exist before that moment will not be fetched**. |
+| Initial Time (`initial_time`) | Yes | The starting point for the very first fetch (or after a checkpoint reset), in `YYYY-MM-DD HH:mm:ss` format. The form defaults to the current time, so **rows that already exist before that moment will not be fetched**. Select an earlier time if you need to backfill historical rows. |
 
 **How pagination works**
 

zh/on-call/analytics/insights.mdx

@@ -108,7 +108,9 @@ keywords: ["分析看板", "数据分析", "故障统计", "报表导出", "运
 </Tab>
 
 <Tab title="数据导出">
-以 CSV 格式导出故障列表数据，支持将故障列表、团队、协作空间和个人维度数据导出，但导出的数据并不会按照展示的字段进行导出。
+以 CSV 格式导出故障列表、团队、协作空间和个人维度数据。导出前可以在弹窗中选择需要的字段；故障列表支持导出 Labels、自定义字段、分派方式原文、处理人员原文、分派策略等字段。开启 **提取 HTML 中的文本内容** 后，故障描述会以纯文本写入 CSV，便于在表格工具中阅读。
+
+当页面展示扩展字段时，CSV 也可以选择导出告警数量、活跃告警数量、告警事件、负责人、关闭人、屏蔽至、曾被收敛、新奇故障等字段。
 
 <Frame>
 <img src="https://download.flashcat.cloud/flashduty/doc/zh/fd/insight-5.png" alt="数据导出示意图" />
@@ -119,7 +121,7 @@ keywords: ["分析看板", "数据分析", "故障统计", "报表导出", "运
 ### 导出限制
 
 <Warning>
-- 故障列表导出时，不包含 Labels 数据，如果需要更详细的数据，建议通过[故障列表 API](/zh/api-reference/on-call/incidents/incident-list) 查询
+- 如果需要比 CSV 更完整或更适合程序处理的数据，建议通过[故障列表 API](/zh/api-reference/on-call/incidents/incident-list) 查询
 - 数据列表的查询和导出的数据量最大是 1 万条，如果需要更多数据，建议分时间段导出
 </Warning>
 

zh/on-call/integration/alert-integration/alert-sources/db-pull.mdx

@@ -65,7 +65,7 @@ DB Pull 适合 **告警数据已落入关系型数据库**、**无法或不希
 | :-: | :-: | :-: | :--- |
 | 查询语句（query） | 是 | - | 一条只读 SELECT 语句（或以 `WITH` 开头的 CTE 查询）。**禁止**包含 `INSERT`、`UPDATE`、`DELETE`、`DROP` 等 DML/DDL 关键字，**禁止**使用 `?` 占位符，**禁止**包含 `LIMIT` / `OFFSET` 等分页子句（系统自动处理分页）。查询输出列中**必须包含**游标字段（`time_column` 与 `id_column`），否则保存时校验失败。 |
 | 超时时间（timeout，秒） | 是 | `5` | 单页查询的最长执行时间，范围 `1 ~ 10` 秒，超过 `10` 秒时系统自动截断为 `10`。 |
-| 拉取周期（cycle_seconds，秒） | 是 | - | Flashduty 触发下一次拉取的间隔（秒）。 |
+| 拉取周期（cycle_seconds，秒） | 是 | `60` | Flashduty 触发下一次拉取的间隔（秒），最小值为 `30`。 |
 | 最大页数（max_pages） | 是 | `5` | 单次拉取最多查询多少页，范围 `1 ~ 10`，超过 `10` 时截断为 `10`。每页行数达到 `page_size` 时翻页，否则停止。 |
 | 每页行数（page_size） | 是 | `500` | 单页最多返回的行数，范围 `1 ~ 1000`，超过 `1000` 时截断为 `1000`。 |
 
@@ -81,7 +81,7 @@ Flashduty 使用 **游标分页**（Keyset Pagination）增量拉取新行，避
 | :-: | :-: | :--- |
 | 时间列（time_column） | 是 | 用于排序和分页的时间类型列名，列名只能包含字母、数字和下划线且不能以数字开头。该列必须出现在 SELECT 输出中。 |
 | ID 列（id_column） | 是 | 与时间列联合用于分页的唯一标识列名（通常为自增主键或 UUID），规则同上。当同一时刻有多行时，ID 列用于消除时间列的排序歧义，防止漏行。 |
-| 初始时间（initial_time） | 否 | 首次拉取（或检查点重置后）使用的起始时间，格式为 `YYYY-MM-DD HH:MM:SS`。若不填，系统以配置保存时的当前时间作为起点，**已存在的历史行不会被拉取**。 |
+| 初始时间（initial_time） | 是 | 首次拉取（或检查点重置后）使用的起始时间，格式为 `YYYY-MM-DD HH:mm:ss`。表单默认使用当前时间作为起点，**已存在的历史行不会被拉取**；如需补拉历史数据，请手动选择更早的时间。 |
 
 **分页查询原理**