On 24 Aug 2009, at 19:02, James Whittington wrote:
I’m trying to understand in Opsview what default host check
intervals are.
We run a reverse ssh distributed Opsview setup and we saw something
that confused us a bit.
One of my co-workers was trying to test a notification on a host he
had set up.
We could get the service check to go critical and the host went
critical but the host stayed in a soft state and did not trigger a
host down alert.
I’m pretty sure the hosts are inheriting settings from the host-
global template but I was confused about the check interval being
set to 0.
Here is the template I think is being used
define host{
name host-global
event_handler_enabled 0 ; Host event handler
is enabled
flap_detection_enabled 1 ; Flap detection is
enabled
process_perf_data 1 ; Process
performance data
retain_status_information 1 ; Retain status
information across program restarts
retain_nonstatus_information 1 ; Retain non-status
information across program restarts
max_check_attempts 2
obsess_over_host 0
check_freshness 0
passive_checks_enabled 1
check_interval 0 ; For the moment,
set check_interval to 0 so hosts only checked on demand, like Nagios 2
contact_groups empty
register 0 ; DONT REGISTER THIS
DEFINITION IT'S JUST A TEMPLATE!
}
Does each soft state service check in a “Non-Okay” state generate a
host check attempt?
It pretty much would have to otherwise you would never see a host
down notification.
We set check_interval for hosts to 0, which means there are no regular
host checks. Host checks will be on-demand, ie when a service state
change occurs.
What state does the slave say the host is in? How many services are on
this host? Is this recreateable?
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
