Projects tagged ‘java’ and ‘logging’

log4j is a Java-based logging utility, and is one of many projects from the Apache Software Foundation. It is used primarily as a debugging tool.

Logback is intended as a successor to the popular log4j project. It was designed by Ceki Gülcü, the founder of log4j. It builds upon experience gained in building industrial-strength logging systems going back as far as 1999.

Centreon is a network, system, applicative supervision and monitoring tool, it is based upon the most effective Open Source monitoring engine: Nagios. Centreon provides a new frontend and new ... [More] functionalities to Nagios. It allows you to be more efficient in your network monitoring, but also allows you to make your supervision information readable by a largest range of users. Indeed, a non technical user can now use the Centreon/Nagios couple to easily understand your network infrastructure thanks to charts and graphical representations of the gathered information. Skilled users still have access to specific and technical information collected by Nagios though. [Less]

OpenNMS is the world's first enterprise grade network management platform developed under the open source model. It consists of a community supported open-source project as well as a commercial services, training and support organization.

EvaProperties is a properties and dependency injection framework. It supports property inheritance, knows Ant or Maven style references and it instantiates and wires Java objects. You can read ... [More] properties from the classpath, any input stream or a file and save them again. [Less]

Xulux is a Front End API for Java.

OverviewMinLog is a Java logging library. Key features: Low overhead Logging statements below a given level can be automatically removed by javac at compile time. Simple and efficient The API is ... [More] concise and very efficient at runtime. Extremely lightweight The entire project consists of one Java file with just over 100 non-comment lines of code. The JAR is 2.6kb (2kb with pack200). UsageMessages are logged using static methods: Log.info("Some message."); Log.debug("Error reading file: " + file, ex);A static import can be used to make the logging more concise: import static com.esotericsoftware.minlog.Log.*; // ... info("Some message."); debug("Error reading file: " + file, ex);While optional, for brevity the rest of this documentation assumes this static import is in place. If log statements from different libraries or areas of an application need to be differentiated, a category can be specified: info("some lib", "Some message."); debug("some lib", "Error reading file: " + file, ex);Log levelSetting the level will log that level, as well as all higher levels: Log.set(LEVEL_INFO);The levels are: LEVEL_NONE disables all logging. LEVEL_ERROR is for critical errors. The application may no longer work correctly. LEVEL_WARN is for important warnings. The application will continue to work correctly. LEVEL_INFO is for informative messages. Typically used for deployment. LEVEL_DEBUG is for debug messages. This level is useful during development. LEVEL_TRACE is for trace messages. A lot of information is logged, so this level is usually only needed when debugging a problem. Conditional loggingThe current log level can be checked before the message is logged: if (ERROR) error("Error reading file: " + file, ex); if (TRACE) { StringBuilder builder = new StringBuilder(); // Do work, append to the builder. trace(builder); }Checking the log level before calling the logging method is optional, but prevents unnecessary method calls and string concatenation for log levels that are disabled. Fixed logging levelsMinLog users can choose from the regular "minlog.jar" or from from a JAR file like "minlog-info.jar" which has a fixed logging level that cannot be changed at runtime (calls to Log.set() have no affect). During compilation, any conditional logging statements below the fixed level will be automatically optimized away by the Java compiler. Please see OverheadAndComparisons for more about the overhead when using MinLog with/without conditional logging and with/without a fixed logging level. The document also compares the MinLog overhead with log4j and java.util.logging. Output customizationThe default logger outputs messages in this format: time level: [category] messageWhere "time" is the time elapsed since the application started. For example: 00:00 TRACE: [kryo] Wrote string: moo 00:00 TRACE: [kryo] Wrote object: NonNullTestClass 00:01 TRACE: [kryo] Wrote string: this is some data 00:01 TRACE: [kryo] Compressed to 7.97% using: DeflateCompressor 00:12 TRACE: [kryo] Decompressed using: DeflateCompressor 00:12 TRACE: [kryo] Read string: this is some dataThe output can be customized: static public class MyLogger extends Logger { public void log (int level, String category, String message, Throwable ex) { StringBuilder builder = new StringBuilder(256); builder.append(new Date()); builder.append(' '); builder.append(level); builder.append('['); builder.append(category); builder.append("] "); builder.append(message); if (ex != null) { StringWriter writer = new StringWriter(256); ex.printStackTrace(new PrintWriter(writer)); builder.append('\n'); builder.append(writer.toString().trim()); } System.out.println(builder); } } // ... Log.set(new MyLogger());Using this mechanism, log messages can be filtered (eg, by category), written to a file, etc. [Less]

Planned Features nice looking and easy-to-use interface multi-platform responsive, high throughput support all major logging frameworks (log4j, logback, java.util.logging, log4cxx, ...) receive log ... [More] events via sockets read log events from file save log events to file advanced filtering and high-lighting options save all settings to file (filters, applications, ...) support custom columns (based on MDC) support compressed log events Powered ByApache MINA Glazed Lists [Less]

SLF4Fxis the opensource framework that allows to integrate Flex logging API on client side with many java logging frameworks on server side. The idea behind is simple. On client side we have ... [More] LoggingTarget that sends all log records to slf4fx server written on java. The server utilizes Simple Logging Facade for Java (SLF4J) for routing all incoming records to supported java logging framework. The list of supported frameworks includes all well-known logging frameworks. They provide many ways for further log manipulations - filtering, saving to file, writing to console, sending to email ant etc. There are also many UI and text based tools for log analysis that works with those logging frameworks. SLF4Fx uses very simple but efficient binary protocol to transfer log records between flex client and java server. The framework also provides ability to collect log records from particular client application instance that could be useful on remote support. In development you can use provided simple sl4fx server or you can integrate the slf4fx server bean into your own java application with just few lines of code. See Integration page for futher details or you can start using SLF4Fx with FourSimpleStepsToStart. StatusCurrent stable version is 1.12 (no fixes, no improvements, maven repository were added) MavenYou can use following repository in your pom. See Maven for details. ... slf4fx-maven-repo slf4fx maven repository http://slf4fx.googlecode.com/svn/repo ... ThanksI used the marvelous Apache Mina framework for design server. Thank you guys! SLF4J is very simple in use and provides freedom to choose any (known by me :) ) java logging framework. flex-mojos is great maven plugin that shift RIA development based on Flex3 to enterprise level. [Less]

A set of advanced Log4J appenders designed for hi-load applications. Among them: TimeAndSizeRollingFileAppender, ThreadSafeAsyncAppender, DbcpDataSourceAppender, JndiDataSourceAppender etc. Also ... [More] includes appender wrappers for use in JBoss environment. [Less]