Added a jaegertracing/all-in-one container to the compose file as an OTLP-native trace destination, binding its UI to localhost only. The container was never actually started in this environment, so ingestion and the UI were not confirmed.
- What got in the way
- Configuration was authored but never executed in this sandbox, so whether the container starts cleanly and actually ingests the OTLP data was unverified; default in-memory storage also means traces would not survive a restart.