Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: julien.desfossez@polymtl.ca (Julien Desfossez)
Subject: [ltt-dev] RFC LTTv TextDump
Date: Wed, 24 Nov 2010 17:49:50 -0500	[thread overview]
Message-ID: <4CED968E.7000903@polymtl.ca> (raw)
In-Reply-To: <4CED7902.3020504@polymtl.ca>

On 24/11/10 03:43 PM, David Goulet wrote:
> On 10-11-24 02:11 PM, Michel Dagenais wrote:
>>
>>>> Note that the textdump can output content coming from multiple traces,
>>>> where having the trace name in the output for each event becomes
>>>> convenient.
>>
>> The problem is having the full path, a short "id" when interleaved
>> events are there would be useful (something about hostname and CPU)
>
> Yep exactly. Just to make it easy to read and easy to refer.
>
> I've also though of a small thing we could add is the time offset in
> nsec (or sec..) between two events.
>
> [...]
> event 1 (+4)
> event 2 (+7)
> [...]
>
> So that way we know *very* quickly what time it took from event 1 to
> event 2 which is 7. Considering a UST trace, this would be of great use!!
>
> We only need someone to do it now :)

While we are in the dream features, I would also like to see a way to 
pass a format string to the program to choose how the output is 
formatted (like the "date" program). For example "%t : %c, %e" to output 
"timestamp : channel, event". That way the output would suit everyone's 
need and specific parsers could be implemented on top of that.

Julien




      reply	other threads:[~2010-11-24 22:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 20:20 David Goulet
2010-11-22 20:52 ` Alexandre Montplaisir
2010-11-23 18:26 ` Mathieu Desnoyers
2010-11-23 19:38   ` Alexandre Montplaisir
2010-11-23 20:15     ` Mathieu Desnoyers
2010-11-24 19:11     ` Michel Dagenais
2010-11-24 20:43       ` David Goulet
2010-11-24 22:49         ` Julien Desfossez [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=4CED968E.7000903@polymtl.ca \
    --to=julien.desfossez@polymtl.ca \
    /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