Apache Log4j Performance Monitor
FusionReactor is able to monitor Java applications running on the Apache Log4j. FusionReactor is the most developer-centric means of seeing into the performance of Java applications running on Apache Log4j.
FusionReactor is the tool you need to troubleshoot the most complex application performance issues. Giving you instant insight into where issues are occurring or where your application is performing poorly.
All the insight you need from the Apache Log4j Performance Monitor
Deliver software faster using your Framework
Actionable insight into your Framework Application
Fix SQL Bottlenecks before they become an issue
Find Critical issues on your Log4j Framework Application
Find out instantly when things go wrong on your Framework Application
See What Our Customers Think
What is Apache Log4j?
Almost every large application includes its own logging or tracing API. In conformance with this rule, the E.U. SEMPER project decided to write its own tracing API. This was in early 1996. After countless enhancements, several incarnations and much work that API has evolved to become log4j, a popular logging package for Java. The package is distributed under the Apache Software License, a fully-fledged open source license certified by the open source initiative.
The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. This allows the Log4j team to improve the implementation safely and in a compatible manner.
The Log4j API is a logging facade that may, of course, be used with the Log4j implementation, but may also be used in front of other logging implementations such as Logback. The Log4j API has several advantages over SLF4J: 1. The Log4j API supports logging Messages instead of just Strings. 2. The Log4j API supports lambda expressions. 3. The Log4j API provides many more logging methods than SLF4J. 4. In addition to the “parameterized logging” format supported by SLF4J, the Log4j API also supports events using the java.text.MessageFormat syntax as well printf-style messages. 5. The Log4j API provides a LogManager.shutdown() method. The underlying logging implementation must implement the Terminable interface for the method to have effect. 6. Other constructs such as Markers, log Levels, and ThreadContext (aka MDC) are fully supported.
To get hands-on experience with Log4j, follow the download.