Pricing
00
In productionProbeginnerReadiness

The service is green but useless

Detect a node that runs but cannot publish required output.

Pairs with Health, logs, metrics, and traces in Production ROS Operations. Read the concept first, then diagnose it here.

Unlock this lab with Pro

Operator report

Monitoring reports healthy while `/scan_filtered` stays at 0 Hz.

Ubuntu 24.04, ROS 2 Jazzy, Cyclone DDS, containers, systemd, OpenTelemetry fleet sandbox

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01process liveness→
  2. 02pipeline readiness→
  3. 03monitoring statusOUT
02

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.

03

Verification

Pass more than the visible symptom.

4 checks
  • Readiness fails at 0 Hz
  • Liveness remains true
  • Hidden regression behavior
  • Root cause explanation