DOC-13913 Product Change- PR #147778 - release-25.2: db-console: add client side hot range filtering by node #19756
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r hot ranges section.
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
angles-n-daemons
approved these changes
Jun 18, 2025
mikeCRL
requested changes
Jun 23, 2025
| @@ -15,9 +15,27 @@ When optimizing or troubleshooting statement performance, this page can help you | |||
|
|
|||
| 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. | |||
|
|
|||
| ## Select nodes | |||
|
|
|||
| In the **Select Nodes** filter, choose one or more nodes with high activity, such as high CPU usage, to investigate potential hotspots. Filtering fewer nodes can help identify the hottest ranges more quickly and improve page load time. | |||
There was a problem hiding this comment.
Suggested change
| In the **Select Nodes** filter, choose one or more nodes with high activity, such as high CPU usage, to investigate potential hotspots. Filtering fewer nodes can help identify the hottest ranges more quickly and improve page load time. | |
| 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. |
If I understand your intended meaning correctly, "selecting" or "displaying" [fewer nodes] is much clearer to me than "filtering", which I find a little ambiguous in this context.
Even so, I'm probably not clear enough on how/why "Filtering fewer nodes can help identify the hottest ranges more quickly"—is it just because the data loads more quickly, or something to do with the user (e.g. less distracted with irrelevant data)? I'm not saying we must spell it all out completely, but perhaps it's a bit too ambiguous as-is?
| ## Filter hot ranges | ||
|
|
||
| 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. | ||
| After [selecting nodes](#select-nodes), use the **Filter** menu to filter the [hot ranges list](#hot-ranges-list) by any combination of database, table, index, or store ID. |
There was a problem hiding this comment.
Not sure if you can select multiple databases, tables, indexes, or store IDs, but if so, I think these should be pluralized.
| 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. | ||
| After [selecting nodes](#select-nodes), use the **Filter** menu to filter the [hot ranges list](#hot-ranges-list) by any combination of database, table, index, or store ID. | ||
|
|
||
| In the **Databases** dropdown list, filter by zero or more databases. |
There was a problem hiding this comment.
Suggested change
| In the **Databases** dropdown list, filter by zero or more databases. | |
| In the **Databases** dropdown list, you can choose to filter by specific databases (optional). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes DOC-13913 DOC-13902
In ui-hot-ranges-page.md, added Select nodes section and update Filter hot ranges section.
Rendered Preview
Select nodes