<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Load on Evan Hoffman</title><link>https://evan.wtf/tags/load/</link><description>Recent content in Load on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Fri, 17 Feb 2012 15:32:25 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/load/index.xml" rel="self" type="application/rss+xml"/><item><title>Using rrdtool to generate server load &amp; bandwidth graphs</title><link>https://evan.wtf/2012/02/17/using-rrdtool-to-generate-server-load-bandwidth-graphs/</link><pubDate>Fri, 17 Feb 2012 15:32:25 +0000</pubDate><guid>https://evan.wtf/2012/02/17/using-rrdtool-to-generate-server-load-bandwidth-graphs/</guid><description>&lt;p&gt;I&amp;rsquo;ve been using MRTG and routers2.cgi for years to graph the various aspects of a server that warrant monitoring. I&amp;rsquo;ve long known that they used something called rrdtool to do&amp;hellip; well, something, but never had a need or desire to figure out exactly what that was.&lt;/p&gt;&#10;&lt;p&gt;But, having just moved my site to a new server, I was curious how the server would handle the load. Rather than setting up some behemoth like Nagios or Zabbix, which are full monitoring/alerting suites, I just wanted graphing. As I said, in the past I&amp;rsquo;ve used MRTG or routers2.cgi for this but both of them were overkill for me in this case. Since both of them used rrdtool, I figured that was a good place to look.&lt;/p&gt;</description></item></channel></rss>