Ron Reeder wrote:
This has bitten me off and on for a couple of years.
See the example of chunky Load graph for a summary of a Cluster of Servers.
http://www.rreeder.net/graph.load.php.gif
What was going on?
There is not enough 'time' in the first level of the RRD database - so
It drops down to the second level to get the requested
one hour duration.
The gmetad daemon was building the RRD database with 240 intervals of
_13_ seconds, _not_ 15 seconds.
I don't know why gmetad was doing this ... I know it was from: rrdtool
info <hostname-metric.rrd>
Since the number 240 for intervals is _hard coded_ in the gmetad server,
I don't know why you don't go
ahead and hard code the length of interval to 15 seconds... I have done
this at my site, and built
a patch and a new rpm based on that patch.
I have also written a simple script to update the RRD databases to fix
the interval problem .... Just add a few intervals
so we have enough for a full hour.
Did this issue ever get addressed in the production code?
Is the script you sent to fix the old databases to work with the new
gmetad? Will all the historic information still be present if you don't
run the script?
Thanks,
Sean
