Typo: intead -> instead

[lttng-docs.git] / 2.8 / lttng-docs-2.8.txt

diff --git a/2.8/lttng-docs-2.8.txt b/2.8/lttng-docs-2.8.txt
index 87e5c2d33b04a9280dd4989299b3356251748f5c..854921596883eb94f4124cef3ded00090b57e9d9 100644 (file)
--- a/2.8/lttng-docs-2.8.txt
+++ b/2.8/lttng-docs-2.8.txt
@@ -1,7 +1,7 @@
 The LTTng Documentation
 =======================
 Philippe Proulx <pproulx@efficios.com>
 The LTTng Documentation
 =======================
 Philippe Proulx <pproulx@efficios.com>

-v2.8, 25 October 2016
+v2.8, 20 February 2017

 
 
 include::../common/copyright.txt[]
 
 
 include::../common/copyright.txt[]


@@ -74,6 +74,15 @@ include::../common/acknowledgements.txt[]
 [[whats-new]]
 == What's new in LTTng {revision}?
 
 [[whats-new]]
 == What's new in LTTng {revision}?
 

+LTTng{nbsp}{revision} bears the name _Isseki Nicho_. The result of a
+collaboration between http://www.dieuduciel.com/[Dieu du Ciel!] and
+Nagano-based Shiga Kogen,
+https://www.beeradvocate.com/beer/profile/1141/53111/[_**Isseki
+Nicho**_] is a strong Imperial Dark Saison offering a rich roasted malt
+flavor combined with a complex fruity finish typical of Saison yeasts.
+
+New features and changes in LTTng{nbsp}{revision}:
+

 * **Tracing control**:
 ** You can attach <<java-application-context,Java application-specific
    context fields>> to a <<channel,channel>> with the
 * **Tracing control**:
 ** You can attach <<java-application-context,Java application-specific
    context fields>> to a <<channel,channel>> with the


@@ -372,70 +381,60 @@ but note that:
   applications.
 
 [role="growable"]
   applications.
 
 [role="growable"]

-.Availability of LTTng{nbsp}{revision} for major Linux distributions.
+.Availability of LTTng{nbsp}{revision} for major Linux distributions as of 2 December 2016.

 |====
 |Distribution |Available in releases |Alternatives
 
 |====
 |Distribution |Available in releases |Alternatives
 

-|Ubuntu
-|<<ubuntu,Ubuntu{nbsp}16.10 _Yakkety Yak_>>
+|https://www.ubuntu.com/[Ubuntu]
+|<<ubuntu,Ubuntu{nbsp}16.10 _Yakkety Yak_>>.

 |LTTng{nbsp}{revision} for Ubuntu{nbsp}14.04 _Trusty Tahr_
 and Ubuntu{nbsp}16.04 _Xenial Xerus_:
 <<ubuntu-ppa,use the LTTng Stable{nbsp}{revision} PPA>>.
 
 |LTTng{nbsp}{revision} for Ubuntu{nbsp}14.04 _Trusty Tahr_
 and Ubuntu{nbsp}16.04 _Xenial Xerus_:
 <<ubuntu-ppa,use the LTTng Stable{nbsp}{revision} PPA>>.
 

+LTTng{nbsp}2.9 for Ubuntu{nbsp}14.04 _Trusty Tahr_
+and Ubuntu{nbsp}16.04 _Xenial Xerus_:
+link:/docs/v2.9#doc-ubuntu-ppa[use the LTTng Stable{nbsp}2.9 PPA].
+

 <<building-from-source,Build LTTng{nbsp}{revision} from source>> for
 other Ubuntu releases.
 
 <<building-from-source,Build LTTng{nbsp}{revision} from source>> for
 other Ubuntu releases.
 

-|Fedora
-|_Not available_
-|LTTng-tools{nbsp}{revision} and LTTng-UST{nbsp}{revision} for
-Fedora{nbsp}25 and Fedora{nbsp}26 (both are not released yet).
-
-<<building-from-source,Build LTTng-modules{nbsp}{revision} from
-source>>.
-
-<<building-from-source,Build LTTng{nbsp}{revision} from source>> for
+|https://getfedora.org/[Fedora]
+|<<fedora,Fedora{nbsp}25>>.
+|<<building-from-source,Build LTTng{nbsp}{revision} from source>> for

 other Fedora releases.
 
 other Fedora releases.
 

