PRTG Manual: Cloud HTTP v2 Sensor
The Cloud HTTP v2 sensor monitors the loading time of a web server via HTTP from different locations worldwide via the PRTG Cloud. The locations are distributed among four continents around the globe.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Cloud HTTP v2
- French: Cloud HTTP v2
- German: Cloud HTTP v2
- Japanese: Cloud HTTP v2
- Portuguese: Cloud HTTP v2
- Russian: Cloud HTTP v2
- Simplified Chinese: Cloud HTTP v2
- Spanish: Cloud HTTP v2
- The probe system must have access to the internet and must be able to reach https://api.prtgcloud.com:443 to communicate with the PRTG Cloud.
- The address you define in the settings of the parent device must be reachable over the internet. You cannot use this sensor to monitor localhost (127.0.0.1) or other target devices that are only reachable within your private network.
- This sensor inherits proxy settings for HTTP sensors from the parent device.
- This sensor supports smart URL replacement.
- This sensor has a low performance impact.
- This sensor uses lookups to determine the status values of one or more channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.
- This sensor has predefined limits for several metrics. You can individually change these limits in the channel settings. For detailed information about channel limits, see section Channel Settings.
- See the Knowledge Base: What is the PRTG Cloud Bot?
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. |
Parent Tags |
Shows 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 ( |
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
Setting |
Description |
---|---|
URL |
Select if you want to inherit the URL from the parent device or if you want to enter a custom URL:
|
Custom URL |
This option is only visible if you select Custom above. Enter a custom URL that the sensor connects to.
|
Request Method |
Select an HTTP request method to determine how the sensor requests the URL:
|
Postdata |
This option is only visible if you select POST as Request Method above. Enter the data part for the POST request. |
Region |
Select the regions from which you want to check the service:
|
Timeout (Sec.) |
Enter a timeout in seconds for the Ping. If the reply takes longer than this value, PRTG cancels the request and shows an error message. Enter an integer value. You can enter a value between 1 and 30 seconds. |
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 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. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
By default, all of the following 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.
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Scanning Interval |
Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:
|
If a Sensor Query Fails |
Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the 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 the Warning status. Choose from:
|
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.
Setting |
Description |
---|---|
Schedule |
Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:
|
Maintenance Window |
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
|
Maintenance Begins |
This setting 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 one-time maintenance window. |
Maintenance Ends |
This setting 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 one-time maintenance window. |
Dependency Type |
Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
Dependency Delay (Sec.) |
This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay. After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
User Group Access |
Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:
|
Click to interrupt the inheritance.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
Setting |
Description |
---|---|
Channel Unit Types |
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, you can inherit these settings to all sensors underneath. You can set units for the following channel types (if available):
|
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.mycompany.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.mycompany.com/
- If you enter /help in the URL field, PRTG automatically creates and monitor the URL http://www.mycompany.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 monitored device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Asia Pacific (Singapore) |
The response time of the target server at the location in msec |
Asia Pacific (Singapore) - HTTP Response Code |
The response code of the target server at the location |
Asia Pacific (Singapore) - PRTG Cloud Response |
If the query of the PRTG Cloud was successful or not:
|
Asia Pacific (Sydney) |
The response time of the target server at the location in msec |
Asia Pacific (Sydney) - HTTP Response Code |
The response code of the target server at the location |
Asia Pacific (Sydney) - PRTG Cloud Response |
If the query of the PRTG Cloud was successful or not:
|
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 in percent. |
Europe (Ireland) |
The response time of the target server at the location in msec |
Europe (Ireland) - HTTP Response Code |
The response code of the target server at the location |
Europe (Ireland) - PRTG Cloud Response |
If the query of the PRTG Cloud was successful or not:
|
Global Average |
The global average in msec
|
US East (Northern Virginia) |
The response time of the target server at the location in msec |
US East (Northern Virginia) - HTTP Response Code |
The response code of the target server at the location |
US East (Northern Virginia) - PRTG Cloud Response |
If the query of the PRTG Cloud was successful or not:
|
US West (Northern California) |
The response time of the target server at the location in msec |
US West (Northern California) - HTTP Response Code |
The response code of the target server at the location |
US West (Northern California) - PRTG Cloud Response |
If the query of the PRTG Cloud was successful or not:
|
Knowledge Base
What is the PRTG Cloud Bot?
What security features does PRTG include?
For more information about sensor settings, see the following sections: