Download JAR files tagged by log4j with all dependencies

The Java Application Monitor (JAMon) is a free, simple, high performance, thread safe, Java API that allows developers to easily monitor production applications. 1) It contains the ability to monitor JDBC/SQL, web page requests, ejb's, log4j, interfaces and more. 2) It tracks aggregate stats for each sql statement, page request etc. and also lets you look at this information and more via the JAMon war. 3) You can also access JAMon statistics via the api

This module contains all code necessary to run Apache Fluo on a YARN cluster using Apache Twill. It was separated from fluo-core to keep dependencies (like Twill) out of Fluo clients which depend on the fluo-core jar. It was also done to limit conflicts. For example, Twill requires logback to be used but fluo-core requires log4j (due to zookeeper requiring it in accumulo-minicluster).

This module contains all code necessary to run Fluo on a YARN cluster using Apache Twill. It was separated from fluo-core to keep dependencies (like Twill) out of Fluo clients which depend on the fluo-core jar. It was also done to limit conflicts. For example, Twill requires logback to be used but fluo-core requires log4j (due to zookeeper requiring it in accumulo-minicluster).

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.

This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.