Closed mauhiz closed 9 months ago
When using JUL to SLF4J bridge, the logger is misconfigured and logs are detected as being sent from "unknown.jul.logger". As a result, it is not straightforward to configure logback to filter out brave debug logs.
This is apparently solvable but setting a logger name to each LogRecord produced, like in https://github.com/asciidoctor/asciidoctorj/pull/834
For people using JUL directly with the default format, this will change the log output slightly.
Before:
Jan 01, 1970 9:00:00 AM null FINE: Some message
After:
Jan 01, 1970 9:00:00 AM brave.Tracer FINE: Some message
Problem:
When using JUL to SLF4J bridge, the logger is misconfigured and logs are detected as being sent from "unknown.jul.logger". As a result, it is not straightforward to configure logback to filter out brave debug logs.
Solution:
This is apparently solvable but setting a logger name to each LogRecord produced, like in https://github.com/asciidoctor/asciidoctorj/pull/834
Drawbacks
For people using JUL directly with the default format, this will change the log output slightly.
Before:
After: