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
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 <<domain,{sect-domain}>> section
|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
|===
You must specify a tracing domain to target a type of LTTng tracer when
-using some man:lttng(1) to avoid ambiguity. For example, because the
-Linux kernel and user space tracing domains support named tracepoints as
-instrumentation points (see the <<"event-rule","{sect-event-rule}">> section
-above), you need to specify a tracing domain when you create an event
-rule because both tracing domains could have tracepoints sharing the
-same name.
+using some man:lttng(1) commands to avoid ambiguity. For example,
+because the Linux kernel and user space tracing domains support named
+tracepoints as instrumentation points (see the
+<<"event-rule","{sect-event-rule}">> section above), you need to specify
+a tracing domain when you create an event rule because both tracing
+domains could have tracepoints sharing the same name.
You can create channels (see the <<channel,{sect-channel}>> section
below) in the Linux kernel and user space tracing domains. The other
Monitor timer::
When this timer expires, the consumer daemon samples some channel
- (see the <<channel,{sect-channel}>> section above)
statistics to evaluate the following trigger conditions:
+
--