RRD Definition in hobbitgraph.cfg and echo in server script

20 Oct 2006


      -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This seemed the right way to do it.  Are there any obvious "no,
dumbass"es in these definitions..?  With no good data, i should see a
blank graph if these were right, yesno?
[cputemp]
TITLE CPU Temperature
YAXIS DegreesF
DEF:cputemp=cputemp.rrd:cputemp:AVERAGE
AREA:cputemp#00CC00:CPU Temp Avg
GPRINT:cputemp:LAST: \: %5.11f (cur)
GPRINT:cputemp:MAX: \: %5.1lf (max)
GPRINT:cputemp:MIN: \: %5.1lf (min)
GPRINT:cputemp:AVERAGE: \: %5.1lf (avg)\n
in cputemp.sh:
echo "DS:cputemp:GAUGE:600:0:U"
name the RRD for the host and test
echo cputemp.rrd
Analyze the message we got.  If it's only one line, grab it.
The interesting number is the fourth element in this case.
CPU=grep CPU $FNAME | awk '{ print $4 }'
echo $CPU

Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFORKmBvBcJFK6xYURAppwAJwPNDmGEibGhuRVuMF2N8Cac1eyKQCeJVzH
yy/Ln3g2XlFWMDVF7xIGl0o=
=6TiM
-----END PGP SIGNATURE-----

RRD Definition in hobbitgraph.cfg and echo in server script

rmunsch＠solutionsforprogress.com

name the RRD for the host and test

Analyze the message we got. If it's only one line, grab it.

The interesting number is the fourth element in this case.