[Nagiosplug-devel] check_load behaves inconsistent | use without setting thresholds

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/05/08 08:20 AM, Christian Schneemann wrote:
> Hi,
> I want to use check_load only for performance data, no warning or critical 
> threshold should be set. Ok, that's not possible at the moment, because the 
> function process_arguments checks if argc < 2. This is also true if just 
> the -r option is set and that results in a critical return value. Shouldn't 
> this also be prohibited without any thresholds? 
> 
> I would prefere a option to switch the test for thresholds to off and return 
> a "OK" if set to use the functinality of the test for creating performance 
> data.
> Any comments on that?

That's something that will definitely change with the new threshold
syntax, but that's not around the corner yet (we barely finished the
specifications).

Meanwhile you can set very high threshold, and/or use negate to change
the status codes so that WARNING and CRITICAL return OK instead.

BTW in the upcoming release (and in current snapshots) negate can change
the status text as well so that in the interface you won't see a service
returning ok with a status text of "CRITICAL: blah blah blah...". See
the --help output of negate for more details.

Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIMZxh6dZ+Kt5BchYRAukOAJ4z8ADuvirDM84IPeKyjux/TFQ9SgCgsbuP
jZr8vfZoMMKOckRnaotb9tA=
=tKWi
-----END PGP SIGNATURE-----