Hi everyone,
at the moment I'm playing around with passive checks.
maybe I'm to stupid, but will I be on the right way?
I've set up a new Server group called "passive-servers' with only one
test server called "muninbsd"
this server will be monitored like a active server. I've only changed
the parameter "active_checks_enabled" to 0 and the parameter
"passive_checks_enabled" to 1. "check_freshness" is set to 1 and
"check_freshness" is 4800.
some services like check_load, check_disk, check_mysql will be done by
check_nrpe, started by the nagios main server.
Is this the right way to works with passive checks?
I've attached my config file "global.cfg" for my passive server.
From my side everythinks looks fine, but ...
Maybe someone can take a look on it, if it is as it should be ;-)
many many thanks
Richard
P.S.: sorry for my poor english ;-)
################################################################################
# HOST DEFINITIONS
################################################################################
# Generic host definition template
define host{
name passive-host ; The name of this host
template - referenced in other host definitions, used for template
recursion/resolution
notifications_enabled 1 ; Host notifications are enabled
event_handler_enabled 1 ; 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
register 0 ; DONT REGISTER THIS DEFINITION
- ITS NOT A REAL HOST, JUST A TEMPLATE!
}
# 'muninbsd.uclv.net' host definition
define host{
use passive-host ; Name of host template
to use
host_name muninbsd.uclv.net
alias muninbsd.uclv.net
address 10.10.41.6
check_command check-host-alive
max_check_attempts 3
notification_interval 0
notification_period 24x7
notification_options d,u,r
contact_groups nosms-admins
}
################################################################################
# HOST GROUP DEFINITIONS
################################################################################
# 'Passive-Server' host group definition
define hostgroup{
hostgroup_name Passive-Server
alias Passive-Server
members muninbsd.uclv.net
}
################################################################################
# SERVICE DEFINITIONS
################################################################################
# Generic service definition template
define service{
name passive-service ; The 'name' of this
service template, referenced in other service definitions
active_checks_enabled 0 ; Active service checks are
enabled
passive_checks_enabled 1 ; Passive service checks are
enabled/accepted
parallelize_check 1 ; Active service checks should
be parallelized (disabling this can lead to major performance problems)
obsess_over_service 1 ; We should obsess over this
service (if necessary)
check_freshness 1 ; Default is to NOT check
service 'freshness'
freshness_threshold 4800 ;
notifications_enabled 1 ; Service notifications are
enabled
event_handler_enabled 1 ; Service 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
register 0 ; DONT REGISTER THIS DEFINITION
- ITS NOT A REAL SERVICE, JUST A TEMPLATE!
}
# Service definition
define service{
use passive-service ; Name of
service template to use
service_description PING
hostgroup_name Passive-Server
is_volatile 1
check_period 24x7
max_check_attempts 3
normal_check_interval 3
retry_check_interval 1
contact_groups nosms-admins
notification_interval 0
notification_period 24x7
notification_options w,u,c,r
check_command check_ping!200.0,20%!800.0,60%
}
# Service definition
define service{
use passive-service ; Name of
service template to use
host_name muninbsd.uclv.net
service_description Free Space /
is_volatile 1
check_period 24x7
max_check_attempts 3
normal_check_interval 3
retry_check_interval 1
contact_groups nosms-admins
notification_interval 0
notification_period 24x7
notification_options w,u,c,r
check_command check_nrpe2!check_disk_root
}
# Service definition
define service{
use passive-service ; Name of
service template to use
host_name muninbsd.uclv.net
service_description LOAD
is_volatile 1
check_period 24x7
max_check_attempts 3
normal_check_interval 3
retry_check_interval 1
contact_groups nosms-admins
notification_interval 0
notification_period 24x7
notification_options w,u,c,r
check_command check_nrpe2!check_load
}
# Service definition
define service{
use passive-service ; Name of
service template to use
host_name muninbsd.uclv.net
service_description Zombi Processes
is_volatile 1
check_period 24x7
max_check_attempts 3
normal_check_interval 3
retry_check_interval 1
contact_groups nosms-admins
notification_interval 0
notification_period 24x7
notification_options w,u,c,r
check_command check_nrpe2!check_zombie_procs
}
# Service definition
define service{
use passive-service ; Name of
service template to use
host_name muninbsd.uclv.net
service_description MYSQL
is_volatile 1
check_period 24x7
max_check_attempts 3
normal_check_interval 3
retry_check_interval 1
contact_groups nosms-admins
notification_interval 0
notification_period 24x7
notification_options w,u,c,r
check_command check_nrpe2!check_mysql_procs
}
# EOF
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Nagios-users mailing list
[email protected]
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
