pingcap · ti-chi-bot · Apr 13, 2026 · Apr 13, 2026 · Apr 13, 2026
diff --git a/dashboard/top-sql.md b/dashboard/top-sql.md
diff --git a/media/dashboard/v8.5-top-sql-access.png b/media/dashboard/v8.5-top-sql-access.png
diff --git a/media/dashboard/v8.5-top-sql-details.png b/media/dashboard/v8.5-top-sql-details.png
diff --git a/media/dashboard/v8.5-top-sql-settings-enable-tikv-network-io.png b/media/dashboard/v8.5-top-sql-settings-enable-tikv-network-io.png
diff --git a/media/dashboard/v8.5-top-sql-usage-agg-by-db-detail.png b/media/dashboard/v8.5-top-sql-usage-agg-by-db-detail.png
diff --git a/media/dashboard/v8.5-top-sql-usage-change-timerange.png b/media/dashboard/v8.5-top-sql-usage-change-timerange.png
diff --git a/media/dashboard/v8.5-top-sql-usage-chart.png b/media/dashboard/v8.5-top-sql-usage-chart.png
diff --git a/media/dashboard/v8.5-top-sql-usage-refresh.png b/media/dashboard/v8.5-top-sql-usage-refresh.png
diff --git a/media/dashboard/v8.5-top-sql-usage-select-agg-by.png b/media/dashboard/v8.5-top-sql-usage-select-agg-by.png
diff --git a/media/dashboard/v8.5-top-sql-usage-select-instance.png b/media/dashboard/v8.5-top-sql-usage-select-instance.png
diff --git a/media/dashboard/v8.5-top-sql-usage-select-order-by.png b/media/dashboard/v8.5-top-sql-usage-select-order-by.png
diff --git a/tidb-cloud/tidb-cloud-clinic.md b/tidb-cloud/tidb-cloud-clinic.md
@@ -29,7 +29,7 @@ To view the **Cluster** page, take the following steps:
 
     - Advanced Metrics
     - Top Slow Queries (only supported when the TiDB version of the cluster is v8.1.1 or later, v7.5.4 or later)
-    - TopSQL (only supported when the TiDB version of the cluster is v8.1.1 or later, v7.5.4 or later)
+    - Top SQL (only supported when the TiDB version of the cluster is v8.1.1 or later, v7.5.4 or later)
     - Benchmark Report
 
 ## Monitor advanced metrics
@@ -91,21 +91,21 @@ The retention policy for slow queries is 7 days.
 
 For more information, see [Slow Queries in TiDB Dashboard](https://docs.pingcap.com/tidb/stable/dashboard-slow-query).
 
-## Monitor TopSQL
+## Monitor Top SQL
 
-TiDB Cloud Clinic provides TopSQL information, enabling you to monitor and visually explore the CPU overhead of each SQL statement in your database in real time. This helps you optimize and resolve database performance issues.
+TiDB Cloud Clinic provides Top SQL information to help you visually analyze the most resource-intensive queries on a specific TiDB or TiKV node over a period of time. By default, Top SQL continuously collects CPU load data. For TiKV nodes, if TiKV network IO collection is enabled, you can also inspect `Network Bytes` and `Logical IO Bytes`, and analyze hotspots by `Query`, `Table`, `DB`, or `Region`. This helps you identify and troubleshoot performance issues across multiple resource dimensions, not just CPU.
 
-To view TopSQL, take the following steps:
+To view Top SQL, take the following steps:
 
 1. In the [TiDB Cloud Clinic console](https://clinic.pingcap.com/), navigate to the **Cluster** page of a cluster.
 
-2. Click **TopSQL**.
+2. Click **Top SQL**.
 
-3. Select a specific TiDB or TiKV instance to observe its load. You can use the time picker or select a time range in the chart to refine your analysis.
+3. Select a specific TiDB or TiKV node to observe its workload. You can use the time picker or select a time range in the chart to refine your analysis.
 
-4. Analyze the charts and tables displayed by TopSQL.
+4. Analyze the charts and tables displayed by Top SQL. Depending on the selected node and enabled metrics, you can use `Order By` and the available aggregation dimensions to inspect CPU, network, or logical I/O hotspots.
 
-For more information, see [TopSQL in TiDB Dashboard](https://docs.pingcap.com/tidb/stable/top-sql). 
+For more information, see [Top SQL in TiDB Dashboard](https://docs.pingcap.com/tidb/stable/top-sql).
 
 ## Generate benchmark reports
 

diff --git a/tikv-configuration-file.md b/tikv-configuration-file.md
@@ -2644,6 +2644,24 @@ To reduce write latency, TiKV periodically fetches and caches a batch of timesta
 + In a default TSO physical time update interval (`50ms`), PD provides at most 262144 TSOs. When requested TSOs exceed this number, PD provides no more TSOs. This configuration item is used to avoid exhausting TSOs and the reverse impact of TSO exhaustion on other businesses. If you increase the value of this configuration item to improve high availability, you need to decrease the value of [`tso-update-physical-interval`](/pd-configuration-file.md#tso-update-physical-interval) at the same time to get enough TSOs.
 + Default value: `8192`
 
+## resource-metering
+
+Configuration items related to resource metering.
+
+### `enable-network-io-collection` <span class="version-mark">New in v8.5.6</span>
+
++ Controls whether to collect TiKV network traffic and logical I/O information in [Top SQL](/dashboard/top-sql.md) in addition to CPU data.
++ When enabled, TiKV additionally records inbound network bytes, outbound network bytes, logical read bytes, and logical write bytes during request processing.
++ When reporting resource consumption, TiKV filters the Top N records based on CPU time, network traffic, and logical I/O, and additionally reports these statistics by Region for more fine-grained analysis of hotspot requests or resource usage sources.
++ Default value: `false`
+
+> **Note:**
+>
+> Logical I/O is not equivalent to physical I/O and cannot be directly correlated:
+>
+> - Logical I/O refers to the logical amount of data processed by requests at the TiKV storage layer, such as data scanned or processed during reads and data written by write requests.
+> - Physical I/O refers to the actual disk read/write traffic on the underlying storage device, which is affected by block cache, compaction, flush, and other factors.
+
 ## resource-control
 
 Configuration items related to resource control of the TiKV storage layer.