-
Notifications
You must be signed in to change notification settings - Fork 161
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
ASCII codes logs #170
Comments
You can start it with I should look into moving that to an environment variable like the rest of the config. |
I think I meant ANSI color codes, not ASCII. I'm not sure hard-to-read-json is better than hard-to-read-with-embedded-ANSI-codes. I've never seen software that emits ANSI codes (if that's what these are) in the logs - is there some kind of environment variable or setting that simply eliminates them? Looks like the rs/zerolog package puts them in so they look pretty and colored...but that doesn't seem to translate well into /var/log/daemon.log, even if I sent my session's TERM to "ansi". |
I didn't see a way to change zerolog w/ environment variables, but I think it does support custom formats. I don't see why Inbucket couldn't support a "syslog" style log format along with the other two. I think the reason it is currently configured via command line is Inbucket used to parse a config file, and that could fail (and be logged), so the log format couldn't be specified in that file. Probably not an issue with env vars. |
My logs have strange codes that look like ASCII codes:
Every single line in the logs looks like this. Is this normal? Can it be changed/suppressed? Thanks.
The text was updated successfully, but these errors were encountered: