ros2_medkit proposes logs-to-faults bridge for ROS 2 diagnostics
New ROS 2 fault gateway ros2_medkit seeks community input on log-to-fault bridging.
The ros2_medkit project introduces a new Apache 2.0 fault aggregation gateway for ROS 2, following the SOVD model (ISO 17978-3). It currently offers two integration paths: a drop-in /diagnostics topic for packages already using diagnostic_updater, and a native FaultReporter instrumentation for controlled codebases. However, the team acknowledges that many production stacks have messy RCLCPP_ERROR/RCLCPP_WARN histories that won't be retroactively converted.
To bridge this gap, they are considering a third path: a logs-to-faults bridge that watches /rosout or arbitrary log streams and promotes selected patterns to structured fault events. This bridge would feature configurable rules for severity mapping, dedup, and rate limiting, enabling teams to adopt structured diagnostics without modifying existing code. The team is seeking community input on which log patterns to auto-promote, barriers to wider /diagnostics use, and requirements for the bridge to avoid noise.
- ros2_medkit proposes a third integration path: a logs-to-faults bridge watching /rosout streams.
- The bridge uses configurable rules for severity mapping, dedup, and rate limiting.
- Aims to enable structured diagnostics adoption without code changes in existing ROS 2 nodes.
Why It Matters
Structured diagnostics for ROS 2 become accessible without costly retrofitting, easing fleet-level fault aggregation and debugging.