From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Zvi Vered <veredz72@gmail.com>, lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] tracing user event from multiple dockers
Date: Mon, 4 Mar 2024 10:11:56 -0500 [thread overview]
Message-ID: <8a7e39ec-f8d8-4f75-b345-81154fffc1ee@efficios.com> (raw)
In-Reply-To: <CABRndgwfhU-e1a7f8dFSwV5Pny4cuEeqbhA_4GCkKK=574bVBA@mail.gmail.com>
Hi Zvika,
To share a sessiond the LTTng home and run directories, and the shared
memory should be shared between the containers.
Eg. https://github.com/mjeanson/gcloud-lttng/blob/master/pods/demo1.yaml.in
In a scenario with multiple sessionds (eg. one per container), the
traces could be combined in post using babeltrace.
thanks,
kienan
On 3/2/24 12:31 AM, Zvi Vered via lttng-dev wrote:
> Hello,
>
> I have an application working with multiple dockers.
> Each docker is a fedora O.S running an application.
> The host is centos 8.5. This host will be upgraded to RHEL 9.2 in the
> near future.
> Is it possible that all traces from multiple dockers will all be written
> to one metadata ?
>
> versions:
> lttng-tools-latest-2.13.tar.bz2
> lttng-ust-latest-2.13.tar.bz2
> userspace-rcu-latest-0.14.tar.bz2
>
> Thank you,
> Zvika
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
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:[~2024-03-04 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 5:31 Zvi Vered via lttng-dev
2024-03-04 15:11 ` Kienan Stewart via lttng-dev [this message]
2024-03-05 19:14 ` Zvi Vered 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=8a7e39ec-f8d8-4f75-b345-81154fffc1ee@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.com \
--cc=veredz72@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