Projects

Octopussy

Octopussy is a solution to manage your logs (also frequently called a SIM/SEM/SIEM Solution). Basically, it stores your logs, produces reports, and raises alerts.

cxxtl

C++ Trivial Logger is a lightweight logger written in C++.

Graylog2

Graylog2 is an open source syslog implementation that stores your logs in MongoDB. It consists of a server written in Java that accepts your syslog messages via TCP or UDP and stores it in the database. The second part is a Ruby on Rails web interface that allows you to view the log messages. It ... [More] also implements GELF. The Graylog Extended Log Format is a simple JSON string that allows you to send long and structured syslog messages and very useful for customized application log monitoring. [Less]

IPHPLog

IPHPLog (IP PHP Log) is a simple software written in PHP, JS and SQL that runs over a SQL language for data management system like MySQL. IPHPLog can log the information of your visitors and organize that on a data base.

SysFink

The unix based guard for checking consistency of system files. Sysfink server periodically scan basic information in the client's file systems and reports changes to administrator.

minlog

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 concise and very efficient at runtime. Extremely lightweight The entire project consists of one Java ... [More] 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]

log5f

It's a logging utility for ActionScript 3.0 language, it supports FlashPlayer 9.0 and AIR 1.0 Log5F uses only FlashPlayer's capabilities, so it can be used for Flash/Flex/AIR applications. Log5F is a port of Log4J.

IrcLogger

irclogger is a simple "bot", a program connecting as a client on IRC servers to provide a web log of what is said. It aims to provide a simple, fast, efficient and web-compliant service. It is quite robust and mature, having be in daily heavy use for personal & business use since 2003.

fileloggersharp

Library of logging classes for .NET

logkeys

logkeys is a linux keylogger. It is no more advanced than other available linux keyloggers, but is a bit more up to date, actively developed, it doesn't unreliably repeat keys and it should never crash your X. All in all, it just seems to work. It relies on event interface of the Linux input ... [More] subsystem. Once set, it logs all common character and function keys, while also being fully aware of Shift and AltGr key modifiers. It works with serial as well as USB keyboards. [Less]