From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] How to use the lttng-untrack command
Date: Tue, 1 Sep 2020 09:37:40 -0400 (EDT) [thread overview]
Message-ID: <1835947492.25584.1598967460978.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <6e9da9cb.16e65.17448f14499.Coremail.xiongyuhua@zju.edu.cn>
----- On Sep 1, 2020, at 5:13 AM, ??? <xiongyuhua at zju.edu.cn> wrote:
> Hi?dear
> Hello, I have encountered some problems in using LTTNG, which is briefly
> described as follows. I am eager to get your help.
> About the use of the untrack command.It is reproduced as follows:
> I type the following commands in turn to start LTTNG, and set up not to monitor
> a particular process.(For example, I input the "top" command in the terminal,
> the PID of the "top" process is 72598, now I want LTTNG not to monitor the
> "top" process)
> 1. lttng create my-kernel-session --output=/tmp/my-kernel-trace
> 2. lttng add-context -k -t pid
> 3. lttng add-context -k -t tid
> 4. lttng enable-event --kernel --all
> 5. lttng untrack --kernel --pid=72598
> 6. lttng start
> 7. lttng destroy
> 8. babeltrace2 /tmp/my-kernel-trace > babeltrace.txt
> Unfortunately, the output still contains the data for PID72598.
> Even after I changed "lttng untrack --kernel -- PID =72598" to "LTTNG untrack-u
> -- PID =72598", this phenomenon still occurred.
> How do I use the lttng-untrack command to achieve my goal?
Based on the lttng-track(1) man page:
The lttng track commands adds one or more values to a process attribute
tracker.
A process attribute tracker is an inclusion set of process attributes.
Tracked processes are allowed to emit events, provided those events are
targeted by enabled event rules (see lttng-enable-event(1)).
Tracker values can be removed from an inclusion set with lttng-
untrack(1).
What you are looking for is a an "exclusion set", which does not exist at this point
in LTTng.
Thanks,
Mathieu
> Looking forward to your reply.
> thanks,
> yuhua
> ------------------
> Yuhua Xiong
> Lab for Internet and Security Technology
> School of Computer Science and Technology
> Zhejiang University
> Hangzhou, 310007, P.R. China
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200901/5b2f3ef8/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1598951079297.png
Type: image/png
Size: 228995 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200901/5b2f3ef8/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1598951286057.png
Type: image/png
Size: 382880 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200901/5b2f3ef8/attachment-0003.png>
next prev parent reply other threads:[~2020-09-01 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 9:13 熊毓华
2020-09-01 13:37 ` Mathieu Desnoyers [this message]
2020-09-03 2:53 ` 熊毓华
2020-09-03 14:17 ` Mathieu Desnoyers
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=1835947492.25584.1598967460978.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@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