-|Debian
-|<<debian,Debian "stretch" (testing)>>
-|
-<<building-from-source,Build LTTng{nbsp}{revision} from source>> for
+|https://www.debian.org/[Debian]
+|<<debian,Debian "stretch" (testing)>>.
+|<<building-from-source,Build LTTng{nbsp}{revision} from source>> for

 previous Debian releases.
 
 previous Debian releases.
 

-|openSUSE
+|https://www.opensuse.org/[openSUSE]

 |_Not available_
 |_Not available_

-|LTTng{nbsp}2.7 for openSUSE Leap{nbsp}42.1.
+|<<building-from-source,Build LTTng{nbsp}{revision} from source>>.

 
 

-<<building-from-source,Build LTTng{nbsp}{revision} from source>> for
-other openSUSE releases.
-
-|Arch Linux
-|<<arch-linux,Latest AUR packages>>
-|
+|https://www.archlinux.org/[Arch Linux]
+|_Not available_
+|link:/docs/v2.9#doc-arch-linux[LTTng{nbsp}2.9 from the AUR].

 
 

-|Alpine Linux
-|<<alpine-linux,Alpine Linux "edge">>
+|https://alpinelinux.org/[Alpine Linux]
+|<<alpine-linux,Alpine Linux "edge">>.

 |LTTng{nbsp}{revision} for Alpine Linux{nbsp}3.5 (not released yet).
 
 <<building-from-source,Build LTTng{nbsp}{revision} from source>> for
 other Alpine Linux releases.
 
 |LTTng{nbsp}{revision} for Alpine Linux{nbsp}3.5 (not released yet).
 
 <<building-from-source,Build LTTng{nbsp}{revision} from source>> for
 other Alpine Linux releases.
 

-|RHEL and SLES
+|https://www.redhat.com/[RHEL] and https://www.suse.com/[SLES]

 |See http://packages.efficios.com/[EfficiOS Enterprise Packages].
 |
 
 |See http://packages.efficios.com/[EfficiOS Enterprise Packages].
 |
 

-|Buildroot
-|_Not available_
-|LTTng{nbsp}{revision} for Buildroot{nbsp}2016.11 (not released yet).
-
-LTTng{nbsp}2.7 for Buildroot{nbsp}2016.02, Buildroot{nbsp}2016.05,
-and Buildroot{nbsp}2016.08.
-
-<<building-from-source,Build LTTng{nbsp}{revision} from source>> for
+|https://buildroot.org/[Buildroot]
+|<<buildroot,Buildroot 2016.11>>.
+|<<building-from-source,Build LTTng{nbsp}{revision} from source>> for

 other Buildroot releases.
 
 other Buildroot releases.
 

-|OpenEmbedded and Yocto
-|<<oe-yocto,Yocto Project{nbsp}2.2 _Morty_>> (`openembedded-core` layer)
+|http://www.openembedded.org/wiki/Main_Page[OpenEmbedded] and
+https://www.yoctoproject.org/[Yocto]
+|<<oe-yocto,Yocto Project{nbsp}2.2 _Morty_>> (`openembedded-core` layer).

 |<<building-from-source,Build LTTng{nbsp}{revision} from source>> for
 other OpenEmbedded releases.
 |====
 |<<building-from-source,Build LTTng{nbsp}{revision} from source>> for
 other OpenEmbedded releases.
 |====


@@ -473,7 +472,7 @@ sudo apt-get install liblttng-ust-agent-java
 --
 
 . **If you need to instrument and trace
 --
 
 . **If you need to instrument and trace

-  <<python-application,Python applications>>**, install the
+  <<python-application,Python{nbsp}3 applications>>**, install the

   LTTng-UST Python agent:
 +
 --
   LTTng-UST Python agent:
 +
 --


@@ -530,7 +529,7 @@ sudo apt-get install liblttng-ust-agent-java
 --
 
 . **If you need to instrument and trace
 --
 
 . **If you need to instrument and trace

