On 2022-10-10 17:12, Maksim Khmelevskiy via lttng-dev wrote:
Hi,
I would like to ask regarding the hot topic - container tracing. I've seen a
youtube video <https://www.youtube.com/watch?v=hra-eu6EOpY>, have read a
message <https://lists.lttng.org/pipermail/lttng-dev/2021-May/029952.html>
from LTTng mailing list and tried to google more about this topic but didn't
find much of info. Could you please direct me where should I continue digging?
My problem:
I would like to have multiple containers where traces are generated by apps
with compiled-in tracepoints. Traces could be stored in these containers as well.
Besides these containers I would have a trace processor container, a master
container which could address a container(or a trace session) and fetch traces
from it and read with babeltrace or similar tool.
So far, intuitively, remote tracing comes to my mind but before continuing
with the task I would be happy to hear an advice from LTTng devs.
Thank you!
Hi,
You can either use lttng-relayd to send the traces over the network to your
trace processor container, or just trace to disk on shared diectories. You
should have a look at trace rotation, https://doc.lttng.org is probably the
best place to start.
Michael
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
