Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

binary content printed in the filterx trace/debug logs #144

Open
jszigetvari opened this issue Jun 6, 2024 · 0 comments
Open

binary content printed in the filterx trace/debug logs #144

jszigetvari opened this issue Jun 6, 2024 · 0 comments
Labels
bug Something isn't working filterx

Comments

@jszigetvari
Copy link
Contributor

AxoSyslog

Version of AxoSyslog

axosyslog 4 (4.7.1.680.gee6232f)
Config version: 4.2
Installer-Version: 4.7.1.680.gee6232f+4.7.1_git20240604
Revision: 
Compile-Date: Jun  4 2024 23:09:15

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.

@jszigetvari jszigetvari added the bug Something isn't working label Jun 6, 2024
@pepov pepov added the filterx label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working filterx
Projects
None yet
Development

No branches or pull requests

2 participants