-  <<python-application,Python applications>>**, install the
+  <<python-application,Python{nbsp}3 applications>>**, install the

   LTTng-UST Python agent:
 +
 --
   LTTng-UST Python agent:
 +
 --


@@ -541,57 +540,77 @@ sudo apt-get install python3-lttngust
 --
 
 
 --
 
 

-[[debian]]
-=== Debian
+[[fedora]]
+=== Fedora

 
 

-To install LTTng{nbsp}{revision} on Debian "stretch" (testing):
+To install LTTng{nbsp}{revision} on Fedora{nbsp}25:

 
 

-. Install the main LTTng{nbsp}{revision} packages:
+. Install the LTTng-tools{nbsp}{revision} and LTTng-UST{nbsp}{revision}
+  packages:

 +
 --
 [role="term"]
 ----
 +
 --
 [role="term"]
 ----

-sudo apt-get install lttng-modules-dkms
-sudo apt-get install liblttng-ust-dev
-sudo apt-get install lttng-tools
+sudo yum install lttng-tools
+sudo yum install lttng-ust

 ----
 --
 
 ----
 --
 

-. **If you need to instrument and trace <<java-application,Java
-  applications>>**, install the LTTng-UST Java agent:
+. Download, build, and install the latest LTTng-modules{nbsp}{revision}:

 +
 --
 [role="term"]
 ----
 +
 --
 [role="term"]
 ----

-sudo apt-get install liblttng-ust-agent-java
+cd $(mktemp -d) &&
+wget http://lttng.org/files/lttng-modules/lttng-modules-latest-2.8.tar.bz2 &&
+tar -xf lttng-modules-latest-2.8.tar.bz2 &&
+cd lttng-modules-2.8.* &&
+make &&
+sudo make modules_install &&
+sudo depmod -a

 ----
 --
 
 ----
 --
 

-. **If you need to instrument and trace <<python-application,Python
-  applications>>**, install the LTTng-UST Python agent:
+[IMPORTANT]
+.Java and Python application instrumentation and tracing
+====
+If you need to instrument and trace <<java-application,Java
+applications>> on openSUSE, you need to build and install
+LTTng-UST{nbsp}{revision} <<building-from-source,from source>> and pass
+the `--enable-java-agent-jul`, `--enable-java-agent-log4j`, or
+`--enable-java-agent-all` options to the `configure` script, depending
+on which Java logging framework you use.
+
+If you need to instrument and trace <<python-application,Python
+applications>> on openSUSE, you need to build and install
+LTTng-UST{nbsp}{revision} from source and pass the
+`--enable-python-agent` option to the `configure` script.
+====
+
+
+[[debian]]
+=== Debian
+
+To install LTTng{nbsp}{revision} on Debian "stretch" (testing):
+
+. Install the main LTTng{nbsp}{revision} packages:

 +
 --
 [role="term"]
 ----
 +
 --
 [role="term"]
 ----

-sudo apt-get install python3-lttngust
+sudo apt-get install lttng-modules-dkms
+sudo apt-get install liblttng-ust-dev
+sudo apt-get install lttng-tools

 ----
 --
 
 ----
 --
 

-
-[[arch-linux]]
-=== Arch Linux
-
-To install LTTng{nbsp}{revision} on Arch Linux using
-https://archlinux.fr/yaourt-en[Yaourt]:
-
-. Install the main LTTng{nbsp}{revision} packages:
+. **If you need to instrument and trace <<java-application,Java
+  applications>>**, install the LTTng-UST Java agent:

 +
 --
 [role="term"]
 ----
 +
 --
 [role="term"]
 ----

-yaourt -S lttng-tools
-yaourt -S lttng-ust
-yaourt -S lttng-modules
+sudo apt-get install liblttng-ust-agent-java

 ----
 --
 
 ----
 --
 


@@ -601,8 +620,7 @@ yaourt -S lttng-modules
 --
 [role="term"]
 ----
 --
 [role="term"]
 ----

-yaourt -S python-lttngust
-yaourt -S python2-lttngust
+sudo apt-get install python3-lttngust

 ----
 --
 
 ----
 --
 


@@ -656,6 +674,36 @@ sudo depmod -a
 --
 
 
 --
 
 

+[[enterprise-distributions]]
+=== RHEL, SUSE, and other enterprise distributions
+
+To install LTTng on enterprise Linux distributions, such as Red Hat
+Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SUSE), please
+see http://packages.efficios.com/[EfficiOS Enterprise Packages].
+
+
+[[buildroot]]
+=== Buildroot
+
+To install LTTng{nbsp}{revision} on Buildroot{nbsp}2016.11:
+
+. Launch the Buildroot configuration tool:
++
+--
+[role="term"]
+----
+make menuconfig
+----
+--
+
+. In **Kernel**, check **Linux kernel**.
+. In **Toolchain**, check **Enable WCHAR support**.
+. In **Target packages**{nbsp}&#8594; **Debugging, profiling and benchmark**,
+  check **lttng-modules** and **lttng-tools**.
+. In **Target packages**{nbsp}&#8594; **Libraries**{nbsp}&#8594;
+  **Other**, check **lttng-libust**.
+
+

 [[oe-yocto]]
 === OpenEmbedded and Yocto
 
 [[oe-yocto]]
 === OpenEmbedded and Yocto
 


@@ -698,14 +746,6 @@ LTTng-UST{nbsp}{revision} from source and pass the
 ====
 
 
 ====
 
 

-[[enterprise-distributions]]
-=== RHEL, SUSE, and other enterprise distributions
-
-To install LTTng on enterprise Linux distributions, such as Red Hat
-Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SUSE), please
-see http://packages.efficios.com/[EfficiOS Enterprise Packages].
-
-

 [[building-from-source]]
 === Build from source
 
 [[building-from-source]]
 === Build from source
 


@@ -831,14 +871,15 @@ This tutorial walks you through the steps to:
 
 The following command lines start with cmd:sudo because you need root
 privileges to trace the Linux kernel. You can avoid using cmd:sudo if
 
 The following command lines start with cmd:sudo because you need root
 privileges to trace the Linux kernel. You can avoid using cmd:sudo if

-your Unix user is a member of the <<lttng-sessiond,tracing group>>.
+your Unix user is a member of the <<tracing-group,tracing group>>.

 
 

-. Create a <<tracing-session,tracing session>>:
+. Create a <<tracing-session,tracing session>> which writes its traces
+  to dir:{/tmp/my-kernel-trace}:

 +
 --
 [role="term"]
 ----
 +
 --
 [role="term"]
 ----

-sudo lttng create my-kernel-session
+sudo lttng create my-kernel-session --output=/tmp/my-kernel-trace

 ----
 --
 
 ----
 --
 


@@ -847,21 +888,24 @@ sudo lttng create my-kernel-session
 --
 [role="term"]
 ----
 --
 [role="term"]
 ----

-lttng list --kernel
+sudo lttng list --kernel
+sudo lttng list --kernel --syscall

 ----
 --
 
 ----
 --
 

-. Create an <<event,event rule>> which matches the desired event names,
-  for example `sched_switch` and `sched_process_fork`:
+. Create <<event,event rules>> which match the desired instrumentation
+  point names, for example the `sched_switch` and `sched_process_fork`
+  tracepoints, and the man:open(2) and man:close(2) system calls:

 +
 --
 [role="term"]
 ----
 sudo lttng enable-event --kernel sched_switch,sched_process_fork
 +
 --
 [role="term"]
 ----
 sudo lttng enable-event --kernel sched_switch,sched_process_fork

+sudo lttng enable-event --kernel --syscall open,close

 ----
 --
 +
 ----
 --
 +

-You can also create an event rule which _matches_ all the Linux kernel
+You can also create an event rule which matches _all_ the Linux kernel

 tracepoints (this will generate a lot of data when tracing):
 +
 --
 tracepoints (this will generate a lot of data when tracing):
 +
 --


@@ -871,7 +915,7 @@ sudo lttng enable-event --kernel --all
 ----
 --
 
 ----
 --
 

-. Start tracing:
+. <<basic-tracing-session-control,Start tracing>>:

 +
 --
 [role="term"]
 +
 --
 [role="term"]


@@ -882,7 +926,8 @@ sudo lttng start
 
 . Do some operation on your system for a few seconds. For example,
   load a website, or list the files of a directory.
 
 . Do some operation on your system for a few seconds. For example,
   load a website, or list the files of a directory.

