I assume that your reports are based on the logging statements in the DB. How do you accomodate for the different information needed for different reports? Do you log all the logging data as XML to a single database column? If so, how do you take advantage of the query capabilities in the DB, wouldn't you need to get all the records and then parse the XML for each record to determine it's type / information?

Also, are there any tools / third-party products out there for generating reports based on Log4Net logs?

Thanks for the help,
Daws



From: "Dawson Mossman" <[EMAIL PROTECTED]>
Reply-To: "Log4NET User" <[email protected]>
To: [email protected]
Subject: Log4Net Reports
Date: Sun, 23 Oct 2005 16:43:26 -0300

Hi,
I know the primary purpose of Log4Net is logging capability in your application. However, I'm wondering if it's also used/recommended for Reporting?

I've heard talk of people using Log4Net to generate logging information that they intend to use for creating reports. Is this a recommended strategy? Or should application reporting be kept separate from Log4Net entries?

From what I understand, it's common for Log4Net to be turned off in a production application and only turned on when required to debug a problem. If this is the typical usage, then clearly reporting based on Log4Net would not be recommended.

If you could clear this for me, it would avoid steering several projects in the wrong direction.

Thanks.




Reply via email to