Without knowing the details, wouldn't it be easy enough to use cron to run the commands, and use check_log to parse the local file created? Or, depending on the parsing logic you require, use the exit codes of a custom plugin script to shoot back to nagios. There is information on plugin development at
<a href="http://nagiosplug.sourceforge.net/developer-guidelines.html">http://nagiosplug.sourceforge.net/developer-guidelines.html</a> that pointed me in the right direction for custom stuff.<br><br>-Marc<br><br><div><span class="gmail_quote">
On 3/27/07, <b class="gmail_sendername">Robert Finney</b> <<a href="mailto:rfinney@co.jefferson.co.us">rfinney@co.jefferson.co.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
List,<br><br>I'm working with a developer to put together a plugin that when executed will login<br>to a host, run a series of commands, and write the output to a local file.<br><br>My question is how to set up Nagios to read the local file and update nagios appropriately.
<br><br>We are using Nagios 2.6, plugin version 1.4.5, OS is Linux Redhat 4.<br><br>Thanks in advance for your help.<br><br>Bob<br><br><br>-------------------------------------------------------------------------<br>Take Surveys. Earn Cash. Influence the Future of IT
<br>Join SourceForge.net's Techsay panel and you'll get the chance to share your<br>opinions on IT & business topics through brief surveys-and earn cash<br><a href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV</a><br>_______________________________________________<br>Nagiosplug-help mailing list<br><a href="mailto:Nagiosplug-help@lists.sourceforge.net">
Nagiosplug-help@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-help">https://lists.sourceforge.net/lists/listinfo/nagiosplug-help</a><br>::: Please include plugins version (-v) and OS when reporting any issue.
<br>::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br>