-. Stop tracing and destroy the tracing session:
+. <<basic-tracing-session-control,Stop tracing>> and destroy the
+  tracing session:

 +
 --
 [role="term"]
 +
 --
 [role="term"]


@@ -895,10 +940,15 @@ sudo lttng destroy
 The man:lttng-destroy(1) command does not destroy the trace data; it
 only destroys the state of the tracing session.
 
 The man:lttng-destroy(1) command does not destroy the trace data; it
 only destroys the state of the tracing session.
 

-By default, LTTng saves the traces in
-+$LTTNG_HOME/lttng-traces/__name__-__date__-__time__+,
-where +__name__+ is the tracing session name. Note that the
-env:LTTNG_HOME environment variable defaults to `$HOME` if not set.
+. For the sake of this example, make the recorded trace accessible to
+  the non-root users:
++
+--
+[role="term"]
+----
+sudo chown -R $(whoami) /tmp/my-kernel-trace
+----
+--

 
 See <<viewing-and-analyzing-your-traces,View and analyze the
 recorded events>> to view the recorded events.
 
 See <<viewing-and-analyzing-your-traces,View and analyze the
 recorded events>> to view the recorded events.


@@ -1110,7 +1160,7 @@ lttng enable-event --userspace hello_world:my_first_tracepoint
 ----
 --
 
 ----
 --
 

-. Start tracing:
+. <<basic-tracing-session-control,Start tracing>>:

 +
 --
 [role="term"]
 +
 --
 [role="term"]


@@ -1121,7 +1171,8 @@ lttng start
 
 . Go back to the running `hello` application and press Enter. The
   program executes all `tracepoint()` instrumentation points and exits.
 
 . Go back to the running `hello` application and press Enter. The
   program executes all `tracepoint()` instrumentation points and exits.

-. Stop tracing and destroy the tracing session:
+. <<basic-tracing-session-control,Stop tracing>> and destroy the
+  tracing session:

 +
 --
 [role="term"]
 +
 --
 [role="term"]


@@ -1136,7 +1187,7 @@ only destroys the state of the tracing session.
 
 By default, LTTng saves the traces in
 +$LTTNG_HOME/lttng-traces/__name__-__date__-__time__+,
 
 By default, LTTng saves the traces in
 +$LTTNG_HOME/lttng-traces/__name__-__date__-__time__+,

-where +__name__+ is the tracing session name. Note that the
+where +__name__+ is the tracing session name. The

 env:LTTNG_HOME environment variable defaults to `$HOME` if not set.
 
 See <<viewing-and-analyzing-your-traces,View and analyze the
 env:LTTNG_HOME environment variable defaults to `$HOME` if not set.
 
 See <<viewing-and-analyzing-your-traces,View and analyze the


@@ -1170,7 +1221,7 @@ Many tools are available to read LTTng traces:
 
 NOTE: This section assumes that the traces recorded during the previous
 tutorials were saved to their default location, in the
 
 NOTE: This section assumes that the traces recorded during the previous
 tutorials were saved to their default location, in the

-dir:{$LTTNG_HOME/lttng-traces} directory. Note that the env:LTTNG_HOME
+dir:{$LTTNG_HOME/lttng-traces} directory. The env:LTTNG_HOME

 environment variable defaults to `$HOME` if not set.
 
 
 environment variable defaults to `$HOME` if not set.
 
 


@@ -1193,7 +1244,7 @@ further filtering:
 
 [role="term"]
 ----
 
 [role="term"]
 ----

-babeltrace ~/lttng-traces/my-kernel-session* | grep sys_
+babeltrace /tmp/my-kernel-trace | grep _switch

 ----
 
 You can pipe the output of cmd:babeltrace into a tool like man:wc(1) to
 ----
 
 You can pipe the output of cmd:babeltrace into a tool like man:wc(1) to


@@ -1201,7 +1252,7 @@ count the recorded events:
 
 [role="term"]
 ----
 
 [role="term"]
 ----

-babeltrace ~/lttng-traces/my-kernel-session* | grep sys_read | wc --lines
+babeltrace /tmp/my-kernel-trace | grep _open | wc --lines

 ----
 
 
 ----
 
 


