[Nagiosplug-devel] check_load behaves inconsistent | use without setting thresholds
Thomas Guyot-Sionnest
dermoth at aei.ca
Mon May 19 17:35:03 CEST 2008
-----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?
Oh one more thing I wanted to add,and I totally forgot... Personally I
prefer checking the load trough SNMP as NRPE often timeout under high
load... That method is a bit more reliable. Only caveat is that you have
to take it as an integer which mean a load of 1.57 will be shown as "157".
Here's an example check command:
> $USER1$/check_snmp -H $HOSTADDRESS$ -o .1.3.6.1.4.1.2021.10.1.5.1,.1.3.6.1.4.1.2021.10.1.5.2,.1.3.6.1.4.1.2021.10.1.5.3 -w 800,600,400 -c 1600,1200,800 -C $USERn$ -l load -m UCD-SNMP-MIB
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIMZ4m6dZ+Kt5BchYRAq2aAKDV4j3tTUckhcs7c24Aanc+jzG1BQCgzYQ2
GROc7tC4bHs/ByRLHxoFidQ=
=GpL3
-----END PGP SIGNATURE-----
More information about the Devel
mailing list