Discussion:
[rrd-users] perfdata not correctly parsed ?
(too old to reply)
Nicolas - rrdtool
2015-01-12 08:33:57 UTC
Permalink
Hi,

I'm using rrdtool in centreon, trying to graph the output of the
check_snmp_storage.pl plugin.

Perfdata is correct, according to me :

'/mnt/disk1'=4149395MB;4873983;4978800;0;5240842
'/mnt/disk2'=3938774MB;4873983;4978800;0;5240842
'/mnt/disk3'=4244850MB;4873983;4978800;0;5240842
'/mnt/disk4'=4267812MB;4873983;4978800;0;5240842

According to the perfdata guidelines
(https://nagios-plugins.org/doc/guidelines.html#AEN200), the UOM is
correct :
10 : UOM (unit of measurement) is one of:
d : B - bytes (also KB, MB, TB)

But the graph displayed has divided the values by 1024/1024. See my
question on this forum for pictures :

http://forum.centreon.com/showthread.php/16199-check_snmp_storage-pl-and-graph

I then modified the plugin so that it outputs raw values, the new
perfdata is the following :

'/mnt/disk1'=4354426724352B;5110741642076;5220650064486;0;5495421120512

But now, the graph doesn't recognize the values (too big ?), as it says
"-nan'.

What solution do I have now ?

Regards
Nicolas
Simon Hobson
2015-01-12 10:51:33 UTC
Permalink
Post by Nicolas - rrdtool
'/mnt/disk1'=4354426724352B;5110741642076;5220650064486;0;5495421120512
But now, the graph doesn't recognize the values (too big ?), as it says "-nan'.
I'd be tempted to have the perfdata output as MB, but with no units (ie just the number). Thee days, it's hard to find a hard disk who's size (in bytes) isn't a very large number !

Also, remember that you need to allow up to a couple of step periods before you have valid data. If you'd just increased the numbers by 2^20, that's a big step and may well have exceeded the upper bounds on rate - or if there had been a gap there may well have been unknowns in the database. So allow at least 2xstep value (assuming you have a consolidation @ 1step resolution) before expecting valid data.
Loading...