X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Funderstanding-lttng%2Fcore-concepts%2Fevent.md;h=2154bfcb56f15dc69a4326b7b7706fdfcff359fb;hb=47bfcb757a0192864b56d12d775f65dc8b180aaf;hp=bca5fcced659000f02bfcf7173bbd74f4eabc3e8;hpb=5e0cbfb01373c18e521217342fd8a9159cc186b1;p=lttng-docs.git diff --git a/contents/understanding-lttng/core-concepts/event.md b/contents/understanding-lttng/core-concepts/event.md index bca5fcc..2154bfc 100644 --- a/contents/understanding-lttng/core-concepts/event.md +++ b/contents/understanding-lttng/core-concepts/event.md @@ -18,11 +18,10 @@ having multiple definitions depending on the context: specific rules which could lead to the transfer of actual occurring events (1) to recorded events (2). -The whole [Core concepts](#doc-core-concepts) section focusses on the +The whole [Core concepts](#doc-core-concepts) section focuses on the third definition. An event is always registered to _one or more_ channels and may be enabled or disabled at will per channel. A disabled -event will never lead to a recorded event, even if its channel -is enabled. +event never leads to a recorded event, even if its channel is enabled. An event (3) is enabled with a few conditions that must _all_ be met when an event (1) happens in order to generate a recorded event (2): @@ -38,8 +37,8 @@ The following illustration summarizes how tracing sessions, domains, channels and events are related:
- - + +