<?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: Hyperic joins SpringSource</title>
	<atom:link href="http://stage.vambenepe.com/archives/747/feed" rel="self" type="application/rss+xml" />
	<link>http://stage.vambenepe.com/archives/747</link>
	<description>IT management in a changing IT world</description>
	<lastBuildDate>Wed, 17 Mar 2010 19:31:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: William Vambenepe&#8217;s blog &#187; Blog Archive &#187; Thoughts on VMWare, SpringSource and PaaS</title>
		<link>http://stage.vambenepe.com/archives/747#comment-86229</link>
		<dc:creator>William Vambenepe&#8217;s blog &#187; Blog Archive &#187; Thoughts on VMWare, SpringSource and PaaS</dc:creator>
		<pubDate>Thu, 27 Aug 2009 05:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=747#comment-86229</guid>
		<description>[...] was wrong to think at the time of the Hyperic acquisition that SpringSource would focus on app-centric management, BTM [...]</description>
		<content:encoded><![CDATA[<p>[...] was wrong to think at the time of the Hyperic acquisition that SpringSource would focus on app-centric management, BTM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; SpringSource Buys Hyperic - What&#8217;s the Hyperic Angle?</title>
		<link>http://stage.vambenepe.com/archives/747#comment-73378</link>
		<dc:creator>People Over Process &#187; SpringSource Buys Hyperic - What&#8217;s the Hyperic Angle?</dc:creator>
		<pubDate>Fri, 08 May 2009 23:23:09 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=747#comment-73378</guid>
		<description>[...] I completely agree with M. Vambenepe: Still on the topic of Hyperic’s monitoring-only capabilities, it means that if Rod Johnson [...]</description>
		<content:encoded><![CDATA[<p>[...] I completely agree with M. Vambenepe: Still on the topic of Hyperic’s monitoring-only capabilities, it means that if Rod Johnson [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Louth</title>
		<link>http://stage.vambenepe.com/archives/747#comment-73154</link>
		<dc:creator>William Louth</dc:creator>
		<pubDate>Tue, 05 May 2009 10:53:59 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=747#comment-73154</guid>
		<description>You would think having access to the source code users would make much better informed decisions regarding the quality of a solution identifying inherent architectural weakness which limit scalability, performance and accuracy of reporting. Maybe users are just somewhat lazy or unable to perform a reasonable due diligence. Even so a few hints in the documentation would fire up anyone (with some performance management backgrounds) spiders senses such as a default sampling window of 15 minutes with a hard minimum limit of 1 minute. It beats me how anyone could spot intermittent problems (yes, the non low hanging fruit types that plague production) within any application code base at such granularity never mind how these are actually correlated (I believe its with your eyes). Lets put that into perspective for those with very little Java performance management experience - our metrica early access release coming this week can sample 100,000 probe based metrics in under 10 ms. We could in theory perform 90,000 samples of 100,000 metrics in 15 minutes compared to Hyperic&#039;s single sample of approximately 100 Java related metrics. 

The news and coverage is completely out of proportion to the value offered. You have to give it to them though, they might not have quality software but they do know how to live up to a company name - hype.</description>
		<content:encoded><![CDATA[<p>You would think having access to the source code users would make much better informed decisions regarding the quality of a solution identifying inherent architectural weakness which limit scalability, performance and accuracy of reporting. Maybe users are just somewhat lazy or unable to perform a reasonable due diligence. Even so a few hints in the documentation would fire up anyone (with some performance management backgrounds) spiders senses such as a default sampling window of 15 minutes with a hard minimum limit of 1 minute. It beats me how anyone could spot intermittent problems (yes, the non low hanging fruit types that plague production) within any application code base at such granularity never mind how these are actually correlated (I believe its with your eyes). Lets put that into perspective for those with very little Java performance management experience &#8211; our metrica early access release coming this week can sample 100,000 probe based metrics in under 10 ms. We could in theory perform 90,000 samples of 100,000 metrics in 15 minutes compared to Hyperic&#8217;s single sample of approximately 100 Java related metrics. </p>
<p>The news and coverage is completely out of proportion to the value offered. You have to give it to them though, they might not have quality software but they do know how to live up to a company name &#8211; hype.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
