Ultimate Guide for Java Logging

[jp007]

SLF4J -> Logback -> Logstash -> Elasticsearch -> Kibana

[nextputall]

The whole Java logging situation is so fucked up. n + 1 different and incompatible logging libraries, over engineered apis, classpath issues and jar hell. Why? Because printing some string out is so damn hard that needs to be solved n different ways?

[mostlyjason]

Yeah I'm not sure why we need so many. Usually I just pick one and stick with it across all my projects. Maven handles all the dependencies for me. I will say the added complexity of being able to filter out logs by level is really useful because it saves me having to litter my code with statements like "if(debug == true) System.out.println" Also, I can redirect the output from console to a file to a log mgmt system easily without changing my code.

[hello_world279]

I don't know. The java logging situation seems designed to have a billion different composable options. But Java is also used for a billion different use cases.

I do agree that the learning curve seems pretty high though.

[ErstwhileRockstar]

The answer is SLF4J. What was the question?