[hobbit] FW: RRD data points - need help with graph distortion

[Everett, Vernon]

I also remember seeing an add-on which allowed you to dump your data points into a MySQL database.
This would allow you to maintain max granularity for as long as your disk space held out.
If I recall, there was no modification or recompilation of the code required. (But don't quote me on that)
Search the archive, and see what comes up.

Cheers
    Vernon

-----Original Message-----
From: Stef Coene [mailto:stef.coene at docum.org]
Sent: Tuesday, 11 November 2008 7:15 AM
To: hobbit at hswn.dk
Subject: Re: [hobbit] FW: RRD data points - need help with graph distortion

On Monday 10 November 2008, Wood, Mike wrote:
> Looks like my graphs didn't come through on the E-mail.  Trying
> different attachment type...
>
>
> From: Wood, Mike [mailto:Mike.Wood at kci1.com]
> Sent: Monday, November 10, 2008 9:06 AM
> To: hobbit at hswn.dk
> Subject: [hobbit] FW: RRD data points - need help with graph
> distortion
>
> Hi All,
>
> I asked this question last week, but maybe I wasn't clear enough as to
> what I was asking... - Management wants to avoid graph distortion on
> my 60 day CPU Util graph if possible.  I think that more datapoints
> would address the problem. The first graph looks good (30 day graph).
> The 2nd one distorts what is really going on (60 day graph - same
> server).  Is there any way to make the 2nd graph more granular?
> Thanks for looking! -
I have a perl script to update all the rrd files:

- it uses rrdtool resize <rrd file> GROW to add extra datapoints so the rrd has 5760 data points / rra (per default it has 756 data points)

- it adds also MAX and MIN rra's, this is more tricky because I export the rrd to xml, change the xml info and revert back to an rrd file.

Unfortunatly, I can not share this script.  But with use RRDs ; use File::Find (); you can get info about the file and find them ;)


Stef

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk



NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.