cockroachdb / cockroachdb/cockroach
Collect Hot Ranges information during critical cluster events in debug zip
Open
A-observability-inf
C-enhancement
C-escalation-improvement
O-support
P-3
T-supportability
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
Similar to the following [issue](https://github.com/cockroachdb/cockroach/issues/102616 ), we should collect Hot Ranges information in the debug zip during critical events.
Ideally this experience is similar to TSDump where we can easily upload hot ranges information into the console for SH troubleshooting.
Jira issue: CRDB-27563
Epic CRDB-32398
Contributor guide
Assessment
This issue has not been assessed yet.