Do you think it would be prudent to publish a ‘warning’ message on its impact on packet forwarding when this cmd is used?
Thanks! -- Regards, Balaji. From: <vpp-dev@lists.fd.io> on behalf of Aleksander Djuric <aleksander.dju...@gmail.com> Date: Thursday, October 31, 2019 at 8:07 AM To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] event-logger output format Hi Dave, Thanks! Now it looks like this: > show event-logger [all] [<nnn>] [delta|no-delta|date-time] Updated patch: https://gerrit.fd.io/r/c/vpp/+/23146 On Thu, Oct 31, 2019 at 04:47 PM, Dave Barach wrote: Yes, we see things differently. I never look at elog data in the debug CLI. I save the data and deal with it offline. See https://fd.io/docs/vpp/master/gettingstarted/developers/eventviewer.html. We often use elog buffer sizes measured in millions of events. The offline tools are happy to deal with 1e7 events. Packet processing comes to a screeching halt while the “show event-logger” debug CLI command runs. If folks decide that it’s worth trying to use the “show event-logger” debug CLI on a regular basis, the first step should be to make and mark the debug CLI command thread-safe. At least when using one or more worker threads, packet processing won’t stop in its tracks for the duration... I would prefer something of the form “show event-logger ... [full-timestamp]” to request date/hms/msusns timestamps, and I would prefer the delta format I described to tagging each event with a full timestamp. Maybe add “[delta|no-delta]” qualifier keywords to the debug CLI command. FWIW... Dave
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14425): https://lists.fd.io/g/vpp-dev/message/14425 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] -=-=-=-=-=-=-=-=-=-=-=-
