locust is a full featured Internet search engine specifically designed to power vertical search, enterprise search, or a knowledge area search applications. It can index 2.5 million documents per 24 hours on a single Dell server. It consists of clean C++/STL code written from scratch.
Log4php is a PHP port of Log4j, the most popular Java logging framework. It supports configuration through XML and properties files (with the same structure as log4j) and custom Configurators. File, RollingFile, DailyFile, Echo, Console, Mail, PEAR::Db, PHP error, Syslog or NT events, and socket appenders are supported. Simple, TTCC, Pattern, Html, and Xml Layouts are supported. It also supports Filters, custom Levels, and Loggers. Internal debugging can be switched on and off. Log4php can be used inside a class or inside a main/sub function.
Logfilter is a tool for performing ad hoc analysis on Apache log files. Logfilter is especially useful when you wish to find records matching very specific criteria, since you can specify exactly which fields to match. The tool also plays well in a Unix environment by accepting input either through files or via stdin.
managelogs is a log processing program to be used in conjunction with Apache's piped logfile feature. It is an alternative to the well known rotatelogs and cronolog programs. Its primary purpose is to solve the "log filesystem full" issue by purging the oldest log files when the total log size exceeds a given value. It can also write compressed files, maintain symbolic links to the current and archive log files, and setuid to a given user. It maintains its state across Apache restarts, and allows writing to several output channels, each one having its own configuration.
The maven-buildmetadata-plugin is a Maven 2 plugin that helps you easily add build metadata to generated archive artifacts. When a product is running on an application server, this tool can tell you which version of which artifact is currently running on that server, which artifact maps to which source code version in the SCM repository, what configuration set (including profiles and environment variables) has been used to generate the artifact, on which machine was the artifact built, and when was the artifact built. The provided metadata include SCM information, build time, operating system, Java runtime, Maven execution information, build user, build host name, and build version.