Please see
https://fd.io/docs/vpp/master/gettingstarted/developers/gitreview.html.
Event log entry timestamps have nanosecond granularity. It might work out to do
something like the following:
2019/10/31 09:18:36:937:123:895 ## initial full timestamp
+0: api-msg: trace_plugin_msg_ids
+1.2us: api-msg-done(mp-safe): trace_plugin_msg_ids
+30us: api-msg: trace_plugin_msg_ids
+1.1us: api-msg-done(mp-safe): trace_plugin_msg_ids
If delta exceeds 100ms (or some such), emit another full timestamp.
This will reduce the average output width considerably, and reduce the
subtrahend / minuend widths when asking questions of the form “how long does
the XYZ API message handler take?”
FWIW... Dave
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Aleksander Djuric
Sent: Thursday, October 31, 2019 2:56 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] event-logger output format
Hi all,
In my opinion, the event-logger cli command has uncomfortable format of output.
I have small suggestion about it. I think that the event-logger output should
be printed in following manner:
vpp# show event-logger
72 of 131072 events in buffer, logger running
2019/10/31 09:18:36:937: api-msg: trace_plugin_msg_ids
2019/10/31 09:18:36:937: api-msg-done(mp-safe): trace_plugin_msg_ids
2019/10/31 09:18:36:937: api-msg: trace_plugin_msg_ids
2019/10/31 09:18:36:937: api-msg-done(mp-safe): trace_plugin_msg_ids
2019/10/31 09:18:36:937: api-msg: trace_plugin_msg_ids
I propose a small patch, which makes human-readable the output format of the
event-logger cli command. Please look at the patch below, is it acceptable?
Any comments and suggestions are welcome.
Thanks in advance,
Aleksander
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14407): https://lists.fd.io/g/vpp-dev/message/14407
Mute This Topic: https://lists.fd.io/mt/40103349/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
