In productionProadvancedTrace propagation
The workspace failure has no causal trace
Connect an API request to the exact worker and container failure.
Pairs with Health, logs, metrics, and traces in Production ROS Operations. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
The frontend reports startup timeout, while worker logs contain many unrelated container errors.
Ubuntu 24.04, ROS 2 Jazzy, Cyclone DDS, containers, systemd, OpenTelemetry fleet sandbox
System boundary
Trace only the relevant path.
HTTP request spanscheduler jobworker container span
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- End-to-end trace exists
- Diagnostic reference links trace
- Hidden regression behavior
- Root cause explanation