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
Is there still a reason to have section 3.2 that uses the ch.qos.logback.contrib dependecy since log logback has native json support as of versions 1.3.8/1.4.8 for json printing that also follows?
JsonEncoder follows the JSON Lines standard. It transforms a logging event into a valid json text in conformance with RFC-8259.
Hi @agreedSkiing , we've described logging output in JSON using JsonEncoder in subsection 3.3.
The older ch.qos.logback.contrib dependencies should only be used if we're working with an older version of Logback (pre-1.3.8/1.4.8) and cannot upgrade.
Thanks for the feedback here - that's always super helpful.
We do naturally try to keep everything updated, but, as you might imagine, in some cases, we also do have to prioritize some updates over others.
This looks to be one that won't have high priority.
We now have a note internally on it - closing this issue here.
Thanks,
Team
Article and Module Links
https://www.baeldung.com/java-log-json-output
https://github.com/eugenp/tutorials/tree/master/logging-modules/logback
Question
Is there still a reason to have section 3.2 that uses the ch.qos.logback.contrib dependecy since log logback has native json support as of versions 1.3.8/1.4.8 for json printing that also follows?
https://logback.qos.ch/manual/encoders.html#JsonEncoder
The text was updated successfully, but these errors were encountered: