rancher / rancher/support-bundle-kit
[Feature] optionally collect profiling data
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 43
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 6
Description
The current implementation of the support bundle contains more or less only the cluster state and logs. This is insufficient to debug some types of faults like unexpected high memory consumption or performance problems. These problems may also only occur in long-running clusters or at customer sites, making them hard to reproduce in development/test setups.
To aide debugging such problems, the support bundle should have an additional optional capability to collect profiling data from certain pods similar to the script here: https://github.com/rancherlabs/support-kb/wiki/One-Liners#rancher-profile-collection-script
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Rancher profile collection script linked in the issue and the repository's support-bundle generation entry points. Determine how profiling should be made optional and limited to selected pods; done means the support bundle can collect that data without changing the default bundle behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100