From: Lin Wang <wanglinseven@gmail.com>
To: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
Cc: linux-trace-users@vger.kernel.org
Subject: Re: how to continuously capture events
Date: Wed, 5 May 2021 10:50:45 -0400 [thread overview]
Message-ID: <CABPy0Fnk-4BXE8qG7BDjjXmNR66g5a3qCuQFfzL=ubFbh6-qFQ@mail.gmail.com> (raw)
In-Reply-To: <20210505134708.GC346954@joraj-alpa>
> > I'm trying to continuously capture certain kernel events, convert them
> > to a different format and then write them to a file.
>
> You might also want to have a look at LTTng and LTTng-modules depending on your
> final use case. [1][2]
From a cursory look, it might be an overkill for what I want to
achieve. I will keep this in
mind in case I need to do something more complex. Thank you for the pointers.
-Lin
On Wed, May 5, 2021 at 9:47 AM Jonathan Rajotte-Julien
<jonathan.rajotte-julien@efficios.com> wrote:
>
> Hi,
>
> > I'm trying to continuously capture certain kernel events, convert them
> > to a different format and then write them to a file.
>
> You might also want to have a look at LTTng and LTTng-modules depending on your
> final use case. [1][2]
>
> LTTng produce CTF traces [3] that can then be read/converted/manipulated with Babeltrace [4].
>
> [1] https://lttng.org/
> [2] https://lttng.org/docs/v2.12/#doc-tracing-the-linux-kernel
> [3] https://diamon.org/ctf/
> [4] https://babeltrace.org/
>
> Cheers
>
> --
> Jonathan Rajotte-Julien
> EfficiOS
prev parent reply other threads:[~2021-05-05 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 12:21 how to continuously capture events Lin Wang
2021-05-05 13:18 ` Steven Rostedt
2021-05-05 14:48 ` Lin Wang
2021-05-05 13:47 ` Jonathan Rajotte-Julien
2021-05-05 14:50 ` Lin Wang [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='CABPy0Fnk-4BXE8qG7BDjjXmNR66g5a3qCuQFfzL=ubFbh6-qFQ@mail.gmail.com' \
--to=wanglinseven@gmail.com \
--cc=jonathan.rajotte-julien@efficios.com \
--cc=linux-trace-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).