passive service freshness with nagios restart

[Michelle Craft]

> Rather than another configuration parameter, can I propose this?
>
>    * If check_freshness_interval is defined, Nagios will use that
> value and only check against the last_check_time. No "funny" stuff is
> calculated
>    * If check_freshness_interval is not defined, then Nagios does a
> calculation on the best value - currently it does things like using
> check_interval, add latency time, lowers it if in a soft state. I'll
> rework my change so that it raises the time if startup time is more
> recent than last_check_time
>
> So if you have a service you definitely want marked as stale after a
> predefined period, use an absolute value (which logically makes sense
> - if you want freshness, state the exact timeout period). Otherwise,
> Nagios will try to calculate one which is optimised to a distributed
> environment (which is the other major use case).
>
> If there's a consensus to this, I'd be happy to make the change,
> update the docs and post the patch here for approval. I'll even try
> and add some tests so that this type of thing is flagged earlier.

That looks perfect to me.  Makes a lot of sense, too.



--
Michelle


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/