1 .TH "LTTNG" "1" "May 13th, 2014" "" ""
4 lttng \(em LTTng 2.x tracer control command line tool
9 lttng [OPTIONS] <COMMAND>
13 The LTTng project aims at providing highly efficient tracing tools for Linux.
14 Its tracers help track down performance issues and debug problems
15 involving multiple concurrent processes and threads. Tracing across multiple
16 systems is also possible.
18 The \fBlttng\fP command line tool from the lttng-tools package is used to control
19 both kernel and user-space tracing. Every interaction with the tracer should
20 be done by this tool or by the liblttng-ctl library provided by the lttng-tools
23 LTTng uses a session daemon (lttng-sessiond(8)), acting as a tracing registry,
24 which allows you to interact with multiple tracers (kernel and user-space)
25 inside the same container, a tracing session. Traces can be gathered from the
26 kernel and/or instrumented applications (lttng-ust(3)). Aggregating and reading
27 those traces is done using the babeltrace(1) text viewer.
29 We introduce the notion of \fBtracing domains\fP which is essentially a type of
30 tracer (kernel, user space or JUL for now). In the future, we could see more
31 tracer like for instance an hypervisor. For some commands, you'll need to
32 specify on which domain the command operates (\-u, \-k or \-j). For instance,
33 the kernel domain must be specified when enabling a kernel event.
35 In order to trace the kernel, the session daemon needs to be running as root.
36 LTTng provides the use of a \fBtracing group\fP (default: tracing). Whomever is
37 in that group can interact with the root session daemon and thus trace the
38 kernel. Session daemons can co-exist, meaning that you can have a session daemon
39 running as Alice that can be used to trace her applications along side with a
40 root daemon or even a Bob daemon. We highly recommend starting the session
41 daemon at boot time for stable and long term tracing.
43 Each user-space application instrumented with lttng-ust(3) will automatically
44 register with the root session daemon and its user session daemon. This allows
45 each daemon to list the available traceable applications and tracepoints at any
46 given moment (See the \fBlist\fP command).
50 This program follow the usual GNU command line syntax with long options starting with
51 two dashes. Below is a summary of the available options.
56 Show summary of possible options and commands.
58 .BR "\-v, \-\-verbose"
60 Three levels of verbosity are available which are triggered by putting additional v to
61 the option (\-vv or \-vvv)
64 Suppress all messages (even errors).
66 .BR "\-g, \-\-group NAME"
67 Set unix tracing group name. (default: tracing)
69 .BR "\-n, \-\-no-sessiond"
70 Don't automatically spawn a session daemon.
72 .BR "\-\-sessiond\-path PATH"
73 Set session daemon full binary path.
75 .BR "\-\-list\-options"
76 Simple listing of lttng options.
78 .BR "\-\-list\-commands"
79 Simple listing of lttng commands.
83 \fBadd-context\fP [OPTIONS]
85 Add context to event(s) and/or channel(s).
87 A context is basically extra information appended to a channel. For instance,
88 you could ask the tracer to add the PID information for all events in a
89 channel. You can also add performance monitoring unit counters (perf PMU) using
92 For example, this command will add the context information 'prio' and two per-CPU
93 perf counters (hardware branch misses and cache misses), to all events in the trace
97 # lttng add-context \-k \-t prio \-t perf:cpu:branch-misses \\
98 \-t perf:cpu:cache-misses
101 Please take a look at the help (\-h/\-\-help) for a detailed list of available
104 Perf counters are available as per-CPU ("perf:cpu:...") and per-thread
105 ("perf:thread:...") counters. Currently, per-CPU counters can only be
106 used with the kernel tracing domain, and per-thread counters can only be
107 used with the UST tracing domain.
109 If no channel is given (\-c), the context is added to all channels that were
110 already enabled. If the session has no channel, a default channel is created.
111 Otherwise the context will be added only to the given channel (\-c).
113 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
120 Show summary of possible options and commands.
122 .BR "\-s, \-\-session NAME"
123 Apply on session name.
125 .BR "\-c, \-\-channel NAME"
126 Apply on channel name.
128 .BR "\-k, \-\-kernel"
129 Apply for the kernel tracer
131 .BR "\-u, \-\-userspace"
132 Apply for the user-space tracer
134 .BR "\-t, \-\-type TYPE"
135 Context type. You can repeat this option on the command line. Please
136 use "lttng add-context \-h" to list all available types.
141 \fBcalibrate\fP [OPTIONS]
143 Quantify LTTng overhead
145 The LTTng calibrate command can be used to find out the combined average
146 overhead of the LTTng tracer and the instrumentation mechanisms used. This
147 overhead can be calibrated in terms of time or using any of the PMU performance
148 counter available on the system.
150 For now, the only calibration implemented is that of the kernel function
151 instrumentation (kretprobes).
153 * Calibrate kernel function instrumentation
155 Let's use an example to show this calibration. We use an i7 processor with 4
156 general-purpose PMU registers. This information is available by issuing dmesg,
157 looking for "generic registers".
159 This sequence of commands will gather a trace executing a kretprobe hooked on
160 an empty function, gathering PMU counters LLC (Last Level Cache) misses
161 information (see lttng add-context \-\-help to see the list of available PMU
165 # lttng create calibrate-function
166 # lttng enable-event calibrate \-\-kernel \\
167 \-\-function lttng_calibrate_kretprobe
168 # lttng add-context \-\-kernel \-t perf:cpu:LLC-load-misses \\
169 \-t perf:cpu:LLC-store-misses \\
170 \-t perf:cpu:LLC-prefetch-misses
172 # for a in $(seq 1 10); do \\
173 lttng calibrate \-\-kernel \-\-function;
176 # babeltrace $(ls \-1drt ~/lttng-traces/calibrate-function-* \\
180 The output from babeltrace can be saved to a text file and opened in a
181 spreadsheet (e.g. oocalc) to focus on the per-PMU counter delta between
182 consecutive "calibrate_entry" and "calibrate_return" events. Note that these
183 counters are per-CPU, so scheduling events would need to be present to account
184 for migration between CPU. Therefore, for calibration purposes, only events
185 staying on the same CPU must be considered.
187 The average result, for the i7, on 10 samples:
191 perf_LLC_load_misses: 5.0 0.577
192 perf_LLC_store_misses: 1.6 0.516
193 perf_LLC_prefetch_misses: 9.0 14.742
196 As we can notice, the load and store misses are relatively stable across runs
197 (their standard deviation is relatively low) compared to the prefetch misses.
198 We can conclude from this information that LLC load and store misses can be
199 accounted for quite precisely, but prefetches within a function seems to behave
200 too erratically (not much causality link between the code executed and the CPU
201 prefetch activity) to be accounted for.
207 Show summary of possible options and commands.
209 .BR "\-k, \-\-kernel"
210 Apply for the kernel tracer
212 .BR "\-u, \-\-userspace"
213 Apply for the user-space tracer
216 Dynamic function entry/return probe (default)
221 \fBcreate\fP [NAME] [OPTIONS]
223 Create tracing session.
225 A tracing session contains channel(s) which contains event(s). It is domain
226 agnostic, meaning that channels and events can be enabled for the
227 user-space tracer and/or the kernel tracer. It acts like a container
228 aggregating multiple tracing sources.
230 On creation, a \fB.lttngrc\fP file is created in your $HOME directory
231 containing the current session name. If NAME is omitted, a session name is
232 automatically created having this form: 'auto-yyyymmdd-hhmmss'.
234 If no \fB\-o, \-\-output\fP is specified, the traces will be written in
237 The $HOME environment variable can be overridden by defining the environment
238 variable LTTNG_HOME. This is useful when the user running the commands has
239 a non-writeable home directory.
241 The session name MUST NOT contain the character '/'.
247 Show summary of possible options and commands.
249 .BR "\-\-list-options"
250 Simple listing of options
252 .BR "\-o, \-\-output PATH"
253 Specify output path for traces
256 Traces will not be output
259 Set the session in snapshot mode. Created in no-output mode and uses the
260 URL, if one is specified, as the default snapshot output. Every channel will be set
261 in overwrite mode and with mmap output (splice not supported).
263 .BR "\-\-live [USEC]"
264 Set the session exclusively in live mode. The paremeter is the delay in micro
265 seconds before the data is flushed and streamed. The live mode allows you to
266 stream the trace and view it while it's being recorded by any tracer. For that,
267 you need a lttng-relayd and this session requires a network URL (\-U or
268 \-C/\-D). If no USEC nor URL is provided, the default is to use a timer value
269 set to 1000000 and the network URL set to net://127.0.0.1.
271 To read a live session, you can use babeltrace(1) or the live streaming
272 protocol in doc/live-reading-protocol.txt. Here is an example:
275 $ lttng-relayd -o /tmp/lttng
276 $ lttng create --live 200000 -U net://localhost
277 $ lttng enable-event -a --userspace
281 After the start, you'll be able to read the events while they are being
282 recorded in /tmp/lttng.
285 .BR "\-U, \-\-set-url=URL"
286 Set URL for the consumer output destination. It is persistent for the
287 session lifetime. Redo the command to change it. This will set both data
288 and control URL for network.
290 .BR "\-C, \-\-ctrl-url=URL"
291 Set control path URL. (Must use -D also)
293 .BR "\-D, \-\-data-url=URL"
294 Set data path URL. (Must use -C also)
296 Using these options, each API call can be controlled individually. For
297 instance, \-C does not enable the consumer automatically. You'll need the \-e
302 proto://[HOST|IP][:PORT1[:PORT2]][/TRACE_PATH]
304 Supported protocols are (proto):
307 Local filesystem full path.
311 This will use the default network transport layer which is TCP for both
312 control (PORT1) and data port (PORT2). The default ports are
313 respectively 5342 and 5343. Note that net[6]:// is not yet supported.
317 Can only be used with -C and -D together
319 NOTE: IPv6 address MUST be enclosed in brackets '[]' (rfc2732)
324 # lttng create -U net://192.168.1.42
326 Uses TCP and default ports for the given destination.
329 # lttng create -U net6://[fe80::f66d:4ff:fe53:d220]
331 Uses TCP, default ports and IPv6.
334 # lttng create s1 -U net://myhost.com:3229
336 Create session s1 and set its consumer to myhost.com on port 3229 for control.
341 \fBdestroy\fP [NAME] [OPTIONS]
343 Teardown tracing session
345 Free memory on the session daemon and tracer side. It's gone!
347 If NAME is omitted, the session name is taken from the .lttngrc file.
353 Show summary of possible options and commands.
358 .BR "\-\-list-options"
359 Simple listing of options
364 \fBenable-channel\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS]
366 Enable tracing channel
368 To enable an event, you must enable both the event and the channel that
371 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
374 Exactly one of \-k or -u must be specified.
376 It is important to note that if a certain type of buffers is used, the session
377 will be set with that type and all other subsequent channel needs to have the
380 Note that once the session has been started and enabled on the tracer side,
381 it's not possible anymore to enable a new channel for that session.
389 .BR "\-\-list-options"
390 Simple listing of options
392 .BR "\-s, \-\-session NAME"
393 Apply on session name
395 .BR "\-k, \-\-kernel"
396 Apply to the kernel tracer
398 .BR "\-u, \-\-userspace"
399 Apply to the user-space tracer
402 Discard event when subbuffers are full (default)
405 Flight recorder mode: overwrites events when subbuffers are full. The
406 number of subbuffer must be 2 or more.
408 .BR "\-\-subbuf-size SIZE"
409 Subbuffer size in bytes {+k,+M,+G}.
410 (default UST uid: 131072, UST pid: 4096, kernel: 262144, metadata: 4096)
411 Rounded up to the next power of 2.
413 The minimum subbuffer size, for each tracer, is the max value between
414 the default above and the system page size. You can issue this command
415 to get the current page size on your system: \fB$ getconf PAGE_SIZE\fP
417 .BR "\-\-num-subbuf NUM"
418 Number of subbuffers. (default UST uid: 4, UST pid: 4, kernel: 4,
419 metadata: 2) Rounded up to the next power of 2.
421 .BR "\-\-switch-timer USEC"
422 Switch subbuffer timer interval in µsec.
423 (default UST uid: 0, UST pid: 0, kernel: 0, metadata: 0)
425 .BR "\-\-read-timer USEC"
426 Read timer interval in µsec.
427 (default UST uid: 0, UST pid: 0, kernel: 200000, metadata: 0)
429 .BR "\-\-output TYPE"
430 Channel output type. Possible values: mmap, splice
431 (default UST uid: mmap, UST pid: mmap, kernel: splice, metadata: mmap)
433 .BR "\-\-buffers-uid"
434 Use per UID buffer (\-u only). Buffers are shared between applications
435 that have the same UID.
437 .BR "\-\-buffers-pid"
438 Use per PID buffer (\-u only). Each application has its own buffers.
440 .BR "\-\-buffers-global"
441 Use shared buffer for the whole system (\-k only)
443 .BR "\-C, \-\-tracefile-size SIZE"
444 Maximum size of each tracefile within a stream (in bytes).
445 0 means unlimited. (default: 0)
446 Note: traces generated with this option may inaccurately report
447 discarded events as per CTF 1.8.
449 .BR "\-W, \-\-tracefile-count COUNT"
450 Used in conjunction with \-C option, this will limit the number of files
451 created to the specified count. 0 means unlimited. (default: 0)
456 $ lttng enable-channel -k -C 4096 -W 32 chan1
458 For each stream, the maximum size of each trace file will be 4096 bytes and
459 there will be a maximum of 32 different files. The file count is appended after
460 the stream number as seen in the following example. The last trace file is
461 smaller than 4096 since it was not completely filled.
464 ~/lttng-traces/[...]/chan1_0_0 (4096)
465 ~/lttng-traces/[...]/chan1_0_1 (4096)
466 ~/lttng-traces/[...]/chan1_0_2 (3245)
467 ~/lttng-traces/[...]/chan1_1_0 (4096)
472 $ lttng enable-channel -k -C 4096
474 This will create trace files of 4096 bytes and will create new ones as long as
475 there is data available.
480 \fBenable-event\fP NAME[,NAME2,...] [-k|-u] [OPTIONS]
484 A tracing event is always assigned to a channel. If \fB\-c, \-\-channel\fP is
485 omitted, a default channel named '\fBchannel0\fP' is created and the event is
486 added to it. If \fB\-c, \-\-channel\fP is omitted, but a non-default
487 channel already exists within the session, an error is returned. For the
488 user-space tracer, using \fB\-a, \-\-all\fP is the same as using the
491 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
498 Show summary of possible options and commands.
500 .BR "\-\-list-options"
501 Simple listing of options
503 .BR "\-s, \-\-session NAME"
504 Apply on session name
506 .BR "\-c, \-\-channel NAME"
507 Apply on channel name
510 Enable all tracepoints and syscalls. This actually enables a single
513 .BR "\-k, \-\-kernel"
514 Apply for the kernel tracer
516 .BR "\-u, \-\-userspace"
517 Apply for the user-space tracer
520 Apply for Java application using Java Util Logging interface (JUL)
523 Tracepoint event (default). Userspace tracer supports wildcards at the end
524 of string. Don't forget to quote to deal with bash expansion.
531 .BR "\-\-loglevel NAME"
532 Tracepoint loglevel range from 0 to loglevel. Listed in the help (\-h).
533 For the JUL domain, the loglevel ranges are detailed with the \-\-help
534 option thus starting from SEVERE to FINEST.
536 .BR "\-\-loglevel-only NAME"
537 Tracepoint loglevel (only this loglevel).
538 The loglevel or loglevel-only options should be combined with a
539 tracepoint name or tracepoint wildcard.
541 .BR "\-\-probe (addr | symbol | symbol+offset)"
542 Dynamic probe. Addr and offset can be octal (0NNN...), decimal (NNN...)
543 or hexadecimal (0xNNN...)
545 .BR "\-\-function (addr | symbol | symbol+offset)"
546 Dynamic function entry/return probe. Addr and offset can be octal
547 (0NNN...), decimal (NNN...) or hexadecimal (0xNNN...)
550 System call event. Enabling syscalls tracing (kernel tracer), you will
551 not be able to disable them with disable-event. This is a known
552 limitation. You can disable the entire channel to do the trick. Also note
553 that per-syscall selection is not supported yet. Use with "-a" to enable
556 .BR "\-\-filter 'expression'"
557 Set a filter on a newly enabled event. Filter expression on event
558 fields and context. The event will be recorded if the filter's
559 expression evaluates to TRUE. Only specify on first activation of a
560 given event within a session.
561 Specifying a filter is only allowed when enabling events within a session before
562 tracing is started. If the filter fails to link with the event
563 within the traced domain, the event will be discarded.
564 Filtering is currently only implemented for the user-space tracer.
569 'intfield > 500 && intfield < 503'
570 '(strfield == "test" || intfield != 10) && intfield > 33'
571 'doublefield > 1.1 && intfield < 5.3'
574 Wildcards are allowed at the end of strings:
576 In string literals, the escape character is a '\\'. Use '\\*' for
577 the '*' character, and '\\\\' for the '\\' character sequence. Wildcard
578 matches any sequence of characters, including an empty sub-string
579 (matches 0 or more characters).
581 Context information can be used for filtering. The examples below shows
582 usage of context filtering on the process name (using a wildcard), process ID
583 range, and unique thread ID. The process and thread IDs of
584 running applications can be found under columns "PID" and "LWP" of the
588 '$ctx.procname == "demo*"'
589 '$ctx.vpid >= 4433 && $ctx.vpid < 4455'
593 Context information is available to all filters whether or not the add-context
594 command has been used to add it to the event's channel, as long as the context
595 field exists for that domain. For example, the filter examples given above will
596 never fail to link: no add-context is required for the event's channel.
599 .BR "\-x, \-\-exclude LIST"
600 Add exclusions to UST tracepoints:
601 Events that match any of the items in the comma-separated LIST are not
602 enabled, even if they match a wildcard definition of the event.
604 This option is also applicable with the \fB\-a, \-\-all\fP option,
605 in which case all UST tracepoints are enabled except the ones whose
606 names match any of the items in LIST.
611 \fBdisable-channel\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS]
613 Disable tracing channel
615 Disabling a channel disables the tracing of all of the channel's events. A channel
616 can be re-enabled by calling \fBlttng enable-channel NAME\fP again.
618 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
625 Show summary of possible options and commands.
627 .BR "\-\-list-options"
628 Simple listing of options
630 .BR "\-s, \-\-session NAME"
631 Apply on session name
633 .BR "\-k, \-\-kernel"
634 Apply for the kernel tracer
636 .BR "\-u, \-\-userspace"
637 Apply for the user-space tracer
642 \fBdisable-event\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS]
644 Disable tracing event
646 The event, once disabled, can be re-enabled by calling \fBlttng enable-event
649 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
652 If \fB\-c, \-\-channel\fP is omitted, the default channel name is used.
653 If \fB\-c, \-\-channel\fP is omitted, but a non-default channel already
654 exists within the session, an error is returned.
660 Show summary of possible options and commands.
662 .BR "\-\-list-options"
663 Simple listing of options
665 .BR "\-s, \-\-session NAME"
666 Apply on session name
668 .BR "\-c, \-\-channel NAME"
669 Apply on channel name
671 .BR "\-a, \-\-all-events"
672 Disable all events. This does NOT disable "*" but rather every known
673 events of the session.
675 .BR "\-k, \-\-kernel"
676 Apply for the kernel tracer
678 .BR "\-u, \-\-userspace"
679 Apply for the user-space tracer
682 Apply for Java application using Java Util Logging interface (JUL)
687 \fBlist\fP [OPTIONS] [SESSION [SESSION OPTIONS]]
689 List tracing session information.
691 With no arguments, it will list available tracing session(s).
693 With the session name, it will display the details of the session including
694 the trace file path, the associated channels and their state (activated
695 and deactivated), the activated events and more.
697 With \-k alone, it will list all available kernel events (except the system
699 With \-j alone, the available JUL event from registered application will be
700 list. The event corresponds to the Logger name in the Java JUL application.
701 With \-u alone, it will list all available user-space events from registered
702 applications. Here is an example of 'lttng list \-u':
705 PID: 7448 - Name: /tmp/lttng-ust/tests/hello/.libs/lt-hello
706 ust_tests_hello:tptest_sighandler (type: tracepoint)
707 ust_tests_hello:tptest (type: tracepoint)
710 You can now enable any event listed by using the name :
711 \fBust_tests_hello:tptest\fP.
717 Show summary of possible options and commands.
719 .BR "\-\-list-options"
720 Simple listing of options
722 .BR "\-k, \-\-kernel"
725 .BR "\-u, \-\-userspace"
726 Select user-space domain.
729 Apply for Java application using JUL
731 .BR "\-f, \-\-fields"
738 .BR "\-c, \-\-channel NAME"
739 List details of a channel
741 .BR "\-d, \-\-domain"
742 List available domain(s)
747 \fBload\fP [OPTIONS] [NAME]
749 Load tracing session configuration
751 If NAME is omitted, all session configurations found in both the user's session
752 configuration directory and the system session configuration directory will be
759 Show summary of possible options and commands.
762 Load all session configurations (default).
764 .BR "\-i, \-\-input-path PATH"
765 Specify the input path for session configurations.
768 Overwrite current session configuration(s) if a session of the same name
774 \fBsave\fP [OPTIONS] [SESSION]
776 Save tracing session configuration
778 If SESSION is omitted, all session configurations will be saved to individual
779 \fB.lttng\fP files under the user's session configuration directory. The
780 default session configuration file naming scheme is \fBSESSION.lttng\fP.
786 Show summary of possible options and commands.
789 Save all session configurations (default).
791 .BR "\-o, \-\-output-path PATH"
792 Specify the output path for saved sessions (default: ~/.lttng/sessions/).
795 Overwrite session configuration file if session name clashes.
800 \fBset-session\fP NAME [OPTIONS]
802 Set current session name
804 Will change the session name in the .lttngrc file.
810 Show summary of possible options and commands.
812 .BR "\-\-list-options"
813 Simple listing of options
818 \fBsnapshot\fP [OPTIONS] ACTION
820 Snapshot command for LTTng session.
826 Show summary of possible options and commands.
828 .BR "\-\-list-options"
829 Simple listing of options
835 \fBadd-output\fP [-m <SIZE>] [-s <NAME>] [-n <NAME>] <URL> | -C <URL> -D <URL>
837 Setup and add an snapshot output for a session. Output are the destination
838 where the snapshot will be sent. Only one output is permitted. To change it,
839 you'll need to delete it and add back the new one.
842 \fBdel-output\fP ID | NAME [-s <NAME>]
844 Delete an output for a session using the ID. You can either specify the
845 output's ID that can be found with list-output or the name.
848 \fBlist-output\fP [-s <NAME>]
850 List the output of a session. Attributes of the output are printed.
853 \fBrecord\fP [-m <SIZE>] [-s <NAME>] [-n <NAME>] [<URL> | -C <URL> -D <URL>]
855 Snapshot a session's buffer(s) for all domains. If an URL is specified, it is
856 used instead of a previously added output. Specifying only a name or/and a max
857 size will override the current output values. For instance, you can record a
858 snapshot with a custom maximum size or with a different name.
861 $ lttng snapshot add-output -n mysnapshot file:///data/snapshot
863 $ lttng snapshot record -n new_name_snapshot
866 The above will create a snapshot in /data/snapshot/new_name_snapshot* directory
867 rather then in mysnapshot*/
870 .B DETAILED ACTION OPTIONS
873 .BR "\-s, \-\-session NAME"
874 Apply to session name.
876 .BR "\-n, \-\-name NAME"
877 Name of the snapshot's output.
879 .BR "\-m, \-\-max-size SIZE"
880 Maximum size in bytes of the snapshot. The maxium size does not include the
881 metadata file. Human readable format is accepted: {+k,+M,+G}. For instance,
884 .BR "\-C, \-\-ctrl-url URL"
885 Set control path URL. (Must use -D also)
887 .BR "\-D, \-\-data-url URL"
888 Set data path URL. (Must use -C also)
893 \fBstart\fP [NAME] [OPTIONS]
897 It will start tracing for all tracers for a specific tracing session.
898 If NAME is omitted, the session name is taken from the .lttngrc file.
904 Show summary of possible options and commands.
906 .BR "\-\-list-options"
907 Simple listing of options
912 \fBstop\fP [NAME] [OPTIONS]
916 It will stop tracing for all tracers for a specific tracing session. Before
917 returning, the command checks for data availability meaning that it will wait
918 until the trace is readable for the session. Use \-\-no-wait to avoid this
921 If NAME is omitted, the session name is taken from the .lttngrc file.
927 Show summary of possible options and commands.
929 .BR "\-\-list-options"
930 Simple listing of options
933 Don't wait for data availability.
940 Show version information
946 Show summary of possible options and commands.
948 .BR "\-\-list-options"
949 Simple listing of options
954 \fBview\fP [SESSION_NAME] [OPTIONS]
956 View traces of a tracing session. By default, the babeltrace viewer
957 will be used for text viewing. If SESSION_NAME is omitted, the session
958 name is taken from the .lttngrc file.
966 .BR "\-\-list-options"
967 Simple listing of options
969 .BR "\-t, \-\-trace-path PATH"
970 Trace directory path for the viewer
972 .BR "\-e, \-\-viewer CMD"
973 Specify viewer and/or options to use This will completely override the
974 default viewers so please make sure to specify the full command. The
975 trace directory path of the session will be appended at the end to the
981 This section explains the JUL domain (\-j, \-\-jul) where JUL stands for Java
982 Util Logging. You can use that feature by using the \fBliblttng-ust-jul.so\fP
983 from the lttng-ust(3) project.
985 The LTTng Java Agent uses JNI to link the UST tracer to the Java application
986 that uses the agent. Thus, it behaves similarly to the UST domain (\-u). When
987 enabling events with the JUL domain, you enable a Logger name that will then be
988 mapped to a default UST tracepoint called \fBlttng_jul:jul_event\fP in the
989 \fBlttng_jul_channel\fP. Using the lttng-ctl API, any JUL events must use the
990 tracepoint event type (same as \-\-tracepoint).
992 Because of the default immutable channel (\fBlttng_jul_channel\fP), the
993 \fBenable-channel\fP command CAN NOT be used with the JUL domain thus not
994 having any \-j option.
996 For JUL event, loglevels are supported with the JUL ABI values. Use \fBlttng
997 enable-event \-h\fP to list them. Wildcards are NOT supported except the "*"
998 meaning all events (same as \-a).
1000 Exactly like the UST domain, if the Java application has the same UID as you,
1001 you can trace it. Same goes for the tracing group accessing root applications.
1003 Finally, you can list every Logger name that are available from JUL registered
1004 applications to the session daemon by using \fBlttng list \-j\fP.
1006 Here is an example on how to use this domain.
1011 $ lttng create aSession
1012 $ lttng enable-event -s aSession -j MyCustomLoggerName
1016 More information can be found in the lttng-ust documentation, see
1017 java-util-logging.txt
1022 On success 0 is returned and a positive value on error. Value of 1 means a command
1023 error, 2 an undefined command, 3 a fatal error and 4 a command warning meaning that
1024 something went wrong during the command.
1026 Any other value above 10, please refer to
1027 .BR "<lttng/lttng-error.h>"
1028 for a detailed list or use lttng_strerror() to get a human readable string of
1032 .SH "ENVIRONMENT VARIABLES"
1035 Note that all command line options override environment variables.
1039 .IP "LTTNG_SESSIOND_PATH"
1040 Allows one to specify the full session daemon binary path to lttng command line
1041 tool. You can also use \-\-sessiond-path option having the same effect.
1045 .IP "LTTNG_SESSION_CONFIG_XSD_PATH"
1046 Set the path in which the \fBsession.xsd\fP session configuration schema may be
1053 .BR lttng-sessiond(8),
1054 .BR lttng-relayd(8),
1059 If you encounter any issues or usability problem, please report it on our
1060 mailing list <lttng-dev@lists.lttng.org> to help improve this project or
1061 at https://bugs.lttng.org which is a bugtracker.
1067 lttng is distributed under the GNU General Public License version 2. See the file
1068 COPYING for details.
1070 A Web site is available at http://lttng.org for more information on the LTTng
1073 You can also find our git tree at http://git.lttng.org.
1075 Mailing lists for support and development: <lttng-dev@lists.lttng.org>.
1077 You can find us on IRC server irc.oftc.net (OFTC) in #lttng.
1082 Thanks to Yannick Brosseau without whom this project would never have been so
1083 lean and mean! Also thanks to the Ericsson teams working on tracing which
1084 helped us greatly with detailed bug reports and unusual test cases.
1086 Thanks to our beloved packager Alexandre Montplaisir-Goncalves (Ubuntu and PPA
1087 maintainer) and Jon Bernard for our Debian packages.
1089 Special thanks to Michel Dagenais and the DORSAL laboratory at Polytechnique de
1090 Montreal for the LTTng journey.
1095 lttng-tools was originally written by Mathieu Desnoyers, Julien Desfossez and
1096 David Goulet. More people have since contributed to it. It is currently
1097 maintained by David Goulet <dgoulet@efficios.com>.