[Nagiosplug-devel] perf data gudelines

[Karl DeBisschop]

On Thu, 2003-09-11 at 06:32, Voon, Ton wrote:
> > -----Original Message-----
> > From: Karl DeBisschop [mailto:karl at debisschop.net] 
> > Sent: Thursday, September 11, 2003 9:11 AM
> > To: NagiosPlug Devel
> > Subject: [Nagiosplug-devel] perf data gudelines
> > 
> > 
> > in the perfdata, we have a format like:
> > 
> > 'label'=value[UOM];[warn];[crit];[min];[max]
> > 
> > There is a parameter in check_http to show an warning status 
> > if the page
> > is less than a given size.
> > 
> > I assume that normally, if [crit] was less than [warn], it would be
> > clear to whatever handled the data that the critical raneg 
> > ran from 0 to
> > [crit].
> 
> I think this is a range issue, rather than a perfdata issue. Maybe we need a
> clarification on ranges in the dev guidelines.

So the general case for [warn] and [crit] becomes [num]:[num] - makes
parsing a little harder, but I guess it's logical.

> I think we should take the general case for ranges from check_procs:
> 1) alert if metric outside start:end where start < end, start (and ":") not
> required if 0
> 2) if end not specified, assume infinity
> 3) if start > end, then alert if inside this range
> 
> (A few thoughts: I don't like the specification for (3) - I'd much prefer
> some identifier like "*start:end" to mean "inclusive alert"; also how do you
> specify  negative infinity?)

When I came up with the rules above, without realizing it, I assumed
that all number were non-negative.

Do you have a proposed fix for this that we should try and get in before
we relase the 1.4.x alpha with its perf data fields?

> So the perf data ranges will take the same format as the warn and crit
> ranges with the same meaning.
> 
> Shall I document this (with the proviso that not all plugins use this range
> definition yet)?

OK with me

> > In this case, there's no [crit] (I guess I could say that [crit] is 0.
> > Or could modify check_http so a critical saze can be given also)
> 
> I would put crit as undefined to mean there is no critical level.

since 0 is the lowest limit for page size, I think in this case it sort
of works. In the general case you are right.

> > But I'm wondering how we should show something where 2 through 10 was
> > OK, but less than 2 or greater than 10 was a warning state (process
> > counting often has that sort of threshold structure).
> 
> With the ranges specified, I think a clever Nagiosplugins->RRD tool could
> draw the appropriate alert areas in yellow and red with the line of data in
> black.

The definition of 'clever tool' keeps expanding here. Oh well, it won't
be written in any case until there are rules on the inputs.

> Ton
> 
> 
> This private and confidential e-mail has been sent to you by Egg.
> The Egg group of companies includes Egg Banking plc
> (registered no. 2999842), Egg Financial Products Ltd (registered
> no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
> carries out investment business on behalf of Egg and is regulated
> by the Financial Services Authority.  
> Registered in England and Wales. Registered offices: 1 Waterhouse Square,
> 138-142 Holborn, London EC1N 2NA.
> If you are not the intended recipient of this e-mail and have
> received it in error, please notify the sender by replying with
> 'received in error' as the subject and then delete it from your
> mailbox.