<figure class="img img-100">
<img src="/images/docs26/ust-flow.png" alt="User space tracing's build process">
+<figcaption>
+ User space tracing build process
+</figcaption>
</figure>
If you followed the
<figure class="img img-100">
<img src="/images/docs26/concepts.png" alt="LTTng concepts">
+<figcaption>
+ A <em>tracing session</em> is a container of domains,
+ channels, and events.
+</figcaption>
</figure>
Conceptually, a tracing session is a per-user object; the
<figure class="img img-100">
<img src="/images/docs26/many-sessions.png" alt="Tracing sessions per user">
+<figcaption>
+ Each user may create as many tracing sessions as desired.
+</figcaption>
</figure>
The trace data generated in a tracing session may be either saved
<figure class="img img-100">
<img src="/images/docs26/lttng-live.png" alt="LTTng live">
+<figcaption>
+ The relay daemon creates a <em>tee</em>, forwarding the trace data
+ to both trace files and a live viewer.
+</figcaption>
</figure>
Using LTTng live
<figure class="img img-100">
<img src="/images/docs26/plumbing-26.png" alt="LTTng plumbing">
+<figcaption>
+ Control and data paths between LTTng components
+</figcaption>
</figure>
Each component is described in the following subsections.
<figure class="img img-100">
<img src="/images/docs26/lttng-live.png" alt="LTTng live">
+<figcaption>
+ The relay daemon creates a <em>tee</em>, forwarding the trace data
+ to both trace files and a live viewer.
+</figcaption>
</figure>
In order to use this feature, a tracing session must created in live