|Home | Products | Documents | Downloads | Purchase | Support | Company | Partners | Contact |

Logging In The J2EE World: log for debugging and for auditing

Overview

Logging is part of the life of Java developers and administrators, since day one of Java and J2EE (JEE).

There are two purposes of logging: log for auditing and log for debugging.

Log for auditing is part of business logic of the application. For example, you want record the resources that a user visited. You know what to log at the development time. This is relatively easy.

Log for debugging is not part of business logic. You do not really know what to log at the development time, so you just generally hard-code many logging statements, hopping some statements will record useful debug information when you need later.

Among the two purposes for logging, log for debugging takes more than 90% of the log volume. More than 90% of the issues in  logging is about log for debugging.

These two logging purpose are very different. So the two different logging should be treated differently. The issues of logging are difficult issues, since day one of Java and J2EE.
 

Log for debugging: the issues of hard-code statements

Traditional logging, for example, Log4J and JDK logging, requires hard-code log statements. There are many issues of hard-code logging. For example:

Log for debugging: LimpidLog does not require hard-code statement

Limpid Log is a revolutionary logging system. You do not need to hard code any log statements. Because there is no hard-code log statements, all issues of hard-code log statements will go away. You get everything without doing anything.

Limpid Log is dynamically configurable. At runtime, you can register a class of interest and the system will log all important information about the class. When you are done, you can de-register the class and the class will not generate any log information.

Limpid Log is for both Java SE (Java Standard Edition) and JEE (Java Enterprise Edition). LimpidLog uses java.lang.instrument.Instrumentation of Java to log, as a Java Agent. This is a new feature of Java 5 (JDK 1.5).

Limpid Log is an open source software with GPL v2 license.

Log for auditing: should be simple and efficient

Log for auditing is part of business logic of the application. It is very difficult to automatically generate these log records. But there is a way to simplify it.

Super Log combines Limpid Log (log for debugging) and AuditLog (log for auditing) into one log system and make the logging be an enjoyable activity.

Super Log is a logging system, not just an API. It works out of the box.

See related paper: Logging and debugging for Java and J2EE.

SuperLog

Super Log combines Limpid Log and traditional logging into one log system and make the logging be an enjoyable activity. The architecture is shown on the following figure:


©Copyright Acelet Corporation. All rights reserved.
Site Map Home Products: Acelet-Filer Super Suite Audit Log Easy EJB Easy JMS Easy JMX Easy Webservice Limpid Debugger Super Environment Super Log SuperStress Super Scheduler Super Log Reader Super Watchdog Super Workflow OpenSource Limpid Log Freeware Mortgage software Downloads Purchase Support Consulting Company Partners Contact us


© 2014 Acelet Corporation.