I noticed when setting up a 'disk used' item in the front end the total for used disk is off from what solaris says the used space is. For example here is the line for a filesystem via CLI:
[root@solaris nameserve]# df -k /nameserve
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0d1s0 10324476 344342 9876890 4% /nameserve
So it is currently using 326ish megs. However the agentd is reporting back this in the log:
8978:20081016:151053 Requested [vfs.fs.size[/nameserve,used]]
8978:20081016:151053 Sending back [440914]
which makes the front end say it is using 432 MB.
The item looks like:
vfs.fs.size[/nameserve,used]
unit: B
custom multiplier: 1024
Has anyone else experienced this? I just started evaluating zabbix, great software. Would like to cross this off as (my) human error.
[root@solaris nameserve]# df -k /nameserve
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0d1s0 10324476 344342 9876890 4% /nameserve
So it is currently using 326ish megs. However the agentd is reporting back this in the log:
8978:20081016:151053 Requested [vfs.fs.size[/nameserve,used]]
8978:20081016:151053 Sending back [440914]
which makes the front end say it is using 432 MB.
The item looks like:
vfs.fs.size[/nameserve,used]
unit: B
custom multiplier: 1024
Has anyone else experienced this? I just started evaluating zabbix, great software. Would like to cross this off as (my) human error.
Comment