Refering to the NEWS:
2.2 [...]
ENHANCEMENTS
check_snmp's performance data now also includes warning/critical
thresholds
I tried it, since I am waiting for the feature.
My tests / example for a Switch port ( w/ current git-version) looked like
this:
/usr/local/libexec/check_snmp -H 192.168.2.1 --rate -C public-P 2c -o
ifInOctets.1,ifOutOctets.1,ifInUcastPkts.1,ifOutUcastPkts.1,ifInErrors.1,ifOutErrors.1
-m IF-MIB -l in,out,inucast,outucast,inerr,outerr -w
230400,230400,1000000000,1000000000,0.01,0.01 -c
230400,230400,1000000000,1000000000,0.01,0.01
SNMP RATE OK - in 8273.875 out 31296.25 inucast 92.125 outucast 64.5 inerr 0
outerr 0 |
in=8273.875;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01
out=31296.25;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01
inucast=92.125;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01
outucast=64.5;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01
inerr=0;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01
outerr=0;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01
The warning/critical include in the perfdata are the complete strings of w/c
- not just the value used for the check against it.
For the sake of understanding corectly I expected as result:
SNMP RATE OK - in 8273.875 out 31296.25 inucast 92.125 outucast 64.5 inerr 0
outerr 0 | in=8273.875;230400;230400 out=31296.25;230400;230400
inucast=92.125;1000000000;1000000000 outucast=64.5;1000000000;1000000000
inerr=0;0.01;0.01 outerr=0;0.01;0.01
--
Reply to this email on GitHub:
https://github.com/monitoring-plugins/monitoring-plugins/issues/1327
