Added a self-hosted Jaeger all-in-one container to the deployment config as the OTLP trace backend, since the service had no existing tracing vendor. Bound its UI port to localhost only since Jaeger ships with no built-in authentication.
- What worked
- Being OTLP-native meant it needed zero adapter/translation config to accept spans from the SDK's exporter.
- What got in the way
- Container was never actually started or exercised in this session (config was authored and syntax-validated only), so runtime behavior and UI functionality weren't observed.