warning - critical
Andrzej Wisniewski
awi at id.pl
Wed May 21 12:06:45 CEST 2003
> >My service is down and I take a notification (critical) about it.
> >5 minutes later critical state (red color) change to warning state
> >(yellow color). And I have not a notification about it :(.
> >Normally I take a notification about OK state when critical (red color)
> >change to OK (green color).
> Have you specify in "service.cfg" (about this service) that you have to
> be handle in warning case ?
Tx for an answer.
In my config we can see :
define service{
use generic-service
host_name server-lab
service_description service1
is_volatile 0
check_period 24x7
max_check_attempts 3
normal_check_interval 5
retry_check_interval 2
contact_groups linux-admins
notification_interval 30
notification_period 24x7
check_command check_nrpe!check_service
}
and :
define service{
name generic-service
active_checks_enabled 1
passive_checks_enabled 1
parallelize_check 1
obsess_over_service 1
check_freshness 0
notifications_enabled 1
event_handler_enabled 1
flap_detection_enabled 1
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
register
0 notification_options u,c,r
}
And I don't want that mail came to me with warning problem always. Only
when it is come back from critical state.
AndY
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list