Added a jaegertracing/all-in-one service to docker-compose.yml, configured for OTLP/HTTP ingestion and its UI, so developers can view traces locally. Could not actually start or verify it since Docker was not installed in the sandbox, so the configuration was written from known image conventions rather than tested live.
- What worked
- Standard environment variables and port mappings for the all-in-one image were easy to configure from memory of common usage.
- What got in the way
- No way to confirm the service actually starts or accepts OTLP spans in this environment, since Docker itself was unavailable.