<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> 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. Links are not followed.

The sensor can show the following:

  • Loading time of the full web page

icon-i-round-redBe careful with this sensor because it can generate a considerable amount of internet traffic if you use it with a short scanning interval.

HTTP Full Web Page Sensor

HTTP Full Web Page Sensor

Sensor in Other Languages

Dutch: HTTP Volledige Webpagina, French: HTTP (page Web complète), German: HTTP (Komplette Webseite), Japanese: HTTP 完全 Web ページ監視, Portuguese: HTTP Página Completa, Russian: HTTP: Полное время загрузки веб-страницы, Simplified Chinese: HTTP 完整网页, Spanish: HTTP Página Web Completa

Remarks

icon-prtg-on-demandYou cannot add this sensor to the hosted probe of a PRTG hosted by Paessler instance. If you want to use this sensor, add it to a remote probe device.

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the setting fields that are required for creating the sensor. Therefore, you do not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.

Sensor Settings

Click the Settings tab of a sensor to change its settings.

icon-i-round-blueUsually, a sensor connects to the IP Address or DNS Name of the parent device on which you created the sensor. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings. See below for details on available settings.

Basic Sensor Settings

Sensor Name

Enter a meaningful 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

Shows tags that this sensor inherits from its parent device, group, and probe. This setting is shown for your information only and cannot be changed here.

Tags

Enter one or more tags, separated by spaces or commas. You can use tags to group sensors and use tag–filtered views later on. Tags are not case sensitive. We recommend that you use the default value.

There are default tags that are automatically predefined in a sensor's settings when you add a sensor. See section Default Tags below.

You can add additional tags to the sensor if you like. Other tags are automatically inherited from objects further up in the device tree. These are visible above as Parent Tags.

icon-i-round-blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

Priority

Select a priority for the sensor. This setting determines where the sensor is placed in sensor lists. A sensor with a top priority is at the top of a list. Choose from one star (low priority) to five stars (top priority).

Default Tags

httpfullsensor

Full web Page Download Settings

Timeout (Sec.)

Enter a timeout in seconds for the request. If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message. Enter an integer value. The maximum value is 900 seconds (15 minutes).

URL

Enter the address of the web page that the sensor loads. It has to be URL encoded. If you enter an absolute URL, this address is independent of the IP Address/DNS Name setting of the parent device.

PRTG uses a smart URL replacement that lets you use the parent device's IP Address/DNS Name setting as part of the URL. For more information, see section Smart URL Replacement.

Browser Engine

Define which browser engine the sensor uses to load the web page:

  • Chromium (recommended): Use the WebKit engine that is delivered with PRTG to measure the loading time. With each scanning interval, PRTG loads the URL in an instance of Chromium and measures the time it takes to fully load the page. This is the recommended setting.
    icon-i-round-blueChromium does not support TLS 1.2-only connections. In this case, we recommend that you use the PhantomJS engine or Internet Explorer instead.
  • PhantomJS (Headless Webkit): Use the PhantomJS engine. This engine can have a high impact on the probe system's CPU and memory load but additional options for result handling are available (see below).
  • Internet Explorer: With each scanning interval, the URL is loaded in the background in an instance of Internet Explorer. PRTG uses the Internet Explorer of the probe system.
    icon-i-round-redFor full functionality, we strongly recommend that you install Internet Explorer 11 or higher on the probe system.

icon-i-round-blueAll browser engines use the proxy settings from the Windows user account that the probe runs on (this is usually the Windows local "system" user account, if not manually changed). To use a proxy, adjust the settings accordingly on the probe system (on all cluster nodes, if in a cluster). For more information, see the Knowledge Base: How can I access proxy settings for the HTTP Full Web Page Sensor?

Security Context

Define the Windows user account that the sensor uses to run the browser engine:

  • Use security context of probe service (default): Run the browser engine under the same Windows user account that the probe runs under. By default, this is the local Windows "system" user account (if not manually changed).
  • Use Windows credentials of parent device: Use the Windows user account defined in the settings of the parent device. Open the sensor's parent device settings to change the Windows credentials.
    icon-i-round-blueWe recommended that you use this setting when using the Chromium browser engine.

