Centralized logging makes application support and troubleshooting much easier, but Windows and Linux/UNIX based systems take different approaches. Syslog4NET provides a way to bridge this gap, allowing Windows applications to directly log to a syslog dameon running on Linux/UNIX.
ETW or Event Tracing for Windows is a high performance logging system that is available for Windows Vista and later operating systems. On a typical system it can handle over 100,000 events per second, but those events are discarded unless something is listening. With the new EventSource library, a portion of those events can be copied to the Windows Event Logged.
Thoughtworks recently released a new installment of their technology radar highlighting techniques enabling infrastructure as code, perimeterless enterprises, applying proven practices to areas without, and lightweight analytics.
Blitz4k, Netflix’ internally optimized version of log4j, has been released to Github. Blitz4j efficiently generates logs within a massively concurrent and heavy traffic environment while consuming fewer resources than other, more traditional logging technologies. Its use has lowered the cost of logging within Netflix by at least 75%.
GWT 2.1 RC1 contains features specified by the roadmap, such as new table and tree widgets, but also features that were initially planned for GWT 2.2, such as logging. Another important feature is an MVP framework.
ModuleFusion 1.0.2, an OSGi service stack designed for enterprise applications, was released. The distribution includes frameworks such as Google Guice, Hibernate, and Jetty, packaged as bundles.
Ceki Gülcü is well known in the world of Java logging. He founded Log4J and then worked on replacing Jakarta commons-logging with SLF4J. InfoQ spoke with Ceki about his new project, LOGBack, "the reliable, generic, fast and flexible logging framework for Java." With a 1.0 release just around the corner and some positive reviews from adopters, this may be the right time to take a look at LOGBack.
In an InfoQ article, Boris Lublinsky highlights the problems with exception handling in SOA, and suggests applying SOA principles to exception handling as a solution.
Ian Roughley shows how to use logging seams to easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes.