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

Bug with HTTP Advanced sensor

Votes:

0

When we define a device as a web server with a specific IP address and then created a HTTP Advanced sensor to monitor the loading for a particular web page, we are expecting the sensor will connect to the specified IP address and post the URL defined in the setting. But what we are seeing is that the sensor will resolve the host name in the URL using DNS and then connect to the IP address returned, overide what we have put into the device setting.

This make the sensor useless for us as we cannot nominate which server and/or network path to measure the loading time.

bug http https

Created on Nov 9, 2012 3:56:09 AM



1 Reply

Votes:

0

Hi,
as stated in the documentation the HTTP advanced sensor is not dependent on the DNS name/IP address of the parent device. Which means if not explicitly referring to the DNS/IP of the parent device this will be a "normal" HTTP Request including DNS resolving.
To use the IP/DNS name of the parent device, you might have a look at the URL Smart Replacement functionality.
Best regards

Created on Nov 9, 2012 12:59:56 PM by Konstantin Wolff [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.