Bug #100828 for jmx4perl: jmx4perl : issue on check_jmx4perl

You are right about this. However it seems that the check, in this case, doesn't seem to bother about the warning and critical thresholds. How can I be sure it will correctly understand values like 0:0 or ~:0 when it appears ? Here's a example with a different mbean: [nagios@FPS37ETU1 ]# check_jmx4perl --url http://localhost:8080/jolokia --name test --value com.bea:Name=portail_ppd1,Type=ServerRuntime/OpenSocketsCurrentCount --critical 7 --target service:jmx:t3://mhm37ppd1:7011/jndi/weblogic.management.mbeanservers.runtime --target-user=monitor --target-password=XXXXXXX OK - test : Value 6 in range | test=6;;7 [nagios@FPS37ETU1 ]# check_jmx4perl --url http://localhost:8080/jolokia --name test --value com.bea:Name=portail_ppd1,Type=ServerRuntime/OpenSocketsCurrentCount --critical 0 --target service:jmx:t3://mhm37ppd1:7011/jndi/weblogic.management.mbeanservers.runtime --target-user=monitor --target-password=XXXXXX CRITICAL - test : Threshold '0' failed for value 6 | test=6;;0 And it works fine! I believe something's wrong when the structure of the attribute is complex (see attached screen capture ): With mbean com.bea:Name=portail_ppd1,Type=ServerRuntime/OpenSocketsCurrentCount: the check gets the value (6) and make the check against the threshold ok. With mbean com.bea:Name=portail_ppd1,Type=ServerRuntime/OverallHealthState/State: The check gets the value (0) but the check is wrong against the threshold. if you delete the "path" in the value field, you can see that the attribute is a HASH: check_jmx4perl --url http://localhost:8080/jolokia --name test --value com.bea:Name=portail_ppd1,Type=ServerRuntime/OverallHealthState --critical 0 --target service:jmx:t3://mhm37ppd1:7011/jndi/weblogic.management.mbeanservers.runtime --target-user=monitor --target-password=XXXXXX UNKNOWN - Response value is a HASH, not a plain value. Did you forget a --path parameter ? Value: $VAR1 = { 'critical' => 'true', 'mBeanName' => 'portail_ppd1', 'mBeanType' => 'ServerRuntime', 'subsystemName' => 'ServerRuntime', 'reasonCode' => '[Ljava.lang.String;@2dbe4ff2', 'state' => '0' }; Hope this helps. Cordialement, Mathieu Wingel Ingénieur Production Direction Production 41 rue Fabienne Landy 37700 Saint Pierre des Corps Tél. 02 47 46 58 87 mathieu.wingel@sihm.fr En harmonie avec votre santé -----Message d'origine----- De : Roland Huss via RT [mailto:bug-jmx4perl@rt.cpan.org] Envoyé : mercredi 10 décembre 2014 14:41 À : WINGEL Mathieu Objet : [rt.cpan.org #100828] jmx4perl : issue on check_jmx4perl <URL: https://rt.cpan.org/Ticket/Display.html?id=100828 > Initially you said, that you need raise a critical when the value is different from 0. So IMO the output of your example is ok, since the value is 0. If you want to check for 0 being not ok, then you should try ~:0 (assuming that tge status is always positive). Am Mi 10. Dez 2014, 08:35:44, Mathieu.WINGEL@sihm.fr schrieb: Show quoted text