Overview
Once your Nagios service is receiving Passive NSCA checks, they will not appear anywhere in Nagios until you define host and service definitions.
The following definitions compliment the guides for installing NSClient++ to send check results to Nagios via NSCA.
The following Nagios Definitions will result in:
-
A Passive Host object for the server DC02
-
Passive Service objects for the server DC02 for the services:
-
CPU Load
-
Drive Usage
-
Memory Usage
-
Operating System Version
-
Which will result in something like this in Nagios:
Command
define command {
command_name check_dummy
command_line $USER1$/check_dummy $ARG1$
}
Templates
Host
define host {
use generic-host
name passive_host
active_checks_enabled 0
passive_checks_enabled 1
flap_detection_enabled 0
register 0
check_period 24x7
max_check_attempts 1
check_interval 5
retry_interval 1
check_freshness 0
contact_groups admins
check_command check_dummy!0
notification_interval 60
notification_period 24x7
notification_options d,u,r
}
Service
define service {
use generic-service
name passive_service
active_checks_enabled 0
passive_checks_enabled 1
flap_detection_enabled 0
register 0
check_period 24x7
max_check_attempts 1
check_interval 5
retry_interval 1
check_freshness 0
contact_groups admins
check_command check_dummy!0
notification_interval 60
notification_period 24x7
notification_options w,u,c,r
}
Host Definition
define host {
use passive_host
host_name DC02
}
Service Definitions
CPU Load
define service {
use passive_service
service_description CPU Load
host_name DC02
}
Drive Usage
define service {
use passive_service
service_description Drive Usage
host_name DC02
}
Memory Usage
define service {
use passive_service
service_description Memory Usage
host_name DC02
}
Operating System Version
define service {
use passive_service
service_description Operating System Version
host_name DC02
}
Final Thoughts
For any support related questions please visit the Nagios Support Forums at: