ESB.NET's cool loggers now ship with async logging functionality.
A separate IIS AppPool is used for the asynchronous logging capability, so no Windows Service installation is necessary.
Further, each instance gets it's own async logger by default (you can change this to use a centralized logger if you like), so you get complete control of which instances do logging, uninterrupted logging capability as instances are added/removed etc.
Using the existing MSMQ Logging queues (per instance), the simple async logger leverages the existing SQL Log Provider to provide a seamless logging experience between sync. & async logging.
Advantages therefore include running detailed production logging loads [with a suitably scaled SQL Server infrastructure], with a minimal resultant loss of performance.
Also, logging has been officially certified to be compatible with SQL Server 2008.
- Slated features in the next few releases are to include:
*Conditional logging options to allow a detailed logging trace for error scenarios, whilst allowing for a lower [user configurable via standard settings] logging level for non Error conditions
*Another Point & Click WSDL generation XSLT template
config driven Client loading of service handlers for ease of certain development scenarios
*Expansion of Request Re-Mapping filter
*Native DataSet object support in ESBEnvelope for a friendlier support when using ESB.NET as an App Server