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
Not sure if this is a bug, kind of a question but I'm not able to label it as "question" (sorry about that)
When I'm on DEBUG mode configured I used to see a log trace with "decoded UPDATE" followed by the decoded JSON from the BGP message. Now in master I lost that trace, when debuging I found that, if I'm correct, the affected line is here.
I've tried to replace locally logfunc.debug(lazyformat('decoded UPDATE', '', parsed), 'parser') by log.debug(f"decoded UPDATE {parsed('')}"), 'parser') and I can now see the trace in the logs.
Is there any extra config that is needed now in order to see that log trace, a part from the debug mode?
thank you in advanced :)
The text was updated successfully, but these errors were encountered:
** Question **
Not sure if this is a bug, kind of a question but I'm not able to label it as "question" (sorry about that)
When I'm on DEBUG mode configured I used to see a log trace with "
decoded UPDATE
" followed by the decoded JSON from the BGP message. Now in master I lost that trace, when debuging I found that, if I'm correct, the affected line is here.I've tried to replace locally
logfunc.debug(lazyformat('decoded UPDATE', '', parsed), 'parser')
bylog.debug(f"decoded UPDATE {parsed('')}"), 'parser')
and I can now see the trace in the logs.Is there any extra config that is needed now in order to see that log trace, a part from the debug mode?
thank you in advanced :)
The text was updated successfully, but these errors were encountered: