[lttng-dev] RFC live trace reading use-cases

Julien Desfossez jdesfossez at efficios.com
Wed Oct 31 15:09:18 EDT 2012


We are currently working on defining a design for live trace reading and
before commiting to one, we would like to have a list of all the
relevant use-cases we have to take into account.

Just to clarify, live trace reading means displaying/analyzing a trace
while it is being recorded by a tracer.

Here are the use-cases I have collected so far :
- reading a trace from the disk of the machine that is currently being
- reading a trace from a remote machine on the disk of the machine
running lttng-relayd (receiving the trace on the network);
- reading the trace directly from the memory of the local tracer (mmap
shared buffers);
- reading the trace from the memory of a lttng-relayd daemon receiving
the trace from the network but never writing it to disk.

In all these cases, the tracing session might be a new one or a session
already started. If the session is already started we could want to
"attach" the viewer to it and read the data either from the beginning or
from "now".

Of course we want to keep the privilege separation and make sure the
viewer is allowed to read the trace.

We at least want to support the C/C++ and Java viewers and for the
remote use-cases we might have to support viewers running on Windows as
So we need an interface between the consumerd/relayd that will be common
to all these possible viewers.

I will not discuss here the early solutions we have right now to avoid
influencing the decision, I am just interested in collecting the
use-cases first.

If you have other use-cases that you think might be interesting to
support, please send them as soon as possible.
We are in brainstorm mode, after that phase we will decide the use-cases
we want to support/prioritize.



More information about the lttng-dev mailing list