MRTG does not give precise value or converts wrong

graphmonitoringmrtgsnmpsystem-monitoring

By example:
I have SNMP response value 59757296, passed to MRTG via conf ("business as usual").
The value is in bytes (I checked specs of the target device plus web interface of device confirms).

In theory I should be getting "58356.7" KB in MRTG graph but I am getting "59682.5 KB".
I know it's average over 5 minutes and value varies a bit (I have manually monitored the value and it randomly goes up/down 200KB over 5 min). Perhaps MRTG divides by 1000 and not by 1024 for KB value?

relevant MRTG setting:

kMG[mem]: b,K
ShortLegend[mem]: B

Best Answer

According to the docs, MRTG uses 1000 as the kilo multiplier by default. You can change it as follows:

kilo[mem]: 1024

Related Solutions

MRTG bandwidth not accurate

This is counter rollover. Make sure you are using SNMPv2(SNMP v2 use 64-bit counters).

Add :::::2 to switch definition(Target[myswitch]: 2:public@switch1:::::2) and enable SNMP v2 on switch.

Linux – nagios nrpe check_procs wrong return value

I think it's a bug in check_procs: it seems to pick up itself when running from nrpe, as opposed to the command line. Maybe a race condition of some sort.

I see you're running Ubuntu, given your command prompt. With the check_procs available on Lucid, I'm able to do something like:

/usr/lib/nagios/plugins/check_procs --ereg-argument-array="[s]tring" -w 1:1

So, we'll do a pattern match on the argument list, but in such a way that the check_procs process won't be matched. Putting one character of the pattern into square brackets causes the expression to match on "string" but it obviously won't match on the check_procs argument "[s]tring".

The check_procs available on Hardy doesn't have the regex option, though.

Best Answer

Related Solutions

MRTG bandwidth not accurate

Linux – nagios nrpe check_procs wrong return value

Related Topic