What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

PRTG, monitoring a LOCAL IIS Site (HTTP sesnsor)




We have several IIS servers in a "cluster" hosting one single site/webshop (a load balancer is setup in front of the cluster). I need a way to monitor each IIS server site via the HTTP or HTTP advance sensor by using an URL. I tried editing the host file and using the same host name in the IIS, and then added the Sensor on one of the IIS server (the Probe is installed on a differant server). However, I'm getting a Socket Error # 11004 (probably a DNS error).

How can I monitor http://xSITExNAMEx.local with the http / http advance sensor?

http http-advanced http-sensor iis

Created on Feb 26, 2015 2:50:40 PM

3 Replies



Dear Annfinn

Please detail in which sense you like to monitor the address. Do you want to know which physical server is used when you access the page, or just if the IIS is up?

If you try to monitor if you can reach content hosted by the IIS, please test of you can access that URL from the computer on which you run PRTG, using a web browser.

Created on Mar 2, 2015 3:50:34 PM by  Arne Seifert [Paessler Support]

Last change on Mar 2, 2015 4:11:06 PM by  Arne Seifert [Paessler Support]




I want to know which virtual/physical server is used when accessing the page. I managed to monitor the site using a dummy entry in the DNS mirroring the real site.

The DNS look something like this

iis1.site.local --> pointing to server1 iis2.site.local --> pointing to server2 iis3.site.local --> pointing to server3

Is there any other way to do this in PRTG?

Created on Mar 3, 2015 7:36:17 AM



Hi Annfinn,

Aside from using the direct URL, is there a way to tell the loadbalancer "I want to be on server #2" with a special flag in the HTTP header? Otherwise, you're solution would be okay, if you're fine with it :)

Created on Mar 3, 2015 12:17:06 PM by  Stephan Linke [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.