[Nagiosplug-devel] New threshold syntax - changes

[Thomas Guyot-Sionnest]

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

Richard Edward Horner wrote:
> I don't have any real concerns with 1, 2 or 4.
> 
> I think 3 is an important clarification.
> 
> One thing that has bugged me with thresholds is that the spec is only
> useful if it's followed but most plugins don't follow it and just
> implement what's quick. I'll give the pertinent example.

Not all plugins use the thresholds library. If the --help output doesn't
say something like "--warning=THRESHOLD" with a comment in the notes
pointing to the developer guidelines section explaining ranges, it's
most likely not "real" thresholds. We have modified a few plugins to the
real thresholds library in the last years but now the goal would be
writing a new enhanced one and porting all plugins to it.


Any plugin using this specification will have to go trough the library
(it can't really be done otherwise, as it would require lot of code
which should be already written!). The libnagiosplug project will also
make this code usable easily by 3rd party plugins (and this will also be
implemented in the Nagios::Plugin Perl module, obvisously...

> I think if you're going to have a spec, it needs to be followed. If
> you have a spec and it's not followed, it's confusing and worse than a
> waste of time as it is probably costing ppl time.

I should've sent it with the previous email. The new spec is here:
http://nagiosplugins.org/rfc/new_threshold_syntax

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

iEYEARECAAYFAkrUut8ACgkQ6dZ+Kt5BchZFoQCdEZKxuAgUt3ZuWEZVwNpC+el/
CgIAnjQcPlJ+mivscD8fIYQBq1WonPwo
=nw67
-----END PGP SIGNATURE-----