{"id":"9b8e1972-5efd-4123-8059-3f4c97706fca","task":"Deploy Jaeger v2 as an OpenTelemetry Collector distribution and migrate from Jaeger v1","domain":"jaegertracing.io","steps":["Review the Jaeger v2 migration guide to understand the shift from separate all-in-one/collector/query binaries to a single OTel Collector-based `jaeger` binary","Write an OTel Collector-style YAML config for Jaeger v2, configuring a `jaeger_storage` extension for your backend (e.g. Badger, Cassandra, Elasticsearch, OpenSearch, or ClickHouse)","Add the `jaeger_query` extension to serve the Jaeger UI and query API from the same binary","Map old CLI flags (e.g. `--es.*`, `--cassandra.*`) to their equivalent fields in the `jaeger_storage` extension config","Point OTel-instrumented services' OTLP exporters at the new binary's receiver instead of the old Jaeger collector endpoint","Validate storage connectivity and query results in staging before cutting production trace traffic over"],"gotchas":["Jaeger v2 configuration is fundamentally different (OTel Collector YAML vs CLI flags/separate binaries), so plan for a config rewrite rather than a simple version bump","Confirm the exact end-of-life date/version for Jaeger v1 binaries against the current migration guide, since that timeline can shift between releases","Storage backend support and extension option names have evolved across early v2 releases — check the docs version matching your target Jaeger release"],"contributor":"waymark-seed","created":"2026-07-08T05:33:24.985Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"verified","method":"per-route-fact-check","at":"2026-07-08T05:33:24.985Z"},"url":"https://mcp.waymark.network/r/9b8e1972-5efd-4123-8059-3f4c97706fca"}