X-Git-Url: https://git.liburcu.org/?a=blobdiff_plain;f=2.12%2Flttng-docs-2.12.txt;fp=2.12%2Flttng-docs-2.12.txt;h=5c1cce63fe130568c80e20fa6cff545f36e7a285;hb=2aced17eaed27e378b2b01e6164d7cd40f0f0164;hp=c3a937d05c85ccf62d9a7eaa952dddc0d993f850;hpb=f9bace78581e1b26112fef8cfc7c7a5835302eb0;p=lttng-docs.git diff --git a/2.12/lttng-docs-2.12.txt b/2.12/lttng-docs-2.12.txt index c3a937d..5c1cce6 100644 --- a/2.12/lttng-docs-2.12.txt +++ b/2.12/lttng-docs-2.12.txt @@ -1114,7 +1114,7 @@ Once you have completed the <> and <> tutorials, you can inspect the recorded events. -There are many tools you can use to read LTTng traces: +There are tools you can use to read LTTng traces: https://babeltrace.org/[Babeltrace{nbsp}2]:: A rich, flexible trace manipulation toolkit which includes @@ -1134,11 +1134,6 @@ http://tracecompass.org/[Trace Compass]:: A graphical user interface for viewing and analyzing any type of logs or traces, including those of LTTng. -https://github.com/lttng/lttng-analyses[**LTTng analyses**]:: - An experimental project which includes many high-level analyses of - LTTng kernel traces, like scheduling statistics, interrupt - frequency distribution, top CPU usage, and more. - NOTE: This section assumes that LTTng saved the traces it recorded during the previous tutorials to their default location, in the dir:{$LTTNG_HOME/lttng-traces} directory. The env:LTTNG_HOME @@ -8061,11 +8056,6 @@ log level:: project which you can use to send and receive control messages to and from a <>. -LTTng analyses:: - The https://github.com/lttng/lttng-analyses[LTTng analyses] project, - which is a set of analyzing programs that you can use to obtain a - higher level view of an <> <>. - cmd:lttng-consumerd:: The name of the <> program.