# What do you use instead of rosmon for ROS2?

**URL:** <https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193>\
**Category:** ROS General\
**Tags:** ros2\
**Created:** [June 12, 2024, 5:29pm UTC](https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193 "2024-06-12T17:29:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![iandareid](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/iandareid/32/21521_2.png) [@iandareid](https://discourse.openrobotics.org/u/iandareid)\
**Post date:** [June 12, 2024, 5:29pm UTC](https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193/1 "2024-06-12T17:29:23Z")

</div>

I find myself wanting a tool like rosmon for my ROS2 projects. Looking at the rosmon github repo, the maintainer has no explicit plans to swap to ROS2 in the foreseeable future. So my question is what does the ROS community use for node management in ROS2?

I am aware of ROS2 node lifecylces, however a clean interface like rosmon gives would be nice, instead of using CLI commands.

---

<div class="post-metadata">

**Author:** ![chfritz](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/chfritz/32/26180_2.png) [@chfritz](https://discourse.openrobotics.org/u/chfritz)\
**Post date:** [June 12, 2024, 5:51pm UTC](https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193/2 "2024-06-12T17:51:59Z")

</div>

Which of the features of `rosmon` are you most interested in:

- the (remote) monitoring,
- the CLI,
- the TUI, or
- the rqt GUI?

---

<div class="post-metadata">

**Author:** ![Guela\_kais](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/guela_kais/32/19525_2.png) [@Guela\_kais](https://discourse.openrobotics.org/u/Guela_kais)\
**Post date:** [June 12, 2024, 5:54pm UTC](https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193/3 "2024-06-12T17:54:49Z")

</div>

That’s exactly what I thought straight away. [Rosmon](https://github.com/xqms/rosmon) seems to have some features and doesn’t really prevent the use of CLI commands - as far as I can tell, rosmon itself is a CLI tool.

---

<div class="post-metadata">

**Author:** ![MCFurry](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/mcfurry/32/6194_2.png) [@MCFurry](https://discourse.openrobotics.org/u/MCFurry)\
**Post date:** [June 20, 2024, 7:35am UTC](https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193/4 "2024-06-20T07:35:22Z")

</div>

I would very much like a ROS2-rosmon as well!  
The features I currently miss most are:

- diagnostics
- remote monitoring
- rqt-GUI
- logging in /rosout if a node crashes
- way faster launch

So all features that don’t even rely on the CLI tool itself.

I understood from the maintainer that it would be harder to create a C++ tool for launching ROS2 systems now that everything is Python based.  
But I hope someone can wrap his head around, maybe by using Python to create a list of processes to launch and from their do the rosmon magic?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/ros/original/3X/b/6/b607ee3cc8e908b1b613bd74a683d749fea635a1.svg) [@system](https://discourse.openrobotics.org/u/system)\
**Post date:** [September 18, 2024, 7:35am UTC](https://discourse.openrobotics.org/t/what-do-you-use-instead-of-rosmon-for-ros2/38193/5 "2024-09-18T07:35:50Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.