Lazy logging, multiple appenders, different layouts, different triggering policies and many more Review collected by and hosted on G2.com.
1) IMHO, documentation is what makes the developers choose among logging frameworks or any other products; easier the implementation (docs), better the usage; this part seems to be very less focussed by organizations when developing a product but i find it the most important than others. Regarding the features, there are already plenty, but we are unaware of most of them. Also in current official docs, there is no opinionated way or example of configuring logging best suited for general application use cases. Also the documentation can only be fully understood by developers those are already experienced to some extent. There should be a basic example describing each statement. And the examples should be upgraded to next level little by little with skip option or levels to go to the matured examples. All the related configuration or options relating to that specific statement should have a separate documentation that contains description for each and every options. The idea of describing the things should be in layman terms and in as simple english as possible, as there are people that are weak at english language; eg some people i know didn't understand the term appender, layouts until i explained them in layman terms with examples and some drawings.
Also as people like me are lazy enough to read the whole single page docs, it would be better to have separated them in multiple pages with very less and informative content in each page.
2) It would be nice to have some online playground for practicing right away.
2) It would be nice to have better default logging implementation in popular frameworks like spring boot i.e. from logback to log4j2 and so on. Review collected by and hosted on G2.com.
The best thing about it is that it's easy to use and configure the log file outputs.
Works great while testing or running production.
It is thread-safe, it uses multiple levels and most importantly it is optimized for speed. Review collected by and hosted on G2.com.
The only hindrance I found was while debugging, to display the log in the debug terminal in IntelliJ. It might have just been me, not understanding, or IntelliJ. In the end it works, it just needs a slightly better documentation on that part. Review collected by and hosted on G2.com.
It allow you to define your own output format of log.
It has ability to Categorize the log at different level like we can do it for debug, trace, warning, info, error.
It allows the class hierarchy which will be useful.
Its an open source Review collected by and hosted on G2.com.
The thing I faced while using log4j is it locks the logfile and you cannot delete the logfile when log4j opens the file Review collected by and hosted on G2.com.
Easy to integrate with java and supports major log level such as info, debug, error and etc. Besides log4j supports async logging which will decrease the latency and improve the performance. Log4J has been developed based on the plugin architecture, thus it is provide the capability to plug and use in any application based on java. Review collected by and hosted on G2.com.
There were issues in filtering the logs with syslog driver when we use docker. Review collected by and hosted on G2.com.
Simple to implement with less configuration
During testing or real time execution it works optimized speed for best performance.
Using Log 4j we have generate log files in text format, so we were able to easily transcript the log file and identify the error with the logging information . By using log4j it has saved our time and helped us to debug issues quickly Review collected by and hosted on G2.com.
The only Challenge is faced was while trying to integrate the log with 3rd party components. if there is format or template/documents can be really helpful Review collected by and hosted on G2.com.
I like the overall logging experience like you can handle everything from a configuration file. Moreover, the default colors for each level are also quite useful as they help in debugging the issues and you can enable/disable log levels whenever you want. Review collected by and hosted on G2.com.
I face memory leak issue few times but that is not a major issue. Log4j should be supported for all platforms and languages like this is how so we may have consistent logging experience for all applications. Review collected by and hosted on G2.com.
Log4j is an amazing tool, easily configurable (just add the dependency in pom file, if using maven) and maintainable. Setting debug log level for Error, Info, Warn, Fatal etc makes logging easier. We can also use it to store logs in database and so on. It supports Apache flume, SLF4j, Splunk etc. Review collected by and hosted on G2.com.
Log4j when used extensively makes the processes slow. Now log4j2 is available which provides multiple configurable ways (xml, properties, java code ) and is faster. Review collected by and hosted on G2.com.
Doing software development gets easy when you have a good logging framework to log all the necessary steps to make testing and debugging easy. Log 4j is a life saver when it comes to logging when it comes to performance. It has good performance especially with large transactions on the backend .Also it can be written in Java easily and has synchronous appenders to send log to different destinations Review collected by and hosted on G2.com.
It has too much initial configuration and logging at info level at high transaction level sucks as it dumps the output with log messages Review collected by and hosted on G2.com.
It can be used to answer the client requirements of logs. Even non technical person can easily differentiate the types of logs. We can create logs files easily and if a certain limit exceeds then next log file is created automatically. Review collected by and hosted on G2.com.
There is not a single thing i dislike about this API. It is a work of art. Review collected by and hosted on G2.com.