improving the 300 second resolution nagiosgraph

[Litwin, Matthew]

I need some assistance with nagiosgraph, specifically with how it handles RRD data.

I am finding that there is a 300 second resolution limitation with nagiosgraph and how it uses rrdtool. I see the 300 second resolution clearly in the graphs themselves (regardless of how much I "zoom") which also correlates to the head of the output of 'rrdtool dump' for any of the RRD files nagiosgrah has created:

<!-- Round Robin Database Dump --><rrd>	<version> 0003 </version>
	<step> 300 </step> <!-- Seconds -->
	<lastupdate> 1262647468 </lastupdate> <!-- 2010-01-04 23:24:28 UTC -->

	<ds>
		<name> errors </name>
		<type> GAUGE </type>
		<minimal_heartbeat> 60 </minimal_heartbeat>
		<min> NaN </min>
		<max> NaN </max>

		<!-- PDP Status -->
		<last_ds> 0 </last_ds>
		<value> 6.0000000000e+01 </value>
		<unknown_sec> 0 </unknown_sec>
	</ds>

The problem with this is that I have monitors the run every 60 seconds and the lack of precision is excessively smoothing the graphs to the point of them being useless.

My question is two-fold:
1) Where is this "step" period of 300 seconds specified in nagiosgraph?
2) If I were to globally change the "step" period in nagiosgraph from 300 seconds to 60 seconds is there some way that I can keep my existing RRD data or would it become corrupted if I tried to change this?

Thanks,
Matthew Litwin
mlitwin at stubhub.com
415.222.8475


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null