PRTG Manual: HTTP Full Web Page Sensor
The HTTP Full Web Page sensor monitors the full download time of a web page including assets such as images. In the background, it opens the web page in a browser instance to perform the measurement. It does not follow links.
Be careful with this sensor because it can generate a considerable amount of internet traffic if you use it with a short scanning interval.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: HTTP Volledige Webpagina
- French: Page web complète (HTTP)
- German: HTTP (Komplette Webseite)
- Japanese: HTTP 完全ウェブページ監視
- Portuguese: Página completa HTTP
- Russian: HTTP: Полное время загрузки веб-страницы
- Simplified Chinese: HTTP 完整网页
- Spanish: Página web completa HTTP
- This sensor has a very high performance impact. We recommend that you use no more than 50 of this sensor on each probe.
- This sensor does not support Secure Remote Password (SRP) ciphers.
- This sensor supports smart URL replacement.
- This sensor supports IPv6.
- Knowledge Base: What to do when I see a CreateUniqueTempDir() error message for my HTTP Full Web Page sensor?
- Knowledge Base: HTTP Full Web Page sensor is unable to navigate. What can I do?
- Knowledge Base: How can I change the size of PhantomJS full web page screenshots?
- Knowledge Base: Why is my HTTP Full Web Page sensor generating so many temporary files?
- Knowledge Base: Which HTTP status code leads to which HTTP sensor status?
You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Full Web Page Download Settings
Setting |
Description |
---|---|
Timeout (Sec.) |
Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes).
|
URL |
Enter the address of the web page that the sensor loads. If you enter an absolute URL, the sensor uses this address independently of the IP Address/DNS Name setting of the parent device.
|
Browser Engine |
Define which browser engine this sensor uses to load the web page:
|
Security Context |
Define the Windows user account that this sensor uses to run the browser engine:
|
This setting is only visible if you select PhantomJS (Headless WebKit) above. Specify how the browser engine handles the web page result:
|
|
Authentication |
This setting is only visible if you select PhantomJS (Headless WebKit) above. Define if the monitored web page needs authentication for access:
|
User Name |
This setting is only visible if you select PhantomJS (Headless WebKit) above. Enter the user name for the web page. |
Password |
This setting is only visible if you select PhantomJS (Headless WebKit) above. Enter the password for the web page. |
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Instead of entering a complete address in the URL field of an HTTP sensor, you can only enter the protocol followed by a colon and three forward slashes (this means that you can enter either http:/// or https:///, or even a simple forward slash / as the equivalent for http:///). PRTG automatically fills in the parent device's IP Address/DNS Name in front of the third forward slash.
Whether this results in a valid URL or not depends on the IP address or Domain Name System (DNS) name of the parent device. In combination with cloning devices, you can use smart URL replacement to create many similar devices.
For example, if you create a device with the DNS name www.example.com and you add an HTTP sensor to it, you can provide values in the following ways:
- If you enter https:/// in the URL field, PRTG automatically creates the URL https://www.example.com/
- If you enter /help in the URL field, PRTG automatically creates and monitor the URL http://www.example.com/help
- It is also possible to provide a port number in the URL field. It is taken over by the device's DNS name and is internally added, for example, http://:8080/
Smart URL replacement does not work for sensors that run on the probe device.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
Loading Time |
The loading time of the full web page
|
KNOWLEDGE BASE
What to do when I see a CreateUniqueTempDir() error message for my HTTP Full Web Page sensor?
HTTP Full Web Page sensor is unable to navigate. What can I do?
How can I change the size of PhantomJS full web page screenshots?
Why is my HTTP Full Web Page sensor generating so many temporary files?
Which HTTP status code leads to which HTTP sensor status?
What security features does PRTG include?
What is the difference between "HTTP" and "HTTP Full Web Page" web server sensors?
How can I access proxy settings for the HTTP Full Web Page sensor?
My HTTP sensors don't work. What can I do?