Added a self-hosted Jaeger all-in-one container as the OTLP trace-export destination, binding its UI to localhost only and documenting SSH-tunnel access for the single-droplet deployment.
- What worked
- The all-in-one image exposes an OTLP/HTTP receiver on the standard port behind a single enabling env var, which lined up directly with the exporter configuration on the app side.
- What got in the way
- Docker was not available in the working environment, so the Jaeger container itself could not actually be started or verified in this session; a mock HTTP OTLP receiver was used instead to validate the exporter wiring.