| |
1. log4j | By: | | License: | Apache Software License | URL: | http://logging.apache.org/log4j/docs/ | Description: | With log4j it is possible to enable logging at runtime without modifying the application binary. The log4j package is designed so that these statements can remain in shipped code without incurring a heavy performance cost. Logging behavior can be controlled by editing a configuration file, without touching the application binary.
|
2. jLo | By: | | License: | BSD License | URL: | http://jlo.jzonic.org/ | Description: | jLo is a logging framework written in Java. It has some unique features compared to other existing frameworks.
List of features:
* supports multiple log configurations
* offers loggers, channels, filters and pipes
* uses either a direct or asynchronous log processor (handle the logging in a separate thread
* auto reload of the configuration if the file has changed
* simple XML structure to configure jLo
* supports filters to limit the output
* supports the use of variables in the configuration
* supports the use of environment variables or java system properties
* comes with mock objects for handler and formatter to be integrated into JUnit testcases for example
* simple profiling tool included
|
3. Monolog | By: | | License: | GNU Library or Lesser General Public License (LGPL) | URL: | http://monolog.objectweb.org | Description: | The goal of Monolog is to define and maintain the ObjectWeb API for the logging.
|
4. Lumberjack | By: | | License: | GNU Library or Lesser General Public License (LGPL) | URL: | http://javalogging.sourceforge.net/ | Description: | The Lumberjack project provides an open source (covered by the GNU Lesser Public License) implementation of the logging APIs first introduced in JDK 1.4 that will work for JDK 1.2 and 1.3. The goal is for this implementation to work transparently on JDK 1.2 and 1.3 without recompile and with no significant difference in behavior between it and the implementation provided in JDK 1.4 (differences will be ruthlessly eradicated when found :-). More information about the logging API can be found in JSR 47, the logging page in the documentation for JDK 1.4, the overview of Logging, and the javadoc for java.util.logging.
|
5. JTraceDump | By: | | License: | GNU Library or Lesser General Public License (LGPL) | URL: | http://jtracedump.sourceforge.net/ | Description: | JTraceDump provides a facility to keep a history of application processing steps in memory and dump it in case of an error. It is not a replacement, but an addition to trace- or debug-logging.
Usually, trace-logs are only active during development and testing stage of an application. When the application goes into production, trace logs are usually disabled for performance reasons. Now, if there is a problem later on (for example a null-pointer-problem due to a threading problem in a server), there is often very few information available about what led to the problem. Typically, as the developer, you'd have to get the administrator to enable the trace logging again and then tell the user to reproduce the error. Then you could analyze the logs to find the problem. However, the error might just not be reproducible at all, and the whole process involves a lot of people (= overhead), especially in large corporate environments.
|
6. qflog | By: | | License: | Mozilla Public License | URL: | http://www.qfs.de/en/qflog/ | Description: | qflog is a tool for displaying log messages which is built on top of the de.qfs.lib.log package of our Java library qflib. It can be used to conveniently browse log messages, searching for those that may be of relevance to some problem. Messages can be sorted, various kinds of filters can be applied and there is support for incremental search and bookmarks.
|
7. Just4Log | By: | | License: | Apache Software License | URL: | http://just4log.sourceforge.net/ | Description: | Just4Log is a library to enhance dynamically the performance of various logging systems inside a java application. Dynamically because the sourcecode in java is not modified but rather the optimization occurs on the compiled ByteCode files.
|
9. commons-logging API | By: | | License: | Apache Software License | URL: | http://jakarta.apache.org/commons/logging/ | Description: | When writing a library it is very useful to log information. However there are many logging implementations out there, and a library cannot impose the use of a particular one on the overall application that the library is a part of.
The Logging package is an ultra-thin bridge between different logging implementations. A library that uses the commons-logging API can be used with any logging implementation at runtime. Commons-logging comes with support for a number of popular logging implementations, and writing adapters for others is a reasonably simple task.
Applications (rather than libraries) may also choose to use commons-logging. While logging-implementation independence is not as important for applications as it is for libraries, using commons-logging does allow the application to change to a different logging implementation without recompiling code.
|
10. SMTPHandler | By: | | License: | Apache Software License | URL: | http://smtphandler.sourceforge.net/ | Description: | SMTPHandler is a handler for the java.util.logging library. The handler sends LogRecord's via email using the Simple Mail Transfer Protocol.
|
11. Simple Log | By: | | License: | Apache Software License | URL: | http:// https://simple-log.dev.java.net/ | Description: | Simple Log is a small library that does logging very simply and requires you to do almost nothing (other than actually logging) to get log output happening.
It is much simpler to use than a logging framework, especially in terms of configuration.
It doesn't attempt to solve every logging problem in one package, but contains enough features to be a viable alternative for most applications that need logging.
|
13. Craftsman Spy | By: | | License: | GNU Library or Lesser General Public License (LGPL) | URL: | http://zer0.free.fr/craftsman/spy.php | Description: | Craftsman Spy is an open source and free framework for JDBC logging. It is a JDBC driver implementation.
This logger logs all SQL connection and processings with execution spent time, all the stored procedures with arguments, all the batch processings and the result sets.
No need to modify your application in order to integrate JDBC logging with Craftsman Spy. The application MUST use the craftsman.spy.SpyDriver and MUST be launched with the -Dspy.driver=... system property.
Be carefull this JDBC driver SHOULD not be used in production mode. Use it only in development or pre-production system.
|
14. Pencil | By: | | License: | GNU General Public License (GPL) | URL: | http://pencil.dev.java.net | Description: | "Pencil" is a log-message-compiler for java (keyword: generative programming). It takes bytecode produced by javac (or another java-compiler), transforms it and enriches it with real logging expressions.
|
15. Simple Logging Facade for Java | By: | | License: | The Artistic License | URL: | http://www.slf4j.org | Description: | The Simple Logging Facade for Java or (SLF4J) is intended to serve as a simple facade for various logging APIs allowing to the end-user to plug in the desired implementation at deployment time. SLF4J also allows for a gradual migration path away from Jakarta Commons Logging (JCL).
Logging API implementations can either choose to implement the the SLF4J interfaces directly, e.g. NLOG4J or SimpleLogger. Alternatively, it is possible (and rather easy) to write SLF4J adapters for the given API implementation, e.g. Log4jLoggerAdapter or JDK14LoggerAdapter..
|
|