Skip to content

db-console: Change "hot ranges" references to "top ranges" #147330

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
angles-n-daemons opened this issue May 27, 2025 · 1 comment · May be fixed by #147358
Open

db-console: Change "hot ranges" references to "top ranges" #147330

angles-n-daemons opened this issue May 27, 2025 · 1 comment · May be fixed by #147358
Assignees
@angles-n-daemons
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-observability

Comments

@angles-n-daemons
Copy link
Contributor

angles-n-daemons commented May 27, 2025 •
edited
Loading

As we're moving our terminology, we'd like to reflect that things we consider "hot ranges" may not actually be considered "hot", rather they're the top ranges in the cluster by some measure.

With this idea, we aim to rename parts of the UI which reference "hot ranges" to use the phrase "top ranges", so that they can be more accurately understood.

Jira issue: CRDB-51003
Epic: CRDB-43150
@angles-n-daemons angles-n-daemons added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label May 27, 2025
@blathers-crl blathers[crl]
Copy link

blathers-crl bot commented May 27, 2025

Hi @angles-n-daemons, please add branch-* labels to identify which branch(es) this C-bug affects.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@angles-n-daemons angles-n-daemons self-assigned this May 27, 2025
angles-n-daemons added a commit to angles-n-daemons/cockroach that referenced this issue May 27, 2025
@angles-n-daemons
db-console: move "hot ranges" page to "top ranges"
044f11c 
Previously, the UI referred to high-activity ranges as "hot ranges",
which implied they were necessarily experiencing high load or activity.
This was inadequate because ranges shown may simply be the highest by
some measure (QPS, CPU usage, etc.) without being truly "hot".

To address this, this patch renames the "hot ranges" page and related
UI components to "top ranges" to more accurately reflect that these
are the top-ranked ranges by various metrics rather than necessarily
experiencing high activity.

Release note (ui change): The "Hot Ranges" page in the DB Console has
been renamed to "Top Ranges" to better reflect that it shows the
highest-ranked ranges by various metrics, not necessarily ranges
experiencing high activity.

Fixes cockroachdb#147330
Epic: CRDB-43150

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@angles-n-daemons angles-n-daemons linked a pull request May 27, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@angles-n-daemons angles-n-daemons

Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-observability
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

db-console: move "hot ranges" page to "top ranges" angles-n-daemons/cockroach
1 participant
@angles-n-daemons