[Nagiosplug-devel] RFC: New threshold syntax

[Max]

On Mon, Mar 31, 2008 at 6:55 PM, Vonnahme, Nathan
<nathan.vonnahme at bannerhealth.com> wrote:
>  check_http https://foo.com
>  --time ok=0..5/s,warn=5..10/s             \
>  --size ok=3..5/kB                         \
>  --ssl-expiry ok=28..inf/d,warn=14..28/d
>
>
>  old:  check_procs -w 8096 -c 16182 -C httpd --metric VSZ
>  new:  check_procs -C httpd --vsize ok=0..8096,warn=8096..16182
>
>  old: check_procs -w 6:13 -c 4:18 -u mqm -a AKBLD
>  new: check_procs -u mqm -a AKBLD --count ok=6..13,warn=4..18
>   (I'm not sure whether that overlapping warn range would work)
>
>  old: check_procs -w 1:1 -c 1:1 -C tnslsnr
>  new: check_procs -C tnslsnr --count ok=1..1

I am sold on the readability of this :), very nice, huge improvement
over current syntax, the 'ok' range will be a huge win, would the
standard then also support the inclusive ... range operator as well as
suggested earlier or is it getting too 'chicken scratch-like' having
both .. and .... ?

Also, are we going to standardize on multiple metrics being or'd as
they currently are (which I think is the way intuitively think about
threshold tests of metrics) or will there be value in also providing a
switch to change from an 'or all'  to an 'and all' threshold check
mode?

check_tcp_states --finwait2 ok=0..50 --synreceived ok=0..100 --or-conditions

check_tcp_states --established ok=30...500 --timewait ok=0..200 --and-conditions

- Max