From: glenkeane.94@gmail.com (Glen Keane)
Subject: [lttng-dev] Change of output format in lttng view?
Date: Tue, 21 Apr 2015 17:26:55 +0100 [thread overview]
Message-ID: <CAJaGzgszPHbfotmpSNWnpChB_jDmvwkFxCST6M=FurcBSRpxcA@mail.gmail.com> (raw)
Hey guys,
Would you please consider changing the '=' char to a ':' char in the event
data output of `lttng view`? it would make it more json-like.
Currently when you `lttng view` something you get
'[13:17:40.642101755] (+0.000213714) vagrant-ubuntu-trusty-64 node:gc_done:
{ cpu_id = 0 }, { gctype = "kGCTypeScavenge", gcflags =
"kNoGCCallbackFlags" }',
I think that
'[13:17:40.642101755] (+0.000213714) vagrant-ubuntu-trusty-64 node:gc_done:
{ cpu_id : 0 }, { gctype : "kGCTypeScavenge", gcflags :
"kNoGCCallbackFlags" }'
would be better.
Any thoughts? It seems to be very similar to json already. :)
Glen.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150421/0f9da4f7/attachment.html>
next reply other threads:[~2015-04-21 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 16:26 Glen Keane [this message]
2015-04-21 20:04 ` Philippe Proulx
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='CAJaGzgszPHbfotmpSNWnpChB_jDmvwkFxCST6M=FurcBSRpxcA@mail.gmail.com' \
--to=glenkeane.94@gmail.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