On Friday 19 January 2007 13:23, Henrik Stoerner wrote:
So if we're going to add MAX/MIN tracking to the RRD-files, we might as
well do it at the same time that we change the granularity. The numbers
I've been thinking of are to keep
* 30 days of 5-minute averages
* 90 days of 15-minute averages
* 360 days on 1-hour averages
* 1080 days of 3-hour averages
Even 1080 days is not enough for me. I have rrd files of backup systems that
are 6 years old.
I also have scripts that monitors devices every hour. So specifying
the --step parameter per rrd can also be handy.
That alone would cause the size of the RRD files to increase 15 times.
Adding MIN+MAX tracking would mean tripling the size. An "average"
host in my setup uses ~400 KB of diskspace for RRD-files, so increasing
that 15x3 times means it would grow to ~16 MB per host. It's a
significant increase (I'd have to get more disk space for my production
systems to handle that), but disks are getting bigger and cheaper -
and I'd still be storing data for 4000 hosts on less than 60 GB.
I agree. We are monitoring TB's of oracle databases. I'm sure they can miss
100 GB for monitoring purpose.
Btw, the trends patch your wrote is working perfect. The next step is finding
a way to create graphs.
Stef