![]() |
rosgraph_monitor package from graph_monitor repormw_stats_shim rosgraph_monitor rosgraph_monitor_msgs |
Package Summary
Tags | No category tags. |
Version | 0.1.1 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-tooling/graph-monitor.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-04-09 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Bonsai Robotics Engineering
Authors
Rosgraph Monitor
Provides a C++ class RosgraphMonitor
, which uses a node’s NodeGraphInterface
and subscribes to /topic_statistics
to monitor the ROS computation graph and produce /diagnostics (DiagnosticArray)
about issues in the graph:
- Missing Nodes (nodes that were present and are now missing)
- Discontinuities in graph (publishers or subscriptions that have no counterparts)
- Data flow issues (topics not publishing at promised rate)
-
/topic_statistics
required for this. Seermw_stats_shim
for how those are produced
-
This also provides a rosgraph_monitor_node
for standalone use, for users who do not need custom integration of the RosgraphMonitor
class.
Topic Statistics Diagnostics
To set expectations for Topic Statistics Diagnostics, you must:
- Set the
Deadline
QoS policy on Publishers - Nothing else. You don’t need to set it on Subscriptions, or register
DeadlineMissed
callbacks. Just state your periodic promise via Deadline QoS.
Configuration
See params_decl.yaml for the full parameters for the rosgraph_monitor
Node.
These parameters mirror the structure rosgraph_monitor::GraphMonitorConfiguration
in monitor.hpp, for those using the class directly instead of in the wrapping Node.
Usage
ros2 run rosgraph_monitor rosgraph_monitor_node
Changelog for package rosgraph_monitor
0.1.1 (2025-04-09)
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rosgraph_monitor at Robotics Stack Exchange
![]() |
rosgraph_monitor package from graph_monitor repormw_stats_shim rosgraph_monitor rosgraph_monitor_msgs |
Package Summary
Tags | No category tags. |
Version | 0.1.1 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-tooling/graph-monitor.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-04-09 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Bonsai Robotics Engineering
Authors
Rosgraph Monitor
Provides a C++ class RosgraphMonitor
, which uses a node’s NodeGraphInterface
and subscribes to /topic_statistics
to monitor the ROS computation graph and produce /diagnostics (DiagnosticArray)
about issues in the graph:
- Missing Nodes (nodes that were present and are now missing)
- Discontinuities in graph (publishers or subscriptions that have no counterparts)
- Data flow issues (topics not publishing at promised rate)
-
/topic_statistics
required for this. Seermw_stats_shim
for how those are produced
-
This also provides a rosgraph_monitor_node
for standalone use, for users who do not need custom integration of the RosgraphMonitor
class.
Topic Statistics Diagnostics
To set expectations for Topic Statistics Diagnostics, you must:
- Set the
Deadline
QoS policy on Publishers - Nothing else. You don’t need to set it on Subscriptions, or register
DeadlineMissed
callbacks. Just state your periodic promise via Deadline QoS.
Configuration
See params_decl.yaml for the full parameters for the rosgraph_monitor
Node.
These parameters mirror the structure rosgraph_monitor::GraphMonitorConfiguration
in monitor.hpp, for those using the class directly instead of in the wrapping Node.
Usage
ros2 run rosgraph_monitor rosgraph_monitor_node
Changelog for package rosgraph_monitor
0.1.1 (2025-04-09)
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rosgraph_monitor at Robotics Stack Exchange
![]() |
rosgraph_monitor package from graph_monitor repormw_stats_shim rosgraph_monitor rosgraph_monitor_msgs |
Package Summary
Tags | No category tags. |
Version | 0.1.1 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-tooling/graph-monitor.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-04-09 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Bonsai Robotics Engineering
Authors
Rosgraph Monitor
Provides a C++ class RosgraphMonitor
, which uses a node’s NodeGraphInterface
and subscribes to /topic_statistics
to monitor the ROS computation graph and produce /diagnostics (DiagnosticArray)
about issues in the graph:
- Missing Nodes (nodes that were present and are now missing)
- Discontinuities in graph (publishers or subscriptions that have no counterparts)
- Data flow issues (topics not publishing at promised rate)
-
/topic_statistics
required for this. Seermw_stats_shim
for how those are produced
-
This also provides a rosgraph_monitor_node
for standalone use, for users who do not need custom integration of the RosgraphMonitor
class.
Topic Statistics Diagnostics
To set expectations for Topic Statistics Diagnostics, you must:
- Set the
Deadline
QoS policy on Publishers - Nothing else. You don’t need to set it on Subscriptions, or register
DeadlineMissed
callbacks. Just state your periodic promise via Deadline QoS.
Configuration
See params_decl.yaml for the full parameters for the rosgraph_monitor
Node.
These parameters mirror the structure rosgraph_monitor::GraphMonitorConfiguration
in monitor.hpp, for those using the class directly instead of in the wrapping Node.
Usage
ros2 run rosgraph_monitor rosgraph_monitor_node