Add sinces

[lttng-docs.git] / contents / using-lttng / controlling-tracing / lttng-live.md

diff --git a/contents/using-lttng/controlling-tracing/lttng-live.md b/contents/using-lttng/controlling-tracing/lttng-live.md
index 26b11c151a47510111b06a7dc68744d4fb3d3c44..95f7bfb440016d78bd35a5871563733612196b2d 100644 (file)
--- a/contents/using-lttng/controlling-tracing/lttng-live.md
+++ b/contents/using-lttng/controlling-tracing/lttng-live.md
@@ -1,5 +1,6 @@
 ---
 id: lttng-live
+since: 2.4
 ---
 
 We have seen how trace files may be produced by LTTng out of generated
@@ -14,15 +15,16 @@ _LTTng live_.
 
 LTTng live is implemented, in LTTng, solely on the relay daemon side.
 As trace data is sent over the network to a relay daemon by a (possibly
-remote) consumer daemon, a _tee_ may be created: trace data will be
-recorded to trace files _as well as_ being transmitted to a
-connected live viewer:
+remote) consumer daemon, a _tee_ is created: trace data is recorded to
+trace files _as well as_ being transmitted to a connected live viewer:
 
-<div class="img img-90">
-    <object data="/images/docs/lttng-live-relayd.svg" type="image/svg+xml">
-        <img src="/images/docs/lttng-live-relayd.svg">
-    </object>
-</div>
+<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
 mode on the target system:
@@ -31,18 +33,18 @@ mode on the target system:
 lttng create --live
 </pre>
 
-An optional parameter may be passed to `--live` to set the interval
-of time (in microseconds) between flushes to the network
-(1&nbsp;second is the default):
+An optional parameter may be passed to `--live` to set the period
+(in microseconds) between flushes to the network
+(1&nbsp;second is the default). With:
 
 <pre class="term">
 lttng create --live 100000
 </pre>
 
-will flush every 100&nbsp;ms.
+the daemons flush their data every 100&nbsp;ms.
 
 If no network output is specified to the `create` command, a local
-relay daemon will be spawned. In this very common case, viewing a live
+relay daemon is spawned. In this very common case, viewing a live
 trace is easy: enable events and start tracing as usual, then use
 `lttng view` to start the default live viewer:
 
@@ -50,7 +52,7 @@ trace is easy: enable events and start tracing as usual, then use
 lttng view
 </pre>
 
-The correct arguments will be passed to the live viewer so that it
+The correct arguments are passed to the live viewer so that it
 may connect to the local relay daemon and start reading live events.
 
 You may also wish to use a live viewer not running on the target
@@ -73,7 +75,7 @@ babeltrace --input-format lttng-live net://localhost
 </pre>
 
 Then, choose a tracing session and start viewing events as they arrive
-using LTTng live, e.g.:
+using LTTng live:
 
 <pre class="term">
 babeltrace --input-format lttng-live net://localhost/host/hostname/my-session