LTTNG-RELAYD(8) | LTTng Manual | LTTNG-RELAYD(8) |
lttng-relayd - LTTng 2 relay daemon
lttng-relayd [--background | --daemonize] [--config=PATH]
[--control-port=URL] [--data-port=URL] [--fd-pool-size=COUNT]
[--live-port=URL] [--output=PATH]
[-v | -vv | -vvv] [--working-directory=PATH]
[--group-output-by-session] [--disallow-clear]
The Linux Trace Toolkit: next generation <https://lttng.org/> is an open source software package used for correlated tracing of the Linux kernel, user applications, and user libraries.
LTTng consists of Linux kernel modules (for Linux kernel tracing) and dynamically loaded libraries (for user application and library tracing).
The LTTng relay daemon is responsible for receiving trace data from possibly remote LTTng session/consumer daemons and for writing it to the local file system. The relay daemon also accepts LTTng live connections from compatible viewers; this is the official approach to viewing LTTng events as they are emitted.
The relay daemon listens by default on all network interfaces to gather trace data, but only on localhost for LTTng live connections.
The relay daemon does not require any particular permissions, as long as it can write to the output directory and listen on the configured ports. If a user is within a secured network and/or has proper firewall settings, lttng-relayd can listen to LTTng live connections from all network interfaces by specifying --live-port=tcp://0.0.0.0:5344.
Once a trace has been streamed completely, the trace can be processed by any tool that can process an LTTng trace located on the local file system.
The relay daemon uses different output path patterns depending on:
Consider the following variables:
BASE
HOSTNAME
SESSION
DATETIME
TRACEPATH
The relay daemon output path patterns are:
Hostname grouping (without --group-output-by-session)
Without a custom trace path
BASE/HOSTNAME/SESSION-DATETIME
With a custom trace path
BASE/HOSTNAME/TRACEPATH
Tracing session grouping (with --group-output-by-session)
Without a custom trace path
The peer’s LTTng session daemon version is at least 2.4
BASE/SESSION/HOSTNAME-DATETIME
Otherwise
BASE/HOSTNAME/SESSION-DATETIME
With a custom trace path
The peer’s LTTng session daemon version is at least 2.4
BASE/SESSION/HOSTNAME-DATETIME/TRACEPATH
Otherwise
BASE/HOSTNAME/TRACEPATH
The --control-port, --data-port, and --live-port options specify URLs.
The format of those URLs is:
tcp://(HOST | IPADDR):PORT
with:
(HOST | IPADDR)
PORT
-b, --background
-f PATH, --config=PATH
-d, --daemonize
-x, --disallow-clear
See also the LTTNG_RELAYD_DISALLOW_CLEAR environment variable.
--fd-pool-size=SIZE
SIZE is the maximum number of file descriptors that may be kept opened simultaneously by the relay daemon.
Default: the soft RLIMIT_NOFILE resource limit of the process (see getrlimit(2)).
-g GROUP, --group=GROUP
-w PATH, --working-directory=PATH
See also the LTTNG_RELAYD_WORKING_DIRECTORY environment variable.
-v, --verbose
Three levels of verbosity are available, which are triggered by appending additional v letters to the option (that is, -vv and -vvv).
See the Output directory section above for more information.
-p, --group-output-by-host
-s, --group-output-by-session
-o PATH, --output=PATH
See the URL format section above for more information about the syntax of the following URL argument.
-C URL, --control-port=URL
-D URL, --data-port=URL
-L URL, --live-port=URL
-h, --help
-V, --version
LTTNG_ABORT_ON_ERROR
LTTNG_NETWORK_SOCKET_TIMEOUT
LTTNG_RELAYD_DISALLOW_CLEAR
The --disallow-clear option overrides this variable.
LTTNG_RELAYD_HEALTH
LTTNG_RELAYD_TCP_KEEP_ALIVE
The TCP keep-alive mechanism allows the detection of dead peers (lttng-sessiond(8)) in cases of unclean termination (for example, a hard reset) of a peer.
Supported on Linux and Solaris only. The default behaviour of the TCP keep-alive mechanism is OS-specific.
Search for tcp_keepalive in tcp(7) for more information.
LTTNG_RELAYD_TCP_KEEP_ALIVE_ABORT_THRESHOLD
Set to 0 or -1 to use the value chosen by the operating system (default).
Supported on Solaris 11 only.
Search for tcp_keepalive_abort_threshold in tcp(7) for more information.
LTTNG_RELAYD_TCP_KEEP_ALIVE_IDLE_TIME
Set to 0 or -1 to use the value chosen by the operating system (default).
Supported on Linux and Solaris 11 only.
On Solaris 11, the accepted values are -1, 0, and 10 to 864000.
Search for tcp_keepalive_time and tcp_keepalive_interval in tcp(7) on Solaris 11 for more information.
LTTNG_RELAYD_TCP_KEEP_ALIVE_MAX_PROBE_COUNT
Set to 0 or -1 to use the value chosen by the operating system (default).
Supported on Linux only.
Search for tcp_keepalive_probes in tcp(7) for more information.
LTTNG_RELAYD_TCP_KEEP_ALIVE_PROBE_INTERVAL
Set to 0 or -1 to use the value chosen by the operating system (default).
Supported on Linux only.
Search for tcp_keepalive_intvl in tcp(7) for more information.
LTTNG_RELAYD_WORKING_DIRECTORY
The --working-directory option overrides this variable.
$LTTNG_HOME/.lttng
$LTTNG_HOME/lttng-traces
$LTTNG_HOME defaults to $HOME when not explicitly set.
0
1
3
As of this version, only the TCP protocol is supported for both control and data ports. In future versions, TCP will remain the sole available protocol for control data since those communications are low-volume and need absolute reliability; trace data could be carried over UDP.
For an unprivileged user running lttng-relayd, the maximum number of file descriptors per process is usually 1024. This limits the number of connections and opened trace files. This limit can be configured with ulimit(3).
If you encounter any issue or usability problem, please report it on the LTTng bug tracker <https://bugs.lttng.org/projects/lttng-tools>.
This program is part of the LTTng-tools project.
LTTng-tools is distributed under the GNU General Public License version 2 <http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html>. See the LICENSE <https://github.com/lttng/lttng-tools/blob/master/LICENSE> file for details.
Special thanks to Michel Dagenais and the DORSAL laboratory <http://www.dorsal.polymtl.ca/> at École Polytechnique de Montréal for the LTTng journey.
Also thanks to the Ericsson teams working on tracing which helped us greatly with detailed bug reports and unusual test cases.
lttng(1), lttng-sessiond(8), lttng-crash(1), lttng-ust(3), babeltrace2(1)
2 April 2020 | LTTng 2.12.3 |