how to create a command that submits a passive service check
Posted: Tue Nov 27, 2012 2:11 pm
Nagios XI 2011 r3.3
I am looking for information on how to set up an existing test to return its result as a passive check.
I have this URL
http://nagios.sourceforge.net/docs/3_0/ ... hecks.html
I have a test check_naf.py to measure disk usage and inode usage for Network Appliance (NetApp) filer exported volumes.
Frequently enough that test takes longer than 60 seconds to complete.
The service_check_timeout directive of 60 seconds then kills the test and raises a Critical event.
In the short term I would like to convert that test into a passive check.
I believe what I need to do is write a script that puts
[<timestamp>] PROCESS_SERVICE_CHECK_RESULT;<host_name>;<svc_description>;<return_code>;<plugin_output>
to the Nagios external command file.
Then, call that script via cron every INTERVAL.
INTERVAL would be something more than 60 seconds. Maybe 300 seconds.
The NetApps which time out are overloaded with traffic intermittently.
My long term goal is to have that test complete in less than 60 seconds by
tuning the NetApps. The NetApp tuning is managed by a separate team at my employer.
Any advice, suggestions or pointers would be appreciated.
Thank you,
David Sloboda
I am looking for information on how to set up an existing test to return its result as a passive check.
I have this URL
http://nagios.sourceforge.net/docs/3_0/ ... hecks.html
I have a test check_naf.py to measure disk usage and inode usage for Network Appliance (NetApp) filer exported volumes.
Frequently enough that test takes longer than 60 seconds to complete.
The service_check_timeout directive of 60 seconds then kills the test and raises a Critical event.
In the short term I would like to convert that test into a passive check.
I believe what I need to do is write a script that puts
[<timestamp>] PROCESS_SERVICE_CHECK_RESULT;<host_name>;<svc_description>;<return_code>;<plugin_output>
to the Nagios external command file.
Then, call that script via cron every INTERVAL.
INTERVAL would be something more than 60 seconds. Maybe 300 seconds.
The NetApps which time out are overloaded with traffic intermittently.
My long term goal is to have that test complete in less than 60 seconds by
tuning the NetApps. The NetApp tuning is managed by a separate team at my employer.
Any advice, suggestions or pointers would be appreciated.
Thank you,
David Sloboda