From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Amir Najafi Zadeh <anajafizadeh@cs.stonybrook.edu>,
lttng-dev@lists.lttng.org
Subject: Re: Question about LTTng Context
Date: Thu, 11 Dec 2025 09:30:23 -0500 [thread overview]
Message-ID: <87a7e3d3-3ce2-4ded-acdf-bc7f152cdcec@efficios.com> (raw)
In-Reply-To: <CAOQX81f1zGCsnr3Ksjv0WoO-J4-OULanefNxzWdrxP8b4+aqJg@mail.gmail.com>
Hi Amir,
On 12/10/25 9:40 PM, Amir Najafi Zadeh via lttng-dev wrote:
> Hello everyone,
>
> I hope you’re doing well. My name is Amir, and I’m a PhD student in the
> Computer Science department at Stony Brook University, New York.
>
> I have a question about the LTTng context that I haven’t been able to
> find an answer for in the docs or man pages. Does LTTng support adding
> the cgroup ID or cgroup path as a context field? I want to filter my
> trace results based on cgroups.
>
I think you're looking for the `cgroup_ns` context which adds the inum
of the cgroup namespace as a context field.
thanks,
kienan
> If this isn’t supported, are there any plans to add it in future
> versions, such as 2.14?
>
> For reference, I’m currently using LTTng 2.13 on Ubuntu 24.04 with
> kernel 6.8.0-87-generic.
>
> Cheers,
> Amir
> --
> *Amirhossein Najafizadeh*
> *PhD Student, Computer Science Department, Stony Brook University, N.Y.
> File systems and Storage Lab (FSL)
>
> *
> najafizadeh21@gmail.com <mailto:najafizadeh21@gmail.com>
> https://amirhnajafiz.github.io/ <https://amirhnajafiz.github.io/>
next prev parent reply other threads:[~2025-12-11 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 2:40 Amir Najafi Zadeh via lttng-dev
2025-12-11 14:30 ` Kienan Stewart via lttng-dev [this message]
2025-12-11 14:57 ` Michael Jeanson via lttng-dev
2025-12-11 15:51 ` Amir Najafi Zadeh via lttng-dev
2025-12-11 16:14 ` Michael Jeanson via lttng-dev
2025-12-11 16:21 ` Amir Najafi Zadeh 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=87a7e3d3-3ce2-4ded-acdf-bc7f152cdcec@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=anajafizadeh@cs.stonybrook.edu \
--cc=kstewart@efficios.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