X-Git-Url: https://git.lttng.org/?a=blobdiff_plain;f=doc%2Fman%2Flttng-concepts.7.txt;h=e4259f9d1ff76794e0d019a47e5b259958f3ad7b;hb=f1cb70fba7cb2517a53acca393e2ef594d97f071;hp=54718afd2d67eee93ed8dab4b41f885aac251f59;hpb=d5e9b731e07b3cbf1367a4ae5d61b562c8f0a162;p=lttng-tools.git diff --git a/doc/man/lttng-concepts.7.txt b/doc/man/lttng-concepts.7.txt index 54718afd2..e4259f9d1 100644 --- a/doc/man/lttng-concepts.7.txt +++ b/doc/man/lttng-concepts.7.txt @@ -1,6 +1,6 @@ lttng-concepts(7) ================= -:revdate: 3 May 2021 +:revdate: 18 May 2021 :sect-event-rule: INSTRUMENTATION POINT, EVENT RULE, AND EVENT :sect-session: TRACING SESSION :sect-domain: TRACING DOMAIN @@ -58,7 +58,7 @@ help understand the journey from an instrumentation point to the execution of actions. The actual creation of an event can be costly because LTTng needs to -evalute the arguments of the instrumentation point. +evaluate the arguments of the instrumentation point. In practice, LTTng implements various optimizations for the Linux kernel and user space tracing domains (see the <> section @@ -522,23 +522,23 @@ There are currently five available tracing domains: |Tracing domain |``Event rule matches'' trigger condition option |Option for other CLI commands |Linux kernel -|nloption:--domain=++kernel++ +|nloption:--type option starts with `kernel:` |nloption:--kernel |User space -|nloption:--domain=++user++ +|nloption:--type option starts with `user:` |nloption:--userspace |`java.util.logging` (JUL) -|nloption:--domain=++jul++ +|nloption:--type option starts with `jul:` |nloption:--jul |Apache log4j -|nloption:--domain=++log4j++ +|nloption:--type option starts with `log4j:` |nloption:--log4j |Python -|nloption:--domain=++python++ +|nloption:--type option starts with `python:` |nloption:--python |=== @@ -895,7 +895,6 @@ man:lttng-enable-channel(1) command. Monitor timer:: When this timer expires, the consumer daemon samples some channel - (see the <> section above) statistics to evaluate the following trigger conditions: + --