Skip to content

rcl_logging_syslog

  • Software
  • Middleware
  • Library

A ROS 2 logging backend that sends log messages through the system syslog interface to rsyslog, for file storage or forwarding to tools like Fluent Bit.

Source on GitHub: github.com/fujitatomoya/rcl_logging_syslog (opens in a new tab). Facts read at commit 5ec0de1 (opens in a new tab).

Licenses

Code
Apache-2.0 (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit 5ec0de1 (opens in a new tab), on 16 Oct 2026.

Commercial use
Yes

What it does

  • Plugs into ROS 2 logging via rcl_logging_interface as an alternative backend to the default one.
  • Sends log data through SYSLOG(3) to rsyslog, which handles file sinks and remote forwarding.
  • Works with dynamic loading on Lyrical and later, selected at runtime with RCL_LOGGING_IMPLEMENTATION.
  • On Kilted, Jazzy, and Humble it must be statically linked by rebuilding rcl, since runtime switching is unavailable.
  • Log files are written under /var/log/ros, named by program, process ID, and date.
  • Includes configuration files for rsyslog and Fluent Bit, plus a test run with colcon test.

Written by Robotheca from the project's README (opens in a new tab) at commit 5ec0de1.

Getting started

Difficulty
Advanced
Hardware it needs, as the project states it
rsyslog must be installed; in containers rsyslogd must be started manually, and Fluent Bit is needed only for forwarding.

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
13 Sept 2026 on rolling
Latest release
None published on GitHub

Checked on GitHub on 16 Oct 2026.

Robots that can run it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.