1 .TH "LTTNGTOP" "1" "April 18, 2012" "" ""
4 lttngtop \(em LTTng Trace Viewer
16 Lttngtop is a ncurses interface for reading and browsing traces recorded by the
17 LTTng tracer and displaying various statistics. As of now, the cpu usage,
18 performance counters and per process/file I/O bandwidth are displayed. This
19 version currently only supports offline traces, but a live version is in alpha
20 and will be available for testing soon.
27 .SH "TRACE REQUIREMENTS"
31 LTTngTop requires that the pid, procname, tid and ppid context information
32 are enabled during tracing.
36 If you want the CPU activity view, you need the sched_switch event, if you
37 want the I/O statistics, you need to enable the system call tracing, and if
38 you want the performance counters, you need to enable them for the events you
39 are interested in (or all of them). Note, there is a hardware limitation for the
40 number of performance counter you can enable, check dmesg for information.
44 The following example creates a trace with all events enabled, the mandatory context informations and
45 three performance counters. It assumes that you are running as root or with a user part of the tracing group and a lttng-sessiond
51 lttng enable-event -k -a
52 lttng add-context -k -t pid -t procname -t tid -t ppid -t perf:cache-misses -t perf:major-faults -t perf:branch-load-misses
62 \ \ \'\fBF2\fR\': \fICPUTop \fR
63 Switch to the CPUTop view which displays the CPU usage of each process
65 \ \ \'\fBF3\fR\': \fIPerfTop \fR
66 Switch to the PerfTop view which displays the performance counters (PMU) value of each process (if enabled during tracing)
68 \ \ \'\fBF4\fR\': \fIIOTop \fR
69 Switch to the IOTop view which displays the I/O usage of each process (as of now read and writes on any file descriptor network or disk)
71 \ \ \'\fBEnter\fR\': \fIProcess details \fR
72 Display all relevant information for the process selected
74 \ \ \'\fBSpace\fR\': \fIHighlight \fR
75 Highlights the process under the blue line to make it easy to find it across all views or toggle view in preference panel\fR
77 \ \ \'\fBq\fR\': \fIQuit \fR
80 \ \ \'\fBr\fR\': \fIPreferences \fR
81 Display the preference menu for the current view, this menu helps select the column displayed (only in PerfTop view for now) and the column to sort, use 's' to sort and 'space' to toggle the view
83 \ \ \'\fBs\fR\': \fISort \fR
84 In preference view, sort on the currently selected line
86 \ \ \'\fBp\fR\': \fIPause/Resume \fR
87 Pause the display, hit again to resume the refresh (only works when the trace has not been fully displayed)
89 \ \ \'\fBRight arrow\fR\': \fIMove forward in time \fR
90 Display the next second of data, can be hit several time to bypass the default 1 second refresh period to fast forward
92 \ \ \'\fBLeft arrow\fR\': \fIMove backward in time \fR
93 Display the previous second of data, automatically switch to pause if not already enabled
95 \ \ \'\fBUp arrow\' / \'k\'\fR: \fIMove UP the cursor \fR
96 Move up the blue line to select processes \fR
98 \ \ \'\fBDown arrow\' / \'j\'\fR: \fIMove DOWN the cursor \fR
99 Move down the blue line to select processes
104 babeltrace(1), babeltrace-log(1), lttng(1), lttng-ust(3), lttng-sessiond(8)
109 No knows bugs at this point.
111 If you encounter any issues or usability problem, please report it on
112 our mailing list <lttng-dev@lists.lttng.org> to help improve this
116 LTTngTop is distributed under the GPLv2 license. See the LICENSE file
117 in the source tree for details.
120 A Web site is available at http://www.efficios.com/babeltrace for more
121 information on Babeltrace and the Common Trace Format. See
122 http://lttng.org for more information on the LTTng project.
124 Mailing list for support and development: <lttng-dev@lists.lttng.org>.
126 You can find us on IRC server irc.oftc.net (OFTC) in #lttng.
132 LTTngTop was originally written by Julien Desfossez, with contribution
133 from Mathieu Bain for the I/O bandwidth view, and suggestions and ideas
134 from the team working with the LTTng project. It is currently
135 maintained by Julien Desfossez <jdesfossez@efficios.com>