<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: HTTP Push Count Sensor

Remote probe

If you want to add this sensor to a remote probe and use an HTTPS connection to send push notifications, you must import a Secure Sockets Layer (SSL) certificate into the \cert subfolder of the PRTG program directory on the remote probe. However, this certificate does not have to match the certificate that you use on the PRTG core server. For more information about SSL certificates, see the Paessler website: How to use your own SSL certificate with the PRTG web server

Cluster probe

This sensor does not support cluster probes. You can only set it up on local probes or remote probes.

IPv6

This sensor supports IPv6.

Performance impact

This sensor has a low performance impact.

Hosted probe

You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.

TLS Settings

Define the security of the incoming HTTP push requests:

• HTTP (unsecure): Send push messages to the probe system via HTTP (not secure).
• HTTPS low security (TLS 1.0 to 1.3 and weak ciphers): Send push messages to the probe system via HTTPS. The sensor supports connections secured with TLS 1.0 to TLS 1.3 and weak ciphers. It uses the SSL certificate that is delivered with PRTG or your own trusted SSL certificate that you imported for the PRTG web server.
  If you install the sensor on a remote probe, make sure that you import the same SSL certificates to the remote probe that you use on the PRTG core server.
• HTTPS high security (TLS 1.2 to 1.3 and strong ciphers): Send push messages to the probe system via HTTPS. The sensor supports connections secured with TLS 1.2 to TLS 1.3 and strong ciphers. It uses the SSL certificate that is delivered with PRTG or your own trusted SSL certificate that you imported for the PRTG web server.
  If you install the sensor on a remote probe, make sure that you import the same SSL certificates to the remote probe that you use on the PRTG core server.

You cannot change this value after sensor creation.

Port

This setting is only visible if you select HTTP (unsecure) above.

Enter the number of the port on which this sensor listens for incoming HTTP requests. The default port is 5050.

You cannot change this value after sensor creation.

TLS Port

This setting is only visible if you select HTTPS low security (TLS 1.0 to 1.3 and weak ciphers) or HTTPS high security (TLS 1.2 to 1.3 and strong ciphers) above.

Enter the number of the port on which this sensor listens for incoming HTTPS requests. The default port is 5051.

You cannot change this value after sensor creation.

Request Method

Select the request method of the webhook:

• any: Do not use any filter for the request method.
• GET (default): Select this method if the webhook uses GET.
• POST: Select this method if the webhook sends POST data.
  POST data must be form-encoded request bodies with the same parameters as for GET requests.

Identification Token

This is the token that PRTG uses to find the matching sensor for the incoming message. When you create the sensor, this token is {__guid__}.

PRTG replaces this token with an automatically generated token after sensor creation. If you want to use a different identification token, you can edit it during or after sensor creation.

PRTG does not automatically replace the token if you change it already during sensor creation.

Request Handling

Define what PRTG does with the incoming messages:

• Discard request: Do not store the pushed messages.
• Store result: Store the last message received from the sensor in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Request for Sensor [ID].txt. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

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.

You can set a different primary channel later by clicking 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.
  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. 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.

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.

Messages Received

The number of messages received

This channel is the primary channel by default.