Improve support for OTEL metrics collection
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Right now, the OTEL metrics support is limited to API pods, and is implemented by each API pod getting an OTEL collector sidecar. This means metrics from only API pods get collected. Content and Worker pods also emit metrics, and they are missed.
Describe the solution you'd like
What if instead of a sidecar pattern, there is a dedicated OTEL collector deployment to which all the pods send their metrics? Was there a specific reason we went with the sidecar pattern, and having N number of OTEL collector containers, instead of a single one?
If we prefer to stick to the sidecar pattern, we need to bring in those sidecars to content and worker pods also so metrics from them can be collected.
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 existing OTEL sidecar configuration for API pods and the deployment definitions for content and worker pods. Compare the sidecar and dedicated-collector approaches, then define which deployment model should collect metrics from all three pod types and how completion will be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100