I recently discovered the solution to a problem I was having and want some
more detail. I initially set up gmetad.conf with my data sources using
default intervals (15sec). I then decided I wanted 10sec intervals so I
changed the conf and restarted the service. I soon discovered that my hour
graphs looked like bar graphs. After much gnashing of teeth (and learning
about rrdtool, and help from #rrdtool), I discovered that the default RRAs
that were initially created by gmetad were dependent on the 15sec interval
(actually, >= 15 sec). In other words, the RRA for the hourly data was not
big enough to store 10 second intervals because it was created for 15 second
intervals; as a consequence, the next largest RRA was used, the daily RRA
which had ~24 times lower resolution! It seems to me that when gmetad
starts up, it should check the RRAs and should either warn that the existing
RRAs are too small or it should resize the RRAs automatically. Is this a
known issue?
Thanks,
Matt Chambers
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers
