linux-trace-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Alexander Aring <aahringo@redhat.com>
Cc: linux-trace-users@vger.kernel.org
Subject: Re: stream based live time synchronized tracing?
Date: Tue, 16 Aug 2022 18:05:03 -0400	[thread overview]
Message-ID: <20220816180503.319dd3e6@gandalf.local.home> (raw)
In-Reply-To: <CAK-6q+hJ4KjhUqNOGT0a046M7t3McbdstJy7xYzUAwHCp4yZRw@mail.gmail.com>

On Mon, 15 Aug 2022 09:28:48 -0400
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.

Are these for guests, or machines on a network?

> 
> 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.

So basically not save to a file? Just record the events live and interleave
them for different machines?

I'm not exactly sure what you are asking for. Can you please elaborate some
more?

Thanks,

-- Steve


      parent reply	other threads:[~2022-08-16 22:05 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
2022-08-16 22:05 ` Steven Rostedt [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=20220816180503.319dd3e6@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --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 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).