The Cloud Ping v2 sensor monitors the Transmission Control Protocol (TCP) ping times to its parent device from different locations worldwide via the PRTG Cloud. These locations are distributed among four continents around the globe.
Cloud Ping v2 Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
Dutch: Cloud Ping v2
French: Cloud Ping v2
German: Cloud Ping v2
Japanese: クラウド Ping v2
Portuguese: Cloud Ping v2
Russian: Cloud Ping v2
Simplified Chinese: Cloud Ping v2
Spanish: Nube ping v2
Remarks
The probe system requires access to the internet and must be able to reach https://api.prtgcloud.com:443 to communicate with the PRTG Cloud.
This sensor requires that the address in the settings of the parent device is reachable via the internet. You cannot use this sensor to monitor localhost (127.0.0.1).
This sensor only supports IPv4.
This sensor has a low performance impact.
This sensor has predefined limits for several metrics.
To monitor the probe system, enter the IP address or the fully qualified domain name (FQDN) of the probe system that is reachable via the internet as Custom Target Address in the Cloud Ping Specific settings or add a device with the IP address or the DNS name of the probe system.
This sensor uses Transmission Control Protocol (TCP) ping.
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
This setting is for your information only. You cannot change it.
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.
It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).
For performance reasons, it can take some minutes until you can filter for new tags that you added.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
cloud
cloudpingsensor
ping
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 () to the highest priority ().
Cloud Ping Specific
Cloud Ping Specific
Setting
Description
Target Address
Select if you want to inherit the IP address or the fully qualified domain name (FQDN) from the parent device or if you want to enter a custom target address:
Inherit (default)
Custom
Custom Target Address
This setting is only visible if you select Custom above.
Enter the IP address or the FQDN of the target device.
Port
Enter the number of the port that this sensor uses for TCP ping. The default port is 80.
This sensor does not support port 25.
Ping Count
Enter the number of pings that PRTG sends in a row to the parent device in one scanning interval. Enter an integer. The minimum value is 1. The maximum value is 10.
Region
Select the regions from which you want to check the service:
Asia Pacific (Singapore)
Asia Pacific (Sydney)
Europe (Ireland)
US East (Northern Virginia)
US West (Northern California)
Timeout (Sec.)
Enter a timeout in seconds per ping. You can enter a value between 1 and 30 seconds.
The actual timeout duration depends on the number of pings that you entered under Ping Count. PRTG calculates this value by multiplying Ping Count by Timeout (Sec.).
Sensor Display
Sensor Display
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.
You can set a different primary channel later by clicking below a channel gauge 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. You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
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.
Debug Options
Debug Options
Setting
Description
Result Handling
Define what PRTG does with the sensor result:
Discard result: Do not store the sensor result.
Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.
This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.
In a cluster, PRTG stores the result in the PRTG data directory of the master node.
Inherited Settings
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.
The minimum scanning interval of this sensor is 1 minute.
The recommended scanning interval of this sensor is 5 minutes.
Scanning Interval
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.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
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.
Channel Unit Configuration
For more information, see section Root Group Settings, section Channel Unit Configuration.
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel
Description
Asia Pacific (Singapore)
The response time of the target server at the location
This channel has default limits
Upper error limit: 5000 msec
Upper warning limit: 3333 msec
Asia Pacific (Singapore) - PRTG Cloud Response
If the query of the PRTG Cloud was successful or not
Up status: OK
Down status: Failed
Asia Pacific (Sydney)
The response time of the target server at the location
This channel has default limits
Upper error limit: 5000 msec
Upper warning limit: 3333 msec
Asia Pacific (Sydney) - PRTG Cloud Response
If the query of the PRTG Cloud was successful or not
Up status: OK
Down status: Failed
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
Europe (Ireland)
The response time of the target server at the location
This channel has default limits
Upper error limit: 5000 msec
Upper warning limit: 3333 msec
Europe (Ireland) - PRTG Cloud Response
If the query of the PRTG Cloud was successful or not
Up status: OK
Down status: Failed
Global Average
The average global response time
This channel has default limits
Upper error limit: 5000 msec
Upper warning limit: 3333 msec
This channel is the primary channel by default.
US East (Northern Virginia)
The response time of the target server at the location
This channel has default limits
Upper error limit: 5000 msec
Upper warning limit: 3333 msec
US East (Northern Virginia) - PRTG Cloud Response
If the query of the PRTG Cloud was successful or not
Up status: OK
Down status: Failed
US West (Northern California)
The response time of the target server at the location
This channel has default limits
Upper error limit: 5000 msec
Upper warning limit: 3333 msec
US West (Northern California) - PRTG Cloud Response
If the query of the PRTG Cloud was successful or not