ros2_tracing
- Software
- Middleware
- Tool
Tracing tools for ROS 2 that instrument core packages and configure LTTng tracing through a CLI command and launch actions. Currently supports Linux only.
Made by ROS 2.
Source on GitHub: github.com/ros2/ros2_tracing (opens in a new tab). Facts read at commit 3e215f8 (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 3e215f8 (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
What it does
- Provides tracing instrumentation (tracepoints) for the core ROS 2 packages.
- Offers a `ros2 trace` CLI command and a launch file `Trace` action to configure and run tracing sessions.
- Supports snapshot mode, which keeps trace data in memory and writes to disk only when a snapshot is taken.
- Supports dual session tracing, separating initialization events in snapshot mode from runtime events.
- Includes packages for LTTng Python bindings, reading traces, and tracing-related tests.
- Trace analysis is handled by a separate project, tracetools_analysis.
Written by Robotheca from the project's README (opens in a new tab) at commit 3e215f8.
Getting started
- Difficulty
- Advanced
- Hardware it needs, as the project states it
- Linux, since only the LTTng tracer is supported; the LTTng kernel tracer must be installed separately to trace kernel events.
- How to start
- The project's website (opens in a new tab)
Maintenance
- Status
- Active: a commit in the last 90 days
- Newest commit
- 12 Oct 2026 on rolling
- Latest release
- None published on GitHub
Checked on GitHub on 16 Oct 2026.
Links
Robots on Robotheca that use 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.