All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serica via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] Enamebling namespace contexts
Date: Thu, 24 Dec 2020 10:55:37 +0800	[thread overview]
Message-ID: <tencent_13C276218B5808AF7848BFEF00E8B4AB3A05@qq.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]

Hi,


ThI found that lttng is working on container awareness in this slides: https://archive.fosdem.org/2019/schedule/event/containers_lttng/attachments/slides/3419/export/events/attachments/containers_lttng/slides/3419/lttng_containers_fosdem19.pdf


On page #13, there is a command:&nbsp; lttng add-context -k -t procname -t pid -t vpid -t tid -t vtid -t pid_ns, where pid_ns and other namespace identifiers are very useful for tracing containers. However, it seems like that lttng of current version doesn't support adding context pid_ns(Error: Unknown context type pid_ns). Do you know how to enable these features?


Thanks a lot.
Btw, have a nice holiday!


Serica

[-- Attachment #1.2: Type: text/html, Size: 863 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

             reply	other threads:[~2020-12-24  2:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  2:55 Serica via lttng-dev [this message]
2020-12-29  3:58 ` [lttng-dev] Enamebling namespace contexts Mathieu Desnoyers via lttng-dev
2020-12-29 13:18   ` [lttng-dev] =?gb18030?b?u9i4tKO6ICBFbmFtZWJsaW5nIG5hbWVzcGFjZSBj?= =?gb18030?q?ontexts?= Serica via lttng-dev
2021-01-04 15:36     ` [lttng-dev] 回复： Enamebling namespace contexts Jonathan Rajotte-Julien 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=tencent_13C276218B5808AF7848BFEF00E8B4AB3A05@qq.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=serica_law@qq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.