logFACES Enterprise Logging Suite is composed by two applications which deal with software integrations, testing, field support or development, should find this product very useful. LogFaces is an out-of-the-box solution built on top of Apache Logging Services.
With the help of logFACES Enterprise Logging Suite you have the possibility to find problems instantly, get notified in real-time when the system has issues and improve collaboration by sharing log information.
There are three players - your system, logFaces Server and logFaces Clients. It works like this, your system sends log data to the logFaces Server using the appenders we provide.
The server collects and routes this data to interested clients in the form that they define. The only requirement is to produce log in the format understood by the logFaces Server, which is currently Apache log4xxx API's schema. In the future we are planning to extend this format to alow other source types but today log4xxx API's are the de-facto standards in software development and most systems already support them. In such cases the integration is straightforward and is only a matter of simple configuration.
Personal Edition
There is a lighter version of logFaces which involves only two players - your system and logFaces Client directly. In this configuration the client runs a small embedded server inside. This variation is available as a Personal Edition for those who only need real-time viewer and typically don't require multi-user environment and database storage.
Limitations:
· 30 days trial
What's New in This Release:
· Improvement - clients of relation databases will now be able to escape special characters when using LIKE statements in fetch dialogs
· Bug - certain characters in app,host,logger names caused JScript errors in admin when generated hints for criterias
· Bug - mongodb cursors weren't closed properly in some queries resulting in resource leaks
· Bug - mongodb read preferences were not honored properly when used on replica sets
· Bug - mongodb converting collection types caused day retention parameter loss
· Bug - mongodb when used with no time index should have delivered unsorted results instead of limiting the result set
· Bug - SQL server when used with cp30 connection pool, removed transaction scope in queries
· Bug - logback appender layout wasn't ecaping special characters in MDC values