X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fgetting-started%2Fviewing-and-analyzing.md;h=988ddec12cfd05c6177ee5b7b6068989f0873c5f;hb=3b5b45ec9eeae44744acb849c1a04eddd9d971c4;hp=61816240f23f751d5fb154d242fa27935e05a2a2;hpb=1d444d312c2111c135cd7622c0a47e53a198e1c9;p=lttng-docs.git diff --git a/contents/getting-started/viewing-and-analyzing.md b/contents/getting-started/viewing-and-analyzing.md index 6181624..988ddec 100644 --- a/contents/getting-started/viewing-and-analyzing.md +++ b/contents/getting-started/viewing-and-analyzing.md @@ -16,20 +16,11 @@ Many ways exist to read your LTTng traces: * Babeltrace also includes a **Python binding** so that you may easily open and read an LTTng trace with your own script, benefiting from the power of Python. - * The ** - Eclise IDE for C/C++ Developers** - includes the Tracing and Monitoring Framework (TMF) plugin which - supports LTTng traces, amongst others. * **Trace Compass** - is an Eclipse plugin, the TMF plugin mentioned above moved to its own - project, used to visualize and analyze various types of traces, - including LTTng's. It also comes as a standalone application and can be - downloaded from - here - for a daily build of the latest source code. A version containing some - experimental features like Virtual Machine analysis and Critical Path - analysis is also available - here. + is an Eclipse plugin used to visualize and analyze various types of + traces, including LTTng's. It also comes as a standalone application + and can be downloaded from + here. LTTng trace files are usually recorded in the `~/lttng-traces` directory. Let's now view the trace and perform a basic analysis using @@ -42,8 +33,8 @@ path to `babeltrace` with no options: babeltrace ~/lttng-traces/my-session -`babeltrace` will find all traces within the given path recursively and -output all their events, merging them intelligently. +`babeltrace` finds all traces within the given path recursively and +prints all their events, merging them in order of time. Listing all the system calls of a Linux kernel trace with their arguments is easy with `babeltrace` and `grep`: @@ -55,7 +46,7 @@ babeltrace ~/lttng-traces/my-kernel-session | grep sys_ Counting events is also straightforward:
-babeltrace ~/lttng-traces/my-kernel-session | grep sys_read | wc -l
+babeltrace ~/lttng-traces/my-kernel-session | grep sys_read | wc --lines
 
The text output of `babeltrace` is useful for isolating events by simple @@ -135,7 +126,7 @@ def top5proc(): last_ts = cur_ts # display top 10 - for name, ns in exec_times.most_common()[:5]: + for name, ns in exec_times.most_common(5): s = ns / 1000000000 print('{:20}{} s'.format(name, s)) @@ -152,8 +143,8 @@ python3 top5proc.py ~/lttng-sessions/my-session-.../kernel Make sure the path you provide is the directory containing actual trace -files (`channel0_0`, `metadata`, etc.): the `babeltrace` utility recurses -directories, but the Python binding does not. +files (`channel0_0`, `metadata`, and the rest): the `babeltrace` utility +recurses directories, but the Python binding does not. Here's an example of output: