Update Pyroscope metrics binders to handle pod lifecycle tracking environment variables
Open
Nobody has claimed this yet.
dotCMS : Containerization
dotCMS : Metrics
Priority : 3 Average
stale
Team : Platform
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Update Pyroscope profiling integration to utilize pod lifecycle tracking environment variables provided by Kubernetes Helm charts. This will enable better correlation of profiling data with pod replacement events and container lifecycle information.
Acceptance Criteria
- [Define what needs to be accomplished]
Additional Notes
[Any additional context or notes]
Contributor guide
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 locating the Pyroscope metrics binders and the Kubernetes Helm chart configuration that provides pod lifecycle tracking environment variables. Clarify which variables must be consumed and how profiling data should reflect pod replacement and container lifecycle events, then add focused validation for the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, java, kubernetes
- Domain
- devops, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100