From: Maksim Khmelevskiy via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] LTTng and containers.
Date: Mon, 10 Oct 2022 18:12:51 +0200 [thread overview]
Message-ID: <CACXehJBSQAmFSKRzSPp9Cg2ZNjmF1UaujnSPeDQvyJBTW0L4Qw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
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!
[-- Attachment #1.2: Type: text/html, Size: 1058 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2022-10-11 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 16:12 Maksim Khmelevskiy via lttng-dev [this message]
2022-10-12 10:25 ` [lttng-dev] LTTng and containers Jérémie Galarneau via lttng-dev
2022-10-12 10:25 ` Michael Jeanson via lttng-dev
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=CACXehJBSQAmFSKRzSPp9Cg2ZNjmF1UaujnSPeDQvyJBTW0L4Qw@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).