All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: linux-trace-users <linux-trace-users@vger.kernel.org>
Subject: Re: stream based live time synchronized tracing?
Date: Mon, 15 Aug 2022 11:02:55 -0400 (EDT)	[thread overview]
Message-ID: <897351806.4484.1660575775681.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAK-6q+hJ4KjhUqNOGT0a046M7t3McbdstJy7xYzUAwHCp4yZRw@mail.gmail.com>

----- On Aug 15, 2022, at 9:28 AM, Alexander Aring aahringo@redhat.com wrote:

> Hi,
> 
> I am curious if there is any way of getting time synchronized traces
> in a kind of stream based communication like pipes, sockets, etc. and
> get high level event representation as ?libtraceevent? provides. I
> would like to get all "merged" events from all machines provided by -A
> parameters. I think it isn't required to get them in order, but the
> timestamp should be synchronized.
> 
> I could probably build something like that with libtracecmd to have it
> directly implemented in an application, but I am curious if there
> exists any interest in having such a feature upstream? E.g. having
> additional parameters like '--tsync-interval'.
> 
> A use-case would be live capturing of time synchronized events or what
> I have in my mind to collect stats and doing kernel runtime
> optimizations.

You may want to have a look at babeltrace2 [1]. It allows merging multiple
traces together as they are read. Using the "lttng-live" source, you can read
traces as they are produced.

Thanks,

Mathieu

[1] https://babeltrace.org


-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2022-08-15 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 13:28 stream based live time synchronized tracing? Alexander Aring
2022-08-15 15:02 ` Mathieu Desnoyers [this message]
2022-08-16 22:05 ` Steven Rostedt

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=897351806.4484.1660575775681.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=aahringo@redhat.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 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.