From: "Jérémie Galarneau via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>,
Maksim Khmelevskiy <mk.void.mail@gmail.com>
Subject: Re: [lttng-dev] LTTng and containers.
Date: Wed, 12 Oct 2022 10:25:01 +0000 [thread overview]
Message-ID: <YQXPR01MB5977C8D851E3796DEB9CF5FBBC229@YQXPR01MB5977.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CACXehJBSQAmFSKRzSPp9Cg2ZNjmF1UaujnSPeDQvyJBTW0L4Qw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2454 bytes --]
Hi Maksim,
It's hard to give general advice without knowing more about your constraints.
I can see three main approaches that are easy to reach:
1. Store the traces in each container and fetch them,
2. Trace to a shared volume (make sure sessions are stopped or rotated before you read them),
3. Or stream traces to a "collector" container (perhaps the one doing the analyses) using network streaming
If you want to continuously consume traces, I would suggest you look into "trace rotations". You could setup periodic trace rotations (based on size or time) and ship traces to your processor node as they become available.
Although my demo wasn't running in a container, the basic idea is what I presented at FOSDEM in 2019:
https://archive.fosdem.org/2019/schedule/event/lttng/
[https://fosdem.org/2019/assets/style/logo-gear-7204a6874eb0128932db10ff4030910401ac06f4e907f8b4a40da24ba592b252.png]<https://archive.fosdem.org/2019/schedule/event/lttng/>
FOSDEM 2019 - Fine-grained Distributed Application Monitoring Using LTTng<https://archive.fosdem.org/2019/schedule/event/lttng/>
archive.fosdem.org
I hope that helps a bit,
Jérémie
--
Jérémie Galarneau
EfficiOS Inc.
https://www.efficios.com
________________________________
From: lttng-dev <lttng-dev-bounces@lists.lttng.org> on behalf of Maksim Khmelevskiy via lttng-dev <lttng-dev@lists.lttng.org>
Sent: October 10, 2022 12:12
To: lttng-dev@lists.lttng.org <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] LTTng and containers.
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: 6276 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 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 [this message]
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=YQXPR01MB5977C8D851E3796DEB9CF5FBBC229@YQXPR01MB5977.CANPRD01.PROD.OUTLOOK.COM \
--to=lttng-dev@lists.lttng.org \
--cc=jgalar@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