<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Matt J. Wilson &#187; Metrics</title>
	<atom:link href="http://www.mattjwilson.com/blog/tag/metrics/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mattjwilson.com/blog</link>
	<description>General ramblings, programming frustrations, and complete randomness.  Have questions? E-mail me.</description>
	<lastBuildDate>Tue, 19 Jan 2010 19:37:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Central Error Tracking for Deployed Systems</title>
		<link>http://www.mattjwilson.com/blog/2010/01/11/central-error-tracking-for-deployed-systems/</link>
		<comments>http://www.mattjwilson.com/blog/2010/01/11/central-error-tracking-for-deployed-systems/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 20:35:26 +0000</pubDate>
		<dc:creator>Matt J. Wilson</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[Metrics]]></category>

		<guid isPermaLink="false">http://www.mattjwilson.com/blog/?p=54</guid>
		<description><![CDATA[At one of my previous employers, we had several remote deployments (hundreds, actually) and a need to track remote errors in a central location; we utilized an ASP site to visually display this combined collection of errors.
I&#8217;ve taken the time to rewrite my own central error tracking mechanism from scratch.  This module includes text [...]]]></description>
			<content:encoded><![CDATA[<p>At one of my previous employers, we had several remote deployments (hundreds, actually) and a need to track remote errors in a central location; we utilized an ASP site to visually display this combined collection of errors.</p>
<p>I&#8217;ve taken the time to rewrite my own central error tracking mechanism from scratch.  This module includes text logs that automatically rotate themselves once a file reaches a certain size (no more trying to have someone email you a 3 GB text file), useful information about what type of error occurred, and a SQL CE database that stores these errors in a local database, counting the number of incidences and whether there is fresh information to report on a schedule to the central database.</p>
<p>There is also a central web service that accepts these exception reporting requests and inserts them into a central SQL database for you to do with what you will (ASP website, Excel sheets with queries, etc., etc.).  You can find a copy of this solution (Visual Studio 2005 written in C#) <a href="http://www.mattjwilson.com/Sample%20Work/Error%20Metrics.zip">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mattjwilson.com/blog/2010/01/11/central-error-tracking-for-deployed-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

