<?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: Internet Titans Not Immune to Downtime</title>
	<atom:link href="http://www.datacenterknowledge.com/archives/2008/09/04/internet-titans-not-immune-to-downtime/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.datacenterknowledge.com/archives/2008/09/04/internet-titans-not-immune-to-downtime/</link>
	<description>News and analysis about data centers, cloud computing, managed hosting and disaster recovery</description>
	<lastBuildDate>Mon, 13 Feb 2012 17:24:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Steve Henning</title>
		<link>http://www.datacenterknowledge.com/archives/2008/09/04/internet-titans-not-immune-to-downtime/comment-page-1/#comment-814</link>
		<dc:creator>Steve Henning</dc:creator>
		<pubDate>Thu, 25 Sep 2008 17:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=2733#comment-814</guid>
		<description>It doesn&#039;t matter how well-heeled a company is, nor how industrial strength their infrastructure. These outages and brownouts are going to continue until these enterprises get their Operations act together and start taking a more proactive approach to performance management. I guarantee you that every one of these companies is using a variety of siloed monitoring solutions and relying on static thresholds for individual metric measurements to determine if they are having a problem. Of course, this is not very effective because if they set the thresholds too high, by the time they get alerts end users are already calling them to complain. Set them lower and they get constant alert flow that masks the real problem precursors and they still find out about problems from end users. Most of these folks are probably not monitoring critical end user experience data and are not incorporating business performance metrics so they focus efforts on problems that are really impacting the business. Even the well-heeled with their fancy BSM dashboards and Event Management systems and complex processes and procedures cannot prevent problems from affecting end users and the bottom line of the business. Lets not even get into the affect on these company&#039;s reputations...

So what is missing... Well... an automated &quot;brain&quot; that can intergrate with their existing monitoring infrastructure and understand the normal behavior of all the components that make up these complex, customer-facing business services. A solution that can add context and tell IT Operations when to pay attention and what to pay attention to. Lets face it... their current tools aren&#039;t giving them these two critical pieces of information. In fact, these tools are confusing the issue unintentionally.

Performance management analytics solutions exist that take metric data from siloed monitoring sources and analyze it holistically, learning the normal behavior of every metric collected and sending a heads up when significant  abnormal behaviors indicate a problem is imminent. These solutions often predict problems hours before occurrence and include the most likely root cause symptoms so that action can be taken to prevent them.

Until IT Operations teams embrace solutions such as these, Pingdom will have plenty to report on...</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t matter how well-heeled a company is, nor how industrial strength their infrastructure. These outages and brownouts are going to continue until these enterprises get their Operations act together and start taking a more proactive approach to performance management. I guarantee you that every one of these companies is using a variety of siloed monitoring solutions and relying on static thresholds for individual metric measurements to determine if they are having a problem. Of course, this is not very effective because if they set the thresholds too high, by the time they get alerts end users are already calling them to complain. Set them lower and they get constant alert flow that masks the real problem precursors and they still find out about problems from end users. Most of these folks are probably not monitoring critical end user experience data and are not incorporating business performance metrics so they focus efforts on problems that are really impacting the business. Even the well-heeled with their fancy BSM dashboards and Event Management systems and complex processes and procedures cannot prevent problems from affecting end users and the bottom line of the business. Lets not even get into the affect on these company&#8217;s reputations&#8230;</p>
<p>So what is missing&#8230; Well&#8230; an automated &#8220;brain&#8221; that can intergrate with their existing monitoring infrastructure and understand the normal behavior of all the components that make up these complex, customer-facing business services. A solution that can add context and tell IT Operations when to pay attention and what to pay attention to. Lets face it&#8230; their current tools aren&#8217;t giving them these two critical pieces of information. In fact, these tools are confusing the issue unintentionally.</p>
<p>Performance management analytics solutions exist that take metric data from siloed monitoring sources and analyze it holistically, learning the normal behavior of every metric collected and sending a heads up when significant  abnormal behaviors indicate a problem is imminent. These solutions often predict problems hours before occurrence and include the most likely root cause symptoms so that action can be taken to prevent them.</p>
<p>Until IT Operations teams embrace solutions such as these, Pingdom will have plenty to report on&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

