From 66b69963941ab91fc59d264ec5f893e5e8ef1b14 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Fri, 4 Sep 2015 01:42:57 -0400 Subject: [PATCH] tracing-session: add diagrams Signed-off-by: Philippe Proulx --- .../core-concepts/tracing-session.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/contents/understanding-lttng/core-concepts/tracing-session.md b/contents/understanding-lttng/core-concepts/tracing-session.md index 1a70b10..96c0071 100644 --- a/contents/understanding-lttng/core-concepts/tracing-session.md +++ b/contents/understanding-lttng/core-concepts/tracing-session.md @@ -34,14 +34,23 @@ which are described in the following sections): * a filter expression All this information is completely isolated between tracing sessions. +As you can see in the list above, even the tracing state +is a per-tracing session attribute, so that you may trace your target +system/application in a given tracing session with a specific +configuration while another one stays inactive. + +
+LTTng concepts +
Conceptually, a tracing session is a per-user object; the [Plumbing](#doc-plumbing) section shows how this is actually implemented. Any user may create as many concurrent tracing sessions -as desired. As you can see in the list above, even the tracing state -is a per-tracing session attribute, so that you may trace your target -system/application in a given tracing session with a specific -configuration while another one stays inactive. +as desired. + +
+Tracing sessions per user +
The trace data generated in a tracing session may be either saved to disk, sent over the network or not saved at all (in which case -- 2.34.1