Hi Dave, Thank you very much for your reply. I think it can be useful to discuss this patch here at first. As I see, we looks at these things little bit differently ) I'm use event-logger mostly for registering such fast events as ACL filter matching. I think that the human-readable format is better suitable for such purpose. Because for technical use you still can save elog file. Isn't it? If I understand you correctly, you suggest the case in which the both modes supported, maybe somethig like the following:
show event-logger [all] [<nnn>] [detail] ? where "detail" means show elog with nanoseconds timestamp. Would it be usefull? Regards, Aleksander On Thu, Oct 31, 2019 at 02:48 PM, Dave Barach wrote: > > > > Please see > https://fd.io/docs/vpp/master/gettingstarted/developers/gitreview.html > ( 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 > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14411): https://lists.fd.io/g/vpp-dev/message/14411 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] -=-=-=-=-=-=-=-=-=-=-=-
