PRTG Manual: HTTP Content Sensor
The HTTP Content sensor monitors numeric values returned by an HTTP request.
In the returned HTML page, each value must be placed between brackets [ ]. See section Example.
This sensor implicitly supports SNI, an extension to the Transport Layer Security (TLS) protocol.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: HTTP (Inhoud)
- French: Contenu (HTTP)
- German: HTTP (Inhalt)
- Japanese: HTTP コンテンツ
- Portuguese: Conteúdo HTTP
- Russian: HTTP: Содержимое
- Simplified Chinese: HTTP 内容
- Spanish: Contenido HTTP
- This sensor does not officially support more than 50 channels.
- This sensor does not support Secure Remote Password (SRP) ciphers.
- This sensor supports smart URL replacement.
- This sensor supports IPv6.
- This sensor has a medium performance impact.
- Knowledge Base: Which HTTP status code leads to which HTTP sensor status?
Setting |
Description |
---|---|
Number of Channels |
Define how many values the .html file returns. The sensor handles each value in its own channel. Each value must be placed between brackets [ ]. Enter the number of bracket-value pairs that the URL returns. Enter an integer.
|
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 ( |
Setting |
Description |
---|---|
Timeout (Sec.) |
Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes).
|
Script URL |
Enter the URL that the sensor connects to. If you enter an absolute URL, the sensor uses this address independently of the IP Address/DNS Name setting of the parent device.
|
Value Type |
Define what kind of values the .html file returns:
|
Setting |
Description |
---|---|
If Content Changes |
Define what the sensor does if the content of the web page changes:
|
Result Handling |
Define what PRTG does with the sensor result:
|
Setting |
Description |
---|---|
Authentication |
Define if authentication is necessary on the web page:
|
User Name |
This setting is only visible if you select Web page needs authentication above. If the proxy requires authentication, enter the user name for the proxy login. Enter a string. |
Password |
This setting is only visible if you select Web page needs authentication above. Enter a password. |
Authentication Method |
This setting is only visible if you select Web page needs authentication above. Select the authentication method that the URL uses:
|
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.
Proxy Settings for HTTP Sensors
The proxy settings determine how a sensor connects to a URL. You can enter data for an HTTP proxy server that sensors use when they connect via HTTP or HTTPS.
This setting only applies to HTTP sensors and how they monitor. To change the proxy settings for the PRTG core server, see section Core & Probes.
For more information, see section Root Group Settings, section Proxy Settings for HTTP Sensors.
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.
For example, consider the URL http://www.example.com/status.html that returns a PHP script with the current system status in a simple HTML page as follows:
<html>
<body>
Description: Script gives back current status of disk free (%) and CPU usage (%).
[85.5][12.0]
</body>
</html>
You would configure the HTTP Content sensor using
- the Script URL from above,
- the value type Float,
- and the number of channels 2.
The sensor calls the URL with every scanning interval and only regards the two values in brackets [ ] and handles each of them in one channel. The additional description text and HTML tags are not necessary. In this example, they are added in case a human calls the URL.
If you define the number of channels as 1, the sensor only reads the first value. The second value is ignored. Using 3 as the number of channels results in a sensor error message.
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 |
[Value] |
The numeric values that an HTTP request returns in several channels |
KNOWLEDGE BASE
How can I monitor internal values of a web application with PRTG?
Which HTTP status code leads to which HTTP sensor status?
What security features does PRTG include?
My HTTP sensors don't work. What can I do?