You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
149372: roachtest: create backup fixtures for azure r=msbutler a=kev-cao
This commit adds support for backup fixtures on Azure blob storage buckets.
Epic: CRDB-52076Fixes: #149370
149704: db-console: add analytics to hot ranges page r=angles-n-daemons a=angles-n-daemons
db-console: add analytics to hot ranges page
So that we can better understand when the hot ranges page is being used, we want analytics on filters, sort and pagination state anytime the page is rendered.
This PR achieves this, by deduplicating with a useEffect.
Fixes: #144395
Epic: none
Release note: none
149713: db-console: change the name of the "Hot Ranges" page to "Top Ranges" r=angles-n-daemons a=angles-n-daemons
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: #147330
Epic: CRDB-43150
Release note (ui change): Changes the name of the "Hot Ranges" page to "Top Ranges".
Co-authored-by: Kevin Cao <[email protected]>
Co-authored-by: Brian Dillmann <[email protected]>
0 commit comments