Search Results for "commons-logging"

...By default, the showExceptions flag is turned on. This shows why the tests failed including the location of the failure. Of course, you can switch off this slightly more verbose logging by setting showExceptions to false. Just like Gradle itself, by default only the last frame that matches the test class's name in a stack trace is printed. For vast majority of cases, that is sufficient. Sometimes, it is useful to remove this filtering in order to see the entirety of the stack trace.

Lilith is a logging and access event viewer for Logback, log4j & java.util.logging. It has features comparable to Chainsaw for log4j. This means that it can receive logging events from remote applications using Logback as their logging backend

Hyperic is application monitoring and performance management for virtual, physical, and cloud infrastructures. Auto-discover resources of 75+ technologies, including vSphere, and collect availability, performance, utilization, and throughput metrics.

A command line tool for text file analyis, filtering, splitting and reporting. Runs under Java (1.5+), supports plugins written in Groovy. Has nix and win batch files in distributions.

Command line tool that can view multiple log files remotely and blend them into a single output based on the appropriate dates within the log files themselves. Has cat and tail modes available. Support for multiple local/remote protocols