Muse Proxy is a highly customizable multi-platform proxy server. It is easy to use and configure, acting successfully as a gateway to authenticated restricted content, rewriting Web server, Web Access Management, proxy server, and reverse proxy. It has been used for more than 10 years within the Muse Federated Search Platform to manage the authentication to resources and the navigation to full text, by restoring the server session on the end-user browser.
ZedLog is a robust cross-platform input logging tool (A.K.A., a key logger). It is based on a flexible data logging system which makes it easy to get the required data. It features logging of all keyboard and mouse events, a replay simulation tool, logging to a file, and hiding in the background.
Lilith is a logging and access event viewer for the Logback logging framework. It has features comparable to Chainsaw, a logging event viewer for log4j. This means that it can receive logging events from remote applications using Logback as their logging backend. It uses files to buffer the received events locally, so it is possible to keep vast amounts of logging events at your fingertip while still being able to check only the ones you are really interested in by using filtering conditions.
NagiosAppender is a pure Java implementation of a Log4j appender that allows the developer/administrator to send log records to Nagios via the NCSA server (using the push model). It provides a simple solution for Nagios administrators whose only alternative is to implement a polling function against against the output of a standard Log4j appender. The log4j configuration file provides for user-specific mappings between Log4j levels and Nagios levels. The configuration file also allows the user to select whether to set the Nagios 'service' and 'host' programmatically via Log4j MDC, or via the config file. Later releases support XOR encryption.
Logback is intended as a successor to the popular log4j project, and was designed by log4j's founder, Ceki Gulcu. The basic architecture is sufficiently generic so as to apply under different circumstances. It is divided into three modules. The Core module lays the groundwork for the other two modules, whereas the Classic module can be assimilated to an improved version of log4j. It natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging systems, such as log4j or JDK14 Logging. The Access module integrates with Servlet containers to provide HTTP access log functionality. You can easily build your own modules on top of the Core module.
jmxtrans is effectively the missing connector between JMX and whatever logging or graphing package that you can dream up. jmxtrans is very powerful tool that reads JSON configuration files specifying servers/ports and JMX domains/attributes and then outputs the data in whatever format you want via special "Writer" objects that you can code up yourself. It does this with a very efficient engine design that will scale to querying literally thousands of machines. The core engine is pretty solid and writers are included for cacti/rrdtool, graphite, and stdout.