Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in Logback while fixing some inherent problems in Logback architecture.
Customer Reviews
Umesh K.
Advanced user of Apache log4jI like the configurable approach for handling the logs which can be customized on runtime. I like that I can change the log format, level and destination of the logs very easily.
Need to work little more on the connector side like publishing logs to elastic in a more configurable way. There are other open libraries to handle it but can be included in this package itself.
Yes, I highly recommend using log4j for logging. The architecture of this framework is pretty easy to understand. It can become the central point of the whole application and logs can be written or directed to a variety of destinations (files, Relational database management systems, non-SQL DBS like elastic, queueing(rabbitmq). It comes with a different level for the logs which can be changed at runtime very easily. We can also manipulate the log format easily.
We are using this for logging purposes. The kind of simplicity it has to manage the logging level and log format is really good. It is fast.
The architecture of this framework is pretty easy to understand. It can become the central point of the whole application and logs can be written or directed to a variety of destinations (files, Relational database management systems, non-SQL DBS like elastic, queueing(rabbitmq). It comes with a different level for the logs which can be changed at runtime very easily. We can also manipulate the log format easily.
