[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
why rrd/do_disk.c couldn't store/extract correct CUR value to RRD?
- To: hobbit (at) hswn.dk
- Subject: why rrd/do_disk.c couldn't store/extract correct CUR value to RRD?
- From: "Jerry Yu" <jjj863 (at) gmail.com>
- Date: Tue, 16 Jan 2007 16:45:10 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=OKSuuOAeeeIWALglABJ2AOWVGaC6lVP8vcS8bvYyYUULCg62urxrI+WM+HvSg1wbreWOr5BNIQDSEFAcxPV36A49GMBEAYt2UilwQWG3M/9owp9uTs1Uhpweh7l28BlwlwUZzgZqIpDGh9gvdvyqNH8+PHYLSH0p1mo7KOofJsU=
In order to piggy-back some database disk usage monitor onto Hobbit's
default 'disk' check, I modifed hobbitclients-linux.sh to call a script
under [df] section, so the following is appended to the regular df output.
The rrd graph shows and alerts get generated when a threshold is
overstepped.
However, for some reason MAX/MIN/CUR data is decimal, while the CUR is not
closer to the AVERAGE than to the real data as reported.
rrd/do_disk.c shows each line of the df output is tokenized using space
character. I can't figure out what caused the CUR (as stored in
disk,db_12_web_DATA.rrd as well) is not the real integer, nor even close to
the real integer reported.
/db_12_web_DATA_dat 100 70 30 70% /db_12_web_DATA
/db_12_web_LOG_dat 100 97 3 97% /db_12_web_LOG
Since the alert is generated, so I'd think Hobbit server does extract the
correct 'pused' at some point
/db_12_web_LOG (97% used) has reached the PANIC level (95%)