@@ -1303,7 +1354,7 @@ Run this script:
 
 [role="term"]
 ----
 
 [role="term"]
 ----

-python3 top5proc.py ~/lttng-traces/my-kernel-session*/kernel
+python3 top5proc.py /tmp/my-kernel-trace/kernel

 ----
 
 Output example:
 ----
 
 Output example:


@@ -3322,7 +3373,7 @@ include::../common/ust-sit-step-tp-so.txt[]
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the

-  following line:
+  following lines:

 +
 --
 [source,c]
 +
 --
 [source,c]


@@ -3409,7 +3460,7 @@ include::../common/ust-sit-step-tp-so.txt[]
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the

-  following line:
+  following lines:

 +
 --
 [source,c]
 +
 --
 [source,c]


@@ -3558,7 +3609,7 @@ include::../common/ust-sit-step-tp-so.txt[]
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the

-  following line:
+  following lines:

 +
 --
 [source,c]
 +
 --
 [source,c]


@@ -3631,7 +3682,7 @@ include::../common/ust-sit-step-tp-so.txt[]
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the
 To build the instrumented user library:
 
 . In path:{emon.c}, before including path:{tpp.h}, add the

-  following line:
+  following lines:

 +
 --
 [source,c]
 +
 --
 [source,c]


@@ -4000,7 +4051,9 @@ wget http://lttng.org/files/lttng-tools/lttng-tools-latest-2.8.tar.bz2 &&
 tar -xf lttng-tools-latest-2.8.tar.bz2 &&
 cd lttng-tools-2.8.* &&
 ./configure --libdir=/usr/local/lib32 CFLAGS=-m32 CXXFLAGS=-m32 \
 tar -xf lttng-tools-latest-2.8.tar.bz2 &&
 cd lttng-tools-2.8.* &&
 ./configure --libdir=/usr/local/lib32 CFLAGS=-m32 CXXFLAGS=-m32 \

-            LDFLAGS='-L/usr/local/lib32 -L/usr/lib32' &&
+            LDFLAGS='-L/usr/local/lib32 -L/usr/lib32' \
+            --disable-bin-lttng --disable-bin-lttng-crash \
+            --disable-bin-lttng-relayd --disable-bin-lttng-sessiond &&

 make &&
 cd src/bin/lttng-consumerd &&
 sudo make install &&
 make &&
 cd src/bin/lttng-consumerd &&
 sudo make install &&


@@ -4311,7 +4364,7 @@ The path:{liblttng-ust-cyg-profile*.so} helpers can add instrumentation
 to the entry and exit points of functions.
 
 man:gcc(1) and man:clang(1) have an option named
 to the entry and exit points of functions.
 
 man:gcc(1) and man:clang(1) have an option named

-https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html[`-finstrument-functions`]
+https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html[`-finstrument-functions`]

 which generates instrumentation calls for entry and exit to functions.
 The LTTng-UST function tracing helpers,
 path:{liblttng-ust-cyg-profile.so} and
 which generates instrumentation calls for entry and exit to functions.
 The LTTng-UST function tracing helpers,
 path:{liblttng-ust-cyg-profile.so} and


@@ -4535,6 +4588,31 @@ lttng view
 ----
 ====
 
 ----
 ====
 

+In the resulting trace, an <<event,event record>> generated by a Java
+application using `java.util.logging` is named `lttng_jul:event` and
+has the following fields:
+
+`msg`::
+  Log record's message.
+
+`logger_name`::
+  Logger name.
+
+`class_name`::
+  Name of the class in which the log statement was executed.
+
+`method_name`::
+  Name of the method in which the log statement was executed.
+
+`long_millis`::
+  Logging time (timestamp in milliseconds).
+
+`int_loglevel`::
+  Log level integer value.
+
+`int_threadid`::
+  ID of the thread in which the log statement was executed.
+

 You can use the opt:lttng-enable-event(1):--loglevel or
 opt:lttng-enable-event(1):--loglevel-only option of the
 man:lttng-enable-event(1) command to target a range of JUL log levels
 You can use the opt:lttng-enable-event(1):--loglevel or
 opt:lttng-enable-event(1):--loglevel-only option of the
 man:lttng-enable-event(1) command to target a range of JUL log levels


