Eelco Chaudron <[email protected]> writes: > Martin Kennelly observes that even though this data is available to > humans via the journal/log files, these aren't exactly easy for a > developer to make any kind of behavioral inferences. This kind of > log and counter would be useful when checking on system health to > let us know that an Open vSwitch component is noticing some kind of > system level hiccup. > > Add a new coverage counter to track information on these events, and > let a developer or system engineer know how long these events have > occurred with some historical context. > > Reported-at: > https://lists.linuxfoundation.org/pipermail/ovs-discuss/2023-June/052523.html > Suggested-by: Martin Kennelly <[email protected]> > Co-Authored-By: Aaron Conole <[email protected]> > Signed-off-by: Aaron Conole <[email protected]> > Signed-off-by: Eelco Chaudron <[email protected]> > Acked-by: Simon Horman <[email protected]> > ---
Thanks, applied. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
