Consider using OpenTelemetry collector presets for logs and container resource usage instead of kube-prometheus-stack
Open
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
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 linked opentelemetry-collector chart values.yaml section at lines 14-78 and comparing its collector presets with the repository's kube-prometheus-stack usage. Clarify which logs and container resource metrics must be covered, then define completion as adopting the appropriate presets without losing the existing coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100