<?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: Using New Relic on Heroku? Read How Our New Ruby Agent Measures Queue Time</title>
	<atom:link href="http://blog.newrelic.com/2013/02/21/using-new-relic-on-heroku-read-how-our-new-ruby-agent-measures-queue-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.newrelic.com/2013/02/21/using-new-relic-on-heroku-read-how-our-new-ruby-agent-measures-queue-time/</link>
	<description>Application Performance Management</description>
	<lastBuildDate>Fri, 24 May 2013 09:04:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Who is Responsible for PaaS Cloud Application Performance? &#124; The Virtualization Practice</title>
		<link>http://blog.newrelic.com/2013/02/21/using-new-relic-on-heroku-read-how-our-new-ruby-agent-measures-queue-time/#comment-23217</link>
		<dc:creator>Who is Responsible for PaaS Cloud Application Performance? &#124; The Virtualization Practice</dc:creator>
		<pubDate>Fri, 12 Apr 2013 13:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.newrelic.com/?p=12465#comment-23217</guid>
		<description><![CDATA[[...] most importantly was very up front about the limitations of the approach used to collect the data. The blog post is here. The key statement in the post is &#8220;Since the Ruby agent lives in your Rails or Ruby [...]]]></description>
		<content:encoded><![CDATA[<p>[...] most importantly was very up front about the limitations of the approach used to collect the data. The blog post is here. The key statement in the post is &#8220;Since the Ruby agent lives in your Rails or Ruby [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
