You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log printout is expected in forwarder-vpp logs at DEBUG log level.
Current Behavior
Setting log level to DEBUG the log printouts after "Startup completed in ..." printout are missing.
Failure Information (for bugs)
At TRACE log level any debug log printout can be seen in forwarder-vpp logs. For example printouts reporting netlink and vpp API operations regarding connection setup.
Steps to Reproduce
Set NSM_LOG_LEVEL to DEBUG value in apps/forwarder-vpp/forwarder.yaml
Start any basic use-case (e.g. Kernel2Ethernet2Kernel)
Expected Behavior
Log printout is expected in forwarder-vpp logs at DEBUG log level.
Current Behavior
Setting log level to DEBUG the log printouts after "Startup completed in ..." printout are missing.
Failure Information (for bugs)
At TRACE log level any debug log printout can be seen in forwarder-vpp logs. For example printouts reporting netlink and vpp API operations regarding connection setup.
Steps to Reproduce
Context
Example
Comparing the forwarder debug level printouts in case of TRACE and DEBUG log level:
trace-level-forwarder-vpp-log.txt
debug-level-forwarder-vpp-log.txt
The text was updated successfully, but these errors were encountered: