DOC-14270 Product Change- PR #149713 - db-console: change the name of the "Hot Ranges" page to "Top Ranges"

- Renamed “Hot Ranges” to “Top Ranges” and adjusted related references and headings.
- ui-hot-ranges-page.md renamed to ui-top-ranges-page.md and added redirect.
- Updated all links to point to the new filename.

Author: florence-crl

src/current/_data/redirects.yml

@@ -521,6 +521,10 @@
   sources: ['admin-ui-storage-dashboard.md']
   versions: ['v20.2', 'v21.1']
 
+- destination: ui-top-ranges-page.md
+  sources: ['ui-hot-ranges-page.md']
+  versions: ['v25.4']
+
 - destination: use-a-local-file-server-for-bulk-operations.md
   sources: ['create-a-file-server.md']
   versions: ['v20.2', 'v21.1']

src/current/_includes/v25.4/sidebar-data/self-hosted-deployments.json

@@ -639,9 +639,9 @@
                         ]
                       },
                       {
-                        "title": "Hot Ranges Page",
+                        "title": "Top Ranges Page",
                         "urls": [
-                          "/${VERSION}/ui-hot-ranges-page.html"
+                          "/${VERSION}/ui-top-ranges-page.html"
                         ]
                       },
                       {

src/current/v25.4/critical-log-messages.md

@@ -213,7 +213,7 @@ toc: true
     - **Impact**: May cause higher latencies for operations that need to write to that range.
     - **Action**: Identify if the range has a disproportionate amount of load and mitigate appropriately, such as splitting ranges manually or using a hash-sharded index.
     - **Related metrics**: NONE
-    - **See also**: [Hot Ranges page]({% link {{ page.version.version }}/ui-hot-ranges-page.md %})
+    - **See also**: [Top Ranges page]({% link {{ page.version.version }}/ui-top-ranges-page.md %})
 
 ## Data Availability
 

src/current/v25.4/performance-recipes.md

@@ -39,7 +39,7 @@ This section describes how to use CockroachDB commands and dashboards to identif
   </tr>
   <tr>
     <td><ul>
-      <li>The <b>Hot Ranges</b> page (DB Console) displays a higher-than-expected QPS for a range.</li>
+      <li>The <b>Top Ranges</b> page (DB Console) displays a higher-than-expected QPS for a range.</li>
       <li>The <b>Key Visualizer</b> (DB Console) shows ranges with much higher-than-average write rates for the cluster.</li>
     </ul></td>
     <td><ul><li>Your cluster has <a href="{% link {{ page.version.version }}/understand-hotspots.md %}">hotspots</a>.</li></ul></td>
@@ -191,10 +191,10 @@ For a detailed explanation of hotspot causes and mitigation strategies, refer to
 #### Indicators that your cluster has hotspots
 
 - The **CPU Percent** graph on the [**Hardware**]({% link {{ page.version.version }}/ui-hardware-dashboard.md %}) and [**Overload**]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) dashboards (DB Console) shows spikes in CPU usage.
-- The **Hot Ranges** list on the [**Hot Ranges** page]({% link {{ page.version.version }}/ui-hot-ranges-page.md %}) (DB Console) displays a higher-than-expected QPS for a range.
+- The **Top Ranges** list on the [**Top Ranges** page]({% link {{ page.version.version }}/ui-top-ranges-page.md %}) (DB Console) displays a higher-than-expected QPS for a range.
 - The [**Key Visualizer**]({% link {{ page.version.version }}/ui-key-visualizer.md %}) (DB Console) shows [ranges with much higher-than-average write rates]({% link {{ page.version.version }}/ui-key-visualizer.md %}#identifying-hotspots) for the cluster.
 
-If you find hotspots, use the [**Range Report**]({% link {{ page.version.version }}/ui-hot-ranges-page.md %}#range-report) and [**Key Visualizer**]({% link {{ page.version.version }}/ui-key-visualizer.md %}) to identify the ranges with excessive traffic. Then take steps to [reduce hotspots](#reduce-hotspots).
+If you find hotspots, use the [**Range Report**]({% link {{ page.version.version }}/ui-top-ranges-page.md %}#range-report) and [**Key Visualizer**]({% link {{ page.version.version }}/ui-key-visualizer.md %}) to identify the ranges with excessive traffic. Then take steps to [reduce hotspots](#reduce-hotspots).
 
 #### Reduce hotspots
 

src/current/v25.4/query-behavior-troubleshooting.md

@@ -329,7 +329,7 @@ A [*hot node*]({% link {{ page.version.version }}/understand-hotspots.md %}#hot-
   - [**Hardware** dashboard]({% link {{ page.version.version }}/ui-hardware-dashboard.md %}#cpu-percent) > **CPU Percent** graph
   - [**SQL** dashboard]({% link {{ page.version.version }}/ui-sql-dashboard.md %}#connection-latency-99th-percentile) > **SQL Connections** graph
   - [**Hardware** dashboard]({% link {{ page.version.version }}/ui-hardware-dashboard.md %}#disk-ops-in-progress) > **Disk IOPS in Progress** graph
-- Open the [**Hot Ranges** page]({% link {{ page.version.version }}/ui-hot-ranges-page.md %}) and check for ranges with significantly higher QPS on any nodes.
+- Open the [**Top Ranges** page]({% link {{ page.version.version }}/ui-top-ranges-page.md %}) and check for ranges with significantly higher QPS on any nodes.
 
 #### Solution
 

src/current/v25.4/ui-key-visualizer.md

@@ -98,6 +98,6 @@ The following image shows the Key Visualizer highlighting a [full-table scan]({%
 
 - [DB Console Overview]({% link {{ page.version.version }}/ui-overview.md %})
 - [Troubleshooting Overview]({% link {{ page.version.version }}/troubleshooting-overview.md %})
-- [Hot Ranges Page]({% link {{ page.version.version }}/ui-hot-ranges-page.md %})
+- [Top Ranges Page]({% link {{ page.version.version }}/ui-top-ranges-page.md %})
 - [Reduce Hotspots]({% link {{ page.version.version }}/understand-hotspots.md %}#reduce-hotspots)
 - [Support Resources]({% link {{ page.version.version }}/support-resources.md %})

src/current/v25.4/ui-overview.md

@@ -122,7 +122,7 @@ DB Console area | System-level privilege | Privileged information
 [Transactions]({% link {{ page.version.version }}/ui-transactions-page.md %}) | [`VIEWACTIVITY`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivity) or [`VIEWACTIVITYREDACTED`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivityredacted) | Transactions
 [Sessions]({% link {{ page.version.version }}/ui-sessions-page.md %}) | [`VIEWACTIVITY`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivity) or [`VIEWACTIVITYREDACTED`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivityredacted) | Sessions
 [Insights]({% link {{ page.version.version }}/ui-insights-page.md %}) | [`VIEWACTIVITY`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivity) or [`VIEWACTIVITYREDACTED`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivityredacted) | Insights
-[Hot Ranges]({% link {{ page.version.version }}/ui-hot-ranges-page.md %}) | [`VIEWCLUSTERMETADATA`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewclustermetadata) | Ranges
+[Top Ranges]({% link {{ page.version.version }}/ui-top-ranges-page.md %}) | [`VIEWCLUSTERMETADATA`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewclustermetadata) | Ranges
 [Jobs]({% link {{ page.version.version }}/ui-jobs-page.md %}) | [`VIEWJOB`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewjob) | Jobs
 [Advanced Debug]({% link {{ page.version.version }}/ui-debug-pages.md %}) | [`VIEWDEBUG`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewdebug) | Debugging and profiling endpoints
 [Advanced Debug > Problem Ranges]({% link {{ page.version.version }}/ui-debug-pages.md %}#reports) | [`VIEWCLUSTERMETADATA`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewclustermetadata) | Ranges

src/current/v25.4/ui-hot-ranges-page.md renamed to src/current/v25.4/ui-top-ranges-page.md

@@ -1,6 +1,6 @@
 ---
-title: Hot Ranges Page
-summary: The Hot Ranges page provides details about ranges receiving a high number of reads or writes.
+title: Top Ranges Page
+summary: The Top Ranges page provides details about the highest-ranked ranges by metrics such as reads, writes, QPS, and CPU.
 toc: true
 docs_area: reference.db_console
 ---
@@ -9,11 +9,11 @@ docs_area: reference.db_console
 On a secure cluster, this area of the DB Console can only be accessed by users belonging to the [`admin` role]({% link {{ page.version.version }}/security-reference/authorization.md %}#admin-role) or a SQL user with the [`VIEWCLUSTERMETADATA`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewclustermetadata) [system privilege]({% link {{ page.version.version }}/security-reference/authorization.md %}#supported-privileges) (or the legacy `VIEWACTIVITY` or `VIEWACTIVITYREDACTED` [role option]({% link {{ page.version.version }}/security-reference/authorization.md %}#role-options)) defined. The [`VIEWACTIVITY`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivity) or [`VIEWACTIVITYREDACTED`]({% link {{ page.version.version }}/security-reference/authorization.md %}#viewactivityredacted) [system privileges]({% link {{ page.version.version }}/security-reference/authorization.md %}#supported-privileges) **do not** grant access to this page.
 {{site.data.alerts.end}}
 
-The **Hot Ranges** page of the DB Console provides details about ranges receiving a high number of reads or writes. These are known as [*hot ranges*]({% link {{ page.version.version }}/understand-hotspots.md %}#hot-range).
+The **Top Ranges** page of the DB Console provides details about the highest-ranked ranges by metrics such as reads, writes, queries per second (QPS), and CPU. Ranges that rank highly by these measures may indicate [*hot ranges*]({% link {{ page.version.version }}/understand-hotspots.md %}#hot-range), but are not necessarily problematic.
 
 When optimizing or troubleshooting statement performance, this page can help you identify nodes, ranges, or tables that are experiencing [hotspots]({% link {{ page.version.version }}/understand-hotspots.md %}).
 
-To view this page, [access the DB Console]({% link {{ page.version.version }}/ui-overview.md %}#db-console-access) and click **Hot Ranges** in the left-hand navigation.
+To view this page, [access the DB Console]({% link {{ page.version.version }}/ui-overview.md %}#db-console-access) and click **Top Ranges** in the left-hand navigation.
 
 ## Select nodes
 
@@ -23,35 +23,35 @@ Selecting a region, such as `us-east1`, selects all nodes in that region.
 
 In the **Select Nodes** search box, enter numbers to search for specific node IDs. For example, in a cluster with 12 nodes, entering `1` returns checkboxes for node IDs `n1`, `n10`, `n11`, and `n12`. 
 
-Click **Apply** to view the [hot ranges list](#hot-ranges-list) for the selected nodes.
+Click **Apply** to view the [top ranges list](#top-ranges-list) for the selected nodes.
 
-## Filter hot ranges
+## Filter top ranges
 
-After [selecting nodes](#select-nodes), use the **Filter** menu to filter the [hot ranges list](#hot-ranges-list). You can choose to view all hot ranges across a specific table, index, store ID, and one or more databases.
+After [selecting nodes](#select-nodes), use the **Filter** menu to filter the [top ranges list](#top-ranges-list). You can choose to view top ranges across a specific table, index, store ID, and one or more databases.
 
 In the **Databases** dropdown list, you can choose to filter by specific databases (optional).
 
 In the **Table** and **Index** search boxes, enter the complete name of a table or index to return results. For example, in the [`movr` database]({% link {{ page.version.version }}/movr.md %}), search for the exact index name `users_pkey` to return results. Entering a partial index name, such as `user` or `users` returns no results.
 
 In the **Store ID** search box, enter numbers to search for specific store IDs. For example, in a cluster with 12 stores, entering `1` returns results for store IDs `1`, `10`, `11`, and `12`.
 
-Click **Apply** to view the filtered [hot ranges list](#hot-ranges-list).
+Click **Apply** to view the filtered [top ranges list](#top-ranges-list).
 
-## Hot ranges list
+## Top ranges list
 
-The **Hot ranges** list displays the ranges with the highest queries per second (QPS) from each node [`store`]({% link {{ page.version.version }}/architecture/storage-layer.md %}).
+The **Top ranges** list displays the ranges with the highest queries per second (QPS) from each node [`store`]({% link {{ page.version.version }}/architecture/storage-layer.md %}).
 
 {{site.data.alerts.callout_info}}
-Hot ranges are not necessarily problematic. Some ranges naturally experience higher QPS than others. For example, a range for a frequently accessed table will have a higher QPS.
+Top ranges are not necessarily problematic. Some ranges naturally experience higher QPS than others. For example, a range for a frequently accessed table will have a higher QPS.
 
 However, a significant increase in traffic can also indicate a *hotspot* on the range that should be reduced. For more information, refer to [Understand hotspots]({% link {{ page.version.version }}/understand-hotspots.md %}#hot-range).
 {{site.data.alerts.end}}
 
-To view the [Range Report](#range-report) for a hot range, click its range ID.
+To view the [Range Report](#range-report) for a top range, click its range ID.
 
 Parameter | Description
 ----------|------------
-Range ID | The ID of the hot range. Click the range ID to view the [Range Report](#range-report) for this range.
+Range ID | The ID of the top range. Click the range ID to view the [Range Report](#range-report) for this range.
 QPS | The total number of [`SELECT`]({% link {{ page.version.version }}/selection-queries.md %}), [`UPDATE`]({% link {{ page.version.version }}/update.md %}), [`INSERT`]({% link {{ page.version.version }}/insert.md %}), and [`DELETE`]({% link {{ page.version.version }}/delete.md %}) queries executed per second on this range. The per-second rate is averaged over the last 30 minutes.
 CPU | The total CPU time per second used in processing this range. The per-second rate is averaged over the last 30 minutes.
 Write (keys) | The total number of keys written per second on this range. The per-second rate is averaged over the last 30 minutes.
@@ -73,10 +73,10 @@ The **Range Report** is typically used for [advanced debugging]({% link {{ page.
 If your aim is to [reduce hotspots]({% link {{ page.version.version }}/understand-hotspots.md %}#reduce-hotspots), refer to the following fields:
 
 - `Key Range` shows the interval of the [key space]({% link {{ page.version.version }}/architecture/distribution-layer.md %}#range-descriptors) that is "hottest" (i.e., read by the processor). This is expressed as a span of key values.
-- `Lease Holder QPS` shows the queries executed per second on the node that holds the [range lease]({% link {{ page.version.version }}/architecture/replication-layer.md %}#leases). If a hot range is not properly using [load-based splitting]({% link {{ page.version.version }}/load-based-splitting.md %}), this will be greater than the value configured by the `kv.range_split.load_qps_threshold` [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) (`2500` by default).
+- `Lease Holder QPS` shows the queries executed per second on the node that holds the [range lease]({% link {{ page.version.version }}/architecture/replication-layer.md %}#leases). If a top range is not properly using [load-based splitting]({% link {{ page.version.version }}/load-based-splitting.md %}), this will be greater than the value configured by the `kv.range_split.load_qps_threshold` [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) (`2500` by default).
 
 ## See also
 
 - [Understand Hotspots]({% link {{ page.version.version }}/understand-hotspots.md %})
 - [Hash-sharded Indexes]({% link {{ page.version.version }}/hash-sharded-indexes.md %})
-- [Architecture Overview]({% link {{ page.version.version }}/architecture/overview.md %})
+- [Architecture Overview]({% link {{ page.version.version }}/architecture/overview.md %})

src/current/v25.4/understand-hotspots.md

@@ -41,7 +41,7 @@ The following image is a graph of [CPU Percent]({% link {{ page.version.version
 
 **Synonyms:** range hotspot
 
-A _hot range_ is one level down from the node hotspot. [Ranges]({% link {{ page.version.version }}/architecture/overview.md %}#range) are the smallest unit of data distribution, making them critical in troubleshooting hotspots. The [DB Console Hot Ranges page]({% link {{ page.version.version }}/ui-hot-ranges-page.md %}) provides details about ranges receiving a high number of reads or writes, which become an issue if they cause a [hot node](#hot-node).
+A _hot range_ is one level down from the node hotspot. [Ranges]({% link {{ page.version.version }}/architecture/overview.md %}#range) are the smallest unit of data distribution, making them critical in troubleshooting hotspots. The [DB Console Top Ranges page]({% link {{ page.version.version }}/ui-top-ranges-page.md %}) provides details about ranges receiving a high number of reads or writes, which become an issue if they cause a [hot node](#hot-node).
 
 A hot node is often caused by a single hot range. The system may split the hot range to redistribute the load ([load-based splitting]({% link {{ page.version.version }}/load-based-splitting.md %})) or the range may stay hot until it fills up and splits ([range size splitting]({% link {{ page.version.version }}/architecture/distribution-layer.md %}#range-splits)). In the second case, the split is likely the continuation of the hotspot (as shown in the [previous image for a hot node](#hotspots-figure-1)). If the system is unable to identify a good splitting point for a hot range (for example, in the case of a [row hotspot](#row-hotspot)), the hot range becomes a bottleneck.