Commit | Line | Data |
---|---|---|
b107a0b1 | 1 | .TH "LTTNG" "1" "July 18th, 2013" "" "" |
6991b181 DG |
2 | |
3 | .SH "NAME" | |
c5db699c | 4 | lttng \(em LTTng 2.x tracer control command line tool |
6991b181 DG |
5 | |
6 | .SH "SYNOPSIS" | |
7 | ||
8 | .PP | |
6991b181 | 9 | lttng [OPTIONS] <COMMAND> |
6991b181 DG |
10 | .SH "DESCRIPTION" |
11 | ||
12 | .PP | |
13 | The LTTng project aims at providing highly efficient tracing tools for Linux. | |
7b4572b7 | 14 | Its tracers help track down performance issues and debug problems |
6991b181 DG |
15 | involving multiple concurrent processes and threads. Tracing across multiple |
16 | systems is also possible. | |
17 | ||
fa072eae | 18 | The \fBlttng\fP command line tool from the lttng-tools package is used to control |
7b4572b7 JG |
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 | |
6991b181 DG |
21 | package. |
22 | ||
23 | LTTng uses a session daemon (lttng-sessiond(8)), acting as a tracing registry, | |
50a3b92a | 24 | which allows you to interact with multiple tracers (kernel and user-space) |
6991b181 DG |
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. | |
28 | ||
50a3b92a DG |
29 | We introduce the notion of \fBtracing domains\fP which is essentially a type of |
30 | tracer (kernel or user space for now). In the future, we could see a third | |
31 | tracer being for instance an hypervisor. For some commands, you'll need to | |
7b4572b7 JG |
32 | specify on which domain the command operates (-u or -k). For instance, the |
33 | kernel domain must be specified when enabling a kernel event. | |
50a3b92a | 34 | |
6991b181 DG |
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 | |
7b4572b7 | 38 | kernel. Session daemons can co-exist, meaning that you can have a session daemon |
fa072eae | 39 | running as Alice that can be used to trace her applications along side with a |
7b4572b7 | 40 | root daemon or even a Bob daemon. We highly recommend starting the session |
6991b181 DG |
41 | daemon at boot time for stable and long term tracing. |
42 | ||
d36f8186 DG |
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). | |
6991b181 DG |
47 | .SH "OPTIONS" |
48 | ||
49 | .PP | |
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. | |
52 | .PP | |
53 | ||
54 | .TP | |
c9e32613 | 55 | .BR "\-h, \-\-help" |
6991b181 DG |
56 | Show summary of possible options and commands. |
57 | .TP | |
c9e32613 | 58 | .BR "\-v, \-\-verbose" |
6991b181 | 59 | Increase verbosity. |
d829b38c | 60 | Three levels of verbosity are available which are triggered by putting additional v to |
fa072eae | 61 | the option (\-vv or \-vvv) |
6991b181 | 62 | .TP |
c9e32613 | 63 | .BR "\-q, \-\-quiet" |
6991b181 DG |
64 | Suppress all messages (even errors). |
65 | .TP | |
c9e32613 | 66 | .BR "\-g, \-\-group NAME" |
6991b181 DG |
67 | Set unix tracing group name. (default: tracing) |
68 | .TP | |
c9e32613 | 69 | .BR "\-n, \-\-no-sessiond" |
6991b181 DG |
70 | Don't automatically spawn a session daemon. |
71 | .TP | |
391b9c72 | 72 | .BR "\-\-sessiond\-path PATH" |
6991b181 DG |
73 | Set session daemon full binary path. |
74 | .TP | |
c9e32613 | 75 | .BR "\-\-list\-options" |
6991b181 DG |
76 | Simple listing of lttng options. |
77 | .TP | |
c9e32613 | 78 | .BR "\-\-list\-commands" |
6991b181 DG |
79 | Simple listing of lttng commands. |
80 | .SH "COMMANDS" | |
81 | ||
812a5eb7 | 82 | .PP |
ee2758e5 | 83 | \fBadd-context\fP [OPTIONS] |
812a5eb7 | 84 | .RS |
6991b181 DG |
85 | Add context to event(s) and/or channel(s). |
86 | ||
391b9c72 DG |
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 | |
90 | the perf kernel API). | |
6991b181 DG |
91 | |
92 | For example, this command will add the context information 'prio' and two perf | |
93 | counters (hardware branch misses and cache misses), to all events in the trace | |
94 | data output: | |
95 | ||
812a5eb7 MD |
96 | .nf |
97 | # lttng add-context \-k \-t prio \-t perf:branch-misses \\ | |
98 | \-t perf:cache-misses | |
99 | .fi | |
6991b181 | 100 | |
c9e32613 | 101 | Please take a look at the help (\-h/\-\-help) for a detailed list of available |
6991b181 DG |
102 | contexts. |
103 | ||
bd337b98 DG |
104 | If no channel is given (\-c), the context is added to all channels that were |
105 | already enabled. If the session has no channel, a default channel is created. | |
31ea4846 | 106 | Otherwise the context will be added only to the given channel (\-c). |
6991b181 | 107 | |
c9e32613 | 108 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 | 109 | file. |
6991b181 DG |
110 | |
111 | .B OPTIONS: | |
112 | ||
812a5eb7 MD |
113 | .TP |
114 | .BR "\-h, \-\-help" | |
115 | Show summary of possible options and commands. | |
116 | .TP | |
117 | .BR "\-s, \-\-session NAME" | |
118 | Apply on session name. | |
119 | .TP | |
120 | .BR "\-c, \-\-channel NAME" | |
121 | Apply on channel name. | |
122 | .TP | |
123 | .BR "\-k, \-\-kernel" | |
124 | Apply for the kernel tracer | |
125 | .TP | |
126 | .BR "\-u, \-\-userspace" | |
127 | Apply for the user-space tracer | |
128 | .TP | |
129 | .BR "\-t, \-\-type TYPE" | |
130 | Context type. You can repeat this option on the command line. Please | |
131 | use "lttng add-context \-h" to list all available types. | |
132 | .RE | |
133 | .PP | |
6991b181 | 134 | |
22019883 MD |
135 | .PP |
136 | \fBcalibrate\fP [OPTIONS] | |
137 | .RS | |
6991b181 DG |
138 | Quantify LTTng overhead |
139 | ||
140 | The LTTng calibrate command can be used to find out the combined average | |
141 | overhead of the LTTng tracer and the instrumentation mechanisms used. This | |
142 | overhead can be calibrated in terms of time or using any of the PMU performance | |
143 | counter available on the system. | |
144 | ||
145 | For now, the only calibration implemented is that of the kernel function | |
146 | instrumentation (kretprobes). | |
147 | ||
148 | * Calibrate kernel function instrumentation | |
149 | ||
150 | Let's use an example to show this calibration. We use an i7 processor with 4 | |
151 | general-purpose PMU registers. This information is available by issuing dmesg, | |
152 | looking for "generic registers". | |
153 | ||
154 | This sequence of commands will gather a trace executing a kretprobe hooked on | |
155 | an empty function, gathering PMU counters LLC (Last Level Cache) misses | |
c9e32613 | 156 | information (see lttng add-context \-\-help to see the list of available PMU |
6991b181 DG |
157 | counters). |
158 | ||
22019883 | 159 | .nf |
6991b181 | 160 | # lttng create calibrate-function |
22019883 MD |
161 | # lttng enable-event calibrate \-\-kernel \\ |
162 | \-\-function lttng_calibrate_kretprobe | |
163 | # lttng add-context \-\-kernel \-t perf:LLC-load-misses \\ | |
164 | \-t perf:LLC-store-misses \\ | |
165 | \-t perf:LLC-prefetch-misses | |
6991b181 DG |
166 | # lttng start |
167 | # for a in $(seq 1 10); do \\ | |
c9e32613 | 168 | lttng calibrate \-\-kernel \-\-function; |
6991b181 DG |
169 | done |
170 | # lttng destroy | |
22019883 MD |
171 | # babeltrace $(ls \-1drt ~/lttng-traces/calibrate-function-* \\ |
172 | | tail \-n 1) | |
173 | .fi | |
6991b181 DG |
174 | |
175 | The output from babeltrace can be saved to a text file and opened in a | |
176 | spreadsheet (e.g. oocalc) to focus on the per-PMU counter delta between | |
177 | consecutive "calibrate_entry" and "calibrate_return" events. Note that these | |
178 | counters are per-CPU, so scheduling events would need to be present to account | |
179 | for migration between CPU. Therefore, for calibration purposes, only events | |
180 | staying on the same CPU must be considered. | |
181 | ||
182 | The average result, for the i7, on 10 samples: | |
183 | ||
22019883 | 184 | .nf |
6991b181 DG |
185 | Average Std.Dev. |
186 | perf_LLC_load_misses: 5.0 0.577 | |
187 | perf_LLC_store_misses: 1.6 0.516 | |
188 | perf_LLC_prefetch_misses: 9.0 14.742 | |
22019883 | 189 | .fi |
6991b181 DG |
190 | |
191 | As we can notice, the load and store misses are relatively stable across runs | |
192 | (their standard deviation is relatively low) compared to the prefetch misses. | |
193 | We can conclude from this information that LLC load and store misses can be | |
194 | accounted for quite precisely, but prefetches within a function seems to behave | |
195 | too erratically (not much causality link between the code executed and the CPU | |
196 | prefetch activity) to be accounted for. | |
6991b181 DG |
197 | |
198 | .B OPTIONS: | |
199 | ||
22019883 MD |
200 | .TP |
201 | .BR "\-h, \-\-help" | |
202 | Show summary of possible options and commands. | |
203 | .TP | |
204 | .BR "\-k, \-\-kernel" | |
205 | Apply for the kernel tracer | |
206 | .TP | |
207 | .BR "\-u, \-\-userspace" | |
208 | Apply for the user-space tracer | |
209 | .TP | |
210 | .BR "\-\-function" | |
211 | Dynamic function entry/return probe (default) | |
212 | .RE | |
213 | .PP | |
6991b181 | 214 | |
ee2758e5 | 215 | .PP |
feb3ca56 | 216 | \fBcreate\fP [NAME] [OPTIONS] |
ee2758e5 | 217 | .RS |
6991b181 DG |
218 | Create tracing session. |
219 | ||
220 | A tracing session contains channel(s) which contains event(s). It is domain | |
7b4572b7 | 221 | agnostic, meaning that channels and events can be enabled for the |
6991b181 DG |
222 | user-space tracer and/or the kernel tracer. It acts like a container |
223 | aggregating multiple tracing sources. | |
224 | ||
225 | On creation, a \fB.lttngrc\fP file is created in your $HOME directory | |
226 | containing the current session name. If NAME is omitted, a session name is | |
fa072eae | 227 | automatically created having this form: 'auto-yyyymmdd-hhmmss'. |
6991b181 | 228 | |
c9e32613 | 229 | If no \fB\-o, \-\-output\fP is specified, the traces will be written in |
6991b181 | 230 | $HOME/lttng-traces. |
feb0f3e5 AM |
231 | |
232 | The $HOME environment variable can be overridden by defining the environment | |
233 | variable LTTNG_HOME. This is useful when the user running the commands has | |
234 | a non-writeable home directory. | |
6991b181 | 235 | |
beb7c148 DG |
236 | The session name MUST NOT contain the character '/'. |
237 | ||
6991b181 DG |
238 | .B OPTIONS: |
239 | ||
ee2758e5 MD |
240 | .TP |
241 | .BR "\-h, \-\-help" | |
242 | Show summary of possible options and commands. | |
243 | .TP | |
244 | .BR "\-\-list-options" | |
245 | Simple listing of options | |
246 | .TP | |
247 | .BR "\-o, \-\-output PATH" | |
248 | Specify output path for traces | |
249 | .TP | |
250 | .BR "\-\-no-output" | |
7b4572b7 | 251 | Traces will not be output |
ee2758e5 MD |
252 | .TP |
253 | .BR "\-\-snapshot" | |
254 | Set the session in snapshot mode. Created in no-output mode and uses the | |
7b4572b7 | 255 | URL, if one is specified, as the default snapshot output. Every channel will be set |
ee2758e5 | 256 | in overwrite mode and with mmap output (splice not supported). |
6b8f2e64 | 257 | |
ee2758e5 MD |
258 | .TP |
259 | .BR "\-U, \-\-set-url=URL" | |
260 | Set URL for the consumer output destination. It is persistent for the | |
261 | session lifetime. Redo the command to change it. This will set both data | |
262 | and control URL for network. | |
263 | .TP | |
264 | .BR "\-C, \-\-ctrl-url=URL" | |
265 | Set control path URL. (Must use -D also) | |
266 | .TP | |
267 | .BR "\-D, \-\-data-url=URL" | |
268 | Set data path URL. (Must use -C also) | |
269 | .PP | |
6b8f2e64 DG |
270 | Using these options, each API call can be controlled individually. For |
271 | instance, \-C does not enable the consumer automatically. You'll need the \-e | |
272 | option for that. | |
273 | ||
785d2d0d DG |
274 | .B URL FORMAT: |
275 | ||
276 | proto://[HOST|IP][:PORT1[:PORT2]][/TRACE_PATH] | |
277 | ||
278 | Supported protocols are (proto): | |
ee2758e5 MD |
279 | .TP |
280 | .BR "file://..." | |
281 | Local filesystem full path. | |
785d2d0d | 282 | |
ee2758e5 MD |
283 | .TP |
284 | .BR "net://..." | |
285 | This will use the default network transport layer which is TCP for both | |
286 | control (PORT1) and data port (PORT2). The default ports are | |
287 | respectively 5342 and 5343. Note that net[6]:// is not yet supported. | |
785d2d0d | 288 | |
ee2758e5 MD |
289 | .TP |
290 | .BR "tcp[6]://..." | |
291 | Can only be used with -C and -D together | |
785d2d0d DG |
292 | |
293 | NOTE: IPv6 address MUST be enclosed in brackets '[]' (rfc2732) | |
6b8f2e64 DG |
294 | |
295 | .B EXAMPLES: | |
296 | ||
ee2758e5 | 297 | .nf |
6b8f2e64 | 298 | # lttng create -U net://192.168.1.42 |
ee2758e5 | 299 | .fi |
6b8f2e64 DG |
300 | Uses TCP and default ports for the given destination. |
301 | ||
ee2758e5 | 302 | .nf |
6b8f2e64 | 303 | # lttng create -U net6://[fe80::f66d:4ff:fe53:d220] |
ee2758e5 | 304 | .fi |
6b8f2e64 DG |
305 | Uses TCP, default ports and IPv6. |
306 | ||
ee2758e5 | 307 | .nf |
6b8f2e64 | 308 | # lttng create s1 -U net://myhost.com:3229 |
6991b181 | 309 | .fi |
ee2758e5 MD |
310 | Create session s1 and set its consumer to myhost.com on port 3229 for control. |
311 | .RE | |
312 | .PP | |
6991b181 | 313 | |
f2b14ef1 MD |
314 | .PP |
315 | \fBdestroy\fP [NAME] [OPTIONS] | |
316 | .RS | |
6991b181 DG |
317 | Teardown tracing session |
318 | ||
319 | Free memory on the session daemon and tracer side. It's gone! | |
320 | ||
321 | If NAME is omitted, the session name is taken from the .lttngrc file. | |
6991b181 DG |
322 | |
323 | .B OPTIONS: | |
324 | ||
f2b14ef1 MD |
325 | .TP |
326 | .BR "\-h, \-\-help" | |
327 | Show summary of possible options and commands. | |
328 | .TP | |
329 | .BR "\-a, \-\-all" | |
330 | Destroy all sessions | |
331 | .TP | |
332 | .BR "\-\-list-options" | |
333 | Simple listing of options | |
334 | .RE | |
335 | .PP | |
6991b181 | 336 | |
05be3802 MD |
337 | .PP |
338 | \fBenable-channel\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS] | |
339 | .RS | |
6991b181 DG |
340 | Enable tracing channel |
341 | ||
004f3466 DG |
342 | To enable an event, you must enable both the event and the channel that |
343 | contains it. | |
b883c01b | 344 | |
c9e32613 | 345 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 | 346 | file. |
7972aab2 | 347 | |
05be3802 MD |
348 | Exactly one of \-k or -u must be specified. |
349 | ||
7972aab2 | 350 | It is important to note that if a certain type of buffers is used, the session |
bd337b98 | 351 | will be set with that type and all other subsequent channel needs to have the |
7972aab2 | 352 | same type. |
bd337b98 | 353 | |
d2f11c4a DG |
354 | Note that once the session has been started and enabled on the tracer side, |
355 | it's not possible anymore to enable a new channel for that session. | |
6991b181 DG |
356 | |
357 | .B OPTIONS: | |
358 | ||
05be3802 MD |
359 | .TP |
360 | .BR "\-h, \-\-help" | |
361 | Show this help | |
362 | .TP | |
363 | .BR "\-\-list-options" | |
364 | Simple listing of options | |
365 | .TP | |
366 | .BR "\-s, \-\-session NAME" | |
367 | Apply on session name | |
368 | .TP | |
369 | .BR "\-k, \-\-kernel" | |
370 | Apply to the kernel tracer | |
371 | .TP | |
372 | .BR "\-u, \-\-userspace" | |
373 | Apply to the user-space tracer | |
374 | .TP | |
375 | .BR "\-\-discard" | |
376 | Discard event when subbuffers are full (default) | |
377 | .TP | |
378 | .BR "\-\-overwrite" | |
379 | Flight recorder mode : overwrites events when subbuffers are full | |
380 | .TP | |
381 | .BR "\-\-subbuf-size SIZE" | |
382 | Subbuffer size in bytes {+k,+M,+G}. | |
383 | (default UST uid: 131072, UST pid: 4096, kernel: 262144, metadata: 4096) | |
384 | Rounded up to the next power of 2. | |
385 | ||
386 | The minimum subbuffer size, for each tracer, is the max value between | |
387 | the default above and the system page size. You can issue this command | |
388 | to get the current page size on your system: \fB$ getconf PAGE_SIZE\fP | |
389 | .TP | |
390 | .BR "\-\-num-subbuf NUM" | |
391 | Number of subbuffers. (default UST uid: 4, UST pid: 4, kernel: 4, | |
392 | metadata: 2) Rounded up to the next power of 2. | |
393 | .TP | |
394 | .BR "\-\-switch-timer USEC" | |
395 | Switch subbuffer timer interval in µsec. | |
396 | (default UST uid: 0, UST pid: 0, kernel: 0, metadata: 0) | |
397 | .TP | |
398 | .BR "\-\-read-timer USEC" | |
399 | Read timer interval in µsec. | |
400 | (default UST uid: 0, UST pid: 0, kernel: 200000, metadata: 0) | |
401 | .TP | |
402 | .BR "\-\-output TYPE" | |
403 | Channel output type. Possible values: mmap, splice | |
404 | (default UST uid: mmap, UST pid: mmap, kernel: splice, metadata: mmap) | |
405 | .TP | |
406 | .BR "\-\-buffers-uid" | |
407 | Use per UID buffer (\-u only). Buffers are shared between applications | |
408 | that have the same UID. | |
409 | .TP | |
410 | .BR "\-\-buffers-pid" | |
411 | Use per PID buffer (\-u only). Each application has its own buffers. | |
412 | .TP | |
413 | .BR "\-\-buffers-global" | |
414 | Use shared buffer for the whole system (\-k only) | |
415 | .TP | |
416 | .BR "\-C, \-\-tracefile-size SIZE" | |
417 | Maximum size of each tracefile within a stream (in bytes). | |
418 | 0 means unlimited. (default: 0) | |
419 | .TP | |
420 | .BR "\-W, \-\-tracefile-count COUNT" | |
421 | Used in conjunction with \-C option, this will limit the number of files | |
422 | created to the specified count. 0 means unlimited. (default: 0) | |
1624d5b7 JD |
423 | |
424 | .B EXAMPLES: | |
425 | ||
05be3802 MD |
426 | .nf |
427 | $ lttng enable-channel -k -C 4096 -W 32 chan1 | |
428 | .fi | |
7b4572b7 | 429 | For each stream, the maximum size of each trace file will be 4096 bytes and |
cea28771 | 430 | there will be a maximum of 32 different files. The file count is appended after |
1624d5b7 JD |
431 | the stream number as seen in the following example. The last trace file is |
432 | smaller than 4096 since it was not completely filled. | |
433 | ||
05be3802 | 434 | .nf |
1624d5b7 JD |
435 | ~/lttng-traces/[...]/chan1_0_0 (4096) |
436 | ~/lttng-traces/[...]/chan1_0_1 (4096) | |
437 | ~/lttng-traces/[...]/chan1_0_2 (3245) | |
438 | ~/lttng-traces/[...]/chan1_1_0 (4096) | |
439 | ... | |
05be3802 | 440 | .fi |
1624d5b7 | 441 | |
05be3802 MD |
442 | .nf |
443 | $ lttng enable-channel -k -C 4096 | |
444 | .fi | |
1624d5b7 JD |
445 | This will create trace files of 4096 bytes and will create new ones as long as |
446 | there is data available. | |
05be3802 MD |
447 | .RE |
448 | .PP | |
6991b181 | 449 | |
6a240cd9 MD |
450 | .PP |
451 | \fBenable-event\fP NAME[,NAME2,...] [-k|-u] [OPTIONS] | |
452 | .RS | |
6991b181 DG |
453 | Enable tracing event |
454 | ||
c9e32613 | 455 | A tracing event is always assigned to a channel. If \fB\-c, \-\-channel\fP is |
6991b181 | 456 | omitted, a default channel named '\fBchannel0\fP' is created and the event is |
85076754 MD |
457 | added to it. If \fB\-c, \-\-channel\fP is omitted, but a non-default |
458 | channel already exists within the session, an error is returned. For the | |
459 | user-space tracer, using \fB\-a, \-\-all\fP is the same as using the | |
460 | wildcard "*". | |
6991b181 | 461 | |
c9e32613 | 462 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 | 463 | file. |
6991b181 DG |
464 | |
465 | .B OPTIONS: | |
466 | ||
6a240cd9 MD |
467 | .TP |
468 | .BR "\-h, \-\-help" | |
469 | Show summary of possible options and commands. | |
470 | .TP | |
471 | .BR "\-\-list-options" | |
472 | Simple listing of options | |
473 | .TP | |
474 | .BR "\-s, \-\-session NAME" | |
475 | Apply on session name | |
476 | .TP | |
477 | .BR "\-c, \-\-channel NAME" | |
478 | Apply on channel name | |
479 | .TP | |
480 | .BR "\-a, \-\-all" | |
7b4572b7 | 481 | Enable all tracepoints and syscalls. This actually enables a single |
6a240cd9 MD |
482 | wildcard event "*". |
483 | .TP | |
484 | .BR "\-k, \-\-kernel" | |
485 | Apply for the kernel tracer | |
486 | .TP | |
487 | .BR "\-u, \-\-userspace" | |
488 | Apply for the user-space tracer | |
489 | .TP | |
490 | .BR "\-\-tracepoint" | |
7b4572b7 | 491 | Tracepoint event (default). Userspace tracer supports wildcards at the end |
6a240cd9 MD |
492 | of string. Don't forget to quote to deal with bash expansion. |
493 | e.g.: | |
6991b181 | 494 | .nf |
6991b181 DG |
495 | "*" |
496 | "app_component:na*" | |
6991b181 | 497 | .fi |
6a240cd9 MD |
498 | .TP |
499 | .BR "\-\-loglevel NAME" | |
500 | Tracepoint loglevel range from 0 to loglevel. Listed in the help (\-h). | |
501 | .TP | |
502 | .BR "\-\-loglevel-only NAME" | |
503 | Tracepoint loglevel (only this loglevel). | |
504 | The loglevel or loglevel-only options should be combined with a | |
505 | tracepoint name or tracepoint wildcard. | |
506 | .TP | |
507 | .BR "\-\-probe (addr | symbol | symbol+offset)" | |
508 | Dynamic probe. Addr and offset can be octal (0NNN...), decimal (NNN...) | |
509 | or hexadecimal (0xNNN...) | |
510 | .TP | |
511 | .BR "\-\-function (addr | symbol | symbol+offset)" | |
512 | Dynamic function entry/return probe. Addr and offset can be octal | |
513 | (0NNN...), decimal (NNN...) or hexadecimal (0xNNN...) | |
514 | .TP | |
515 | .BR "\-\-syscall" | |
516 | System call event. Enabling syscalls tracing (kernel tracer), you will | |
517 | not be able to disable them with disable-event. This is a known | |
518 | limitation. You can disable the entire channel to do the trick. | |
519 | .TP | |
520 | .BR "\-\-filter 'expression'" | |
521 | Set a filter on a newly enabled event. Filter expression on event | |
7b4572b7 JG |
522 | fields and context. The event will be recorded if the filter's |
523 | expression evaluates to TRUE. Only specify on first activation of a | |
524 | given event within a session. | |
525 | Specifying a filter is only allowed when enabling events within a session before | |
6a240cd9 MD |
526 | tracing is started. If the filter fails to link with the event |
527 | within the traced domain, the event will be discarded. | |
7b4572b7 | 528 | Filtering is currently only implemented for the user-space tracer. |
6a240cd9 MD |
529 | |
530 | Expression examples: | |
531 | ||
532 | .nf | |
533 | 'intfield > 500 && intfield < 503' | |
534 | '(strfield == "test" || intfield != 10) && intfield > 33' | |
535 | 'doublefield > 1.1 && intfield < 5.3' | |
536 | .fi | |
537 | ||
538 | Wildcards are allowed at the end of strings: | |
539 | 'seqfield1 == "te*"' | |
540 | In string literals, the escape character is a '\\'. Use '\\*' for | |
7b4572b7 JG |
541 | the '*' character, and '\\\\' for the '\\' character sequence. Wildcard |
542 | matches any sequence of characters, including an empty sub-string | |
543 | (matches 0 or more characters). | |
6a240cd9 | 544 | |
7b4572b7 JG |
545 | Context information can be used for filtering. The examples below shows |
546 | usage of context filtering on the process name (using a wildcard), process ID | |
547 | range, and unique thread ID. The process and thread IDs of | |
6a240cd9 MD |
548 | running applications can be found under columns "PID" and "LWP" of the |
549 | "ps -eLf" command. | |
550 | ||
551 | .nf | |
552 | '$ctx.procname == "demo*"' | |
553 | '$ctx.vpid >= 4433 && $ctx.vpid < 4455' | |
554 | '$ctx.vtid == 1234' | |
555 | .fi | |
556 | ||
557 | .RE | |
558 | .PP | |
6991b181 | 559 | |
272c6a17 MD |
560 | .PP |
561 | \fBdisable-channel\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS] | |
562 | .RS | |
6991b181 DG |
563 | Disable tracing channel |
564 | ||
7b4572b7 JG |
565 | Disabling a channel disables the tracing of all of the channel's events. A channel |
566 | can be reenabled by calling \fBlttng enable-channel NAME\fP again. | |
6991b181 | 567 | |
c9e32613 | 568 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 | 569 | file. |
6991b181 DG |
570 | |
571 | .B OPTIONS: | |
572 | ||
272c6a17 MD |
573 | .TP |
574 | .BR "\-h, \-\-help" | |
575 | Show summary of possible options and commands. | |
576 | .TP | |
577 | .BR "\-\-list-options" | |
578 | Simple listing of options | |
579 | .TP | |
580 | .BR "\-s, \-\-session NAME" | |
581 | Apply on session name | |
582 | .TP | |
583 | .BR "\-k, \-\-kernel" | |
584 | Apply for the kernel tracer | |
585 | .TP | |
586 | .BR "\-u, \-\-userspace" | |
587 | Apply for the user-space tracer | |
588 | .RE | |
589 | .PP | |
6991b181 | 590 | |
c138a39b MD |
591 | .PP |
592 | \fBdisable-event\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS] | |
593 | .RS | |
6991b181 DG |
594 | Disable tracing event |
595 | ||
596 | The event, once disabled, can be re-enabled by calling \fBlttng enable-event | |
597 | NAME\fP again. | |
598 | ||
c9e32613 | 599 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
6991b181 | 600 | file. |
6991b181 | 601 | |
85076754 MD |
602 | If \fB\-c, \-\-channel\fP is omitted, the default channel name is used. |
603 | If \fB\-c, \-\-channel\fP is omitted, but a non-default channel already | |
604 | exists within the session, an error is returned. | |
605 | ||
6991b181 DG |
606 | .B OPTIONS: |
607 | ||
c138a39b MD |
608 | .TP |
609 | .BR "\-h, \-\-help" | |
610 | Show summary of possible options and commands. | |
611 | .TP | |
612 | .BR "\-\-list-options" | |
613 | Simple listing of options | |
614 | .TP | |
615 | .BR "\-s, \-\-session NAME" | |
616 | Apply on session name | |
617 | .TP | |
85076754 MD |
618 | .BR "\-c, \-\-channel NAME" |
619 | Apply on channel name | |
620 | .TP | |
c138a39b MD |
621 | .BR "\-a, \-\-all-events" |
622 | Disable all events. This does NOT disable "*" but rather every known | |
623 | events of the session. | |
624 | .TP | |
625 | .BR "\-k, \-\-kernel" | |
626 | Apply for the kernel tracer | |
627 | .TP | |
628 | .BR "\-u, \-\-userspace" | |
629 | Apply for the user-space tracer | |
630 | .RE | |
631 | .PP | |
6991b181 | 632 | |
747361fe MD |
633 | .PP |
634 | \fBlist\fP [OPTIONS] [SESSION [SESSION OPTIONS]] | |
635 | .RS | |
c9e32613 | 636 | List tracing session information. |
6991b181 DG |
637 | |
638 | With no arguments, it will list available tracing session(s). | |
639 | ||
fa072eae YB |
640 | With the session name, it will display the details of the session including |
641 | the trace file path, the associated channels and their state (activated | |
d829b38c | 642 | and deactivated), the activated events and more. |
fa072eae | 643 | |
c9e32613 | 644 | With \-k alone, it will list all available kernel events (except the system |
6991b181 | 645 | calls events). |
c9e32613 DG |
646 | With \-u alone, it will list all available user-space events from registered |
647 | applications. Here is an example of 'lttng list \-u': | |
6991b181 | 648 | |
747361fe | 649 | .nf |
6991b181 DG |
650 | PID: 7448 - Name: /tmp/lttng-ust/tests/hello/.libs/lt-hello |
651 | ust_tests_hello:tptest_sighandler (type: tracepoint) | |
652 | ust_tests_hello:tptest (type: tracepoint) | |
747361fe | 653 | .fi |
6991b181 DG |
654 | |
655 | You can now enable any event listed by using the name : | |
656 | \fBust_tests_hello:tptest\fP. | |
6991b181 DG |
657 | |
658 | .B OPTIONS: | |
659 | ||
747361fe MD |
660 | .TP |
661 | .BR "\-h, \-\-help" | |
662 | Show summary of possible options and commands. | |
663 | .TP | |
664 | .BR "\-\-list-options" | |
665 | Simple listing of options | |
666 | .TP | |
667 | .BR "\-k, \-\-kernel" | |
668 | Select kernel domain | |
669 | .TP | |
670 | .BR "\-u, \-\-userspace" | |
671 | Select user-space domain. | |
6991b181 | 672 | |
747361fe | 673 | .PP |
6b8f2e64 DG |
674 | .B SESSION OPTIONS: |
675 | ||
747361fe MD |
676 | .TP |
677 | .BR "\-c, \-\-channel NAME" | |
678 | List details of a channel | |
679 | .TP | |
680 | .BR "\-d, \-\-domain" | |
681 | List available domain(s) | |
682 | .RE | |
683 | .PP | |
6991b181 | 684 | |
7c96a096 MD |
685 | .PP |
686 | \fBset-session\fP NAME [OPTIONS] | |
687 | .RS | |
6991b181 DG |
688 | Set current session name |
689 | ||
690 | Will change the session name in the .lttngrc file. | |
6991b181 DG |
691 | |
692 | .B OPTIONS: | |
693 | ||
7c96a096 MD |
694 | .TP |
695 | .BR "\-h, \-\-help" | |
696 | Show summary of possible options and commands. | |
697 | .TP | |
698 | .BR "\-\-list-options" | |
699 | Simple listing of options | |
700 | .RE | |
701 | .PP | |
6991b181 | 702 | |
8df3bfe9 MD |
703 | .PP |
704 | \fBsnapshot\fP [OPTIONS] ACTION | |
705 | .RS | |
b872baea | 706 | Snapshot command for LTTng session. |
b872baea DG |
707 | |
708 | .B OPTIONS: | |
709 | ||
8df3bfe9 MD |
710 | .TP |
711 | .BR "\-h, \-\-help" | |
712 | Show summary of possible options and commands. | |
713 | .TP | |
714 | .BR "\-\-list-options" | |
715 | Simple listing of options | |
b872baea | 716 | |
8df3bfe9 | 717 | .PP |
b872baea DG |
718 | .B ACTION: |
719 | ||
8df3bfe9 | 720 | .TP |
b872baea DG |
721 | \fBadd-output\fP [-m <SIZE>] [-s <NAME>] [-n <NAME>] <URL> | -C <URL> -D <URL> |
722 | ||
723 | Setup and add an snapshot output for a session. Output are the destination | |
724 | where the snapshot will be sent. Only one output is permitted. To change it, | |
725 | you'll need to delete it and add back the new one. | |
726 | ||
8df3bfe9 | 727 | .TP |
b872baea DG |
728 | \fBdel-output\fP ID | NAME [-s <NAME>] |
729 | ||
730 | Delete an output for a session using the ID. You can either specify the | |
731 | output's ID that can be found with list-output or the name. | |
732 | ||
8df3bfe9 | 733 | .TP |
b872baea DG |
734 | \fBlist-output\fP [-s <NAME>] |
735 | ||
736 | List the output of a session. Attributes of the output are printed. | |
737 | ||
8df3bfe9 | 738 | .TP |
b872baea DG |
739 | \fBrecord\fP [-m <SIZE>] [-s <NAME>] [-n <NAME>] [<URL> | -C <URL> -D <URL>] |
740 | ||
741 | Snapshot a session's buffer(s) for all domains. If an URL is specified, it is | |
742 | used instead of a previously added output. Specifying only a name or/and a max | |
743 | size will override the current output values. For instance, you can record a | |
744 | snapshot with a custom maximum size or with a different name. | |
745 | ||
8df3bfe9 | 746 | .nf |
ceaf583b | 747 | $ lttng snapshot add-output -n mysnapshot file:///data/snapshot |
b872baea DG |
748 | [...] |
749 | $ lttng snapshot record -n new_name_snapshot | |
8df3bfe9 | 750 | .fi |
b872baea DG |
751 | |
752 | The above will create a snapshot in /data/snapshot/new_name_snapshot* directory | |
753 | rather then in mysnapshot*/ | |
b872baea | 754 | |
8df3bfe9 MD |
755 | .PP |
756 | .B DETAILED ACTION OPTIONS | |
b872baea | 757 | |
8df3bfe9 MD |
758 | .TP |
759 | .BR "\-s, \-\-session NAME" | |
760 | Apply to session name. | |
761 | .TP | |
762 | .BR "\-n, \-\-name NAME" | |
763 | Name of the snapshot's output. | |
764 | .TP | |
765 | .BR "\-m, \-\-max-size SIZE" | |
a8f307d8 SM |
766 | Maximum size in bytes of the snapshot. The maxium size does not include the |
767 | metadata file. Human readable format is accepted: {+k,+M,+G}. For instance, | |
768 | \-\-max-size 5M | |
8df3bfe9 MD |
769 | .TP |
770 | .BR "\-C, \-\-ctrl-url URL" | |
771 | Set control path URL. (Must use -D also) | |
772 | .TP | |
773 | .BR "\-D, \-\-data-url URL" | |
774 | Set data path URL. (Must use -C also) | |
775 | .RE | |
776 | .PP | |
b872baea | 777 | |
afb8ca1b MD |
778 | .PP |
779 | \fBstart\fP [NAME] [OPTIONS] | |
780 | .RS | |
6991b181 DG |
781 | Start tracing |
782 | ||
783 | It will start tracing for all tracers for a specific tracing session. | |
6991b181 | 784 | If NAME is omitted, the session name is taken from the .lttngrc file. |
6991b181 DG |
785 | |
786 | .B OPTIONS: | |
787 | ||
afb8ca1b MD |
788 | .TP |
789 | .BR "\-h, \-\-help" | |
790 | Show summary of possible options and commands. | |
791 | .TP | |
792 | .BR "\-\-list-options" | |
793 | Simple listing of options | |
794 | .RE | |
795 | .PP | |
6991b181 | 796 | |
6c09bfdb MD |
797 | .PP |
798 | \fBstop\fP [NAME] [OPTIONS] | |
799 | .RS | |
6991b181 DG |
800 | Stop tracing |
801 | ||
391b9c72 DG |
802 | It will stop tracing for all tracers for a specific tracing session. Before |
803 | returning, the command checks for data availability meaning that it will wait | |
804 | until the trace is readable for the session. Use \-\-no-wait to avoid this | |
805 | behavior. | |
6991b181 DG |
806 | |
807 | If NAME is omitted, the session name is taken from the .lttngrc file. | |
6991b181 DG |
808 | |
809 | .B OPTIONS: | |
810 | ||
6c09bfdb MD |
811 | .TP |
812 | .BR "\-h, \-\-help" | |
813 | Show summary of possible options and commands. | |
814 | .TP | |
815 | .BR "\-\-list-options" | |
816 | Simple listing of options | |
817 | .TP "\-\-no-wait" | |
818 | Don't wait for data availability. | |
819 | .RE | |
820 | .PP | |
6991b181 | 821 | |
5975c30a MD |
822 | .PP |
823 | \fBversion\fP | |
824 | .RS | |
6991b181 | 825 | Show version information |
6991b181 DG |
826 | |
827 | .B OPTIONS: | |
828 | ||
5975c30a MD |
829 | .TP |
830 | .BR "\-h, \-\-help" | |
831 | Show summary of possible options and commands. | |
832 | .TP | |
833 | .BR "\-\-list-options" | |
834 | Simple listing of options | |
835 | .RE | |
836 | .PP | |
6991b181 | 837 | |
5b4c1410 MD |
838 | .PP |
839 | \fBview\fP [SESSION_NAME] [OPTIONS] | |
840 | .RS | |
841 | View traces of a tracing session. By default, the babeltrace viewer | |
842 | will be used for text viewing. If SESSION_NAME is omitted, the session | |
843 | name is taken from the .lttngrc file. | |
6991b181 DG |
844 | |
845 | .B OPTIONS: | |
846 | ||
5b4c1410 MD |
847 | .TP |
848 | .BR "\-h, \-\-help" | |
849 | Show this help | |
850 | .TP | |
851 | .BR "\-\-list-options" | |
852 | Simple listing of options | |
853 | .TP | |
854 | .BR "\-t, \-\-trace-path PATH" | |
855 | Trace directory path for the viewer | |
856 | .TP | |
857 | .BR "\-e, \-\-viewer CMD" | |
858 | Specify viewer and/or options to use This will completely override the | |
859 | default viewers so please make sure to specify the full command. The | |
860 | trace directory path of the session will be appended at the end to the | |
861 | arguments | |
862 | .RE | |
863 | .PP | |
6991b181 | 864 | |
c206d957 | 865 | .SH "EXIT VALUES" |
b107a0b1 | 866 | .PP |
6b8f2e64 DG |
867 | On success 0 is returned and a positive value on error. Value of 1 means a command |
868 | error, 2 an undefined command, 3 a fatal error and 4 a command warning meaning that | |
869 | something went wrong during the command. | |
c206d957 | 870 | |
6b8f2e64 | 871 | Any other value above 10, please refer to |
b107a0b1 | 872 | .BR "<lttng/lttng-error.h>" |
6b8f2e64 DG |
873 | for a detailed list or use lttng_strerror() to get a human readable string of |
874 | the error code. | |
c206d957 | 875 | .PP |
b107a0b1 | 876 | |
6991b181 DG |
877 | .SH "ENVIRONMENT VARIABLES" |
878 | ||
879 | .PP | |
880 | Note that all command line options override environment variables. | |
881 | .PP | |
882 | ||
883 | .PP | |
05833633 | 884 | .IP "LTTNG_SESSIOND_PATH" |
c9e32613 DG |
885 | Allows one to specify the full session daemon binary path to lttng command line |
886 | tool. You can also use \-\-sessiond-path option having the same effect. | |
b107a0b1 MD |
887 | .PP |
888 | ||
6991b181 | 889 | .SH "SEE ALSO" |
6b8f2e64 DG |
890 | .BR babeltrace(1), |
891 | .BR lttng-ust(3), | |
892 | .BR lttng-sessiond(8), | |
893 | .BR lttng-relayd(8), | |
894 | .BR lttng-health-check(3) | |
b107a0b1 | 895 | |
6991b181 DG |
896 | .SH "BUGS" |
897 | ||
b107a0b1 | 898 | .PP |
6991b181 | 899 | If you encounter any issues or usability problem, please report it on our |
6b8f2e64 DG |
900 | mailing list <lttng-dev@lists.lttng.org> to help improve this project or |
901 | at https://bugs.lttng.org which is a bugtracker. | |
b107a0b1 MD |
902 | .PP |
903 | ||
6991b181 DG |
904 | .SH "CREDITS" |
905 | ||
906 | .PP | |
c9e32613 | 907 | lttng is distributed under the GNU General Public License version 2. See the file |
6991b181 DG |
908 | COPYING for details. |
909 | .PP | |
910 | A Web site is available at http://lttng.org for more information on the LTTng | |
911 | project. | |
912 | .PP | |
913 | You can also find our git tree at http://git.lttng.org. | |
914 | .PP | |
915 | Mailing lists for support and development: <lttng-dev@lists.lttng.org>. | |
916 | .PP | |
917 | You can find us on IRC server irc.oftc.net (OFTC) in #lttng. | |
918 | .PP | |
919 | .SH "THANKS" | |
920 | ||
921 | .PP | |
922 | Thanks to Yannick Brosseau without whom this project would never have been so | |
923 | lean and mean! Also thanks to the Ericsson teams working on tracing which | |
fa072eae | 924 | helped us greatly with detailed bug reports and unusual test cases. |
6991b181 DG |
925 | |
926 | Thanks to our beloved packager Alexandre Montplaisir-Goncalves (Ubuntu and PPA | |
927 | maintainer) and Jon Bernard for our Debian packages. | |
928 | ||
929 | Special thanks to Michel Dagenais and the DORSAL laboratory at Polytechnique de | |
930 | Montreal for the LTTng journey. | |
c9e32613 | 931 | .PP |
6991b181 DG |
932 | .SH "AUTHORS" |
933 | ||
934 | .PP | |
935 | lttng-tools was originally written by Mathieu Desnoyers, Julien Desfossez and | |
936 | David Goulet. More people have since contributed to it. It is currently | |
937 | maintained by David Goulet <dgoulet@efficios.com>. | |
938 | .PP |