ROSMonitoring in Action: Runtime Monitoring and Enforcement for ROS 2 Actions
Organizations: University of Modena and Reggio Emilia · Department of Physics, Informatics and Mathematics, University of Modena and Reggio Emilia, Italy
Abstract
Robotic applications often rely on long-running operations, such as navigation, manipulation, and inspection, which in ROS2 are commonly implemented as actions. Unlike topics and services, actions involve a structured lifecycle comprising goal submission and acceptance, feedback, status updates, result retrieval, and cancellation. Existing versions of ROSMonitoring support topics and services, but do not reconstruct this lifecycle or expose action-level events to a runtime-verification oracle. In this paper, we extend ROSMonitoring with runtime monitoring and enforcement for ROS2 actions. Actions are declared directly in the monitoring configuration and automatically instrumented through the underlying ROS~2 communication endpoints. The generated monitor reconstructs action-level events, correlates them through goal identifiers, maintains the state of active goals, and translates violations into protocol-aware enforcement operations. These include goal rejection, cancellation, message suppression, and protocol-compliant responses generated directly by the monitor when the original communication cannot be forwarded. We evaluate the implementation through controlled stress tests that vary the number of action invocations, workload size, and clientâserver topology. The results show approximately linear growth in monitoring cost with repeated action invocations under a fixed workload, while larger action workloads and a greater number of configured clientâserver pairs introduce additional overhead. These results characterise the scaling behaviour of the current implementation under the tested sequential workloads while highlighting the main performance limitations of the current synchronous implementation.
Runtime Assurance
Runtime assurance monitors and constrains AI or autonomous-system actions during execution to preserve safety and operational limits.
See all 71 papers