From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: Not capturing ust events
Date: Thu, 8 May 2025 13:25:08 -0400 [thread overview]
Message-ID: <0e6f9c3b-8daa-43ae-a3ee-6d7917b05b2e@efficios.com> (raw)
In-Reply-To: <CAJK_ieibZJjJus6PdOnWAiLFOymm6D8AmkG3vdpDnuazG1wAbA@mail.gmail.com>
Hi David,
On 5/8/25 1:02 PM, David Aldrich wrote:
> Hi Kienan
>
> Thanks very much for your reply. I can now capture UST events. (My
> actual problem was that I was not linking to lttng-ust).
>
Glad you caught that. I had assumed it was linked in :)
> I am now using the method you described:
>
>> lttng create my_proj
>> lttng enable-event --userspace 'lttng_ust_tracef:*'
>> lttng start
>> ./my_app
>> lttng stop
>> lttng view # [Optional]
>
> This works and captures UST events but I am not capturing Kernel
> events. My reason for running this experiment is that occasionally
> our application shows glitches where a task takes longer than
> expected. So I want to see what happens in that occurrence - perhaps
> an ISR is running or something like that. So I assume that I need to
> capture Kernel and UST events.
>
> Can you please advise me why Kernel events aren't being captured?
>
In the setup above, only a userspace channel is created.
Assuming the user you are running the `lttng` commands with is a member
of the tracing group and a root lttng-sessiond is running, a complete
example might look like:
```
lttng create my_proj
lttng enable-event --userspace 'lttng_ust_tracef:*' # this will
automatically create a channel if one doesn't exist in the session
lttng enable-channel --kernel --session my_proj kernel_channel # [1]
lttng enable-event --kernel --all --channel kernel_channel --session
my_proj # [2]
lttng start
./my_app
lttng stop
lttng view
```
> Best regards
> David
thanks,
kienan
[1]: https://lttng.org/man/1/lttng-enable-channel/v2.13/
[2]: https://lttng.org/man/1/lttng-enable-event/v2.13/
next prev parent reply other threads:[~2025-05-08 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 16:50 David Aldrich via lttng-dev
2025-05-08 13:51 ` Kienan Stewart via lttng-dev
2025-05-08 17:02 ` David Aldrich via lttng-dev
2025-05-08 17:25 ` Kienan Stewart via lttng-dev [this message]
2025-05-08 17:59 ` David Aldrich 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=0e6f9c3b-8daa-43ae-a3ee-6d7917b05b2e@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=david.aldrich.ntml@gmail.com \
--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