From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: Maksim Khmelevskiy <mk.void.mail@gmail.com>
Subject: Re: [lttng-dev] LTTng and containers.
Date: Wed, 12 Oct 2022 11:25:25 +0100 [thread overview]
Message-ID: <f69eeb15-2c5d-6346-6b97-b56ff3b7e5c3@efficios.com> (raw)
In-Reply-To: <CACXehJBSQAmFSKRzSPp9Cg2ZNjmF1UaujnSPeDQvyJBTW0L4Qw@mail.gmail.com>
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
prev parent reply other threads:[~2022-10-12 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 16:12 Maksim Khmelevskiy via lttng-dev
2022-10-12 10:25 ` Jérémie Galarneau via lttng-dev
2022-10-12 10:25 ` Michael Jeanson via lttng-dev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f69eeb15-2c5d-6346-6b97-b56ff3b7e5c3@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mjeanson@efficios.com \
--cc=mk.void.mail@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox