All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: Serica <serica_law@qq.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev]  回复: Enamebling namespace contexts
Date: Mon, 4 Jan 2021 10:36:18 -0500	[thread overview]
Message-ID: <20210104153618.GC60341@joraj-alpa> (raw)
In-Reply-To: <tencent_4C429FE980FC54AC7AC796244B4048B19805@qq.com>

Hi,

> The version of my lttng is: lttng (LTTng Trace Control) 2.10.7 - KeKriek.

Please upgrade to lttng 2.12.x. Container awareness was added in the 2.12 release
cycle.

Cheers

> Thanks,
> Serica
> 
> 
> ------------------&nbsp;原始邮件&nbsp;------------------
> 发件人:                                                                                                                        "Mathieu Desnoyers"                                                                                    <mathieu.desnoyers@efficios.com&gt;;
> 发送时间:&nbsp;2020年12月29日(星期二) 中午11:58
> 收件人:&nbsp;"Serica"<serica_law@qq.com&gt;;
> 抄送:&nbsp;"lttng-dev"<lttng-dev@lists.lttng.org&gt;;
> 主题:&nbsp;Re: [lttng-dev] Enamebling namespace contexts
> 
> 
> 
> ----- On Dec 23, 2020, at 9:55 PM, lttng-dev <lttng-dev@lists.lttng.org&gt; wrote:
> 
> 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?
> 
> What version of LTTng do you use (output of "lttng --version"), and what is the output of "lttng add-context --list" ?
> 
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

      reply	other threads:[~2021-01-04 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  2:55 [lttng-dev] Enamebling namespace contexts Serica via lttng-dev
2020-12-29  3:58 ` 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     ` Jonathan Rajotte-Julien via lttng-dev [this message]

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=20210104153618.GC60341@joraj-alpa \
    --to=lttng-dev@lists.lttng.org \
    --cc=jonathan.rajotte-julien@efficios.com \
    --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.