RE: Audit Logging Best Practices?

[Jim Rand]

Title: Message

Hi Bob,   I've used Log4Net for two projects. It has proved invaluable for diagnosing problems in a perpetual data conversion system.   Attached is a sample of the log output exported to a Microsoft Excel CSV file.   For future projects, I'm switching to the Microsoft Enterprise Library which also has logging.  This has nothing to do with the capabilities of Log4Net (outstanding) but rather to a completely different approach to application development.   Jim       -----Original Message----- From: Bob Pinna [mailto:[EMAIL PROTECTED] Sent: Thursday, March 10, 2005 8:15 PM To: Log4NET Dev Subject: Audit Logging Best Practices? We’re evaluating log4net for both general purpose logging and for managing an audit log that will be visible to non-technical users.  We have a need to log three types of audit events:   Success – Operation completed successfully Soft Failure – Operation failed but will be retried Hard Failure – Operation permanently failed and will not be retried.   We think we understand how to implement this within the log4net framework, but since this seems like a common problem I thought we would post to see if there are any best practices.   Our current thoughts are to:   Add three custom levels: Success, SoftFail, HardFail just above Error in priority. Log audit messages within the context of other debugging messages via the “standard” root appender model. Add a separate “audit message only” appender that filters out events below the audit message priority to create a log suitable for display (possibly after massaging) to customers.   Thoughts?   Best, Bob Pinna http://www.marketvoyce.com

loggerSample.csv
Description: Binary data