NSClient++ Help (#1) - NSClient 0.3.8 only returns date if at least one upper or lower bound is set - is that by design ? (#608) - Message List

NSClient 0.3.8 only returns date if at least one upper or lower bound is set - is that by design ?

Sorry for double-posting this, my first attempt (606) has no subject line and didn't turn up on the forum.

Is the difference below and intentional change between 0.3.7 and 0.3.8 ? Note the last line - in 0.3.8 the part following | is missing.

0.3.7 ====

checkCounter "\Processor(_Total)\% Idle Time" d NSClient++.cpp(1073) Injecting: checkCounter: \Processor(_Total)\% Idle Time perf data: 1 d \checkHelpers.hpp(758) Missing bounds for maxmin-bounds check: \Processor(_Total)\% Idle Time d NSClient++.cpp(1109) Injected Result: OK 'OK all counters within bounds.' d NSClient++.cpp(1110) Injected Performance Result: \Processor(_Total)\% Idle Time'=96.051948;0;0; ' OK:OK all counters within bounds.|'\Processor(_Total)\% Idle Time'=96.051948;0;0;

0.3.8 ====

checkCounter "\Processor(_Total)\% Idle Time" d NSClient++.cpp(1106) Injecting: checkCounter: \Processor(_Total)\% Idle Time perf data: 1 d NSClient++.cpp(1142) Injected Result: OK 'OK all counters within bounds.' d NSClient++.cpp(1143) Injected Performance Result: OK:OK all counters within bounds.

However, give it a lower bound (even zero) and both versions behave the same.

0.3.7

checkCounter "\Processor(_Total)\% Idle Time" MinCrit=0 d NSClient++.cpp(1073) Injecting: checkCounter: \Processor(_Total)\% Idle Time, MinCrit=0 perf data: 1 d NSClient++.cpp(1109) Injected Result: OK 'OK all counters within bounds.' d NSClient++.cpp(1110) Injected Performance Result: \Processor(_Total)\% Idle Time'=98.394679;0;0; ' OK:OK all counters within bounds.|'\Processor(_Total)\% Idle Time'=98.394679;0;0;

0.3.8

checkCounter "\Processor(_Total)\% Idle Time" MinCrit=0 d NSClient++.cpp(1106) Injecting: checkCounter: \Processor(_Total)\% Idle Time, MinCrit=0 perf data: 1 d NSClient++.cpp(1142) Injected Result: OK 'OK all counters within bounds.' d NSClient++.cpp(1143) Injected Performance Result: \Processor(_Total)\% Idle Time'=97.613768;0;0; ' OK:OK all counters within bounds.|'\Processor(_Total)\% Idle Time'=97.613768;0;0;
  • Message #1889

    The short answer is: Yes this is by design.

    I reworked some of the performance data counter code and the previous result was a "bug" which I fixed...

    Is there a reason to not have bounds? Without them the performance data you get sort of does not make sense right?

    Michael Medin

    • Message #1946

      It makes sense to us. We use NSClient for routine collection of performance data for capacity planning/trend analysis purposes as well as alerting against thresholds.

      No problem with the change - I just pass MinCrit=-1 in situations where no thresholds are set.

      • Message #1948

        I vaugley recall fixing this in the nightly builds (since)...

        Michael Medin

Subscriptions