[review][YDB] Перевод истории перегруженных шардовtranslation-history-of-overloaded-shards

translation-history-of-overloaded-shards

3 files changed, 32 insertions, 5 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 23021bd786..d9dc88cbf8 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,11 +1,12 @@
-# Database system tables
+# 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.
 
 Hereinafter, in the descriptions of available fields, the **Key** column contains the corresponding table's primary key field index.
 
-The article describes the following system tables:
+System views contain the following information:
 
-* [Partitions](#partitions)
-* [Top queries](#top-queries)
-* [Query details](#query-metrics)
+* [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).
diff --git a/ydb/docs/en/core/troubleshooting/_includes/system_views/top-overload-partitions.md b/ydb/docs/en/core/troubleshooting/_includes/system_views/top-overload-partitions.md
new file mode 100644
index 0000000000..9c10fb6d05
--- /dev/null
+++ b/ydb/docs/en/core/troubleshooting/_includes/system_views/top-overload-partitions.md
@@ -0,0 +1,24 @@
+## History of overloaded partitions {#top-overload-partitions}
+
+The following system views (tables) store the history of points in time when the load on individual DB table partitions was high:
+
+* `top_partitions_one_minute`: The data is split into one-minute intervals, contains the history for the last 6 hours.
+* `top_partitions_one_hour`: The data is split into one-hour intervals, contains the history for the last 2 weeks.
+
+These tables contain partitions with peak loads of more than 70% (`CPUCores` > 0.7). Partitions within a single interval are ranked by peak load value.
+
+Both 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` | Partition rank within an interval (by CPUCores).<br>Type: `Uint32`.<br>Key: `1`. |
+| `TabletId` | ID of the tablet serving the partition.<br>Type: `Uint64`. |
+| `Path` | Full path to the table.<br>Type: `Utf8`. |
+| `PeakTime` | Peak time within an interval.<br>Type: `Timestamp`. |
+| `CPUCores` | Peak load per partition (CPU share).<br>Type: `Double`. |
+| `NodeId` | ID of the node where the partition was located during the peak load.<br>Type: `Uint32`. |
+| `DataSize` | Approximate partition size, in bytes, during the peak load.<br>Type: `Uint64`. |
+| `RowCount` | Approximate row count during the peak load.<br>Type: `Uint64`. |
+| `IndexSize` | Partition index size per tablet during the peak load.<br>Type: `Uint64`. |
+| `InFlightTxCount` | The number of in-flight transactions during the peak load.<br>Type: `Uint32`. |
diff --git a/ydb/docs/en/core/troubleshooting/system_views_db.md b/ydb/docs/en/core/troubleshooting/system_views_db.md
index 68735978be..f111ba0dc4 100644
--- a/ydb/docs/en/core/troubleshooting/system_views_db.md
+++ b/ydb/docs/en/core/troubleshooting/system_views_db.md
@@ -6,4 +6,6 @@
 
 {% 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) %}