Brohammad / Brohammad/VoxForge
OpenTelemetry collector compose profile
- Dominant language
- Python
- Stars
- 4
- Forks
- 1
- Avg merge
- 5d 13m
- Merged PRs (30d)
- 10
Description
## Summary
App can export via `OTEL_EXPORTER_OTLP_ENDPOINT`. There is no bundled collector. Roadmap v1.2: OTel collector compose profile.
## Context
- `docs/deployment/operations.md` Observability section
- `docs/architecture/observability.md`
- Grafana/Prometheus already optional in compose
## Scope
- [ ] Optional profile: otel-collector receiving OTLP, exporting to logging or Prometheus remote
- [ ] Example env pointing the app at the collector
- [ ] Short doc: when to use collector vs scraping `/api/v1/metrics`
- [ ] Not enabled by default on 2GB VPS
## Out of scope
Hosted vendor backends (Honeycomb, Tempo Cloud) as required deps.
Contributor guide
Research direction
Read docs/deployment/operations.md and docs/architecture/observability.md, then inspect the existing compose configuration for the optional Grafana/Prometheus services. Implement an optional otel-collector profile, add an example app endpoint environment setting, and document collector use versus scraping /api/v1/metrics. Done means it is not enabled by default and the documented profile supports the requested OTLP flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, prometheus, python
- Domain
- devops, documentation, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100