infra(jaeger): bump Jaeger 2.17.0 → 2.19.0 (latest) #470

New Issue

2026-07-11T04:12:21Z

spikerj commented

2026-07-11 04:12:21 +00:00

Summary

Pin the jaeger tracing service to the latest release, jaegertracing/jaeger:2.19.0 (released 2026-06-03), up from the currently-declared 2.17.0. Minor bump within the Jaeger v2 line.

Scope

jaeger/docker-stack.yml — image: jaegertracing/jaeger:2.17.0 → jaegertracing/jaeger:2.19.0.

The collector/storage env config (SPAN_STORAGE_TYPE, ES_SERVER_URLS, COLLECTOR_OTLP_*, etc.) is unchanged and still supported.

Breaking-change review (2.17 → 2.19) — no config impact

2.19 (UI): search migrated to the new /api/v3/trace-summaries endpoint (ADR-010); backend query param num_traces → search_depth with deprecated aliases retained. We don't call these directly — UI-only.
2.18 (backend): metrics changes from an OTEL-collector package upgrade; metricstore dropped its min-step API. We don't consume those metrics or that API.

Net: safe image-tag bump; no stack config changes required.

Out of scope (pre-existing, see README §8.1)

The elasticsearch service in this stack is documented as running the wrong image in production (atmoz/sftp instead of elasticsearch:7.17.0), breaking trace storage / the UI. That anomaly is tracked separately and is not addressed here — this PR is a version pin only. A redeploy from the committed file is still needed to restore ES.

Deploy / verify

docker stack deploy -c jaeger/docker-stack.yml jaeger

After rollout: Jaeger UI reachable at http://<node-ip>:16686, OTLP ingest on 4317/4318 healthy, traces from services (traefik + backend workers) landing.

Repo: spikersoft-infrastructure

## Summary Pin the `jaeger` tracing service to the latest release, **jaegertracing/jaeger:2.19.0** (released 2026-06-03), up from the currently-declared **2.17.0**. Minor bump within the Jaeger v2 line. ## Scope - `jaeger/docker-stack.yml` — `image: jaegertracing/jaeger:2.17.0` → `jaegertracing/jaeger:2.19.0`. The collector/storage env config (`SPAN_STORAGE_TYPE`, `ES_SERVER_URLS`, `COLLECTOR_OTLP_*`, etc.) is unchanged and still supported. ## Breaking-change review (2.17 → 2.19) — no config impact - **2.19 (UI):** search migrated to the new `/api/v3/trace-summaries` endpoint (ADR-010); backend query param `num_traces` → `search_depth` with deprecated aliases retained. We don't call these directly — UI-only. - **2.18 (backend):** metrics changes from an OTEL-collector package upgrade; `metricstore` dropped its min-step API. We don't consume those metrics or that API. Net: safe image-tag bump; no stack config changes required. ## Out of scope (pre-existing, see README §8.1) The `elasticsearch` service in this stack is documented as running the wrong image in production (`atmoz/sftp` instead of `elasticsearch:7.17.0`), breaking trace storage / the UI. That anomaly is tracked separately and is **not** addressed here — this PR is a version pin only. A redeploy from the committed file is still needed to restore ES. ## Deploy / verify ``` docker stack deploy -c jaeger/docker-stack.yml jaeger ``` After rollout: Jaeger UI reachable at `http://<node-ip>:16686`, OTLP ingest on 4317/4318 healthy, traces from services (traefik + backend workers) landing. Repo: `spikersoft-infrastructure`

spikerj commented

2026-07-11 23:26:27 +00:00