NSCA + NSClient

[Ryan C Ash]

The short answer is yes,  the service description you configure on the
client nsca message needs to match that of the service description on
your nagios server.   If you want to migrate to a passive check you need
to disable active checks and enable passive ones.  You can leave the
check command in place and incorporate freshness checks to force an
active check if the passive fail.  For me I don't want to do active if
passive fail.  I would rather cut a ticket "service stale".    The
nagios doc clearly shows how to configure passive service checks so give
it a read.  

 

So you need "my_cpu_check" to be a service description so nagios knows
what to match that incoming nsca message to.  

 

Ash

 

From: Mirza Dedic [mailto:mirde at oppy.com] 
Sent: Thursday, June 24, 2010 2:56 PM
To: 'Nagios-Users'
Subject: [Nagios-users] NSCA + NSClient

 

Hi,

 

I have NSCA configured on my Nagios host, and enabled the necessary
plugins on NSClient++ to support NSCA, configure XINETD appropriately
inside my NSClient config I have:

 

[NSCA Commands]

my_cpu_check=checkCPU warn=80 crit=90 time=20m time=10s time=4

my_mem_check=checkMem MaxWarn=80% MaxCrit=90% ShowAll type=page

 

This is just for testing, I also have in my nagios.cfg:

 

accept_passive_service_checks=1

accept_passive_host_checks=1

 

In my NSClient Log I can see:

 

2010-06-24 12:48:44: debug:modules\NSCAAgent\NSCAThread.cpp:205:
Executing (from NSCA): my_cpu_check

2010-06-24 12:48:44: debug:NSClient++.cpp:1106: Injecting: checkCPU:
warn=80, crit=90, time=20m, time=10s, time=4

2010-06-24 12:48:44: debug:NSClient++.cpp:1142: Injected Result: OK 'OK
CPU Load ok.'

2010-06-24 12:48:44: debug:NSClient++.cpp:1143: Injected Performance
Result: ''20m'=0%;80;90; '10s'=6%;80;90; '4'=0%;80;90; '

2010-06-24 12:48:44: debug:modules\NSCAAgent\NSCAThread.cpp:205:
Executing (from NSCA): my_mem_check

2010-06-24 12:48:44: debug:NSClient++.cpp:1106: Injecting: checkMem:
MaxWarn=80%, MaxCrit=90%, ShowAll, type=page

2010-06-24 12:48:44: debug:NSClient++.cpp:1142: Injected Result: OK 'OK:
page file: 8.82G'

2010-06-24 12:48:44: debug:NSClient++.cpp:1143: Injected Performance
Result: ''page file %'=45%;80;90; 'page file'=8.81G;15.6;17.59;0;19.5; '

 

What I want to know is, until now I have been using active checks, and
for some servers I want to use passive_checks as well, so that the
server updates Nagios.

 

If I have active checks defined within my Nagios installation such as:

 

define service{

        use                             generic-service

        host_name                       van-mail01

        service_description             D - Disk Space

        check_command
check_nt_disk!D!98!99

}

 

Can I modify this to also read from the passive_check, and what would my
[NSCA Commands] definition look like? Does the first part have to
reflect the service description? 

 

How does the information coming from the NSCA Client get mapped to my
configured checks?

 

Thank you.

The Oppenheimer Group ---- CONFIDENTIAL
 
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100624/49beb653/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
-------------- next part --------------
_______________________________________________
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