homelab/stack
1
0
Fork 0
Code Issues 70 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

infra: deploy OTel Collector as fan-out layer in compose.yml #210

New Issue
Closed
opened 2026-03-24 23:50:07 +00:00 by kert · 2 comments
kert commented 2026-03-24 23:50:07 +00:00
Owner
Copy Link

Add OTel Collector service to route traces→Jaeger, metrics→Prometheus, logs→Loki.

Tasks

  • Add otel-collector service to compose.yml (image: otel/opentelemetry-collector-contrib:latest)
  • Create infra/otel/otel-collector.yml with receivers (OTLP gRPC 4317), processors (batch), exporters (otlp/jaeger, prometheus :8889, loki)
  • Network: observability (internal)
  • Add otel-collector:8889 to Prometheus scrape targets
  • Migrate Traefik, Nessie, Polaris, Trino OTLP endpoints from jaeger:4317 to otel-collector:4317
  • Add health check for collector
  • Traefik route for collector status page (optional)
  • Test: docker compose up otel-collector + verify receivers/exporters healthy
Add OTel Collector service to route traces→Jaeger, metrics→Prometheus, logs→Loki. ## Tasks - [ ] Add `otel-collector` service to `compose.yml` (image: `otel/opentelemetry-collector-contrib:latest`) - [ ] Create `infra/otel/otel-collector.yml` with receivers (OTLP gRPC 4317), processors (batch), exporters (otlp/jaeger, prometheus :8889, loki) - [ ] Network: `observability` (internal) - [ ] Add `otel-collector:8889` to Prometheus scrape targets - [ ] Migrate Traefik, Nessie, Polaris, Trino OTLP endpoints from `jaeger:4317` to `otel-collector:4317` - [ ] Add health check for collector - [ ] Traefik route for collector status page (optional) - [ ] Test: `docker compose up otel-collector` + verify receivers/exporters healthy
kert added this to the P26: Pipeline Telemetry — OTel instrumentation, perf module, Grafana dashboards milestone 2026-03-24 23:50:07 +00:00
kert commented 2026-03-25 00:07:04 +00:00
Author
Owner
Copy Link

Starting infra work.

  1. Create infra/otel/otel-collector.yml config
  2. Add otel-collector service to compose.yml
  3. Add to Prometheus scrape targets
  4. Migrate existing OTLP endpoints from jaeger:4317 → otel-collector:4317
Starting infra work. 1. Create `infra/otel/otel-collector.yml` config 2. Add otel-collector service to compose.yml 3. Add to Prometheus scrape targets 4. Migrate existing OTLP endpoints from jaeger:4317 → otel-collector:4317
kert commented 2026-03-25 00:08:49 +00:00
Author
Owner
Copy Link

Complete.

Created:

  • infra/otel/otel-collector.yml — OTLP gRPC+HTTP receiver, batch processor, fan-out exporters:
    • traces → otlp/jaeger (jaeger:4317)
    • metrics → Prometheus scrape (:8889)
    • logs → Loki (loki:3100)
    • health_check extension on :13133

Modified:

  • compose.yml — added otel-collector service (image: otel/opentelemetry-collector-contrib:latest, observability network, health check)
  • compose.yml — migrated Nessie, Polaris, API from jaeger:4317 → otel-collector:4317
  • infra/traefik/traefik.yml — OTLP endpoint → otel-collector:4317
  • infra/trino/etc/config.properties — tracing endpoint → otel-collector:4317
  • infra/prometheus/targets/services.yml — added otel-collector:8889 scrape target

✅ docker compose config --quiet passes.

Complete. **Created:** - `infra/otel/otel-collector.yml` — OTLP gRPC+HTTP receiver, batch processor, fan-out exporters: - traces → `otlp/jaeger` (jaeger:4317) - metrics → Prometheus scrape (:8889) - logs → Loki (loki:3100) - health_check extension on :13133 **Modified:** - `compose.yml` — added `otel-collector` service (image: `otel/opentelemetry-collector-contrib:latest`, observability network, health check) - `compose.yml` — migrated Nessie, Polaris, API from `jaeger:4317` → `otel-collector:4317` - `infra/traefik/traefik.yml` — OTLP endpoint → `otel-collector:4317` - `infra/trino/etc/config.properties` — tracing endpoint → `otel-collector:4317` - `infra/prometheus/targets/services.yml` — added `otel-collector:8889` scrape target ✅ `docker compose config --quiet` passes.
kert closed this issue 2026-03-25 00:08:50 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label
Milestone
No items
No Milestone P26: Pipeline Telemetry — OTel instrumentation, perf module, Grafana dashboards
Projects
Clear projects
No project Skin Subs
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#210
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?