@@ -4683,6 +4761,37 @@ lttng view
 ----
 ====
 
 ----
 ====
 

+In the resulting trace, an <<event,event record>> generated by a Java
+application using log4j is named `lttng_log4j:event` and
+has the following fields:
+
+`msg`::
+  Log record's message.
+
+`logger_name`::
+  Logger name.
+
+`class_name`::
+  Name of the class in which the log statement was executed.
+
+`method_name`::
+  Name of the method in which the log statement was executed.
+
+`filename`::
+  Name of the file in which the executed log statement is located.
+
+`line_number`::
+  Line number at which the log statement was executed.
+
+`timestamp`::
+  Logging timestamp.
+
+`int_loglevel`::
+  Log level integer value.
+
+`thread_name`::
+  Name of the Java thread in which the log statement was executed.
+

 You can use the opt:lttng-enable-event(1):--loglevel or
 opt:lttng-enable-event(1):--loglevel-only option of the
 man:lttng-enable-event(1) command to target a range of Apache log4j log levels
 You can use the opt:lttng-enable-event(1):--loglevel or
 opt:lttng-enable-event(1):--loglevel-only option of the
 man:lttng-enable-event(1) command to target a range of Apache log4j log levels


@@ -5002,6 +5111,33 @@ lttng view
 ----
 ====
 
 ----
 ====
 

+In the resulting trace, an <<event,event record>> generated by a Python
+application is named `lttng_python:event` and has the following fields:
+
+`asctime`::
+  Logging time (string).
+
+`msg`::
+  Log record's message.
+
+`logger_name`::
+  Logger name.
+
+`funcName`::
+  Name of the function in which the log statement was executed.
+
+`lineno`::
+  Line number at which the log statement was executed.
+
+`int_loglevel`::
+  Log level integer value.
+
+`thread`::
+  ID of the Python thread in which the log statement was executed.
+
+`threadName`::
+  Name of the Python thread in which the log statement was executed.
+

 You can use the opt:lttng-enable-event(1):--loglevel or
 opt:lttng-enable-event(1):--loglevel-only option of the
 man:lttng-enable-event(1) command to target a range of Python log levels
 You can use the opt:lttng-enable-event(1):--loglevel or
 opt:lttng-enable-event(1):--loglevel-only option of the
 man:lttng-enable-event(1) command to target a range of Python log levels


@@ -5049,8 +5185,8 @@ Any event that the LTTng logger emits is named `lttng_logger` and
 belongs to the Linux kernel <<domain,tracing domain>>. However, unlike
 other instrumentation points in the kernel tracing domain, **any Unix
 user** can <<enabling-disabling-events,create an event rule>> which
 belongs to the Linux kernel <<domain,tracing domain>>. However, unlike
 other instrumentation points in the kernel tracing domain, **any Unix
 user** can <<enabling-disabling-events,create an event rule>> which

-matches its event name, not only the root user or users in the tracing
-group.
+matches its event name, not only the root user or users in the
+<<tracing-group,tracing group>>.

 
 To use the LTTng logger:
 
 
 To use the LTTng logger:
 


@@ -6481,7 +6617,7 @@ remote system. See man:lttng-create(1) for the exact URL format.
 
 . On the target system, use the man:lttng(1) command-line tool as usual.
   When tracing is active, the target's consumer daemon sends sub-buffers
 
 . On the target system, use the man:lttng(1) command-line tool as usual.
   When tracing is active, the target's consumer daemon sends sub-buffers

-  to the relay daemon running on the remote system intead of flushing
+  to the relay daemon running on the remote system instead of flushing

   them to the local file system. The relay daemon writes the received
   packets to the local file system.
 
   them to the local file system. The relay daemon writes the received
   packets to the local file system.
 


@@ -7308,7 +7444,7 @@ tracer::
 <<domain,tracing domain>>::
   A namespace for event sources.
 
 <<domain,tracing domain>>::
   A namespace for event sources.
 

-tracing group::
+<<tracing-group,tracing group>>::

   The Unix group in which a Unix user can be to be allowed to trace the
   Linux kernel.
 
   The Unix group in which a Unix user can be to be allowed to trace the
   Linux kernel.