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
When havig debug and trace logs enabled, axosyslog will print the result of a filterx block into its internal log.
In practice this is the value of the last statement in the block.
If that last statement is of a complex value, then it can happen that axosyslog will print the content of a protobuf's binary contents to its internal log, which may cause problems in any tools trying to parse the content of the internal log (as utf-8, in my case).
When printing to the internal log, we at least should try to escape or convert to text, the things being written to internal logs.
The text was updated successfully, but these errors were encountered:
AxoSyslog
Version of AxoSyslog
Platform
docker, amd64
Debug bundle
N/A
Issue
Failure
When havig debug and trace logs enabled, axosyslog will print the result of a filterx block into its internal log.
In practice this is the value of the last statement in the block.
If that last statement is of a complex value, then it can happen that axosyslog will print the content of a protobuf's binary contents to its internal log, which may cause problems in any tools trying to parse the content of the internal log (as utf-8, in my case).
When printing to the internal log, we at least should try to escape or convert to text, the things being written to internal logs.
The text was updated successfully, but these errors were encountered: