[review][YDB] Перевод страницы "Системные таблицы базы данных"

Тикет: https://st.yandex-team.ru/
Ключи:

9 files changed, 192 insertions, 198 deletions

diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/intro_db.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/intro_db.md
index d9dc88cbf89..eaf9f909305 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/intro_db.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/intro_db.md
@@ -1,12 +1,14 @@
 # Database system views
 
-To enable internal introspection of the DB state, the user can make queries to special service tables (system views). These tables are accessible from the root of the database tree and use the `.sys` system path prefix.
+You can make queries to special service tables (system views) to monitor the DB status. These tables are accessible from the root of the database tree and use the `.sys` system path prefix.
 
-Hereinafter, in the descriptions of available fields, the **Key** column contains the corresponding table's primary key field index.
+You can find the corresponding table's primary key field index in the descriptions of available fields below.
 
-System views contain the following information:
+DB system views contain:
 
 * [Details of individual DB table partitions](#partitions).
 * [Top queries by certain characteristics](#top-queries).
 * [Query details](#query-metrics).
 * [History of overloaded partitions](#top-overload-partitions).
+
+{% include [notes](notes.md) %}
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/notes.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/notes.md
index c647143589e..da3a535d0df 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/notes.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/notes.md
@@ -1,4 +1,5 @@
-## Notes
+{% note info %}
 
-Please keep in mind that load caused by accessing system views is more analytical in nature, and therefore making frequent queries to them in large DBs will consume a lot of system resources. A load of about 1-2 rps is quite acceptable.
+Loads caused by accessing system views are more analytical in nature. Making frequent queries to them in large DBs will consume a lot of system resources. The recommended load is no more than 1-2 RPS.
 
+{% endnote %}
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_example_yql.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_example_yql.md
index 490f7ec11e5..c703e8b226b 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_example_yql.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_example_yql.md
@@ -1,25 +1,24 @@
-Top 5 of most loaded partitions among all DB tables
+Top 5 of most loaded partitions among all DB tables:
 
-  ```sql
-  SELECT
-      Path,
-      PartIdx,
-      CPUCores
-  FROM `.sys/partition_stats`
-  ORDER BY CPUCores DESC
-  LIMIT 5
-  ```
+> ```sql
+> SELECT
+>     Path,
+>     PartIdx,
+>     CPUCores
+> FROM `.sys/partition_stats`
+> ORDER BY CPUCores DESC
+> LIMIT 5
+> ```
 
-  List of DB tables with in-flight sizes and loads
-
-  ```sql
-  SELECT
-      Path,
-      COUNT(*) as Partitions,
-      SUM(RowCount) as Rows,
-      SUM(DataSize) as Size,
-      SUM(CPUCores) as CPU
-  FROM `.sys/partition_stats`
-  GROUP BY Path
-  ```
+List of DB tables with in-flight sizes and loads:
 
+> ```sql
+> SELECT
+>     Path,
+>     COUNT(*) as Partitions,
+>     SUM(RowCount) as Rows,
+>     SUM(DataSize) as Size,
+>     SUM(CPUCores) as CPU
+> FROM `.sys/partition_stats`
+> GROUP BY Path
+> ```
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_header.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_header.md
index 379cc4064e1..bc6d74116c0 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_header.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/partitions_header.md
@@ -1,38 +1,37 @@
 ## Partitions {#partitions}
 
-* **partition_stats**
+The following system view stores detailed information about individual [partitions](../../../concepts/datamodel/table.md#partitioning) of all DB tables:
 
-A system view that provides detailed information about individual partitions of all DB tables. Contains information about instant metrics, such as CPU load or count of in-flight transactions, as well as cumulative counters of a variety of operations on a partition (for example, total number of rows read). Primarily designed for detecting various irregularities in the load on a table partition or in the size of table partition data.
+* `partition_stats`: Contains information about instant metrics and cumulative operation counters. Instant metrics are, for example, CPU load or count of in-flight [transactions](../../../concepts/transactions.md). Cumulative counters, for example, count the total number of rows read.
 
-Table structure:
-
-| **Field** | **Type** | **Key** | **Value** |
-| --- | --- | --- | --- |
-| OwnerId | Uint64 | 0 | ID of the SchemeShard serving the table |
-| PathId | Uint64 | 1 | Path ID in the SchemeShard |
-| PartIdx | Uint64 | 2 | Partition sequence number |
-| DataSize | Uint64 |  | Approximate partition size in bytes |
-| RowCount | Uint64 |  | Approximate number of rows |
-| IndexSize | Uint64 |  | Partition index size in a tablet |
-| CPUCores | Double |  | Instant value of load per partition (CPU share) |
-| TabletId | Uint64 |  | ID of the tablet serving the partition |
-| Path | Utf8 |  | Full table path |
-| NodeId | Uint32 |  | ID of the node that the partition is being served on |
-| StartTime | Timestamp |  | Last time when the tablet serving the partition was launched |
-| AccessTime | Timestamp |  | Last time when data from the partition was read |
-| UpdateTime | Timestamp |  | Last time when data was written to the partition |
-| RowReads | Uint64 |  | Number of point reads since the start of the partition tablet |
-| RowUpdates | Uint64 |  | Number of rows written since the start |
-| RowDeletes | Uint64 |  | Number of rows deleted since the start |
-| RangeReads | Uint64 |  | Number of row ranges read since the start |
-| RangeReadRows | Uint64 |  | Number of rows read in the ranges since the start |
-| InFlightTxCount | Uint64 |  | Number of in-flight transactions |
-| ImmediateTxCompleted | Uint64 |  | Number of one-shard transactions completed since the start |
-| CoordinatedTxCompleted | Uint64 |  | Number of coordinated transactions completed since the start |
-| TxRejectedByOverload | Uint64 |  | Number of transactions rejected due to overload (since the start) |
-| TxRejectedByOutOfStorage | Uint64 |  | Number of transactions rejected due to lack of storage space (since the start) |
+The system view is designed to detect various irregularities in the load on a table partition or show the size of table partition data.
 
-Restrictions:
+Cumulative fields (`RowReads`, `RowUpdates`, and so on) store the accumulated values since the last start of the tablet serving the partition.
 
-* Cumulative fields (RowReads, RowUpdates, and so on) store the accumulated values since the last start of the tablet serving the partition
+Table structure:
 
+| Field | Description |
+--- | ---
+| `OwnerId` | ID of the SchemeShard serving the table.<br>Type: `Uint64`.<br>Key: `0`. |
+| `PathId` | ID of the SchemeShard path.<br>Type: `Uint64`.<br>Key: `1`. |
+| `PartIdx` | Partition sequence number.<br>Type: `Uint64`.<br>Key: `2`. |
+| `DataSize` | Approximate partition size in bytes.<br>Type: `Uint64`. |
+| `RowCount` | Approximate number of rows.<br>Type: `Uint64`. |
+| `IndexSize` | Partition index size in a tablet.<br>Type: `Uint64`. |
+| `CPUCores` | Double Instant value of load per partition (CPU share) |
+| `TabletId` | ID of the tablet serving the partition.<br>Type: `Uint64`. |
+| `Path` | Full path to the table.<br>Type: `Utf8`. |
+| `NodeId` | ID of the node that the partition is being served on.<br>Type: `Uint32`. |
+| `StartTime` | Last time when the tablet serving the partition was started.<br>Type: `Timestamp`. |
+| `AccessTime` | Last time when data from the partition was read.<br>Type: `Timestamp`. |
+| `UpdateTime` | Last time when data was written to the partition.<br>Type: `Timestamp`. |
+| `RowReads` | Number of point reads since the start of the partition tablet.<br>Type: `Uint64`. |
+| `RowUpdates` | Number of rows written since the start.<br>Type: `Uint64`. |
+| `RowDeletes` | Number of rows deleted since the start.<br>Type: `Uint64`. |
+| `RangeReads` | Number of row range reads since the start.<br>Type: `Uint64`. |
+| `RangeReadRows` | Number of rows read in the ranges since the start.<br>Type: `Uint64`. |
+| `InFlightTxCount` | Number of in-flight transactions.<br>Type: `Uint64`. |
+| `ImmediateTxCompleted` | Number of one-shard transactions completed since the start.<br>Type: `Uint64`. |
+| `CoordinatedTxCompleted` | Number of coordinated transactions completed since the start.<br>Type: `Uint64`. |
+| `TxRejectedByOverload` | Number of transactions rejected due to overload (since the start).<br>Type: `Uint64`. |
+| `TxRejectedByOutOfStorage` | Number of transactions rejected due to lack of storage space (since the start).<br>Type: `Uint64`. |
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_example_yql.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_example_yql.md
index c37a4fbb4bb..af2330e85f4 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_example_yql.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_example_yql.md
@@ -1,28 +1,27 @@
-Top 10 queries for the last 6 hours by the total number of rows updated per minute
+Top 10 queries for the last 6 hours by the total number of rows updated per minute:
 
-  ```sql
-  SELECT
-      SumUpdateRows,
-      Count,
-      QueryText,
-      IntervalEnd
-  FROM `.sys/query_metrics_one_minute`
-  ORDER BY SumUpdateRows DESC LIMIT 10
-  ```
+> ```sql
+> SELECT
+>     SumUpdateRows,
+>     Count,
+>     QueryText,
+>     IntervalEnd
+> FROM `.sys/query_metrics_one_minute`
+> ORDER BY SumUpdateRows DESC LIMIT 10
+> ```
 
-  Recent queries that read the most bytes per minute:
-
-  ```sql
-  SELECT
-      IntervalEnd,
-      SumReadBytes,
-      MinReadBytes,
-      SumReadBytes / Count as AvgReadBytes,
-      MaxReadBytes,
-      QueryText
-  FROM `.sys/query_metrics_one_minute`
-  WHERE SumReadBytes > 0
-  ORDER BY IntervalEnd DESC, SumReadBytes DESC
-  LIMIT 100
-  ```
+Recent queries that read the most bytes per minute:
 
+> ```sql
+> SELECT
+>     IntervalEnd,
+>     SumReadBytes,
+>     MinReadBytes,
+>     SumReadBytes / Count as AvgReadBytes,
+>     MaxReadBytes,
+>     QueryText
+> FROM `.sys/query_metrics_one_minute`
+> WHERE SumReadBytes > 0
+> ORDER BY IntervalEnd DESC, SumReadBytes DESC
+> LIMIT 100
+> ```
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_header.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_header.md
index 4c5d104988b..68711228cb9 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_header.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/query_metrics_header.md
@@ -1,46 +1,48 @@
 ## Query details {#query-metrics}
 
-* **query_metrics_one_minute**
+The following system view stores detailed information about queries:
 
-Detailed information about queries, broken down by minute. Each table row contains information about a set of queries with identical text that were made during one minute. The table fields provide the minimum, maximum, and total values for each query metric tracked. Within the interval, queries are sorted in descending order of the total CPU time used.
+* `query_metrics_one_minute`: Data is split into one-minute intervals, contains up to 256 queries for the last 6 hours.
 
-Table structure:
-
-| **Field** | **Type** | **Key** | **Value** |
-| --- | --- | --- | --- |
-| IntervalEnd | Timestamp | 0 | Closing time of a minute interval |
-| Rank | Uint32 | 1 | Query rank per interval (by the SumCPUTime field) |
-| QueryText | Utf8 |  | Query text |
-| Count | Uint64 |  | Number of query runs |
-| SumDuration | Interval |  | Total query duration |
-| MinDuration | Interval |  | Minimum query duration |
-| MaxDuration | Interval |  | Maximum query duration |
-| SumCPUTime | Uint64 |  | Total CPU time used |
-| MinCPUTime | Uint64 |  | Minimum CPU time used |
-| MaxCPUTime | Uint64 |  | Maximum CPU time used |
-| SumReadRows | Uint64 |  | Total number of rows read |
-| MinReadRows | Uint64 |  | Minimum number of rows read |
-| MaxReadRows | Uint64 |  | Maximum number of rows read |
-| SumReadBytes | Uint64 |  | Total number of bytes read |
-| MinReadBytes | Uint64 |  | Minimum number of bytes read |
-| MaxReadBytes | Uint64 |  | Maximum number of bytes read |
-| SumUpdateRows | Uint64 |  | Total number of rows updated |
-| MinUpdateRows | Uint64 |  | Minimum number of rows updated |
-| MaxUpdateRows | Uint64 |  | Maximum number of rows updated |
-| SumUpdateBytes | Uint64 |  | Total number of bytes updated |
-| MinUpdateBytes | Uint64 |  | Minimum number of bytes updated |
-| MaxUpdateBytes | Uint64 |  | Maximum number of bytes updated |
-| SumDeleteRows | Uint64 |  | Total number of rows deleted |
-| MinDeleteRows | Uint64 |  | Minimum number of rows deleted |
-| MaxDeleteRows | Uint64 |  | Maximum number of rows deleted |
-| SumRequestUnits | Uint64 |  | Total number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used |
-| MinRequestUnits | Uint64 |  | Minimum number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used |
-| MaxRequestUnits | Uint64 |  | Maximum number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used |
+Each table row contains information about a set of queries with identical text that were made during one minute. The table fields provide the minimum, maximum, and total values for each query metric tracked. Within the interval, queries are sorted in descending order of the total CPU time used.
 
 Restrictions:
 
 * Query text limit is 4 KB.
-* The table contains the history for the last 6 hours.
-* Within the interval, information is provided for no more than 256 different queries.
 * Statistics may be incomplete if the database is under heavy load.
 
+Table structure:
+
+| Field | Description |
+---|---
+| `IntervalEnd` | The end of a one-minute interval.<br>Type: `Timestamp`.<br>Key: `0`. |
+| `Rank` | Query rank within an interval (by the SumCPUTime field).<br>Type: `Uint32`.<br>Key: `1`. |
+| `QueryText` | Query text.<br>Type: `Utf8`. |
+| `Count` | Number of query runs.<br>Type: `Uint64`. |
+| `SumDuration` | Total duration of queries.<br>Type: `Interval`. |
+| `Count` | Number of query runs.<br>Type: `Uint64`. |
+| `SumDuration` | Total duration of queries.<br>Type: `Interval`. |
+| `MinDuration` | Minimum query duration.<br>Type: `Interval`. |
+| `MaxDuration` | Maximum query duration.<br>Type: `Interval`. |
+| `SumCPUTime` | Total CPU time used.<br>Type: `Uint64`. |
+| `MinCPUTime` | Minimum CPU time used.<br>Type: `Uint64`. |
+| `MaxCPUTime` | Maximum CPU time used.<br>Type: `Uint64`. |
+| `SumReadRows` | Total number of rows read.<br>Type: `Uint64`. |
+| `MinReadRows` | Minimum number of rows read.<br>Type: `Uint64`. |
+| `MaxReadRows` | Maximum number of rows read.<br>Type: `Uint64`. |
+| `SumReadBytes` | Total number of bytes read.<br>Type: `Uint64`. |
+| `MinReadBytes` | Minimum number of bytes read.<br>Type: `Uint64`. |
+| `MaxReadBytes` | Maximum number of bytes read.<br>Type: `Uint64`. |
+| `SumUpdateRows` | Total number of rows written.<br>Type: `Uint64`. |
+| `MinUpdateRows` | Minimum number of rows written.<br>Type: `Uint64`. |
+| `MaxUpdateRows` | Maximum number of rows written.<br>Type: `Uint64`. |
+| `SumUpdateBytes` | Total number of bytes written.<br>Type: `Uint64`. |
+| `MinUpdateBytes` | Minimum number of bytes written.<br>Type: `Uint64`. |
+| `MaxUpdateBytes` | Maximum number of bytes written.<br>Type: `Uint64`. |
+| `SumDeleteRows` | Total number of rows deleted.<br>Type: `Uint64`. |
+| `MinDeleteRows` | Minimum number of rows deleted.<br>Type: `Uint64`. |
+| `MaxDeleteRows` | Maximum number of rows deleted.<br>Type: `Uint64`. |
+| `SumRequestUnits` | Total number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used.<br>Type: `Uint64`. |
+| `MinRequestUnits` | Minimum number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used.<br>Type: `Uint64`. |
+| `MaxRequestUnits` | Maximum number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used.<br>Type: `Uint64`. |
+
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_example_yql.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_example_yql.md
index e21ca67b6fc..91134b6ab9a 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_example_yql.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_example_yql.md
@@ -1,31 +1,30 @@
-Top queries by execution time for the last minute when queries were made
+Top queries by execution time for the last minute when queries were made:
 
-  ```sql
-  PRAGMA AnsiInForEmptyOrNullableItemsCollections;
-  $last = (
-      SELECT
-          MAX(IntervalEnd)
-      FROM `.sys/top_queries_by_duration_one_minute`
-  );
-  SELECT
-      IntervalEnd,
-      Rank,
-      QueryText,
-      Duration
-  FROM `.sys/top_queries_by_duration_one_minute`
-  WHERE IntervalEnd IN $last
-  ```
+> ```sql
+> PRAGMA AnsiInForEmptyOrNullableItemsCollections;
+> $last = (
+>     SELECT
+>         MAX(IntervalEnd)
+>     FROM `.sys/top_queries_by_duration_one_minute`
+> );
+> SELECT
+>     IntervalEnd,
+>     Rank,
+>     QueryText,
+>     Duration
+> FROM `.sys/top_queries_by_duration_one_minute`
+> WHERE IntervalEnd IN $last
+> ```
 
-  Queries that read the most bytes, broken down by minute
-
-  ```sql
-  SELECT
-      IntervalEnd,
-      QueryText,
-      ReadBytes,
-      ReadRows,
-      Partitions
-  FROM `.sys/top_queries_by_read_bytes_one_minute`
-  WHERE Rank = 1
-  ```
+Queries that read the most bytes, broken down by minute:
 
+> ```sql
+> SELECT
+>     IntervalEnd,
+>     QueryText,
+>     ReadBytes,
+>     ReadRows,
+>     Partitions
+> FROM `.sys/top_queries_by_read_bytes_one_minute`
+> WHERE Rank = 1
+> ```
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_header.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_header.md
index 89cc7f346d6..b9eee3210c3 100644
--- a/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_header.md
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/tops_header.md
@@ -1,55 +1,50 @@
 ## Top queries {#top-queries}
 
-* **top_queries_by_duration_one_minute**
-* **top_queries_by_duration_one_hour**
-* **top_queries_by_read_bytes_one_minute**
-* **top_queries_by_read_bytes_one_hour**
-* **top_queries_by_cpu_time_one_minute**
-* **top_queries_by_cpu_time_one_hour**
+The following system views store data for analyzing the flow of user queries:
 
-A group of system views for analyzing the flow of user queries. They let you see a time-limited query history divided into intervals. Within a single interval, the top 5 queries by a specific metric are saved. Currently, minute and hour intervals are available, and the top list can be made based on the total query execution time (the slowest), the number of bytes read from the table (the widest), and the total CPU time used (the heaviest).
+* `top_queries_by_duration_one_minute`: Data is split into one-minute intervals, contains Top 5 queries with the maximum total execution time for the last 6 hours.
+* `top_queries_by_duration_one_hour`: Data is split into one-hour intervals, contains Top 5 queries with the maximum total execution time for the last 2 weeks.
+* `top_queries_by_read_bytes_one_minute`: Data is split into one-minute intervals, contains Top 5 queries with the maximum number of bytes read from the table for the last 6 hours.
+* `top_queries_by_read_bytes_one_hour`: Data is split into one-hour intervals, contains Top 5 queries with the maximum number of bytes read from the table for the last 2 weeks.
+* `top_queries_by_cpu_time_one_minute`: Data is split into one-minute intervals, contains Top 5 queries with the maximum CPU time used for the last 6 hours.
+* ` top_queries_by_cpu_time_one_hour`: Data is split into one-hour intervals, contains Top 5 queries with the maximum CPU time used for the last 2 weeks.
 
 Different runs of a query with the same text are deduplicated. The top list contains information about a specific run with the maximum value of the corresponding query metric within a single interval.
 
-Fields that provide information about the used CPU time (...CPUTime) are expressed in ms.
-
-Table structure:
-
-| **Field** | **Type** | **Key** | **Value** |
-| --- | --- | --- | --- |
-| IntervalEnd | Timestamp | 0 | Closing time of a minute or hour interval |
-| Rank | Uint32 | 1 | Rank of a top query |
-| RequestUnits | Uint64 |  | Number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used |
-| QueryText | Utf8 |  | Query text |
-| Duration | Interval |  | Total time of query execution |
-| EndTime | Timestamp |  | Query execution end time |
-| Type | String |  | Query type (data, scan, or script) |
-| ReadRows | Uint64 |  | Number of rows read |
-| ReadBytes | Uint64 |  | Number of bytes read |
-| UpdateRows | Uint64 |  | Number of rows updated |
-| UpdateBytes | Uint64 |  | Number of bytes updated |
-| DeleteRows | Uint64 |  | Number of rows deleted |
-| DeleteBytes | Uint64 |  | Number of bytes deleted |
-| Partitions | Uint64 |  | Number of table partitions used during query execution |
-| UserSID | String |  | User security ID |
-| ParametersSize | Uint64 |  | Size of query parameters in bytes |
-| CompileDuration | Interval |  | Query compile duration |
-| FromQueryCache | Bool |  | Shows whether the cache of prepared queries was used |
-| CPUTime | Uint64 |  | Total CPU time used to execute the query (ms) |
-| ShardCount | Uint64 |  | Number of shards used during query execution |
-| SumShardCPUTime | Uint64 |  | Total CPU time used in shards |
-| MinShardCPUTime | Uint64 |  | Minimum CPU time used in shards |
-| MaxShardCPUTime | Uint64 |  | Maximum CPU time used in shards |
-| ComputeNodesCount | Uint64 |  | Number of compute nodes used during query execution |
-| SumComputeCPUTime | Uint64 |  | Total CPU time used in compute nodes |
-| MinComputeCPUTime | Uint64 |  | Minimum CPU time used in compute nodes |
-| MaxComputeCPUTime | Uint64 |  | Maximum CPU time used in compute nodes |
-| CompileCPUTime | Uint64 |  | CPU time used to compile a query |
-| ProcessCPUTime | Uint64 |  | CPU time used for overall query handling |
-
-Restrictions:
-
-* Query text limit is 4 KB.
-* Tables with minute intervals contain the history for the last 6 hours.
-* Tables with hourly intervals contain the history for the last 2 weeks.
-
+Fields that provide information about the used CPU time (...`CPUTime`) are expressed in microseconds.
+
+Query text limit is 4 KB.
+
+All tables have the same set of fields:
+
+| Field | Description |
+--- | ---
+| `IntervalEnd` | The end of a one-minute or one-hour interval.<br>Type: `Timestamp`.<br>Key: `0`. |
+| `Rank` | Rank of a top query.<br>Type: `Uint32`.<br>Key: `1`. |
+| `RequestUnits` | Number of [RequestUnits](../../../concepts/serverless_and_dedicated.md#serverless-options) used. |
+| `QueryText` | Query text.<br>Type: `Utf8`. |
+| `Duration` | Total query execution time.<br>Type: `Interval`. |
+| `EndTime` | Query execution end time. <br>Type: `Timestamp`. |
+| `Type` | Query type (data, scan, or script).<br>Type: `String`. |
+| `ReadRows` | Number of rows read.<br>Type: `Uint64`. |
+| `ReadBytes` | Number of bytes read.<br>Type: `Uint64`. |
+| `UpdateRows` | Number of rows written.<br>Type: `Uint64`. |
+| `UpdateBytes` | Number of bytes written.<br>Type: `Uint64`. |
+| `DeleteRows` | Number of rows deleted.<br>Type: `Uint64`. |
+| `DeleteBytes` | Number of bytes deleted.<br>Type: `Uint64`. |
+| `Partitions` | Number of table partitions used during query execution.<br>Type: `Uint64`. |
+| `UserSID` | User Security ID.<br>Type: `String`. |
+| `ParametersSize` | Size of query parameters in bytes.<br>Type: `Uint64`. |
+| `CompileDuration` | Duration of query compilation.<br>Type: `Interval`. |
+| `FromQueryCache` | Shows whether the cache of prepared queries was used.<br>Type: `Bool`. |
+| `CPUTime` | Total CPU time used to execute the query (microseconds).<br>Type: `Uint64`. |
+| `ShardCount` | Number of shards used during query execution.<br>Type: `Uint64`. |
+| `SumShardCPUTime` | Total CPU time used in shards.<br>Type: `Uint64`. |
+| `MinShardCPUTime` | Minimum CPU time used in shards.<br>Type: `Uint64`. |
+| `MaxShardCPUTime` | Maximum CPU time used in shards.<br>Type: `Uint64`. |
+| `ComputeNodesCount` | Number of compute nodes used during query execution.<br>Type: `Uint64`. |
+| `SumComputeCPUTime` | Total CPU time used in compute nodes.<br>Type: `Uint64`. |
+| `MinComputeCPUTime` | Minimum CPU time used in compute nodes.<br>Type: `Uint64`. |
+| `MaxComputeCPUTime` | Maximum CPU time used in compute nodes.<br>Type: `Uint64`. |
+| `CompileCPUTime` | CPU time used to compile a query.<br>Type: `Uint64`. |
+| `ProcessCPUTime` | CPU time used for overall query handling.<br>Type: `Uint64`. |
diff --git a/ydb/docs/en/core/troubleshooting/system_views_db.md b/ydb/docs/en/core/troubleshooting/system_views_db.md
index f111ba0dc43..0c8c26a7590 100644
--- a/ydb/docs/en/core/troubleshooting/system_views_db.md
+++ b/ydb/docs/en/core/troubleshooting/system_views_db.md
@@ -7,5 +7,3 @@
 {% include [query_metrics.md](_includes/system_views/query_metrics.md) %}
 
 {% include [top-overload-partitions.md](_includes/system_views/top-overload-partitions.md) %}
-
-{% include [notes.md](_includes/system_views/notes.md) %}