I understand this part, but for example right now the service description for each host is CheckString. That way I can group all of them into a service group based on that description so we can pull availability reports for the host and the only service being monitored. If I wanted to do it your way, wouldn't I have to use the service description of each check in the servicegroups config file?
On Nov 12, 2007 5:13 PM, Marc Powell <[EMAIL PROTECTED]> wrote: > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:nagios-users- > > [EMAIL PROTECTED] On Behalf Of Jerad Riggin > > Sent: Monday, November 12, 2007 4:52 PM > > To: [email protected] > > Subject: [Nagios-users] Host monitoring > > > > So what would be the best way to monitor in this situation? > > > > I have Host A, hosting two websites. > > > > Currently I have both websites configured as separate hosts, so in > > nagios it shows up as ServerA - site.com, and another host ServerA - > > siteb.com > > > > This doesn't seem efficient since I am pinging both sites, but it's > > the same host. Ideally I would want to just ping the host, and check > > strings on each site under that host. Any recommendations? > > Unless I'm missing something obvious, this seems pretty straightforward. > host{} definition for the web server machine, service{} definitions for > each vhost using check_http to check them. You can craft a command{} > definition to pass the variable parameters like vhost name, uri and > search string like so -- > > define command { > command_name check_http_url > command_line $USER1$/check_http -I $HOSTADDRESS$ > -H $ARG1$ -u $ARG2$ -wt 20 -ct 30 -to 35 -s $ARG3$ > } > > To check to vhosts -- > > define service { > use generic-service > host_name my_webserver > service_description HTTP VHOST site1 > check_command > check_http_url!www.site1.com!/mypage!/html > } > > define service { > use generic-service > host_name my_webserver > service_description HTTP VHOST site2 > check_command > check_http_url!www.site2.com!/someotherpage!/html > } > > -- > Marc > > ------------------------------------------------------------------------- > 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 > [email protected] > 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 [email protected] 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
