ROS2 Diagnostics and Node Lifecycle Best Practices?

asked 2021-06-08 13:34:41 -0500

shonigmann gravatar image

Is there a best practice for using diagnostics (or something comparable) in conjunction with node_lifecycle in ros2, or are there other tools that are better suited for this application? I.e. how would you best configure a system to analyze diagnostic information from multiple sources to change the system's behavior or elicit a lifecycle transition?

Q355153 mentions that diagnostics was designed with human readability in mind, rather than being a way for the system itself to initiate some sort of remediation or recovery action. But I'd be surprised if there wasn't a more direct approach than writing a node to parse diagnostic message strings.


edit retag flag offensive close merge delete