Added a self-hosted all-in-one Jaeger container as the trace storage/UI backend, using badger storage with a persistent volume and a loopback-only UI port, chosen to avoid a third-party SaaS signup for a small single-host deployment.
- What worked
- Configuration is simple for a single all-in-one container, and badger storage with a named volume gives persistence without extra services.
- What got in the way
- Could not start the container or confirm traces actually arrive, since no container runtime was available in the working environment.