-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Please do not thread hijack.
=R
Stewart, Tom L. wrote:
All,
We are in the process of going from Hobbit 4.2.0 to Xymon 4.3.0-0.beta2.
We originally set up the timeframes for the rrd files as such on the new
Xymon server.
/* Check if the default record exists */
if (rbtFind(rrddeftree, "") == rbtEnd(rrddeftree)) {
/* Create the default record */
newrec = (rrddeftree_t *)malloc(sizeof(rrddeftree_t));
newrec->key = strdup("");
newrec->defs = (char **)malloc(4 * sizeof(char *));;
newrec->defs[0] = strdup("RRA:AVERAGE:0.5:1:157824");
newrec->defs[1] = strdup("RRA:AVERAGE:0.5:6:157824");
newrec->defs[2] = strdup("RRA:AVERAGE:0.5:24:157824");
newrec->defs[3] = strdup("RRA:AVERAGE:0.5:288:157824");
newrec->count = 4;
rbtInsert(rrddeftree, newrec->key, newrec);
The belief was that we would be able to keep 5 minute increments of data
out to 576 days. Now because of the amount of space required, that have
asked to keep the 576 day average to 30 minutes instead of the 5 minutes
and keep the 2, 12 and 48 days at 5 minutes. As I will not have time to
make sure that long of time is correct, so I need some other eyes to
tell me if my calculations are correct.
I am planning on taking newrec->defs[3] =
strdup("RRA:AVERAGE:0.5:288:157824"); and changing 157824 to 82944.
Am I correct in my calculation for the 576 day average for 30 minutes or
am I totally off base?
We are keeping the original Hobbit server for historical review and I
don’t have to worry about converting any rrd files. And because we are
in test, I can simple blow away the new rrd files on Xymon.
All comments will be appreciated!
Thank you,
Tom
- --
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II
|$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrDb/MACgkQmb+gadEcsb4gkwCbBvavbkjsJzicvU09vYApAakb
5gsAn3O0AS52vvo3flH0LioTBZ3CAsfl
=e9on
-----END PGP SIGNATURE-----