<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: MQTT Round Trip Sensor

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

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?

Parent Tags

The tags that the sensor inherits from its parent device, parent group, and parent probe.

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:

• roundtrip
• mqttroundtrip

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

Topic

Enter the topic for the round trip. The default is PRTG/roundtrip/%sensorid.

PRTG replaces %sensorid with the sensor's ID.

Connection Settings

Define the connection settings for the connection to the MQTT broker:

• Use default settings: Use the default connection settings.
• Use custom settings: Use a ClientID that you can specify below.

ClientID

This setting is only visible if you select Use custom settings above. Enter the ClientID for the connection to the MQTT broker. The default is PRTG_%sensorid.

PRTG replaces %sensorid with the sensor's ID. For the subscribing client, PRTG automatically adds _subscriber to the ClientID. For the publishing client, PRTG automatically adds _publisher to the ClientID.

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

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.

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

Publisher Connection Time

The time it takes the publisher to connect

Round Trip Time

The RTT of the message (after both publisher and subscriber connect)

This channel is the primary channel by default.

Status

The round trip status

• Up status: Roundtrip Complete
• Down status: Message Not Received, Message Not Sent, Publisher Could Not Connect, Subscriber Could Not Connect

Subscribe Connection Time

The time it takes the subscriber to connect