Why don't you just do a nontent check on a page that wont change much? It beats the hell out off writing one?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jaime Ventura Sent: 08 October 2007 11:41 To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] using web content to determine the nagios status Hello, Im trying to monitor a webserver (and its services) without installing a client on it. For that I was hopping to use a created php page which tests several services(mysql, ...) and prints a status message. Is there any way to take the status message presented by the php page (OK, WARNING, ERROR,..) and map it to nagios status? I tried check_http -H webserver -u /status.htm -s "STATUS OK", but this way I can only get a status ok or error on nagios status. Is there any other way to do it, besides developing a specific plug-in? Thanks jaime ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list Nagios-users@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 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list Nagios-users@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
