Java log component

Log4j: log4j is an open-source project of Apache, we can control the log information delivery destination, including the console, files, Gui components, and even the interface server, NT event recorder, and Unix Syslog daemon; you can also control the output format of each log. By defining the level of each log information, you can control the log generation process in greater detail. These can be configured flexibly through a configuration file without modifying the program code. [Log4e: plug-in of log4j in eclipse]

Monolog is an API used for monitoring and log operations and is supported internationally.

Jtracedump is a tool used to keep the content information during the running of the program, and dumps it in a separate file (similar to the core dump) When an error occurs ).

Commons logging Jakarta commons logging (jcl) provides a log interface that is lightweight and independent from specific log implementation tools. It provides a simple log operation abstraction for middleware/log Tool developers, allowing program developers to use different log implementation tools. The user is assumed to be familiar with more advanced details of a log implementation tool. Interfaces provided by jcl are simply packaged for other log tools, including log4j, aveon logkit, and JDK 1.4. This interface is closer to the implementation of log4j and logkit.

For JDK 1.2 and 1.3, lumberjack implements Java log APIs (introduced in JDK ).

Houston is an open source lightweight diary toolkit. It provides a plug-in system that allows you to use sophisticated logging tools such as Apache log4j and jdk1.4 logging at the underlying layer.

Just4log just4log is to enhance the existing logging system (log4j, Apache commons logging, JDK 1.4 logging) as much as possible during runtime configuration, without too many settings in the Java source code.
More information about just4log

Smtphandler is a Java. util. Logging processor that can send log messages through SMTP.

Jlo JLo is a Java open-source logging framework. It has some features different from other frameworks, such:
* Supports multiple log deployments.
* When the configuration file changes, you can re-read the file * configure JLo through a simple XML structure
* Supports filtering and limiting log output.

A tool for displaying the log information. It is built on the De. qfs. Lib. Log package.

Simple log simple log is a logging anti-framework.Simple log is a class library that makes diary operations simple but small and can get the output of the log without any operation. compared with other diary frameworks, it is easy to use, especially in terms of condition configuration. it does not intend to solve all the diary problems in a package, but it provides enough functionality to meet the logging operations required by most applications.

Ln2 ln2 is a log processing framework. it processes programs based on pattern matching. ln2 is loosely designed on log4j and does not need to be bound to the log level too tightly.

Log bridge allows you to extract a log from a specific log implementation package. it provides a simple API for playing the bridge role to extract the diary from the specific diary implementation package selected by the developer. currently, log bridge supports the following log packages:

Simple log
J2se Logging
Log4j
IBM's logging toolkit for Java
Jlo
Protomatter Syslog

Craftsman spy craftsman spy is an open source JDBC diary framework. it implements the JDBC driver. this diary will record all SQL connections, all batch processing, all returned record sets, all stored procedures with parameters, and the time when the processing is performed.

Log4j2-log4j2-is used for log4j on the j2-based platform. When you move your code to the j2se/J2EE platform, you do not need to change the code. Instead, you only need to replace log4j2-jar with the log4j JAR file. Unlike log4j, log4j cannot be configured using the log4j. properties file in the j2s environment, but the configuration can be read from the JAD file. There are other differences in the j2-based platform. log4j2-based solutions are provided.

Slf4j simple log facade (facade) slf4j provides a simple and unified interface for various loging APIs, so that end users can configure their desired loging APIs implementation during deployment. You can choose to directly implement loging APIs connected to slf4j, such as nlog4j and simplelogger. You can also use the API provided by slf4j to develop corresponding adapters such as log4jloggeradapter and jdk14loggeradapter.

Logback is another open-source log component designed by the founder of log4j. Logback is divided into three modules: logback-core, logback-classic, and logback-access. Logback-core is the basic module of the other two modules. Logback-Classic is an improved version of log4j. In addition, logback-Classic's complete implementation of slf4j API allows you to easily replace it with other log systems such as log4j or jdk14 logging. The logback-Access access module integrates with the servlet container to provide access to the log through HTTP.

Log4javascript log4javascript is a log4j-based JavaScript logging framework.

JDBC logger developers can use the JDBC logger tool to monitor the SQL statements generated by ejbs, hibernate, or other data access tools.

Limpid log is a novel log system. You do not have to encode any log control statements. You only need to register the classes you are interested in at runtime. the limpid log system can record all important information about the classes during runtime. Limpidlog provides a swing manager for dynamically registering and logging out your applications. All recorded log data can be provided to limpiddebugger for source code-level debugging. Limpiddebugger is a GUI debugger independent of limpid log. In addition, limpidlog can be used as a netbeans plug-in.