<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Application logging principles</title>
	<atom:link href="http://www.thekua.com/atwork/2008/11/application-logging-principles/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thekua.com/atwork/2008/11/application-logging-principles/</link>
	<description>thekua&#039;s reflections on work related topics</description>
	<lastBuildDate>Fri, 12 Mar 2010 17:25:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glen</title>
		<link>http://www.thekua.com/atwork/2008/11/application-logging-principles/comment-page-1/#comment-46150</link>
		<dc:creator>Glen</dc:creator>
		<pubDate>Wed, 14 Jan 2009 14:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=318#comment-46150</guid>
		<description>Nice blog Pat, logging is a much underrated subject.  One thing that is worth keeping in mind at all times is that you are not the only consumer of the log file.  Operational teams and other developers need to read and understand quickly what is being logged and why.  They also need to have confidence in what is being logged or they will quickly develop log blindness and ignore potentially serious issues.

Personally I like to log variable contents inside [] so its easy to see, and shows things like the dreaded additional whitespace.  Also doing simple things like this and thinking about your logging style makes it easier to scrape logs with another tool.

And beware the developer who tries to do something too fancy using logging - I&#039;ve seen systems brought to a halt because of reflection being done over a swathe of objects for assistance during debugging (doesn&#039;t smell good to start with) and worse that reflection was being done regardless of the defined log level :(</description>
		<content:encoded><![CDATA[<p>Nice blog Pat, logging is a much underrated subject.  One thing that is worth keeping in mind at all times is that you are not the only consumer of the log file.  Operational teams and other developers need to read and understand quickly what is being logged and why.  They also need to have confidence in what is being logged or they will quickly develop log blindness and ignore potentially serious issues.</p>
<p>Personally I like to log variable contents inside [] so its easy to see, and shows things like the dreaded additional whitespace.  Also doing simple things like this and thinking about your logging style makes it easier to scrape logs with another tool.</p>
<p>And beware the developer who tries to do something too fancy using logging &#8211; I&#8217;ve seen systems brought to a halt because of reflection being done over a swathe of objects for assistance during debugging (doesn&#8217;t smell good to start with) and worse that reflection was being done regardless of the defined log level <img src='http://www.thekua.com/atwork/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #221</title>
		<link>http://www.thekua.com/atwork/2008/11/application-logging-principles/comment-page-1/#comment-34829</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #221</dc:creator>
		<pubDate>Wed, 12 Nov 2008 08:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=318#comment-34829</guid>
		<description>[...] Application logging principles - Patrick Kua talks about the importance of good logging within your application, and how good logging can help to dramatically reduce debugging time and provide a better user experience for you application. [...]</description>
		<content:encoded><![CDATA[<p>[...] Application logging principles &#8211; Patrick Kua talks about the importance of good logging within your application, and how good logging can help to dramatically reduce debugging time and provide a better user experience for you application. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rahul</title>
		<link>http://www.thekua.com/atwork/2008/11/application-logging-principles/comment-page-1/#comment-34815</link>
		<dc:creator>Rahul</dc:creator>
		<pubDate>Wed, 12 Nov 2008 05:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=318#comment-34815</guid>
		<description>Chris Petrilli&#039;s blog posts about the problems with logging and how to fix them make for good read on this subject.

http://blog.amber.org/2008/11/07/fixing-logging-pt-2-message-catalogs/</description>
		<content:encoded><![CDATA[<p>Chris Petrilli&#8217;s blog posts about the problems with logging and how to fix them make for good read on this subject.</p>
<p><a href="http://blog.amber.org/2008/11/07/fixing-logging-pt-2-message-catalogs/" rel="nofollow">http://blog.amber.org/2008/11/07/fixing-logging-pt-2-message-catalogs/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
