PRTG Manual: HTTP Push Count Sensor

The HTTP Push Count sensor counts received messages that are pushed via an HTTP request to PRTG. It provides a URL that you can use to push messages to the probe system via HTTP (secured with TLS 1.2 or not secure).

HTTP Push Count Sensor

HTTP Push Count Sensor

i_square_cyanFor more information about the sensor usage, see section How to Use.

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: HTTP Push Aantal
  • French: Compteur (HTTP Push)
  • German: HTTP Push-Anzahl
  • Japanese: HTTP プッシュ数
  • Portuguese: Contagem de push (HTTP)
  • Russian: HTTP: Количество push-объектов
  • Simplified Chinese: HTTP 推送计数
  • Spanish: Recuento Push (HTTP)

Remarks

  • If you want to install this sensor on a remote probe and use an HTTPS connection to send push notifications, you need to make sure that you import the same Secure Sockets Layer (SSL) certificates to the \cert subfolder of the PRTG program directory on the remote probe that you use on the PRTG core server. For more information, see the PRTG Manual: Using Your Own SSL Certificate with the PRTG Web Server
  • You cannot use this sensor in cluster mode. You can only set it up on a local probe or a remote probe but not on a cluster probe.
  • This sensor supports the IPv6 protocol.
  • This sensor has a low performance impact.
  • For more information about the sensor usage, see the PRTG Manual: How to Use.

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

Add Sensor

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.

HTTP Push

Setting

Description

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 (secured with TLS 1.2 only): Send push messages to the probe system via HTTPS. The sensor only supports connections secured with TLS 1.2. It uses the SSL certificate that is delivered with PRTG or your own trusted SSL certificate that you imported for the PRTG web server.
    i_round_redIf 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.

Port

This setting is only visible if you enable HTTP (unsecure) above. Enter the number of the port on which this sensor listens for incoming HTTP requests. The default port is 5050.

TLS Port

This setting is only visible if you enable HTTPS (secured with TLS 1.2 only) above. Enter the number of the port on which this sensor listens for incoming HTTPS requests. The default port is 5051.

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Basic Sensor Settings

Basic Sensor 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.

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

i_round_blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

i_round_blueFor 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:

  • pushsensor
  • pushcount
  • httppushsensor

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 (i_priority_1) to the highest priority (i_priority_5).

i_round_blueUsually, 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.

HTTP Push

HTTP Push

HTTP Push

Setting

Description

TLS Settings

Shows whether the sensor accepts push messages via HTTP or HTTPS.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Port

This setting is only visible for sensors that accept push messages via HTTP. It shows the port number on which this sensor listens for incoming HTTP requests.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

TLS Port

This setting is only visible for sensors that accept push messages via HTTPS. It shows the port number on which this sensor listens for incoming HTTPS requests.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Request Method

Select the request method of the webhook:

  • ANY: Do not use any filter for the request method.
  • GET: Select this method if the webhook uses GET.
  • POST: Select this method if the webhook sends POST data.
    i_round_redPOST 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.

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

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

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

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.

Scanning Interval

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou 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

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

How to Use

This function is known as webhook. Basically, a webhook works like a push notification. Webhooks are usually triggered by an event (for example, a new comment on a blog post) and send according information to a specified URL. The HTTP Push Count sensor then displays the number of pushed and received messages.

The HTTP Push Count sensor uses the following URL:

http://<probe_ip>:<port_number>/<token>

Replace the parameters <probe_ip>, <port_number>, and <token> with the corresponding values.

  • The <probe_ip> is the IP address of the probe system with the sensor.
  • The <port_number> is where the sensor listens for incoming HTTP calls.
  • The <token> is used to define the matching sensor.

Example:

http://192.0.2.0:5050/XYZ123

i_round_blueYou can use several sensors with the same port and identification token. In this case, the number of push messages is shown in each of these sensors.

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

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.

Messages Received

The number of messages received per second

i_round_blueThis channel is the primary channel by default.

More

i_square_blueKnowledge Base

What security features does PRTG include?

My HTTP sensors don't work. What can I do?