Comments on: Logging Guidelines http://watchitlater.com/blog/2009/12/logging-guidelines/ A reluctant foray into the world of blogging. Thu, 17 May 2012 02:38:18 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Tom http://watchitlater.com/blog/2009/12/logging-guidelines/comment-page-1/#comment-5552 Tom Fri, 08 Jan 2010 10:52:50 +0000 http://watchitlater.com/blog/?p=115#comment-5552 Felix, absolutely spot on with categories, thanks for reminding me. On my current project we also have a bunch of instances of the same class, but we use the NDC to provide the name of the queue, etc for each message logged during the processing of a request by an instance. Felix, absolutely spot on with categories, thanks for reminding me. On my current project we also have a bunch of instances of the same class, but we use the NDC to provide the name of the queue, etc for each message logged during the processing of a request by an instance.

]]> By: felix http://watchitlater.com/blog/2009/12/logging-guidelines/comment-page-1/#comment-5551 felix Fri, 08 Jan 2010 09:10:17 +0000 http://watchitlater.com/blog/?p=115#comment-5551 As per usual insightful article. Good job at capturing these things. One more thing you are not mentioning is logging categories. The default is people using fully qualified class names, i.e. one static logger per class. I found that it is more to sometimes share loggers between different classes and inject them, e.g. for an audit trail. Also if you have more than one instance of a class in your system add a bit that identifies the instance, e.g. in one system we had a class for polling queues being good developers we had four instances - one for each queue we were polling, and we made the logger an instance variable containing the queue name rather than the class name as the last fragment of the category. As per usual insightful article. Good job at capturing these things.

One more thing you are not mentioning is logging categories. The default is people using fully qualified class names, i.e. one static logger per class. I found that it is more to sometimes share loggers between different classes and inject them, e.g. for an audit trail. Also if you have more than one instance of a class in your system add a bit that identifies the instance, e.g. in one system we had a class for polling queues being good developers we had four instances – one for each queue we were polling, and we made the logger an instance variable containing the queue name rather than the class name as the last fragment of the category.

]]> By: John Sonmez http://watchitlater.com/blog/2009/12/logging-guidelines/comment-page-1/#comment-5418 John Sonmez Mon, 21 Dec 2009 15:23:58 +0000 http://watchitlater.com/blog/?p=115#comment-5418 Very nice article. Thank you. It is always difficult to know when to use what logging level and what the message contains. I think this is a very accurate guideline. Very nice article. Thank you. It is always difficult to know when to use what logging level and what the message contains. I think this is a very accurate guideline.

]]>