<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Top 5 Reasons for a Predictive/Proactive Solution</title>
	<atom:link href="http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/</link>
	<description>thoughts on business, service and technology operations and management</description>
	<lastBuildDate>Thu, 29 Jul 2010 22:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: A Look Back and a Look Forward - June 2008 &#8212; dougmcclure.net</title>
		<link>http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/comment-page-1/#comment-54194</link>
		<dc:creator>A Look Back and a Look Forward - June 2008 &#8212; dougmcclure.net</dc:creator>
		<pubDate>Sat, 05 Jul 2008 17:54:01 +0000</pubDate>
		<guid isPermaLink="false">http://dougmcclure.net/blog/?p=706#comment-54194</guid>
		<description>[...] Top 5 Reasons for a Predictive/Proactive Solution I take a whack at what the drivers are for making an investment in these solutions. Please share [...]</description>
		<content:encoded><![CDATA[<p>[...] Top 5 Reasons for a Predictive/Proactive Solution I take a whack at what the drivers are for making an investment in these solutions. Please share [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Fielding</title>
		<link>http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/comment-page-1/#comment-53476</link>
		<dc:creator>J Fielding</dc:creator>
		<pubDate>Thu, 19 Jun 2008 01:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://dougmcclure.net/blog/?p=706#comment-53476</guid>
		<description>These real-time analytic tools aren&#039;t cheap, so we clearly have to justify the value to the business.  The approach I&#039;m taking is focusing on two areas.
  
First is to improve application performance.  If application X performs better than you&#039;re able to sell more products and services.  Analyzing performance datasets from SAN to OS to DB to middleware to CE allows the operations teams to better understand and resolve performance problems.   The advancements in these tools finally make it possible to do this in real-time.

Second is to reduce the amount of time spent adjusting thresholds manually for performance metrics.  The self-learning analytical tools improve the threshold management and the result is time saved.</description>
		<content:encoded><![CDATA[<p>These real-time analytic tools aren&#8217;t cheap, so we clearly have to justify the value to the business.  The approach I&#8217;m taking is focusing on two areas.</p>
<p>First is to improve application performance.  If application X performs better than you&#8217;re able to sell more products and services.  Analyzing performance datasets from SAN to OS to DB to middleware to CE allows the operations teams to better understand and resolve performance problems.   The advancements in these tools finally make it possible to do this in real-time.</p>
<p>Second is to reduce the amount of time spent adjusting thresholds manually for performance metrics.  The self-learning analytical tools improve the threshold management and the result is time saved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doug</title>
		<link>http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/comment-page-1/#comment-53451</link>
		<dc:creator>doug</dc:creator>
		<pubDate>Wed, 18 Jun 2008 13:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://dougmcclure.net/blog/?p=706#comment-53451</guid>
		<description>Excellent points Steve!  I think those should definitely be highlighted in this space, maybe even more so than the other &quot;sexy&quot; stuff.  I think these things are much more realistic and believable to clients.

Send some of your clients over and ask them to join the conversation!</description>
		<content:encoded><![CDATA[<p>Excellent points Steve!  I think those should definitely be highlighted in this space, maybe even more so than the other &#8220;sexy&#8221; stuff.  I think these things are much more realistic and believable to clients.</p>
<p>Send some of your clients over and ask them to join the conversation!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Henning</title>
		<link>http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/comment-page-1/#comment-53418</link>
		<dc:creator>Steve Henning</dc:creator>
		<pubDate>Tue, 17 Jun 2008 23:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://dougmcclure.net/blog/?p=706#comment-53418</guid>
		<description>Interesting questions, Doug. It would be great to hear from some customers of Real time analytics solutions (proactive/predictive solutions) here, however there is one important thing I&#039;d like to point out. 

Although the &quot;sexy&quot; part of the real time analytics solution&#039;s capabilities is the proactive/predictive stuff, there are other capabilities that can make a big impact for an Ops team. For example, simply understanding the normal behavior of your infrastructure can significantly improve the problem resolution process. It automates a lot of the manual work that goes into sifting through siloed monitoring alert storms trying to figure out which alerts are relevant to the current problem and which are not. It eliminates false positives related to normal behavior obscured by static thresholds and uncovers real problem precursor behavior. These solutions can also provide an understanding of how infrastructure components are related to user experience and business performance. This information can be used to build an adaptive Performance Management Database (PMDB) that helps identify performance relationships between IT infrastructure components much like a CMDB defines their physical relationships. You can get reports that show you the top infrastructure influencers of business performance and user experience key indicator (KI) breaches. Rather than using tribal knowledge to address problems, you have a map that indicates what to look for based on actual performance. Additionally, capturing models of the abnormal behaviors that lead to KI breaches provides a forensics capability that can pinpoint root cause of problems much more efficiently tha getting a representative of every silo on a bridge call. None of the things I&#039;ve mentioned here are about prediction or proactive alerting, these capabilities are about providing the intelligence that fuels improved troubleshooting efforts. The focus in the press and analyst community on the nirvana of predictive alerting (and the challenges) sometimes diverts attention from other capabilities of real time analytics solutions that can provide tangible, measurable increases in efficiency to existing performance management processes through increased intelligence.</description>
		<content:encoded><![CDATA[<p>Interesting questions, Doug. It would be great to hear from some customers of Real time analytics solutions (proactive/predictive solutions) here, however there is one important thing I&#8217;d like to point out. </p>
<p>Although the &#8220;sexy&#8221; part of the real time analytics solution&#8217;s capabilities is the proactive/predictive stuff, there are other capabilities that can make a big impact for an Ops team. For example, simply understanding the normal behavior of your infrastructure can significantly improve the problem resolution process. It automates a lot of the manual work that goes into sifting through siloed monitoring alert storms trying to figure out which alerts are relevant to the current problem and which are not. It eliminates false positives related to normal behavior obscured by static thresholds and uncovers real problem precursor behavior. These solutions can also provide an understanding of how infrastructure components are related to user experience and business performance. This information can be used to build an adaptive Performance Management Database (PMDB) that helps identify performance relationships between IT infrastructure components much like a CMDB defines their physical relationships. You can get reports that show you the top infrastructure influencers of business performance and user experience key indicator (KI) breaches. Rather than using tribal knowledge to address problems, you have a map that indicates what to look for based on actual performance. Additionally, capturing models of the abnormal behaviors that lead to KI breaches provides a forensics capability that can pinpoint root cause of problems much more efficiently tha getting a representative of every silo on a bridge call. None of the things I&#8217;ve mentioned here are about prediction or proactive alerting, these capabilities are about providing the intelligence that fuels improved troubleshooting efforts. The focus in the press and analyst community on the nirvana of predictive alerting (and the challenges) sometimes diverts attention from other capabilities of real time analytics solutions that can provide tangible, measurable increases in efficiency to existing performance management processes through increased intelligence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tiffany Winman</title>
		<link>http://dougmcclure.net/blog/2008/06/top-5-reasons-for-a-predictiveproactive-solution/comment-page-1/#comment-53415</link>
		<dc:creator>Tiffany Winman</dc:creator>
		<pubDate>Tue, 17 Jun 2008 20:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://dougmcclure.net/blog/?p=706#comment-53415</guid>
		<description>Doug, excellent post!</description>
		<content:encoded><![CDATA[<p>Doug, excellent post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
