PRTG Manual: QoS (Quality of Service) Round Trip Sensor
The QoS (Quality of Service) Round Trip sensor monitors parameters regarding the quality of a network connection between two probes.
The sensor sends a series of User Datagram Protocol (UDP) packets from the source probe to a target probe at the end of the connection line. Then, the target probe sends the packets back to the source probe.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: QoS (Quality of Service) Heen en weer
- French: Quality of Service (QoS) aller-retour
- German: QoS (Quality of Service) Round Trip
- Japanese: ラウンドトリップ QoS(Quality of Service)
- Portuguese: Ida e volta QoS (qualidade de serviço)
- Russian: Цикл тестирования качества обслуживания
- Simplified Chinese: QoS (服务质量) 往返
- Spanish: Ida y vuelta QoS (calidad de servicio)
- This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires that you configure at least one remote probe in your PRTG Network Monitor setup and at least two remote probes in PRTG Hosted Monitor, or you must set up the PRTG QoS Reflector tool on the target system at the endpoint of the connection that you want to monitor.
- This sensor does not support cluster probes. You can only set it up on local probes or remote probes.
- This sensor only supports IPv4.
- Knowledge Base: How can I monitor QoS round trips without using remote probes?
- Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
- Knowledge Base: What connection settings are necessary for the QoS (Quality of Service) Round Trip sensor?
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.
Setting |
Description |
---|---|
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:
|
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 (). |
Quality of Service Measurement
Setting |
Description |
---|---|
Timeout (Sec.) |
Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes). If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message. |
QoS Target |
Define the type of target that receives the UDP packets:
For more information about the QoS Reflector, see the Knowledge Base: How can I monitor QoS round trips without using remote probes? |
Target Probe |
This setting is only visible if you select Probe (default) above. Define the target probe that receives the UDP packets. The dropdown list shows all local probes and remote probes in your setup. If you want to run the sensor on the local probe, select a remote probe as the Target Probe. If no remote probe is available, install and connect a remote probe first. Alternatively, you can use the PRTG QoS Reflector. If you want to run the sensor on a remote probe, select either a different remote probe or the local probe as the target. The sensor measures values for the network track between the parent probe and the target probe. You must make sure that firewalls or network address translation (NAT) rules allow UDP packets to reach the target probe. The probe automatically opens the Windows firewall on the target system. For more information, see the Knowledge Base: What connection settings are necessary for the QoS (Quality of Service) Round Trip sensor? In PRTG Hosted Monitor, you can only select a different remote probe as the target probe. QoS measurements for connections to the hosted probe are not possible. |
Target Host/IP Address |
Define the IP address of the QoS target:
|
Port |
Define the source and target port for the UDP packets. Both the source probe and the target probe use this port. Enter an integer. The default port is 50000. PRTG supports the port numbers 1024-65536 for UDP packets. Use a different port for each QoS (Quality of Service) Round Trip sensor to make sure that packets can be assigned correctly. The port must be available on both the source system and the target system. |
Number of Packets |
Define the number of packets that the sensor sends with each scanning interval. Enter an integer. The default value is 1000. The minimum value is 10. The maximum value is 1000. We recommend that you use the default value. |
Packet Size (Bytes) |
Define the size of the packets in bytes that the sensor sends. Enter an integer. The default value is 172. The minimum value is 172. The maximum value is 4500. We recommend that you use the default value. |
Packet Delay (ms) |
Define the time in milliseconds (ms) that the sensor waits between two packets. Enter an integer. The default value is 20. The minimum value is 10. The maximum value is 1000. We recommend that you use the default value. |
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:
|
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. |
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.
For more information, see section Inheritance of Settings.
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.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window (default).
For more information, see section Root Group Settings, section Access Rights.
Which 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 |
Jitter Average |
The average jitter |
Jitter Max |
The maximum jitter This channel is the primary channel by default. |
Jitter Min |
The minimum jitter |
MOS |
The MOS |
Packet Delay Variation Average |
The average packet delay variation |
Packet Delay Variation Max |
The maximum packet delay variation |
Packet Delay Variation Min |
The minimum packet delay variation This channel has a default limit
|
Packets Corrupted |
The corrupted packets (%) This channel has a default limit
|
Packets Duplicated |
The duplicated packets (%) This channel has a default limit
|
Packets Lost |
The lost packets (%) This channel has a default limit
|
Packets Out Of Order |
The out of order packets (%) This channel has a default limit
|
RTT (Average) |
The average RTT |
RTT (Maximum) |
The maximum RTT |
RTT (Minimum) |
The minimum RTT |
KNOWLEDGE BASE
How can I monitor QoS round trips without using remote probes?
How does PRTG calculate the MOS score for QoS sensors?
What connection settings are necessary for the QoS (Quality of Service) Round Trip sensor?
What security features does PRTG include?
PAESSLER WEBSITE
How to connect PRTG through a firewall in 4 steps