Commit | Line | Data |
---|---|---|
391b9c72 | 1 | .TH "LTTNG" "1" "December 3rd, 2012" "" "" |
6991b181 DG |
2 | |
3 | .SH "NAME" | |
391b9c72 | 4 | lttng \(em LTTng 2.1.x tracer control command line tool |
6991b181 DG |
5 | |
6 | .SH "SYNOPSIS" | |
7 | ||
8 | .PP | |
9 | .nf | |
10 | lttng [OPTIONS] <COMMAND> | |
11 | .fi | |
12 | .SH "DESCRIPTION" | |
13 | ||
14 | .PP | |
15 | The LTTng project aims at providing highly efficient tracing tools for Linux. | |
16 | It's tracers help tracking down performance issues and debugging problems | |
17 | involving multiple concurrent processes and threads. Tracing across multiple | |
18 | systems is also possible. | |
19 | ||
fa072eae | 20 | The \fBlttng\fP command line tool from the lttng-tools package is used to control |
6991b181 DG |
21 | both kernel and user-space tracing. Every interactions with the tracer should |
22 | be done by this tool or by the liblttng-ctl provided with the lttng-tools | |
23 | package. | |
24 | ||
25 | LTTng uses a session daemon (lttng-sessiond(8)), acting as a tracing registry, | |
50a3b92a | 26 | which allows you to interact with multiple tracers (kernel and user-space) |
6991b181 DG |
27 | inside the same container, a tracing session. Traces can be gathered from the |
28 | kernel and/or instrumented applications (lttng-ust(3)). Aggregating and reading | |
29 | those traces is done using the babeltrace(1) text viewer. | |
30 | ||
50a3b92a DG |
31 | We introduce the notion of \fBtracing domains\fP which is essentially a type of |
32 | tracer (kernel or user space for now). In the future, we could see a third | |
33 | tracer being for instance an hypervisor. For some commands, you'll need to | |
34 | specify on which domain the command applies (-u or -k). For instance, enabling | |
35 | a kernel event, you must specify the kernel domain to the command so we know | |
36 | for which tracer this event is for. | |
37 | ||
6991b181 DG |
38 | In order to trace the kernel, the session daemon needs to be running as root. |
39 | LTTng provides the use of a \fBtracing group\fP (default: tracing). Whomever is | |
40 | in that group can interact with the root session daemon and thus trace the | |
41 | kernel. Session daemons can co-exist meaning that you can have a session daemon | |
fa072eae YB |
42 | running as Alice that can be used to trace her applications along side with a |
43 | root daemon or even a Bob daemon. We highly recommend to start the session | |
6991b181 DG |
44 | daemon at boot time for stable and long term tracing. |
45 | ||
46 | Every user-space applications instrumented with lttng-ust(3), will | |
47 | automatically register to the session daemon. This feature gives you the | |
48 | ability to list available traceable applications and tracepoints on a per user | |
49 | basis. (See \fBlist\fP command). | |
50 | .SH "OPTIONS" | |
51 | ||
52 | .PP | |
53 | This program follow the usual GNU command line syntax with long options starting with | |
54 | two dashes. Below is a summary of the available options. | |
55 | .PP | |
56 | ||
57 | .TP | |
c9e32613 | 58 | .BR "\-h, \-\-help" |
6991b181 DG |
59 | Show summary of possible options and commands. |
60 | .TP | |
c9e32613 | 61 | .BR "\-v, \-\-verbose" |
6991b181 | 62 | Increase verbosity. |
d829b38c | 63 | Three levels of verbosity are available which are triggered by putting additional v to |
fa072eae | 64 | the option (\-vv or \-vvv) |
6991b181 | 65 | .TP |
c9e32613 | 66 | .BR "\-q, \-\-quiet" |
6991b181 DG |
67 | Suppress all messages (even errors). |
68 | .TP | |
c9e32613 | 69 | .BR "\-g, \-\-group NAME" |
6991b181 DG |
70 | Set unix tracing group name. (default: tracing) |
71 | .TP | |
c9e32613 | 72 | .BR "\-n, \-\-no-sessiond" |
6991b181 DG |
73 | Don't automatically spawn a session daemon. |
74 | .TP | |
391b9c72 | 75 | .BR "\-\-sessiond\-path PATH" |
6991b181 DG |
76 | Set session daemon full binary path. |
77 | .TP | |
c9e32613 | 78 | .BR "\-\-list\-options" |
6991b181 DG |
79 | Simple listing of lttng options. |
80 | .TP | |
c9e32613 | 81 | .BR "\-\-list\-commands" |
6991b181 DG |
82 | Simple listing of lttng commands. |
83 | .SH "COMMANDS" | |
84 | ||
85 | .TP | |
86 | \fBadd-context\fP | |
87 | .nf | |
88 | Add context to event(s) and/or channel(s). | |
89 | ||
391b9c72 DG |
90 | A context is basically extra information appended to a channel. For instance, |
91 | you could ask the tracer to add the PID information for all events in a | |
92 | channel. You can also add performance monitoring unit counters (perf PMU) using | |
93 | the perf kernel API). | |
6991b181 DG |
94 | |
95 | For example, this command will add the context information 'prio' and two perf | |
96 | counters (hardware branch misses and cache misses), to all events in the trace | |
97 | data output: | |
98 | ||
c9e32613 | 99 | # lttng add-context \-k \-t prio \-t perf:branch-misses \-t perf:cache-misses |
6991b181 | 100 | |
c9e32613 | 101 | Please take a look at the help (\-h/\-\-help) for a detailed list of available |
6991b181 DG |
102 | contexts. |
103 | ||
391b9c72 DG |
104 | If no channel is given (\-c), the context is added to all channels. Otherwise |
105 | the context will be added only to the given channel (\-c). | |
6991b181 | 106 | |
c9e32613 | 107 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 DG |
108 | file. |
109 | .fi | |
110 | ||
111 | .B OPTIONS: | |
112 | ||
113 | .nf | |
c9e32613 | 114 | \-h, \-\-help |
6991b181 | 115 | Show summary of possible options and commands. |
c9e32613 | 116 | \-s, \-\-session NAME |
6991b181 | 117 | Apply on session name. |
c9e32613 | 118 | \-c, \-\-channel NAME |
6991b181 | 119 | Apply on channel name. |
c9e32613 | 120 | \-k, \-\-kernel |
6991b181 | 121 | Apply for the kernel tracer |
c9e32613 | 122 | \-u, \-\-userspace |
6991b181 | 123 | Apply for the user-space tracer |
c9e32613 | 124 | \-t, \-\-type TYPE |
6991b181 | 125 | Context type. You can repeat this option on the command line. Please |
c9e32613 | 126 | use "lttng add-context \-h" to list all available types. |
6991b181 DG |
127 | .fi |
128 | ||
129 | .IP | |
130 | ||
131 | .IP "\fBcalibrate\fP" | |
132 | .nf | |
133 | Quantify LTTng overhead | |
134 | ||
135 | The LTTng calibrate command can be used to find out the combined average | |
136 | overhead of the LTTng tracer and the instrumentation mechanisms used. This | |
137 | overhead can be calibrated in terms of time or using any of the PMU performance | |
138 | counter available on the system. | |
139 | ||
140 | For now, the only calibration implemented is that of the kernel function | |
141 | instrumentation (kretprobes). | |
142 | ||
143 | * Calibrate kernel function instrumentation | |
144 | ||
145 | Let's use an example to show this calibration. We use an i7 processor with 4 | |
146 | general-purpose PMU registers. This information is available by issuing dmesg, | |
147 | looking for "generic registers". | |
148 | ||
149 | This sequence of commands will gather a trace executing a kretprobe hooked on | |
150 | an empty function, gathering PMU counters LLC (Last Level Cache) misses | |
c9e32613 | 151 | information (see lttng add-context \-\-help to see the list of available PMU |
6991b181 DG |
152 | counters). |
153 | ||
154 | # lttng create calibrate-function | |
c9e32613 DG |
155 | # lttng enable-event calibrate \-\-kernel \-\-function lttng_calibrate_kretprobe |
156 | # lttng add-context \-\-kernel \-t perf:LLC-load-misses \-t perf:LLC-store-misses \\ | |
157 | \-t perf:LLC-prefetch-misses | |
6991b181 DG |
158 | # lttng start |
159 | # for a in $(seq 1 10); do \\ | |
c9e32613 | 160 | lttng calibrate \-\-kernel \-\-function; |
6991b181 DG |
161 | done |
162 | # lttng destroy | |
c9e32613 | 163 | # babeltrace $(ls \-1drt ~/lttng-traces/calibrate-function-* | tail \-n 1) |
6991b181 DG |
164 | |
165 | The output from babeltrace can be saved to a text file and opened in a | |
166 | spreadsheet (e.g. oocalc) to focus on the per-PMU counter delta between | |
167 | consecutive "calibrate_entry" and "calibrate_return" events. Note that these | |
168 | counters are per-CPU, so scheduling events would need to be present to account | |
169 | for migration between CPU. Therefore, for calibration purposes, only events | |
170 | staying on the same CPU must be considered. | |
171 | ||
172 | The average result, for the i7, on 10 samples: | |
173 | ||
174 | Average Std.Dev. | |
175 | perf_LLC_load_misses: 5.0 0.577 | |
176 | perf_LLC_store_misses: 1.6 0.516 | |
177 | perf_LLC_prefetch_misses: 9.0 14.742 | |
178 | ||
179 | As we can notice, the load and store misses are relatively stable across runs | |
180 | (their standard deviation is relatively low) compared to the prefetch misses. | |
181 | We can conclude from this information that LLC load and store misses can be | |
182 | accounted for quite precisely, but prefetches within a function seems to behave | |
183 | too erratically (not much causality link between the code executed and the CPU | |
184 | prefetch activity) to be accounted for. | |
185 | .fi | |
186 | ||
187 | .B OPTIONS: | |
188 | ||
189 | .nf | |
c9e32613 | 190 | \-h, \-\-help |
6991b181 | 191 | Show summary of possible options and commands. |
c9e32613 | 192 | \-k, \-\-kernel |
6991b181 | 193 | Apply for the kernel tracer |
c9e32613 | 194 | \-u, \-\-userspace |
6991b181 | 195 | Apply for the user-space tracer |
c9e32613 | 196 | \-\-function |
6991b181 DG |
197 | Dynamic function entry/return probe (default) |
198 | .fi | |
199 | ||
200 | .IP | |
201 | ||
6b8f2e64 | 202 | .IP "\fBcreate\fP [NAME] [OPTIONS] |
6991b181 DG |
203 | .nf |
204 | Create tracing session. | |
205 | ||
206 | A tracing session contains channel(s) which contains event(s). It is domain | |
207 | agnostic meaning that you can enable channels and events for either the | |
208 | user-space tracer and/or the kernel tracer. It acts like a container | |
209 | aggregating multiple tracing sources. | |
210 | ||
211 | On creation, a \fB.lttngrc\fP file is created in your $HOME directory | |
212 | containing the current session name. If NAME is omitted, a session name is | |
fa072eae | 213 | automatically created having this form: 'auto-yyyymmdd-hhmmss'. |
6991b181 | 214 | |
c9e32613 | 215 | If no \fB\-o, \-\-output\fP is specified, the traces will be written in |
6991b181 DG |
216 | $HOME/lttng-traces. |
217 | .fi | |
218 | ||
219 | .B OPTIONS: | |
220 | ||
221 | .nf | |
c9e32613 | 222 | \-h, \-\-help |
6991b181 | 223 | Show summary of possible options and commands. |
c9e32613 | 224 | \-\-list-options |
6991b181 | 225 | Simple listing of options |
c9e32613 | 226 | \-o, \-\-output PATH |
6991b181 | 227 | Specify output path for traces |
6b8f2e64 DG |
228 | |
229 | Using these options, each API call can be controlled individually. For | |
230 | instance, \-C does not enable the consumer automatically. You'll need the \-e | |
231 | option for that. | |
232 | ||
a59af249 | 233 | \-U, \-\-set-url=URL |
6b8f2e64 DG |
234 | Set URL for the enable-consumer destination. It is persistent for the |
235 | session lifetime. Redo the command to change it. This will set both | |
236 | data and control URL for network. | |
237 | \-C, \-\-ctrl-url=URL | |
238 | Set control path URL. (Must use -D also) | |
239 | \-D, \-\-data-url=URL | |
240 | Set data path URL. (Must use -C also) | |
241 | \-\-no-consumer | |
242 | Don't activate a consumer for this session. | |
243 | \-\-disable-consumer | |
244 | Disable consumer for this session. | |
245 | ||
246 | See \fBenable-consumer\fP command below for the supported URL format. | |
247 | ||
248 | .B EXAMPLES: | |
249 | ||
250 | # lttng create -U net://192.168.1.42 | |
251 | Uses TCP and default ports for the given destination. | |
252 | ||
253 | # lttng create -U net6://[fe80::f66d:4ff:fe53:d220] | |
254 | Uses TCP, default ports and IPv6. | |
255 | ||
256 | # lttng create s1 -U net://myhost.com:3229 | |
257 | Create session s1 and set its consumer to myhost.com on port 3229 for control. | |
6991b181 DG |
258 | .fi |
259 | ||
260 | .IP | |
261 | ||
262 | .IP "\fBdestroy\fP [OPTIONS] [NAME]" | |
263 | .nf | |
264 | Teardown tracing session | |
265 | ||
266 | Free memory on the session daemon and tracer side. It's gone! | |
267 | ||
268 | If NAME is omitted, the session name is taken from the .lttngrc file. | |
269 | .fi | |
270 | ||
271 | .B OPTIONS: | |
272 | ||
273 | .nf | |
c9e32613 | 274 | \-h, \-\-help |
6991b181 | 275 | Show summary of possible options and commands. |
a3c5b534 FG |
276 | \-a, \-\-all |
277 | Destroy all sessions | |
c9e32613 | 278 | \-\-list-options |
6991b181 DG |
279 | Simple listing of options |
280 | .fi | |
281 | ||
282 | .IP | |
283 | ||
284 | .IP "\fBenable-channel\fP NAME[,NAME2,...] [-k|-u] [OPTIONS]" | |
285 | .nf | |
286 | Enable tracing channel | |
287 | ||
b5412c5f DG |
288 | To enable an event, you must enable both the event and the channel that |
289 | contains it. | |
b883c01b | 290 | |
c9e32613 | 291 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 DG |
292 | file. |
293 | .fi | |
294 | ||
295 | .B OPTIONS: | |
296 | ||
297 | .nf | |
c9e32613 | 298 | \-h, \-\-help |
6991b181 | 299 | Show this help |
c9e32613 | 300 | \-\-list-options |
6991b181 | 301 | Simple listing of options |
391b9c72 | 302 | \-s, \-\-session NAME |
6991b181 | 303 | Apply on session name |
c9e32613 | 304 | \-k, \-\-kernel |
6991b181 | 305 | Apply to the kernel tracer |
c9e32613 | 306 | \-u, \-\-userspace |
6991b181 DG |
307 | Apply to the user-space tracer |
308 | ||
c9e32613 | 309 | \-\-discard |
6991b181 | 310 | Discard event when subbuffers are full (default) |
c9e32613 | 311 | \-\-overwrite |
6991b181 | 312 | Flight recorder mode : overwrites events when subbuffers are full |
391b9c72 | 313 | \-\-subbuf-size SIZE |
6991b181 | 314 | Subbuffer size in bytes (default: 4096, kernel default: 262144) |
b5412c5f | 315 | Needs to be a power of 2 for both tracers |
391b9c72 | 316 | \-\-num-subbuf NUM |
d829b38c | 317 | Number of subbuffers (default: 4) |
b5412c5f | 318 | Needs to be a power of 2 for both tracers |
391b9c72 | 319 | \-\-switch-timer USEC |
b5412c5f | 320 | Switch subbuffer timer interval in µsec (default: 0) |
391b9c72 | 321 | \-\-read-timer USEC |
b5412c5f | 322 | Read timer interval in µsec (default: 200) |
391b9c72 DG |
323 | \-\-output TYPE |
324 | Channel output type. Possible values: mmap, splice | |
6991b181 DG |
325 | .fi |
326 | ||
327 | .IP | |
328 | ||
6b8f2e64 DG |
329 | .IP "\fBenable-consumer\fP [-u|-k] [URL] [OPTIONS]" |
330 | .nf | |
331 | Enable a consumer for the tracing session and domain. | |
332 | ||
333 | By default, every tracing session has a consumer attached to it using the local | |
334 | filesystem as output. The trace is written in $HOME/lttng-traces. This command | |
335 | allows the user to specify a specific URL after the session was created for a | |
336 | specific domain. If no domain is specified, the consumer is applied on all | |
337 | domains. | |
338 | ||
339 | Without options, the behavior is to enable a consumer to the current URL. The | |
340 | default URL is the local filesystem at the path of the session mentioned above. | |
341 | ||
342 | The enable-consumer feature supports both local and network transport. You must | |
343 | have a running \fBlttng-relayd(8)\fP for network transmission or any other daemon | |
344 | that can understand the streaming protocol of LTTng. | |
345 | .fi | |
346 | ||
347 | .B OPTIONS: | |
348 | ||
349 | .nf | |
350 | \-h, \-\-help | |
351 | Show summary of possible options and commands. | |
352 | \-\-list-options | |
353 | Simple listing of options | |
391b9c72 | 354 | \-s, \-\-session NAME |
6b8f2e64 DG |
355 | Apply on session name |
356 | \-k, \-\-kernel | |
357 | Apply for the kernel tracer | |
358 | \-u, \-\-userspace | |
359 | Apply for the user-space tracer | |
360 | ||
361 | Using these options, each API call can be controlled individually. For | |
362 | instance, \-C does not enable the consumer automatically. You'll need the \-e | |
363 | option for that. | |
364 | ||
a59af249 | 365 | \-U, \-\-set-url=URL |
6b8f2e64 DG |
366 | Set URL for the enable-consumer destination. It is persistent for the |
367 | session lifetime. Redo the command to change it. This will set both | |
368 | data and control URL for network. | |
369 | \-C, \-\-ctrl-url=URL | |
370 | Set control path URL. (Must use -D also) | |
371 | \-D, \-\-data-url=URL | |
372 | Set data path URL. (Must use -C also) | |
373 | \-e, \-\-enable | |
374 | Enable consumer | |
375 | ||
376 | .B URL FORMAT: | |
377 | ||
378 | proto://[HOST|IP][:PORT1[:PORT2]][/TRACE_PATH] | |
379 | ||
380 | Supported protocols are (proto): | |
381 | > file://... | |
382 | Local filesystem full path. | |
383 | ||
391b9c72 | 384 | > net://... |
6b8f2e64 DG |
385 | This will use the default network transport layer which is TCP for both |
386 | control (PORT1) and data port (PORT2). The default ports are | |
391b9c72 | 387 | respectively 5342 and 5343. Note that net[6]:// is not yet supported. |
6b8f2e64 DG |
388 | |
389 | > tcp[6]://... | |
390 | Can only be used with -C and -D together | |
391 | ||
392 | NOTE: IPv6 address MUST be enclosed in brackets '[]' (rfc2732) | |
393 | ||
394 | .B EXAMPLES: | |
395 | ||
396 | $ lttng enable-consumer -u net://192.168.1.42 | |
397 | ||
398 | Uses TCP and default ports for user space tracing (-u) where the IP address | |
399 | above is the destination machine where the traces will be streamed and a | |
400 | \fBlttng-relayd(8)\fP is listening. | |
401 | .fi | |
402 | ||
6991b181 DG |
403 | .IP "\fBenable-event\fP NAME[,NAME2,...] [-k|-u] [OPTIONS]" |
404 | .nf | |
405 | Enable tracing event | |
406 | ||
c9e32613 | 407 | A tracing event is always assigned to a channel. If \fB\-c, \-\-channel\fP is |
6991b181 | 408 | omitted, a default channel named '\fBchannel0\fP' is created and the event is |
c9e32613 | 409 | added to it. For the user-space tracer, using \fB\-a, \-\-all\fP is the same as |
6991b181 DG |
410 | using the wildcard "*". |
411 | ||
c9e32613 | 412 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 DG |
413 | file. |
414 | .fi | |
415 | ||
416 | .B OPTIONS: | |
417 | ||
418 | .nf | |
c9e32613 | 419 | \-h, \-\-help |
6991b181 | 420 | Show summary of possible options and commands. |
c9e32613 | 421 | \-\-list-options |
6991b181 | 422 | Simple listing of options |
391b9c72 | 423 | \-s, \-\-session NAME |
6991b181 | 424 | Apply on session name |
391b9c72 | 425 | \-c, \-\-channel NAME |
6991b181 | 426 | Apply on channel name |
c9e32613 | 427 | \-a, \-\-all |
c5650942 DG |
428 | Enable all tracepoints and syscalls. This actually enable a single |
429 | wildcard event "*". | |
c9e32613 | 430 | \-k, \-\-kernel |
6991b181 | 431 | Apply for the kernel tracer |
c9e32613 | 432 | \-u, \-\-userspace |
6991b181 DG |
433 | Apply for the user-space tracer |
434 | ||
c9e32613 | 435 | \-\-tracepoint |
6991b181 DG |
436 | Tracepoint event (default) |
437 | - userspace tracer supports wildcards at end of string. Don't forget to | |
438 | quote to deal with bash expansion. | |
439 | e.g.: | |
440 | "*" | |
441 | "app_component:na*" | |
391b9c72 DG |
442 | \-\-loglevel NAME |
443 | Tracepoint loglevel range from 0 to loglevel. Listed in the help (\-h). | |
444 | \-\-loglevel-only NAME | |
445 | Tracepoint loglevel (only this loglevel). | |
446 | ||
447 | The loglevel or loglevel-only options should be combined with a | |
448 | tracepoint name or tracepoint wildcard. | |
c9e32613 | 449 | \-\-probe [addr | symbol | symbol+offset] |
6991b181 DG |
450 | Dynamic probe. Addr and offset can be octal (0NNN...), decimal (NNN...) |
451 | or hexadecimal (0xNNN...) | |
c9e32613 | 452 | \-\-function [addr | symbol | symbol+offset] |
6991b181 DG |
453 | Dynamic function entry/return probe. Addr and offset can be octal |
454 | (0NNN...), decimal (NNN...) or hexadecimal (0xNNN...) | |
c9e32613 | 455 | \-\-syscall |
6b8f2e64 DG |
456 | System call event. Enabling syscalls tracing (kernel tracer), you will |
457 | not be able to disable them with disable-event. This is a known | |
458 | limitation. You can disable the entire channel to do the trick. | |
9bd578f5 | 459 | |
919e300c | 460 | \-\-filter 'expression' |
6b8f2e64 DG |
461 | Set a filter on a newly enabled event. Filter expression on event |
462 | fields, event recording depends on evaluation. Only specify on first | |
463 | activation of a given event within a session. Filter only allowed when | |
464 | enabling events within a session before tracing is started. If the | |
465 | filter fails to link with the event within the traced domain, the event | |
466 | will be discarded. Currently, filter is only implemented for the | |
467 | user-space tracer. | |
468 | ||
469 | Expression examples: | |
470 | ||
471 | 'intfield > 500 && intfield < 503' | |
472 | '(stringfield == "test" || intfield != 10) && intfield > 33' | |
473 | 'doublefield > 1.1 && intfield < 5.3' | |
474 | ||
475 | Wildcards are allowed at the end of strings: | |
476 | 'seqfield1 == "te*"' | |
477 | In string literals, the escape character is a '\\'. Use '\\*' for | |
478 | the '*' character, and '\\\\' for the '\\' character. | |
6991b181 DG |
479 | .fi |
480 | ||
c9e32613 | 481 | .IP "\fBdisable-channel\fP NAME[,NAME2,...] [\-k|\-u] [OPTIONS]" |
6991b181 DG |
482 | .nf |
483 | Disable tracing channel | |
484 | ||
485 | Disabling a channel makes all event(s) in that channel to stop tracing. You can | |
486 | enable it back by calling \fBlttng enable-channel NAME\fP again. | |
487 | ||
c9e32613 | 488 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 DG |
489 | file. |
490 | .fi | |
491 | ||
492 | .B OPTIONS: | |
493 | ||
494 | .nf | |
c9e32613 | 495 | \-h, \-\-help |
6991b181 | 496 | Show summary of possible options and commands. |
c9e32613 | 497 | \-\-list-options |
6991b181 | 498 | Simple listing of options |
6b8f2e64 DG |
499 | \-s, \-\-session NAME |
500 | Apply on session name | |
501 | \-k, \-\-kernel | |
502 | Apply for the kernel tracer | |
503 | \-u, \-\-userspace | |
504 | Apply for the user-space tracer | |
505 | .fi | |
506 | ||
507 | .IP "\fBdisable-consumer\fP [\-k|\-u] [OPTIONS]" | |
508 | .nf | |
509 | Disable the consumer of a tracing session. | |
510 | ||
511 | This call MUST be done BEFORE tracing has started. | |
512 | .fi | |
513 | ||
514 | .B OPTIONS: | |
515 | ||
516 | .nf | |
517 | \-h, \-\-help | |
518 | Show summary of possible options and commands. | |
519 | \-\-list-options | |
520 | Simple listing of options | |
521 | \-s, \-\-session NAME | |
6991b181 | 522 | Apply on session name |
c9e32613 | 523 | \-k, \-\-kernel |
6991b181 | 524 | Apply for the kernel tracer |
c9e32613 | 525 | \-u, \-\-userspace |
6991b181 DG |
526 | Apply for the user-space tracer |
527 | .fi | |
528 | ||
c9e32613 | 529 | .IP "\fBdisable-event\fP NAME[,NAME2,...] [\-k|\-u] [OPTIONS]" |
6991b181 DG |
530 | .nf |
531 | Disable tracing event | |
532 | ||
533 | The event, once disabled, can be re-enabled by calling \fBlttng enable-event | |
534 | NAME\fP again. | |
535 | ||
c9e32613 | 536 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 DG |
537 | file. |
538 | .fi | |
539 | ||
540 | .B OPTIONS: | |
541 | ||
542 | .nf | |
c9e32613 | 543 | \-h, \-\-help |
6991b181 | 544 | Show summary of possible options and commands. |
c9e32613 | 545 | \-\-list-options |
6991b181 | 546 | Simple listing of options |
391b9c72 | 547 | \-s, \-\-session NAME |
6991b181 | 548 | Apply on session name |
c5650942 DG |
549 | \-a, \-\-all-events |
550 | Disable all events. This does NOT disable "*" but rather | |
551 | every known events of the session. | |
c9e32613 | 552 | \-k, \-\-kernel |
6991b181 | 553 | Apply for the kernel tracer |
c9e32613 | 554 | \-u, \-\-userspace |
6991b181 DG |
555 | Apply for the user-space tracer |
556 | .fi | |
557 | ||
c9e32613 | 558 | .IP "\fBlist\fP [\-k|\-u] [SESSION [SESSION_OPTIONS]]" |
6991b181 | 559 | .nf |
c9e32613 | 560 | List tracing session information. |
6991b181 DG |
561 | |
562 | With no arguments, it will list available tracing session(s). | |
563 | ||
fa072eae YB |
564 | With the session name, it will display the details of the session including |
565 | the trace file path, the associated channels and their state (activated | |
d829b38c | 566 | and deactivated), the activated events and more. |
fa072eae | 567 | |
c9e32613 | 568 | With \-k alone, it will list all available kernel events (except the system |
6991b181 | 569 | calls events). |
c9e32613 DG |
570 | With \-u alone, it will list all available user-space events from registered |
571 | applications. Here is an example of 'lttng list \-u': | |
6991b181 DG |
572 | |
573 | PID: 7448 - Name: /tmp/lttng-ust/tests/hello/.libs/lt-hello | |
574 | ust_tests_hello:tptest_sighandler (type: tracepoint) | |
575 | ust_tests_hello:tptest (type: tracepoint) | |
576 | ||
577 | You can now enable any event listed by using the name : | |
578 | \fBust_tests_hello:tptest\fP. | |
579 | .fi | |
580 | ||
581 | .B OPTIONS: | |
582 | ||
583 | .nf | |
c9e32613 | 584 | \-h, \-\-help |
6991b181 | 585 | Show summary of possible options and commands. |
c9e32613 | 586 | \-\-list-options |
6991b181 | 587 | Simple listing of options |
c9e32613 | 588 | \-k, \-\-kernel |
d829b38c | 589 | Select kernel domain |
c9e32613 | 590 | \-u, \-\-userspace |
6991b181 DG |
591 | Select user-space domain. |
592 | ||
6b8f2e64 DG |
593 | .B SESSION OPTIONS: |
594 | ||
c9e32613 | 595 | \-c, \-\-channel NAME |
6991b181 | 596 | List details of a channel |
c9e32613 | 597 | \-d, \-\-domain |
6991b181 DG |
598 | List available domain(s) |
599 | .fi | |
600 | ||
601 | .IP "\fBset-session\fP NAME" | |
602 | .nf | |
603 | Set current session name | |
604 | ||
605 | Will change the session name in the .lttngrc file. | |
606 | .fi | |
607 | ||
608 | .B OPTIONS: | |
609 | ||
610 | .nf | |
c9e32613 | 611 | \-h, \-\-help |
6991b181 | 612 | Show summary of possible options and commands. |
c9e32613 | 613 | \-\-list-options |
6991b181 DG |
614 | Simple listing of options |
615 | .fi | |
616 | ||
617 | .IP | |
618 | ||
6b8f2e64 | 619 | .IP "\fBstart\fP [NAME] [OPTIONS]" |
6991b181 DG |
620 | .nf |
621 | Start tracing | |
622 | ||
623 | It will start tracing for all tracers for a specific tracing session. | |
624 | ||
625 | If NAME is omitted, the session name is taken from the .lttngrc file. | |
626 | .fi | |
627 | ||
628 | .B OPTIONS: | |
629 | ||
630 | .nf | |
c9e32613 | 631 | \-h, \-\-help |
6991b181 | 632 | Show summary of possible options and commands. |
c9e32613 | 633 | \-\-list-options |
6991b181 DG |
634 | Simple listing of options |
635 | .fi | |
636 | ||
637 | .IP | |
638 | ||
6b8f2e64 | 639 | .IP "\fBstop\fP [NAME] [OPTIONS]" |
6991b181 DG |
640 | .nf |
641 | Stop tracing | |
642 | ||
391b9c72 DG |
643 | It will stop tracing for all tracers for a specific tracing session. Before |
644 | returning, the command checks for data availability meaning that it will wait | |
645 | until the trace is readable for the session. Use \-\-no-wait to avoid this | |
646 | behavior. | |
6991b181 DG |
647 | |
648 | If NAME is omitted, the session name is taken from the .lttngrc file. | |
649 | .fi | |
650 | ||
651 | .B OPTIONS: | |
652 | ||
653 | .nf | |
c9e32613 | 654 | \-h, \-\-help |
6991b181 | 655 | Show summary of possible options and commands. |
c9e32613 | 656 | \-\-list-options |
6991b181 | 657 | Simple listing of options |
391b9c72 DG |
658 | \-\-no-wait |
659 | Don't wait for data availability. | |
6991b181 DG |
660 | .fi |
661 | ||
662 | .IP | |
663 | ||
664 | .IP "\fBversion\fP" | |
665 | .nf | |
666 | Show version information | |
667 | .fi | |
668 | ||
669 | .B OPTIONS: | |
670 | ||
671 | .nf | |
c9e32613 | 672 | \-h, \-\-help |
6991b181 | 673 | Show summary of possible options and commands. |
c9e32613 | 674 | \-\-list-options |
6991b181 DG |
675 | Simple listing of options |
676 | .fi | |
677 | ||
678 | .IP | |
679 | ||
680 | .IP "\fBview\fP [SESSION_NAME] [OPTIONS]" | |
681 | .nf | |
682 | View traces of a tracing session | |
683 | ||
684 | By default, the babeltrace viewer will be used for text viewing. | |
685 | ||
fa072eae YB |
686 | If SESSION_NAME is omitted, the session name is taken from the .lttngrc file. |
687 | ||
6991b181 DG |
688 | .fi |
689 | ||
690 | .B OPTIONS: | |
691 | ||
692 | .nf | |
c9e32613 | 693 | \-h, \-\-help |
6991b181 | 694 | Show this help |
c9e32613 | 695 | \-\-list-options |
6991b181 | 696 | Simple listing of options |
c9e32613 | 697 | \-t, \-\-trace-path PATH |
6991b181 | 698 | Trace directory path for the viewer |
c9e32613 | 699 | \-e, \-\-viewer CMD |
6991b181 DG |
700 | Specify viewer and/or options to use |
701 | This will completely override the default viewers so | |
702 | please make sure to specify the full command. The trace | |
703 | directory path of the session will be appended at the end | |
704 | to the arguments | |
705 | .fi | |
706 | ||
c206d957 | 707 | .SH "EXIT VALUES" |
6b8f2e64 DG |
708 | On success 0 is returned and a positive value on error. Value of 1 means a command |
709 | error, 2 an undefined command, 3 a fatal error and 4 a command warning meaning that | |
710 | something went wrong during the command. | |
c206d957 | 711 | |
6b8f2e64 DG |
712 | Any other value above 10, please refer to |
713 | .BR <lttng/lttng-error.h> | |
714 | for a detailed list or use lttng_strerror() to get a human readable string of | |
715 | the error code. | |
c206d957 | 716 | |
c206d957 | 717 | .PP |
6991b181 DG |
718 | .SH "ENVIRONMENT VARIABLES" |
719 | ||
720 | .PP | |
721 | Note that all command line options override environment variables. | |
722 | .PP | |
723 | ||
724 | .PP | |
05833633 | 725 | .IP "LTTNG_SESSIOND_PATH" |
c9e32613 DG |
726 | Allows one to specify the full session daemon binary path to lttng command line |
727 | tool. You can also use \-\-sessiond-path option having the same effect. | |
6991b181 | 728 | .SH "SEE ALSO" |
6b8f2e64 DG |
729 | .BR babeltrace(1), |
730 | .BR lttng-ust(3), | |
731 | .BR lttng-sessiond(8), | |
732 | .BR lttng-relayd(8), | |
733 | .BR lttng-health-check(3) | |
6991b181 DG |
734 | .SH "BUGS" |
735 | ||
6991b181 | 736 | If you encounter any issues or usability problem, please report it on our |
6b8f2e64 DG |
737 | mailing list <lttng-dev@lists.lttng.org> to help improve this project or |
738 | at https://bugs.lttng.org which is a bugtracker. | |
6991b181 DG |
739 | .SH "CREDITS" |
740 | ||
741 | .PP | |
c9e32613 | 742 | lttng is distributed under the GNU General Public License version 2. See the file |
6991b181 DG |
743 | COPYING for details. |
744 | .PP | |
745 | A Web site is available at http://lttng.org for more information on the LTTng | |
746 | project. | |
747 | .PP | |
748 | You can also find our git tree at http://git.lttng.org. | |
749 | .PP | |
750 | Mailing lists for support and development: <lttng-dev@lists.lttng.org>. | |
751 | .PP | |
752 | You can find us on IRC server irc.oftc.net (OFTC) in #lttng. | |
753 | .PP | |
754 | .SH "THANKS" | |
755 | ||
756 | .PP | |
757 | Thanks to Yannick Brosseau without whom this project would never have been so | |
758 | lean and mean! Also thanks to the Ericsson teams working on tracing which | |
fa072eae | 759 | helped us greatly with detailed bug reports and unusual test cases. |
6991b181 DG |
760 | |
761 | Thanks to our beloved packager Alexandre Montplaisir-Goncalves (Ubuntu and PPA | |
762 | maintainer) and Jon Bernard for our Debian packages. | |
763 | ||
764 | Special thanks to Michel Dagenais and the DORSAL laboratory at Polytechnique de | |
765 | Montreal for the LTTng journey. | |
c9e32613 | 766 | .PP |
6991b181 DG |
767 | .SH "AUTHORS" |
768 | ||
769 | .PP | |
770 | lttng-tools was originally written by Mathieu Desnoyers, Julien Desfossez and | |
771 | David Goulet. More people have since contributed to it. It is currently | |
772 | maintained by David Goulet <dgoulet@efficios.com>. | |
773 | .PP |