LTTng‑tools is a set of components to control LTTng tracing.
The project includes:
-
The LTTng session daemon.
-
The LTTng consumer daemon.
-
The LTTng relay daemon.
-
liblttng‑ctl, a library with a C API used to communicate with the session daemon.
-
Python 3 bindings of liblttng‑ctl.
-
lttng, a command-line tool over liblttng‑ctl. -
lttng‑crash, a command-line tool to recover and view LTTng 2 trace buffers in the event of a crash.
You need the following dependencies to build and run the LTTng‑tools components:
-
Linux kernel ≥ 2.6.27
Use
‑‑disable‑epollat build configuration time to build LTTng‑tools for an older kernel. However, note that we can’t provide any guarantee below 2.6.27. -
Userspace RCU ≥ 0.9.0.
Debian/Ubuntu package:
liburcu‑dev. -
popt ≥ 1.13
Debian/Ubuntu package:
libpopt‑dev. -
Libxml2 ≥ 2.7.6
Debian/Ubuntu package:
libxml2‑dev
The following dependencies are optional:
-
Babeltrace 2: default viewer of the
lttng viewcommand.Debian/Ubuntu package:
babeltrace2 -
LTTng‑UST (same minor version as LTTng‑tools): LTTng user space tracing (applications and libraries).
Debian/Ubuntu package:
liblttng‑ust‑dev -
Perl:
make checkand tests. -
Python ≥ 3.0:
make checkand tests.Debian/Ubuntu package:
python3 -
SWIG ≥ 2.0 and Python 3 development headers: Python bindings (enabled at build configuration time with the
‑‑enable‑python‑bindingsoption).Debian/Ubuntu packages:
swig2.0andpython3‑dev -
modprobe and/or kmod ≥ 22: automatic LTTng kernel modules loading (kernel tracing).
-
Bash:
make check. -
man(manual pager): viewlttngcommand manual pages with the‑‑helpoption or with thelttng helpcommand.NoteYou can use the build configuration option ‑‑enable‑embedded‑helpto embed the manual pages into thelttng,lttng‑sessiond,lttng‑relayd, andlttng‑crashprograms so that you don’t needmanto view them. -
libpfm ≥ 4.0: perf regression test suite.
Debian/Ubuntu package:
libpfm4-dev
LTTng‑tools supports both the LTTng Linux kernel tracer and LTTng user space tracer sharing the same minor version. While some minor releases do not change the tracer ABIs and could work, no testing is performed to ensure that cross-version compatibility is maintained.
You don’t need to rebuild or modify applications instrumented with older versions of the LTTng‑UST project to make them work with the components of the latest LTTng‑tools release.
See the LTTng Documentation for more information on versioning.
You need the following tools to build LTTng‑tools:
-
GNU Autotools (Automake ≥ 1.10, Autoconf ≥ 2.64, and Autoheader ≥ 2.50)
-
GNU Libtool ≥ 2.2
-
Flex ≥ 2.5.35
-
Bison ≥ 2.4
To build the LTTng‑tools manual pages:
If you use GNU gold, which is not mandatory:
-
GNU gold ≥ 2.22
|
Note
|
With GNU gold, you might need to add
-L/usr/local/lib to the LDFLAGS environment variable.
|
-
If you have the LTTng‑tools Git source, run:
$ ./bootstrap
This script creates the
configurescript. -
$ ./configure
If you want the liblttng‑ctl Python bindings, use the
‑‑enable‑python‑bindingsoption. See also thePYTHONandPYTHON_CONFIGenvironment variables in./configure ‑‑help.If you don’t want to build the manual pages, use the
‑‑disable‑man‑pagesoption.If you want to embed the manual pages into the
lttng,lttng‑sessiond,lttng‑relayd, andlttng‑crashprograms so that you don’t needmanto view them, use the‑‑enable‑embedded‑helpoption.If your Linux kernel is older than 2.6.27, use the
‑‑disable‑epolloption.This build configuration script finds LTTng‑UST with pkg‑config: set the
PKG_CONFIG_PATHenvironment variable accordingly if pkg‑config cannot find thelttng‑ustpackage information.See
./configure ‑‑helpfor the complete list of options. -
Build the project:
$ make
-
Install the project:
$ sudo make install $ sudo ldconfig
See the Tracing control section of the LTTng Documentation to learn how to use the LTTng‑tools components.
See also the LTTng manual pages (all section 1 and 8 pages).
As there’s no official liblttng‑ctl Python bindings yet, see
doc/python-howto.txt to understand how to
use them.
- Mailing list
- IRC channel
-
#lttngon the OFTC network - Bug tracker
- GitHub project
- Continuous integration
-
LTTng‑tools’s master build on LTTng’s CI
- Code review
-
lttng‑tools project on LTTng Review