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

[Question] JSON Logback section 3.2 #17554

Closed
agreedSkiing opened this issue Sep 9, 2024 · 3 comments
Closed

[Question] JSON Logback section 3.2 #17554

agreedSkiing opened this issue Sep 9, 2024 · 3 comments
Labels
on-jira triaged Issues reviewed by a dev and considered valid. Will be added in Jira.

Comments

@agreedSkiing
Copy link

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?

JsonEncoder follows the JSON Lines standard. It transforms a logging event into a valid json text in conformance with RFC-8259.

https://logback.qos.ch/manual/encoders.html#JsonEncoder

@ulisseslima
Copy link
Collaborator

Hey, @agreedSkiing.

Thanks for the feedback. We'll look into this.

This issue will remain open until then.

@ulisseslima ulisseslima added the triaged Issues reviewed by a dev and considered valid. Will be added in Jira. label Nov 13, 2024
@hmdrzsharifi
Copy link
Contributor

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.

@collaboratewithakash
Copy link
Collaborator

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

@collaboratewithakash collaboratewithakash closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on-jira triaged Issues reviewed by a dev and considered valid. Will be added in Jira.
Projects
None yet
Development

No branches or pull requests

4 participants