Skip to content

Commit b31bf17

Browse files
authored
DOC-13913 Product Change- PR #147778 - release-25.2: db-console: add client side hot range filtering by node (#19756)
* In ui-hot-ranges-page.md, added Select Nodes section and update Filter hot ranges section. * Incorporated Mike’s feedback.
1 parent 16b81c3 commit b31bf17

File tree

2 files changed

+38
-2
lines changed

2 files changed

+38
-2
lines changed

src/current/v25.2/ui-hot-ranges-page.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,27 @@ When optimizing or troubleshooting statement performance, this page can help you
1515

1616
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.
1717

18+
## Select nodes
19+
20+
In the **Select Nodes** filter, choose one or more nodes with high activity, such as high CPU usage, to investigate potential hotspots. Selecting fewer nodes can help identify the hottest ranges more quickly and improve page load time.
21+
22+
Selecting a region, such as `us-east1`, selects all nodes in that region.
23+
24+
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`.
25+
26+
Click **Apply** to view the [hot ranges list](#hot-ranges-list) for the selected nodes.
27+
1828
## Filter hot ranges
1929

20-
Use the **Filter** menu to filter the [hot ranges list](#hot-ranges-list) on any combination of: node ID, store ID, database, table, index, or locality.
30+
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.
31+
32+
In the **Databases** dropdown list, you can choose to filter by specific databases (optional).
33+
34+
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.
35+
36+
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`.
37+
38+
Click **Apply** to view the filtered [hot ranges list](#hot-ranges-list).
2139

2240
## Hot ranges list
2341

src/current/v25.3/ui-hot-ranges-page.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,27 @@ When optimizing or troubleshooting statement performance, this page can help you
1515

1616
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.
1717

18+
## Select nodes
19+
20+
In the **Select Nodes** filter, choose one or more nodes with high activity, such as high CPU usage, to investigate potential hotspots. Selecting fewer nodes can help identify the hottest ranges more quickly and improve page load time.
21+
22+
Selecting a region, such as `us-east1`, selects all nodes in that region.
23+
24+
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`.
25+
26+
Click **Apply** to view the [hot ranges list](#hot-ranges-list) for the selected nodes.
27+
1828
## Filter hot ranges
1929

20-
Use the **Filter** menu to filter the [hot ranges list](#hot-ranges-list) on any combination of: node ID, store ID, database, table, index, or locality.
30+
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.
31+
32+
In the **Databases** dropdown list, you can choose to filter by specific databases (optional).
33+
34+
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.
35+
36+
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`.
37+
38+
Click **Apply** to view the filtered [hot ranges list](#hot-ranges-list).
2139

2240
## Hot ranges list
2341

0 commit comments

Comments
 (0)