// the take
ros2probe is an eBPF-based observability tool for ROS 2 systems running on DDS (RTPS) or Zenoh middleware. It attaches socket filters to capture traffic passively, reconstructs the node/topic graph from discovery packets, and exposes hz/bandwidth/delay metrics and MCAP recording through a CLI and a desktop GUI. Aimed at robotics engineers debugging multi-host ROS 2 deployments without wanting to instrument every node.
Passive kernel-level capture via eBPF means you don't modify or relaunch the nodes you're inspecting, which matters a lot for debugging live robots. The SHM workaround (spinning up a shadow subscriber to force UDP loopback traffic) shows they've actually dealt with DDS's shared-memory transport rather than just ignoring it. CLI and GUI share the same runtime over a Unix socket, so there's one capture pipeline instead of two codebases drifting apart. Shipping prebuilt binaries for both x86-64 and aarch64 (Jetson/RPi) covers the actual hardware robotics people deploy on, not just dev laptops.
Linux-only and requires kernel 5.15+ with eBPF and raw socket access, so it's a non-starter in many sandboxed CI or cloud-container setups without extra privileges; the daemon also auto-escalates to root, which is a meaningful attack surface for something sniffing all your DDS/Zenoh traffic. The GUI is x86-64 only, so the ARM boards (Jetson, RPi) where ros2probe's own install story targets you get CLI-only — exactly the platforms where a visual graph would help most during field debugging. `rp topic echo` depends on a separate Python + rclpy install, breaking the 'no Rust, no compiler, just download and run' pitch. It's a young academic project (DGIST lab, v0.2.1, ~100 stars, one arXiv paper) — RTPS/Zenoh protocol parsing is notoriously fiddly (fragmentation, vendor-specific extensions), and with support routed through two personal emails rather than an active maintainer team, how it holds up against real-world DDS implementations (Fast DDS, Cyclone, RTI) over time is unproven.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →