New host/service properties for return_code modulation

[nap]

There are some proposal of new properties for hosts/services:
*critical_is_warning (host, service, implicit inheritance from host to service)
*hot_period (host, service, implicit inheritance from host to service)
and:
*inverse_ok_critical (service only).

Theses properties are used for no production hosts.

== Qualification and developement hosts ==
There something I use to do : the Critical state is for Production
only. When someone see the Nagios web site, a red mean : "to do now".
Orange is "must be done". But a Red in a qualification host can be
less important than a warning in a production server.

That why all my checks are double :
normal command :
$USER1$/check_blabla -h $HOSTADRESS$

qualification command:
$USER1$/nocritical.sh "$USER1$/check_blabla -h $HOSTADRESS$"

nocritical.sh is a dumb script that launch $1 and if return_code == 2
-> return_code =1.

But It need 2 times checks and 2 times services too. I think we can
nearly divide by 2 the number of services with a new host/service
property : critical_is_warning. For the host, the only interest is to
be inherited by the service (an host DOWN is always important, no 2->
1 here). And in a qualification host, nearly all services are in low
priority (max = Warning), but some can be still Critical (like
security services). So this property need to be add to the host for
service implicit inheritance (default = 0) and to service (default =0
too) to be set at 1 for trully important services.

The hot_period can be add in host and service too (same for implicit
inheritance). the idea is to "tag" low priority host with
critical_is_warning. But some hosts are production just in some
periods (like at the end of the month for financial servers). So you
put hot_period in host (or service) and in this period critical is
still critical. So In all the other times, this low level host is a
low level host. If not specified, there is no hot_period (so always
low level).

This 2 properties can divided by 2 the number of services and commands
for thom who have qualification and productions hosts and do not like
Critical in Qualification hosts.

Do you think it can be usefull?


== Inverse_ok_critical ==
Far less usefull, it just do the negate job but without making a new
check_command (but still 2 services). It's easier to explain to
someone that a passive service must be tag inverse_ok_critical than to
use negate.



Jean

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev