Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

How do I monitor a website on an individual node? When I set up the HTTP monitor, it tests the external website availablity. I need it to test if the site works on the individual node.

When I set up the HTTP monitor, it tests the external website availablity. I need it to test if the site works on the individual node.

Whenever I use the HTTP monitor or Web Link component, it only verifies the URL through DNS, not on the specific node I've attached the component.

If the website is hosted on 3 different servers, I want to know when one of those servers is not serving up the content.

Find more posts tagged with

Accepted answers

aLTeReGo

It sounds like you have three web servers in a load balanced cluster. If that's the case, you should create three separate HTTP User Experience Monitors, each using the IP address of the server it's assigned to in the "URL" field. Populate the "Host Header" with the FQDN you would normally put in your browsers URL field. Then assign these components to each respective web server you wish to monitor.

HTTP Monitor.png

All comments

aLTeReGo

HTTP Monitor.png

terryhallal

Thank you for your quick response.

I've added the HTTP Monitor, and modified the HostHeader, but I'm finding that if the webserver is listening to all traffic, not specific host headers, SAM thinks it passes the test. For example, if I have a Dev server and it listens for everything on port 80, it seems that www.blah.com and www.google.com pass the SAM test. If I specify the host header in for the site, SAM would mark either of those Down since there is no Header being hosted as www.blah.com or www.google.com.

aLTeReGo

If the server is simply bound to port 80 and not using host headers, then there's no need to specify anything in the host header field. Simply using the IP address of the actual server in the URL field instead of the FQDN of the cluster VIP should be sufficient.

terryhallal

Both of your answers work. Thank you aLTeReGo for the much needed assistance!