diff options
| author | Paul Elder <paul.elder@ideasonboard.com> | 2021-11-26 16:42:19 +0900 |
|---|---|---|
| committer | Kieran Bingham <kieran.bingham@ideasonboard.com> | 2021-12-01 15:42:55 +0000 |
| commit | 8acc82ec0d317b2d8cae6ba57904fbd3811f89e0 (patch) | |
| tree | 8fc334a5a3c8a1e6f2a31cadb2093d539dcc637b | |
| parent | 437cc396685a8c50974688b814b08d36e086a9b1 (diff) | |
guides: tracing: Mention where to find the trace file
Add a couple sentences describing where to find the trace file, and how
to view it even after the tracing session is destroyed.
Signed-off-by: Paul Elder <paul.elder@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
| -rw-r--r-- | Documentation/guides/tracing.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/guides/tracing.rst b/Documentation/guides/tracing.rst index 9c688b93..ae960d85 100644 --- a/Documentation/guides/tracing.rst +++ b/Documentation/guides/tracing.rst @@ -117,6 +117,12 @@ A trace can be collected fairly simply from lttng: See the `lttng documentation <https://lttng.org/docs/>`_ for further details. +The location of the trace file is printed when running +``lttng create $SESSION_NAME``. After destroying the session, it can still be +viewed by: ``lttng view -t $PATH_TO_TRACE``, where ``$PATH_TO_TRACE`` is the +path that was printed when the session was created. This is the same path that +is used when analyzing traces programatically, as described in the next section. + Analyzing a trace ----------------- |