<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Cloud Ping v2 Sensor

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. The locations are distributed among four continents around the globe.

Cloud Ping v2 Sensor

Cloud Ping v2 Sensor

i_square_cyanFor 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

Consider the following remarks and requirements for this sensor:

Remark

Description

Internet access

  • 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.

Localhost

You cannot use this sensor to monitor localhost (127.0.0.1).

IPv4

This sensor only supports IPv4.

Performance impact

This sensor has a low performance impact.

Limits

This sensor has predefined limits for several metrics.

Probe system

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.

TCP

This sensor uses Transmission Control Protocol (TCP) ping.

Inheritance

This sensor inherits proxy settings from the parent device.

Scanning interval

  • The minimum scanning interval of this sensor is 1 minute.
  • The recommended scanning interval of this sensor is 5 minutes.

Multi-platform probe

You can add this sensor to a multi-platform probe.

Knowledge Base

Knowledge Base: What is the PRTG Cloud Bot?

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

  • cloud
  • cloudpingsensor
  • ping

i_square_cyanFor more information about basic sensor settings, see section Sensor Settings.

Cloud Ping Specific

Cloud Ping Specific

Cloud Ping Specific

Setting

Description

Target Address

Select if you want to inherit the IP address or the 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.

i_round_redThis 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.

i_round_blueThe 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

Sensor Display

Setting

Description

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

  • 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.
    i_round_redYou 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. PRTG stacks all channels with this unit 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

Debug Options

Setting

Description

Result Handling

Define what PRTG does with the sensor result:

  • Discard result (default): Do not store the sensor result.
  • Store result: Store the sensor result and the last response 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.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn 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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Channel List

i_round_blueWhich 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

i_round_blueThis channel has default limits:

  • Upper error limit: 5000 msec
  • Upper warning limit: 3333 msec

Asia Pacific (Singapore) - PRTG Cloud Response

If the PRTG Cloud query was successful or not

  • Up status: OK
  • Down status: Failed

Asia Pacific (Sydney)

The response time of the target server at the location

i_round_blueThis channel has default limits:

  • Upper error limit: 5000 msec
  • Upper warning limit: 3333 msec

Asia Pacific (Sydney) - PRTG Cloud Response

If the PRTG Cloud query 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

i_round_blueThis channel has default limits:

  • Upper error limit: 5000 msec
  • Upper warning limit: 3333 msec

Europe (Ireland) - PRTG Cloud Response

If the PRTG Cloud query was successful or not

  • Up status: OK
  • Down status: Failed

Global Average

The average global response time

i_round_blueThis channel has default limits:

  • Upper error limit: 5000 msec
  • Upper warning limit: 3333 msec

i_round_blueThis channel is the primary channel by default.

US East (Northern Virginia)

The response time of the target server at the location

i_round_blueThis channel has default limits:

  • Upper error limit: 5000 msec
  • Upper warning limit: 3333 msec

US East (Northern Virginia) - PRTG Cloud Response

If the PRTG Cloud query was successful or not

  • Up status: OK
  • Down status: Failed

US West (Northern California)

The response time of the target server at the location

i_round_blueThis channel has default limits:

  • Upper error limit: 5000 msec
  • Upper warning limit: 3333 msec

US West (Northern California) - PRTG Cloud Response

If the PRTG Cloud query was successful or not

  • Up status: OK
  • Down status: Failed

More

i_square_blueKNOWLEDGE BASE

What is the PRTG Cloud Bot?

What security features does PRTG include?