Result Handling

This setting is only visible if you select the PhantomJS engine above. Specify how the browser engine handles the result:

  • Discard HTML result (recommended): Do not store the requested web page.
  • Render and store a screenshot of most recent sensor result as JPG: Render and store the last result of the web page to the \Logs\sensors subfolder of the PRTG data directory on the probe system (master node, if in a cluster). This is for debugging purposes. The file is overwritten with each scanning interval. It is named using the pattern Fullpage of Sensor (ID).jpg.
  • Render and store screenshots of all sensor results as JPGs (requires lots of disk space): Render and store one new screenshot of the web page with each sensor scan, and store the screenshots in the \Screenshots (Fullpage Sensor) subfolder of the PRTG data directory on the probe system. You can use this option to create a visual history of the web page.
    icon-i-round-redDepending on the monitored website and the scanning interval of the sensor, this option can create a very high amount of data. Use this option with care and make sure you set appropriate data purging limits in the System Administration—Core & Probes settings.

icon-square-cyanIf necessary, you can change the window size of the rendered screenshots. For details, see the Knowledge Base: How can I change the size of PhantomJS full web page screenshots?

icon-i-round-blueDepending on the result handling method you choose, the sensor not only stores files in the screenshot directory but also in an extra cache directory. If the disk on the probe system runs full, check this path (you might have to appropriately set folder options to see this directory):

C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5

Authentication

This field is only visible if you enable PhantomJS (Headless Webkit) above. Define if the monitored web page needs authentication for access:

  • No authentication needed: Access to the web page is granted without authentication.
  • Web page needs authentication: PRTG automatically tries to use HTTP basic authentication (BA) or Windows NT LAN Manager (NTLM) to access the web page with authentication. Enter the credentials below.
    icon-i-round-blueBasic access authentication forwards the credentials in plain text.

User

This field is only visible if you enable PhantomJS (Headless Webkit) above. Enter the username for the web page.

Password

This field is only visible if you enable PhantomJS (Headless Webkit) above. Enter the password for the web page.

Sensor Display

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.

icon-i-round-blueYou can set a different primary channel later by clicking the pin symbol of a channel on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    icon-i-round-blueThis option cannot be used in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This field is only visible if you enable Stack channels on top of each other as Graph Type. 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.

Inherited Settings

By default, all of the following settings are inherited from objects that are higher in the hierarchy and should be changed there if necessary. Often, best practice is to change them centrally in the Root group's settings. For more information, see section Inheritance of Settings. To change a setting for this object only, disable inheritance by clicking the button next to inherit from under the corresponding setting name. You then see the options described below.

Scanning Interval

Click inherited_settings_button to interrupt the inheritance. See section Inheritance of Settings for more information.

Scanning Interval

Select a scanning interval (seconds, minutes, or hours). The scanning interval determines the amount of time that the sensor waits between two scans. You can change the available intervals in the system administration on PRTG on premises installations.

If a Sensor Query Fails

Define the number of scanning intervals that the sensor has time to reach and check a device again in case a sensor query fails. Depending on the option that you select, the sensor can try to reach and check a device again several times before the sensor shows a Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows a Warning status. Choose from:

  • Set sensor to down immediately: Set the sensor to a Down status immediately after the first failed request.
  • Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to a Warning status after the first failed request. If the following request also fails, the sensor shows an error.
  • Set sensor to warning for 2 intervals, then set to down: Set the sensor to a Down status only after three consecutively failed requests.
  • Set sensor to warning for 3 intervals, then set to down: Set the sensor to a Down status only after four consecutively failed requests.
  • Set sensor to warning for 4 intervals, then set to down: Set the sensor to a Down status only after five consecutively failed requests.
  • Set sensor to warning for 5 intervals, then set to down: Set the sensor to a Down status only after six consecutively failed requests.

icon-i-round-blueSensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show a Down status. It is not possible to immediately set a WMI sensor to a Down status, so the first option does not apply to these sensors. All other options can apply.

icon-i-round-blueIf you define error limits for a sensor's channels, the sensor immediately shows a Down status. No "wait" option applies.

