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
147089: db-console: add client side hot range filtering by node r=angles-n-daemons a=angles-n-daemons
db-console: add client side hot range filtering by node
Loading the hot ranges page is a performance intensive operation in large clusters, due to the fact the a cluster fanout is required to gather the information. Despite having a node filter within the component, the filtering has historically been applied after the api has responded with the full cluster's information.
This change moves the filtering of the nodes to the back end, and cleans up some of how the filters are organized. It also merges the uses of the NodeRegionSelector so that it can be shared between the Databases and Hot Ranges pages.
Fixes: #143528
Epic: CRDB-43150
Release note (ui change): Moves the hot ranges node filter out of the primary filter container in the hot ranges page, and applies the filtering on the backend.
147439: ui: surface SQL commenter query tags in insights r=angles-n-daemons a=angles-n-daemons
This commit adds support for displaying SQL commenter query tags in the CockroachDB DB Console insights UI, addressing GitHub issue #146664.
Changes:
- Add query_tags to statement insights API response
- Update TypeScript types to include queryTags field
- Add Query Tags column to statement insights table (hidden by default)
- Display query tags on statement insight detail pages
- Add proper column titles and tooltips for query tags
The query tags were already being stored in the backend execution insights tables by PR #145435. This change surfaces that data in the frontend UI, allowing users to correlate query performance with application context provided via SQL commenter tags.
Fixes#146664
Release note (ui change): The DB Console insights page now displays SQL commenter query tags for statement executions. Query tags provide application context (such as application name, user ID, or feature flags) embedded in SQL comments using the sqlcommenter format. This information can help correlate slow query performance with specific application state. The Query Tags column is available in the statement insights table but hidden by default - it can be enabled via the Columns selector.
🤖 Generated with [Claude Code](https://claude.ai/code)
147447: ui: fix statement activity timepicker for sub-hour ranges r=angles-n-daemons a=angles-n-daemons
ui: fix statement activity timepicker for sub-hour ranges
This commit fixes a bug where the statement activity time picker wasn't working correctly with time ranges less than an hour when sql.stats.aggregation.interval is set to values smaller than 1h.
The issue was that API calls were using toRoundedDateRange() which rounds timestamps to hour boundaries instead of toDateRange() which uses the exact selected time range. This prevented sub-hour time ranges from working properly even when the aggregation interval supported them.
Changed the following components to use toDateRange():
- StatementsPage
- TransactionsPage
- TransactionDetails
- StatementDetails selectors
- IndexDetails API
Fixes#145430
Epic: None
Release note (bug fix): Fixed statement activity page time picker to work correctly with time ranges less than an hour when sql.stats.aggregation.interval is configured to sub-hour values. Previously, selecting a 10-minute window would query for a full hour of data instead of the precise selected range.
147635: roachtest: fail fixture roachtests on failed backups r=msbutler a=kev-cao
Previously, if a backup job failed during the fixture roachtest, the test would continue along until the required number of backups completed. In this situation, if a backup failed for whatever reason, we would ignore it. This commit teaches the fixture roachtest to detect when a backup job has failed and to fail with the corresponding error.
Epic: None
Release note: None
Co-authored-by: Brian Dillmann <[email protected]>
Co-authored-by: Kevin Cao <[email protected]>
0 commit comments