julien/apf_portal
1
0
Fork 0
Code Issues 1 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

chore(infra): migrate Jaeger to v2 for built-in dark theme #64

Merged
julien merged 1 commits from chore/infra/jaeger-v2-migration into main 2026-05-08 23:31:17 +02:00
Conversation 0 Commits 1 Files Changed 1
+8 -3
julien commented 2026-05-08 23:30:43 +02:00
Owner
Copy Link
Copy Source

Summary

Jaeger v1's web UI has no theme selector — it ships light-only. v2 (the OTel-Collector-based rewrite, image jaegertracing/jaeger, distinct from v1's jaegertracing/all-in-one) ships a Light / Dark / Auto switcher in the UI nav. v2 is also the actively-developed line; v1 is on the way out within ~6-12 months.

Migration is mechanical:

  • Image: jaegertracing/all-in-one:1.76.0 → jaegertracing/jaeger:2.17.0.
  • Drop COLLECTOR_OTLP_ENABLED: 'true' env — v2 enables OTLP receivers by default.
  • UI port (16686) and OTLP ports (4317 / 4318) are unchanged, so the collector → jaeger:4317 forwarding pipeline keeps working without touching otel-collector.yaml.

Test plan

  • After merge: docker compose -f infra/local/dev.compose.yml --profile observability up -d --force-recreate jaeger → container stays healthy.
  • http://localhost:16686 loads the v2 UI; nav shows the Light/Dark/Auto switcher.
  • Send a synthetic OTLP trace to localhost:4317 (e.g., via grpcurl or once the BFF is wired in B) → it appears in the Jaeger UI.
  • OTel Collector logs no longer warn abou
## Summary Jaeger v1's web UI has no theme selector — it ships light-only. v2 (the OTel-Collector-based rewrite, image `jaegertracing/jaeger`, distinct from v1's `jaegertracing/all-in-one`) ships a **Light / Dark / Auto** switcher in the UI nav. v2 is also the actively-developed line; v1 is on the way out within ~6-12 months. Migration is mechanical: - Image: `jaegertracing/all-in-one:1.76.0` → `jaegertracing/jaeger:2.17.0`. - Drop `COLLECTOR_OTLP_ENABLED: 'true'` env — v2 enables OTLP receivers by default. - UI port (`16686`) and OTLP ports (`4317` / `4318`) are unchanged, so the collector → `jaeger:4317` forwarding pipeline keeps working without touching `otel-collector.yaml`. ## Test plan - [ ] After merge: `docker compose -f infra/local/dev.compose.yml --profile observability up -d --force-recreate jaeger` → container stays healthy. - [ ] http://localhost:16686 loads the v2 UI; nav shows the Light/Dark/Auto switcher. - [ ] Send a synthetic OTLP trace to `localhost:4317` (e.g., via grpcurl or once the BFF is wired in B) → it appears in the Jaeger UI. - [ ] OTel Collector logs no longer warn abou
julien added 1 commit 2026-05-08 23:30:43 +02:00
chore(infra): migrate Jaeger to v2 for built-in dark theme
CI / commits (pull_request) Successful in 1m8s
Details
CI / scan (pull_request) Successful in 1m13s
Details
CI / check (pull_request) Successful in 1m17s
Details
CI / a11y (pull_request) Successful in 1m13s
Details
CI / perf (pull_request) Successful in 2m54s
Details
9ce8d18759 
Jaeger v1's web UI has no theme selector — it ships light-only.
v2 (the OTel-Collector-based rewrite, image
`jaegertracing/jaeger`, distinct from v1's `jaegertracing/
all-in-one`) ships a Light / Dark / Auto switcher in the UI nav.
v2 is also the actively-developed line; v1 will be phased out
within ~6-12 months.

Migration is mechanical:

- Image: `jaegertracing/all-in-one:1.76.0` →
  `jaegertracing/jaeger:2.17.0`.
- Drop `COLLECTOR_OTLP_ENABLED: 'true'` env — v2 enables OTLP
  receivers by default.
- UI port (16686) and OTLP ports (4317 / 4318) are unchanged, so
  the collector → jaeger:4317 forwarding pipeline keeps working
  without touching `otel-collector.yaml`.

The compose comment is updated to reflect v2's distinct image
name and UI capabilities.
julien merged commit a893f8e06b into main 2026-05-08 23:31:17 +02:00
julien deleted branch chore/infra/jaeger-v2-migration 2026-05-08 23:31:17 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adastra-bot (AdAstra Bot) julien (Julien Gautier)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: julien/apf_portal#64
Delete Branch "chore/infra/jaeger-v2-migration"

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?