icon-i-round-blueIf a channel uses lookup values, the sensor immediately shows a Down status. No "wait" options apply.

Schedules, Dependencies, and Maintenance Window

icon-i-round-blueYou 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 settings here. They are active at the same time as the parent objects' settings.

Schedule

Select a schedule from the list. Schedules can be used to monitor for a certain time span (days or hours) every week.

icon-square-cyanYou can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Account Settings—Schedules.

icon-i-round-blueSchedules are generally inherited. New schedules are added to existing schedules, so all schedules are active at the same time.

Maintenance Window

Specify if you want to set up a one-time maintenance window. During a maintenance window, the current object and all child objects are not monitored. They are in a Paused status instead. Choose between:

  • Not set (monitor continuously): No maintenance window is set and monitoring is always active.
  • Set up a one-time maintenance window: Pause monitoring within a maintenance window. You can define a time span for a monitoring pause below and change it even for a currently running maintenance window.

icon-i-round-blueTo terminate a current maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.

Maintenance Begins

This field is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the maintenance window.

Maintenance Ends

This field is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the maintenance window.

Dependency Type

Define a dependency type. You can use dependencies to pause monitoring for an object depending on the status of another object. You can choose from:

  • Use parent: Use the dependency type of the parent object.
  • Select a sensor: Use the dependency type of the parent object. Additionally, pause the current object if another specific sensor is in a Down status or in a Paused status caused by another dependency.
  • Master sensor for parent: Make this sensor the master object for its parent device. The sensor influences the behavior of its parent device: If the sensor is in a Down status, the device is paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor is paused if the parent group is paused by another dependency.

icon-i-round-blueTo test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects are paused. You can check all dependencies under Devices | Dependencies in the main menu bar.

Dependency

This field is only visible if you enable Select a sensor above. Click the Search button and use the object selector to select a sensor on which the current object will depend.

Dependency Delay (Sec.)

This field is only visible if you enable Select a sensor above. Define a time span in seconds for dependency delay.

After the master sensor for this dependency comes back to an Up status, monitoring of the dependent objects is additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Enter an integer value.

icon-i-round-redThis setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent device settings or in its parent group settings.

Access Rights

Click inherited_settings_button to interrupt the inheritance. See section Inheritance of Settings for more information.

User Group Access

Define the user groups that have access to the selected object. A table with user groups and types of access rights is shown. It contains all user groups from your setup. For each user group, you can choose from the following access rights:

  • Inherited: Use the access rights settings of the parent object.
  • None: Users in this group cannot see or edit the object. The object neither shows up in lists nor in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree but it cannot be accessed.
  • Read: Users in this group can see the object and review its monitoring results.
  • Write: Users in this group can see the object, review its monitoring results, and edit its settings. They cannot edit access rights settings.
  • Full: Users in this group can see the object, review its monitoring results, edit its settings, and edit access rights settings.

You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option.

icon-square-cyanFor more details on access rights, see section User Access Rights.

Smart URL Replacement

Instead of entering a complete address in the URL field of an HTTP sensor, you can just 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 or 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, smart URL replacement makes it easy 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/

icon-i-round-redSmart URL replacement does not work for sensors that run on the probe device.

More

icon-square-bluePRTG MANUAL

 

icon-square-blueKNOWLEDGE BASE

Which HTTP status code leads to which HTTP sensor status?

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?

What is the difference between "HTTP" and "HTTP Full Web Page" Web Server sensors?

Why is my HTTP Full Web Page Sensor generating so many temporary files?

How can I access proxy settings for the HTTP Full Web Page Sensor?

My HTTP sensors don't work. What can I do?

Edit Channels

To change display settings, spike filtering, and limits, switch to the sensor's Overview tab and click the gear icon of a specific channel. For detailed information, see section Sensor Channel Settings.

Notification Triggers

Click the Notification Triggers tab to change notification triggers. For detailed information, see section Sensor Notification Triggers Settings.

Others

For more general information about settings, see section Object Settings.

Sensor Settings Overview

For information about sensor settings, see the following sections:

Keywords: