Merge pull request #317 from flashcatcloud/doc-review/20260827-080700

docs: doc-review 2026-08-27 incremental fixes

Author: ysyneu

docs.json

@@ -1945,6 +1945,13 @@
                   "zh/monitors/data-sources/data-sources"
                 ]
               },
+              {
+                "group": "查询工作台",
+                "icon": "magnifying-glass-chart",
+                "pages": [
+                  "zh/monitors/explore/explore"
+                ]
+              },
               {
                 "group": "实体树",
                 "icon": "sitemap",
@@ -3308,6 +3315,13 @@
                   "en/monitors/data-sources/data-sources"
                 ]
               },
+              {
+                "group": "Query Workbench",
+                "icon": "magnifying-glass-chart",
+                "pages": [
+                  "en/monitors/explore/explore"
+                ]
+              },
               {
                 "group": "Entity Tree",
                 "icon": "sitemap",

en/ai-sre/skills.mdx

@@ -26,6 +26,10 @@ When triggering explicitly, you can append arguments: `/<skill-name> arg1 arg2`.
 
 If you just want to **mention** `/skill-name` in a message (for example, asking "what does `\/skill-name` do?") without triggering it, add a backslash escape at the start of the message: a message starting with `\/` has that leading backslash stripped and is sent as plain text instead of being parsed as a command.
 
+<Info>
+**Cross-team skill name conflicts and the `@` qualifier.** Skill names must be unique within a team, but different teams may each own a skill with the same name. When two teams both have an enabled skill with the same name and both are in scope for the current session, a bare `/<skill-name>` cannot resolve to either and is rejected with a hint listing the qualified forms. In that case, use `/<skill-name>@<team_id>` to disambiguate (e.g., `/deploy@5`). The `@` character is therefore reserved and cannot be used in skill names.
+</Info>
+
 <Tip>
 The difference between Skills and MCP: MCP provides **connectivity to external tools**; Skills provide **the methodology for orchestrating those tools to complete a category of tasks**. They work together — a skill declares in SKILL.md which tools it needs, including built-in tools and MCP tools in the form `mcp:server/tool`.
 </Tip>
@@ -135,7 +139,7 @@ In addition to installing from the Marketplace, you can upload your own skill pa
 | Owner | Team / Account | Yes | Select the scope for this skill: **Account** (visible to all members account-wide) or a specific **Team** (visible only to members of that team). To upload into a team scope, you must belong to the target team; account-level upload is limited to the account owner or admins. See "Scope" below. |
 | Zip file | File | Yes | An archive containing `SKILL.md` (required) and any optional resource files. `.zip` / `.skill` / `.tar.gz` / `.tgz` archives are accepted. |
 
-At upload time, the system automatically validates that: the archive is a valid zip, `SKILL.md` exists in the root directory, the frontmatter is parseable, `name` follows kebab-case naming, and all declared tools are valid (built-in tools exist, MCP servers exist). **Skill names must be unique within an account** — a duplicate name is rejected with a prompt to choose a different name.
+At upload time, the system automatically validates that: the archive is a valid zip, `SKILL.md` exists in the root directory, the frontmatter is parseable, `name` follows kebab-case naming, and all declared tools are valid (built-in tools exist, MCP servers exist). **Skill names must be unique within a team** — a duplicate name within the same team is rejected with a prompt to choose a different name; different teams may each own a skill with the same name.
 
 <Note>
 All metadata other than the skill name (description, version, tags, author, tools, etc.) is parsed from `SKILL.md`'s frontmatter and does not need to be entered separately in the form.

en/monitors/explore/explore.mdx

@@ -0,0 +1,77 @@
+---
+title: "Query Workbench"
+description: "Run ad-hoc queries against Prometheus, Loki, VictoriaLogs, SLS, CLS, and SQL data sources in Flashduty Monitors. Supports graph, raw, and log volume views."
+keywords: ["Explore", "Query Workbench", "ad-hoc query", "Prometheus", "Loki", "data source"]
+---
+
+The Query Workbench (Explore) is an ad-hoc query interface in Flashduty Monitors for running temporary queries against data sources without creating alert rules. It supports Prometheus, Loki, VictoriaLogs, Alibaba Cloud SLS, Tencent Cloud CLS, and MySQL, PostgreSQL, Oracle, ClickHouse, Elasticsearch data sources.
+
+## Access
+
+- **From the data source list**: Go to **Monitors → Data Sources** and click the "Query Workbench" entry on the target data source row.
+- **Direct URL**: Navigate to `/monit/explore` and select a data source in the page.
+- **From incident/alert labels**: In the label area of incident or alert detail, the "Explore" icon on query-type label rows opens the workbench with the alert's triggering query and time window pre-filled.
+
+## Query Types
+
+Different data sources support different query types, switched above the editor:
+
+| Data Source | Query Type | Description |
+|-------------|-----------|-------------|
+| Prometheus | Graph + Raw | Shows both a line chart and raw samples |
+| Prometheus | Graph only | Shows only the line chart (range query) |
+| Prometheus | Raw only | Shows only raw samples (instant query) |
+| Loki | Range | Returns log lines within the time range |
+| Loki | Instant | Returns matching log lines at the current moment |
+| VictoriaLogs | Raw logs | Returns raw log lines |
+| VictoriaLogs | Instant stats | Returns instant aggregate statistics |
+| VictoriaLogs | Range stats | Returns range trend statistics |
+| SLS / CLS | — | No query type selector; vendor-classified logs/tables |
+| MySQL / PostgreSQL / Oracle / ClickHouse / ES | — | SQL/query expression executed directly |
+
+## Result Display
+
+The result area auto-layouts based on data source and query type:
+
+- **Prometheus**: Split pane — line chart (Graph) on top, raw samples (Raw) below, with a draggable splitter.
+- **Other data sources**: Single result pane showing log view, table view, or samples view depending on the query type.
+
+### Graph Features
+
+- **Drag-to-zoom**: Drag-select a time range on the chart to zoom in.
+- **Legend facet filtering**: The legend area supports searching by label value and grouping by metric name. Series beyond the display limit are collapsed; click to expand.
+- **Tooltip**: Hover to see values for all series at a given time point. Series beyond the limit are summarized in the tooltip.
+
+### Log Time Distribution
+
+When the query type includes logs, a log time distribution chart appears above the result area:
+
+- Time range ≤ 24 hours: auto-loaded.
+- 24 hours – 30 days: requires manual click to load.
+- Beyond 30 days: not supported.
+
+## Query Parameters
+
+In addition to the query expression, some data sources support private parameters:
+
+| Parameter | Data Sources | Description |
+|-----------|-------------|-------------|
+| Limit | Loki / VictoriaLogs | Caps the number of returned rows |
+| Min step (seconds) | Prometheus | Lower bound for auto step calculation |
+| Direction | Loki / VictoriaLogs | Latest-first or earliest-first |
+| Project / Logstore | SLS | Required; used in the request URL |
+| Region / Topic / Syntax | Tencent CLS | Required |
+| PowerSQL | SLS | Enables PowerSQL mode |
+| Time macros | SQL data sources | `$__timeFilter(column)`, `$__timeFrom()`, `$__timeTo()` make the time range take effect |
+
+## Query History
+
+Each successful query is automatically saved to query history, which stores only the query expression — not the time range or results. History is isolated per data source, stored in the browser locally, and retains up to 200 entries. When the limit is exceeded, the oldest entry is evicted. Oversized query expressions are not saved to history but the query itself still succeeds. You can delete individual entries or clear all history for the current data source from the history panel.
+
+## Sharing and URL State
+
+The workbench encodes the current data source, query expression, time range, and query type into URL parameters. Copy the browser address bar to share the current query state — opening the link restores it automatically. If the data source in the link doesn't exist, is disabled, or the user lacks permissions, the page prompts and does not auto-execute.
+
+## Edge Version Requirements
+
+The Query Workbench relies on monit-edge to execute queries. If the Edge version in the data source's cluster is too low or versions are mixed, the page shows an upgrade prompt and disables querying. All Edge instances in the cluster must be upgraded to the required version before use.

en/on-call/channel/escalation-rule.mdx

@@ -81,6 +81,10 @@ Determines how users are reached.
     <Note>
     **Don't use any of the above IM platforms?** You can select any bot type and set the webhook URL to your own server endpoint (the system does not validate domains), then implement the corresponding message protocol on your server. See [FAQ](/en/on-call/quickstart/faq#custom-bot-notifications).
     </Note>
+
+    <Info>
+    **Cross-team webhook address scoping.** When selecting a Webhook bot address in a dispatch policy, addresses are grouped by ownership tier: **Current Channel** (already referenced by this channel), **Same Team** (referenced by other channels in the same team), and **Other Team** (referenced only by channels in other teams). Other-team addresses are collapsed by default and require manual expansion. Selecting an other-team address shows a **Cross-team** badge and warning; on save, a confirmation modal appears when cross-team addresses are present, preventing alerts from being sent to another team's chat by accident.
+    </Info>
   </Tab>
 </Tabs>
 

en/on-call/incident/handle-update-incident.mdx

@@ -65,6 +65,7 @@ You have three ways to acknowledge a newly triggered incident.
 <Tab title="Acknowledge via Console">
 - **Single Acknowledge**: Click incident details in console, click **Acknowledge** button to complete
 - **Batch Operation**: In console incident list, select multiple triggered incidents, click **Acknowledge** button for batch acknowledgment
+- **AI Analysis**: After selecting multiple incidents, click the **AI Analysis** button to batch-send the selected incidents as context to the AI SRE Agent for analysis. This button requires the AI SRE module to be enabled and the `AiSreChatVisit` permission; if all selected incidents belong to the same team, the session defaults to that team's scope.
 </Tab>
 
 <Tab title="Acknowledge via IM App">

en/on-call/incident/search-view-incident.mdx

@@ -117,6 +117,8 @@ Incident labels are displayed in the **Details** area of the details page. When
 
 Jumping to an entity-tree rule requires contextual labels such as `__entity_alert_account_id`, `__entity_alert_entity_definition_id`, `__entity_alert_data_source_id`, and `__entity_alert_policy_scope_group_id` for locating; when any required label is missing or invalid, the label value is shown as plain text. Standalone alert rules (`rule_id` / `__alert_rule_id`) likewise require a positive integer value (e.g. `123`); when the value is empty, `0`, or non-numeric, the label is shown as plain text to avoid generating an invalid link. This deep-link capability also applies to the label area of the alert details page.
 
+Additionally, when a label carries query-type information (such as the PromQL / log expression that was active when the alert triggered), an **Explore** icon appears on the right side of the label row. Clicking it opens the Query Workbench in a new tab, pre-filled with the alert's triggering query and a time window set around the alert's start time. A single query links directly; multiple queries (primary + related) display a popover list for selection.
+
 ### Detail Tabs
 
 The incident details page contains 7 tabs; some appear only under certain conditions:

en/rum/analytics/native.mdx

@@ -12,9 +12,9 @@ The Insights dashboard includes 4 core analysis dimensions: **Overview**, **Perf
 <Note>
 **Platform Differences**
 
-The Native dashboard applies to Android, iOS, HarmonyOS, and Flutter apps, with the following platform-specific differences:
+The Native dashboard applies to Android, iOS, HarmonyOS, Flutter, and React Native apps, with the following platform-specific differences:
 
-- **Flutter**: A single Flutter app spans both Android and iOS, so the filter bar additionally pins the `os_name` filter to let you slice metrics by device OS. In the Overview and Error Analysis, the **ANR Rate** (from Android devices) and **Unresponsive Time Rate** (from App Hangs on iOS devices) cards are displayed side by side.
+- **Flutter / React Native**: A single Flutter or React Native app spans both Android and iOS, so the filter bar additionally pins the `os_name` filter to let you slice metrics by device OS. In the Overview and Error Analysis, the **ANR Rate** (from Android devices) and **Unresponsive Time Rate** (from App Hangs on iOS devices) cards are displayed side by side.
 - **HarmonyOS**: The SDK does not report performance or hang metrics yet, so hang-related cards are hidden and the "Performance" tab is not available.
 - **Electron**: Does not use the Native dashboard — Electron apps reuse the **Web Insights dashboard**, but UV is keyed on the anonymous ID (the Electron SDK does not report `usr_id`). See "Metrics Reference" below.
 </Note>
@@ -510,7 +510,7 @@ Flashduty RUM typically completes data collection and display within **1-3 minut
 | App Startup Time | vital_duration (vital_type=app_launch, vital_app_launch_metric=ttid) | Within 2s | Within 4s | Over 4s |
 | Frame Rate | view_refresh_rate_average | 55 FPS or above | 50 FPS or above | Below 50 FPS |
 | CPU Usage | view_cpu_ticks_per_second | Below 40 ticks/s | Below 60 ticks/s | 60 ticks/s or above |
-| Memory Usage | view_memory_average | Below 100 MB | Below 200 MB | 200 MB or above |
+| Memory Usage | view_memory_average | Below 200 MB | Below 400 MB | 400 MB or above |
 | Peak Memory | view_memory_max | Below 200 MB | Below 400 MB | 400 MB or above |
 | JS Thread Frame Rate | view_js_refresh_rate_avg | 55 FPS or above | 50 FPS or above | Below 50 FPS |
 

en/rum/explorer/overview.mdx

@@ -133,6 +133,15 @@ Each saved view contains the following information:
   </Tab>
 </Tabs>
 
+## Event Export
+
+The event table in the Sessions Explorer provides a **CSV Export** button that exports the data under the current filter conditions and column configuration.
+
+- **Export limit**: A single export caps at 5000 rows. If the filtered data exceeds the limit, a toast notification appears after export completes, indicating that the first N rows were exported and more data remains.
+- **Column matching**: Exported columns match the current event type's column settings — names, order, and units follow the on-screen configuration. When field metadata is not yet loaded, the export uses raw field names and bare values.
+- **Cancel export**: Clicking the button again during an export cancels it; any fetched data is not saved.
+- **Scope**: All view types in the Sessions Explorer event table support export.
+
 ## Next Steps
 
 <CardGroup cols={2}>

en/rum/sdk/react-native/sdk-integration.mdx

@@ -7,7 +7,7 @@ keywords: ["RUM", "React Native SDK", "user monitoring", "mobile monitoring", "J
 The React Native SDK wraps the native iOS / Android SDKs and provides RUM capabilities through `@flashcatcloud/mobile-react-native`. After initialization, the SDK reports the application's views, user actions, network requests, errors, and crashes to Flashduty RUM, with `source: "react-native"` identifying the data source.
 
 <Info>
-The current SDK version is `0.1.x` and supports the **iOS and Android** platforms (React Native Web is not supported). JavaScript class names begin with `Dd*` (such as `DdSdkReactNative`, `DdSdkReactNativeConfiguration`, and `DdRum`). Session Replay is not supported; Logs only work on Android and are a no-op on iOS.
+The current SDK version is `0.1.x` and supports the **iOS and Android** platforms (React Native Web is not supported). The SDK provides two API entry points: `DatadogProvider` / `DatadogProviderConfiguration` (recommended, declarative initialization via a React component wrapper) and `DdSdkReactNative` / `DdSdkReactNativeConfiguration` / `DdRum` (imperative API, still available). Session Replay is not supported; Logs only work on Android and are a no-op on iOS.
 </Info>
 
 ## Prerequisites
@@ -58,16 +58,16 @@ module.exports = withDatadogMetroConfig(
 
 ## Initialize the SDK
 
-Initialize as early as possible in the application entry, and only once. The three boolean constructor arguments control automatic collection of user actions, network requests, and JS errors respectively.
+Initialize as early as possible in the application entry, and only once. Using the `DatadogProvider` component to wrap your app root is recommended — it installs JS-layer instrumentation (the XHR proxy behind `track XHR / fetch resources`) before initializing the native SDK, capturing network requests during startup. The imperative `DdSdkReactNative.initialize()` is still available but loses the startup-window resource collection. The three boolean constructor arguments control automatic collection of user actions, network requests, and JS errors respectively.
 
 ```typescript App.tsx
 import {
-  DdSdkReactNative,
-  DdSdkReactNativeConfiguration,
+  DatadogProvider,
+  DatadogProviderConfiguration,
   TrackingConsent,
 } from '@flashcatcloud/mobile-react-native';
 
-const config = new DdSdkReactNativeConfiguration(
+const config = new DatadogProviderConfiguration(
   '<CLIENT_TOKEN>',
   'production',
   '<APPLICATION_ID>',
@@ -80,8 +80,15 @@ config.site = 'CN';
 config.serviceName = 'com.example.shopping'; // Recommended: keeps Android and iOS under one service
 config.nativeCrashReportEnabled = true; // Collect native Android / iOS crashes
 config.sessionSamplingRate = 100;
+config.firstPartyHosts = ['<YOUR_API_HOST>']; // Matching hosts get tracing headers
 
-DdSdkReactNative.initialize(config);
+export default function App() {
+  return (
+    <DatadogProvider configuration={config}>
+      {/* your app */}
+    </DatadogProvider>
+  );
+}
 ```
 
 <Tip>