<?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: Graphing requests per second out of apache log files</title>
	<atom:link href="http://blog.hongens.nl/2009/03/19/graphing-requests-per-second-out-of-apache-log-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hongens.nl/2009/03/19/graphing-requests-per-second-out-of-apache-log-files/</link>
	<description>A systems administrator's diary</description>
	<lastBuildDate>Thu, 22 Jul 2010 01:48:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Andrew</title>
		<link>http://blog.hongens.nl/2009/03/19/graphing-requests-per-second-out-of-apache-log-files/comment-page-1/#comment-39998</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 22 Jul 2010 01:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=86#comment-39998</guid>
		<description>You&#039;re right, the timestamps being out of order is because of the difference between the time at which a request starts (the timestamp on the log line) and when it finishes (which is when it&#039;s written into the log line).

This is very useful information.  It may not be something you want for your current purpose, but it would be a shame to throw this information away.

It&#039;s very useful to be able to identify the log lines where the timestamp recorded is significantly behind the latest timestamp seen by that point in the logs, as this identifies the long running requests, which are likely to be performance issues on your site.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, the timestamps being out of order is because of the difference between the time at which a request starts (the timestamp on the log line) and when it finishes (which is when it&#8217;s written into the log line).</p>
<p>This is very useful information.  It may not be something you want for your current purpose, but it would be a shame to throw this information away.</p>
<p>It&#8217;s very useful to be able to identify the log lines where the timestamp recorded is significantly behind the latest timestamp seen by that point in the logs, as this identifies the long running requests, which are likely to be performance issues on your site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: angelo</title>
		<link>http://blog.hongens.nl/2009/03/19/graphing-requests-per-second-out-of-apache-log-files/comment-page-1/#comment-36662</link>
		<dc:creator>angelo</dc:creator>
		<pubDate>Sat, 23 Jan 2010 09:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=86#comment-36662</guid>
		<description>The link works for me, but here&#039;s a mirror: http://files.hongens.nl/2010/01/23/requests.rb</description>
		<content:encoded><![CDATA[<p>The link works for me, but here&#8217;s a mirror: <a href="http://files.hongens.nl/2010/01/23/requests.rb" rel="nofollow">http://files.hongens.nl/2010/01/23/requests.rb</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.hongens.nl/2009/03/19/graphing-requests-per-second-out-of-apache-log-files/comment-page-1/#comment-36643</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 22 Jan 2010 02:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=86#comment-36643</guid>
		<description>I&#039;ve been looking all over fro something that does this for quite a while. Your requests.rb link is broken. Do you have a copy of this available?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been looking all over fro something that does this for quite a while. Your requests.rb link is broken. Do you have a copy of this available?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
