.Net exception logging tools
I am looking for a good tool that will give me detailed analysis of the exception in product releases.
I know EurekaLog and one day I saw an add-on for frog software or something similar in the title, googled it with no results.
Does anyone have a recommendation?
My main goal is to extract as much useful information as possible when a production crash occurs.
Also, maybe a little off topic, something similar for lock detection.
source to share
Not sure if you are looking for a Winforms or ASP.NET solution here. But for ASP.NET, I'm using Elmah ( http://code.google.com/p/elmah/ ).
source to share
We are using the Enterprise Library logging application block.
http://msdn.microsoft.com/en-us/library/dd139916.aspx
You determine how many records are logged through configuration and where you place the logging statements. It also allows you to change the amount of information that is logged without stopping the system.
source to share
If you want freedom of choice without making a heavy reliance on a specific logging framework (Log4Net, nLog, EntLib), you can take a look at the Common.Logging library. It basically abstracts the logger implementation by providing only a common interface for all available logging blocks.
Cm:
http://netcommon.sourceforge.net/
Disclaimer: I haven't used it (yet), but I'm going to try it soon. The idea of not being tied to a specific logger appeals to me as I like to stick to one log library per project. Imagine creating a project that uses nLog for logging, but then you add NHibernate. NH uses Log4Net, so we now have two logging libraries in our dependencies; -)
source to share
Thanks for your answers, but this is not the direction I was looking for. I am more interested in exceptional error / crash messages and the maximum amount of data that can be retrieved to understand why this happened, for example, stack traces of all threads, last user actions (clicks), etc.
The logging framework is as valuable as the material I write in.
source to share