Just 6 weeks have passed since our last release and already a new one is ready. PRTG Network Monitor version 22.2.76 is now available in the stable release channel and comes with Okta as a new SSO...
Read the complete blog post here
Release notes
for the "stable" release channel
Software versions in this channel are updated about once a month. In this most conservative channel you receive the best tested versions. We recommend that you use PRTG's stable versions for live environments.
Please use the "Auto-Update" feature to update your PRTG installation: In the PRTG web interface, simply navigate to Setup | Auto Update. You can also obtain the latest version from the PRTG download page!
Download PRTG · Manual: "Software Auto-Update" · Previous Versions and other Release Channels

April 26th 2022 – Version 22.2.76.1705
Blog article
New
Single sign-on
Okta |
You can now use Okta as provider for single sign-on (SSO) to login to PRTG with multi-factor authentication. Okta is the second SSO provider that you can integrate to PRTG. Azure Active Directory (Azure AD) is available since PRTG 21.2.68. You can choose the SSO provider that you work with in the system administration of PRTG and configure the settings for your SSO access. Please note that this feature is only available for Paessler PRTG Network Monitor, not for Paessler PRTG Hosted Monitor. |
New
Sensors
AWS Alarm v2 |
The new AWS Alarm v2 sensor monitors your favorite metric and composite AWS alarms and will be the successor of the existing Amazon CloudWatch Alarm sensor. |
AWS EBS v2 |
The new AWS EBS v2 sensor monitors the status and performance of an AWS EBS volume and will be the successor of the existing Amazon CloudWatch EBS sensor. |
AWS EC2 v2 |
The new AWS EC2 v2 sensor monitors the performance of an Amazon EC2 instance and will be the successor of the existing Amazon CloudWatch EC2 sensor. Note: If you use the same IAM policy that you use for the Amazon CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG? |
AWS ELB v2 |
The new AWS ELB v2 sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor. |
HPE 3PAR Drive Enclosure |
The new HPE 3PAR Drive Enclosure sensor monitors a drive enclosure of your HPE 3PAR storage system and shows status and temperature metrics. |
HPE 3PAR Virtual Volume |
The new HPE 3PAR Virtual Volume sensor monitors a virtual volume of your HPE 3PAR storage system and shows the status as well as used and free space on the volume. |
Redfish Power Supply |
The new Redfish Power Supply sensor monitors the status of the power supply of your servers, the power efficiency, and various other parameters. |
Redfish System Health |
The new Redfish System Health sensor monitors the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac. |
SNMP Rittal CMC III Hardware Status |
The new SNMP Rittal CMC III Hardware Status sensor monitors the hardware status of a Rittal CMC III processing unit and shows the status of every attached external sensor. |
Improved
Sensors
Modbus sensors |
Modbus RTU Custom and Modbus TCP Custom sensors now support connection sharing for multiple unit IDs on the same device. Previously, connection sharing only worked for a single unit ID on a device, so that you could only create a few Modbus sensors until the maximum number of allowed sessions was reached. |
MySQL v2 |
The MySQL v2 sensor now supports MariaDB version 10.6 as we updated the MySQL data library that PRTG uses to version 8.0.28. |
PostgreSQL |
The PostgreSQL sensor now supports TLS 1.2 connections as we updated the Npgsql library that the PostgreSQL sensor uses to monitor your database to version 6.0.3. |
SSH sensors |
We updated the SSH library that SSH sensors use to monitor the target devices. The update improves the security of SSH sensors. |
Sensor security |
We updated the logging library log4net that several sensor types use to version 2.0.14 to improve the security of PRTG. Affected sensor types are DICOM sensors, Exchange Mailbox (PowerShell), HL7, NetApp (cDOT/ONTAP) sensors, Windows Update Status (PowerShell), SQL v2 sensors. |
Fixed
Sensors
Microsoft Azure SQL Database |
The Microsoft Azure SQL Database sensor works again. Due to a change in the Azure API, the sensor recently showed a down status with the error message The queried field "average" is empty. on all instances. |
Veeam Backup Job Status Advanced |
The Veeam Backup Job Status Advanced sensor now supports the status Postprocessing and shows more expressive error messages in many cases instead of just Reason: Unknown. or The queried field "Reason" is empty. |
Fixed
Server
XML |
The View as XML button returns data again when you generate the XML from a sensor's Logs tab, for example. |
Lab
Sensors
Cisco Meraki Network Health |
The experimental Cisco Meraki Network Health (BETA) sensor now supports the uplink status not connected. |
NetApp Volume v2 |
You can try out the experimental NetApp Volume v2 (BETA) sensor that supports the new ONTAP REST API as of ONTAP 9.6 and will be the successor of the existing NetApp Volume sensor. |
Lab
New UI
Administration |
You can now globally hide the “Activate New UI And New API (Alpha)” banner in PRTG. For more information, see the Knowledge Base: https://kb.paessler.com/en/topic/90566. |
Improvement |
We reduced the installation size of the new PRTG web interface. |
Lab
New API
Objects |
Objects that were moved or cloned now receive a correct update of their path. |
PRTG application server |
We fixed an issue that caused a start loop of the PRTG application server when the default port was blocked. |
Performance |
We have increased the performance of the PRTG application server. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated German and Spanish language files, updated user manual |
Note
Sensors
Python Script Advanced |
PRTG version 22.2.77 that we will publish in June 2022 will include a new Python distribution. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.9 when you update to PRTG 22.2.77. You only need to consider the change if you are using the Python Script Advanced sensor. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/90484. |
Note
Known issue
Signature |
In certain cases, the PRTG core server does not start anymore after updating to PRTG 22.2.76 and the log file core.log contains the message
You can resolve the issue by adding the trusted root certificate for timestamp signature. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/90610. |

March 24th 2022 – Version 22.1.75.1588/22.1.75.1594
Important
Security
Server |
This version includes an important security update for your PRTG core server. We updated the OpenSSL library that PRTG uses to version 1.0.2zd, which patches the recently disclosed OpenSSL vulnerability CVE-2022-0778. For more information, see the Knowledge Base: https://kb.paessler.com/en/topic/90462. We recommend that you update as soon as possible. Note: Under certain circumstances, the PRTG core server could not successfully start after updating to version 22.1.75.1569 or 22.1.75.1588. We fixed the issue with PRTG 22.1.75.1594. |

March 15th 2022 – Version 22.1.75.1569
Improved
Security
Server |
PRTG now sanitizes channel names to close a potential XSS vulnerability. (CVE-2021-42695) |
Improved
Sensors
Packet Sniffer |
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 1.60. The new version includes several fixes and improvements compared to the previously delivered version 1.10. If you encounter issues with your Packet Sniffer sensors after the update, please see the Knowledge Base article https://kb.paessler.com/en/topic/86904 |
Improved
Server
Single sign-on |
|
Fixed
Sensors
HTTP Push Data Advanced |
We improved the stability of the HTTP Push Data Advanced sensor. In previous versions, the sensor occasionally showed a down status with the error message could not bind socket after some time. The issue appeared in cases when there were more than one sensor of this type running. |
Microsoft Azure sensors |
Microsoft Azure sensors now can handle all name strings as specified in the Resource name rules by Microsoft. In previous versions, the Microsoft Azure SQL sensor, for example, could not handle whitespaces in elastic pool names and showed HTTP error 400 after creation. |
SQL v2 sensors |
SQL v2 sensors show data table values in the sensor message again if you enable the Use Data Table Value in Sensor Message setting. In previous versions, the defined value of the data table was missing in the message of the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, PostgreSQL, and Oracle SQL v2. |
Syslog Receiver |
We improved the reliability of the Syslog Receiver sensor in case of probe restarts to reduce issues with blocked ports. |
Fixed
Server
Historic data |
You can generate historic data files in XML and CSV format via the web interface again. In the previous version, running historic data reports for sensors did not work via the web interface and returned an Unauthorized error if the file format was XML or CSV. |
Stability |
This version comes with a number of stability improvements for the PRTG core server. |
Lab
Sensors
Cisco Meraki sensors |
|
NetApp System Health |
You can try out the experimental NetApp System Health (BETA) sensor that supports the new ONTAP REST API as of ONTAP 9.6 and will be the successor of the existing NetApp System Health sensor. |
Redfish sensors |
We implemented several improvements for the experimental Redfish sensors.
|
REST Custom v2 |
You can now define up to 5 individual placeholders for the experimental REST Custom v2 (BETA) sensor in the Credentials for REST API settings of devices. You can use the placeholders, as well as newly introduced placeholders for credentials, in the Request URL, POST Body, and Custom Header fields of the REST Custom v2 sensor. PRTG does not display the corresponding values in the sensor log nor in the sensor settings. |
Lab
New UI
Device list |
You can now select the Device List view to see all devices on root group, probes, or groups. |
Web interface |
|
Controls |
The Open new UI button in the classic PRTG web interface in German language no longer causes the global sensor status symbols to overlap the search box. |
Tables |
We updated the style of linked sensor names in tables. |
Lab
New API
POST Requests |
We increased the maximum size of the request body of POST requests to 15 kB. |
Sensors |
|
Certificates |
The PRTG application server does not use a hard-coded fallback certificate anymore. If the PRTG application server cannot load the provided certificate, it stops the startup process. |
Performance |
We have increased the performance of the PRTG application server. |
Documentation |
We improved the documentation. |
Lab
PRTG Desktop
Probe transfer |
We improved the stability of the probe transfer when transferring large probe configuration files. |
Improved
Various
Languages |
We updated and improved all language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |

February 1st 2022 – Version 22.1.74.1869
Blog article
PRTG v. 22.1.74 comes with 3 beta sensors and security improvements

The first release of PRTG Network Monitor in 2022 is version 22.1.74, and is available in the stable release channel. It includes 3 beta sensors and a major security improvement. Here are the new...
Read the complete blog post here
Read the complete blog post here
Improved
Security
Server |
We hardened PRTG against Cross Site Request Forgery (CSRF) attacks. This prevents changes to PRTG via web forms not originating from PRTG that attackers may use to trick PRTG users into performing requests with the user account's context. (CVE-2021-34547) Note: API calls now always explicitly require credentials even if the user account is currently logged in in PRTG. Otherwise, PRTG will return Unauthorized. If you have issues with saving changes to settings, clear your browser cache with CTRL+F5 after updating and opening the PRTG web interface because we also updated the JavaScript version with this security improvement. |
Improved
Sensors
AWS Cost |
You can now create device templates that include the AWS Cost sensor. You can use the device templates to add AWS Cost sensors via auto-discovery. |
DNS v2 |
|
Veeam Backup Job Status Advanced |
|
Changed
Sensors
Oracle Tablespace |
We changed the name of the Database Size channel of the Oracle Tablespace sensor to Tablespace Size. Tablespace Size is the correct naming because this is what the channel monitors. The same is for the Tablespace Size on Disk channel that we accordingly changed as well. |
SSL Security Check |
We changed the TLS 1.1 (Strong) channel of the SSL Security Check sensor to TLS 1.1 (Weak). This means that the sensor will now show a warning status if the target device accepts TLS 1.1 connections. We also changed the TLS 1.2 (Perfect) channel to TLS 1.2 (Strong), which comes without a changed behavior for the sensor status. |
Changed
Channel units
Channel Unit Configuration |
We changed the default channel units for probes, group, devices and sensors. New PRTG installations and newly created probes, group, devices, and sensors with turned off inheritance now have the following units defined by default as you can check in the Channel Unit Configuration settings.
|
Fixed
Sensors
SNMP Cisco CBQoS |
Running an auto-discovery with a device template that includes SNMP Cisco CBQoS sensors now successfully adds sensors of this type. In previous versions, this did not work due to incorrect entries for this sensor type in created device templates and the sensors were not added. |
Fixed
Server
API |
Filtering in table API calls returns only exact matches again. In previous versions, the filter also returned objects if it matched their prefixes. |
Cluster |
PRTG properly synchronizes the settings of notification templates from the master node to failover nodes again. In previous versions, defined settings of newly created notification templates were not taken over on failover nodes, which could result in notifications not being sent from a failover. |
Down (Acknowledged) |
The sensor message of sensors in Down (Acknowledged) status shows the original error message again. The error message was missing for acknowledged sensors in previous versions. |
Installation |
The command line parameter /LANG for the language used in PRTG works again when installing PRTG via command line as specified in the Knowledge Base article What command line codes and exit codes can I use with Paessler setups? You can now even use /LANG for silent installations. In previous version, PRTG was always installed with the default English language file when using the command line for setup. |
Libraries |
We fixed the channel selection of notification triggers in cloned libraries. In previous versions, you could not select a sensor channel in the settings of speed, threshold, and volume triggers if the library was a clone. |
Limits |
You can save changes to sensor channels again even if another channel of the same sensor has the setting Enable alerting based on limits with no defined limits activated. In previous versions, the input validation failed in such cases and you received an Error (Bad Request) dialog window with the message The validation of the data you entered failed. You have set Alerting to limit-based, but have entered no limit value. |
Lab
Sensors
Cisco Meraki License |
You can try out the experimental Cisco Meraki License (BETA) sensor as of this version and monitor the status of your Meraki licenses. It shows days to expiration, license model, and license count. |
Cisco Meraki Network Health |
You can try out the experimental Cisco Meraki Network Health (BETA) sensor as of this version and monitor the health of Cisco Meraki network devices. |
FortiGate VPN Overview |
You can try out the experimental FortiGate VPN Overview (BETA) sensor as of this version and monitor VPN connections of your Fortinet FortiGate firewall. The sensor shows the number of connected SSL clients, as well as the number of both up and down IPsec tunnels. |
REST Custom v2 |
|
Lab
New UI
Context menus |
You can now open the corresponding context menu if you right-click linked objects or headers. |
Devices |
You can now sort sensor lists based on the time since the last scan. |
Notifications |
Line breaks in notifications no longer break up single words. |
Lab
New API
Sensors |
Sensors now immediately display measurements after the start of the PRTG application server regardless of the sensor’s scanning interval. |
Documentation |
We improved the documentation. |
PRTG application server |
|
Sensor Factory |
The channels of the Sensor Factory sensor receive measurements as expected again. |
Channels |
Channels that are created after the first sensor scan work as expected again. |
Lab
Multi-platform probe
Supported platforms |
The multi-platform probe now supports ARM based systems with either ARMv7 or aarch64 architecture. This enables you to deploy your probe on systems like Raspberry Pi, AWS EC2 with Graviton CPU, and NAS systems, for example. See the Knowledge Base for more details: What is the Multi-Platform Probe and how can I use it? |
Lab
PRTG Desktop
Probe transfer |
You can now allow PRTG Desktop to access the configuration files of your probes to transfer a probe to another server. You find the setting Probe Transfer in the Experimental Features section of the PRTG web interface. |
Note
Update notes
Cache recalculation |
The update to this PRTG version will immediately cause a cache recalculation upon starting the PRTG server. While PRTG is usable during the cache recalculation, it will considerably consume more hardware resources like CPU and memory. Depending on your monitoring configuration, you may encounter negative effects on the performance of PRTG during this process. We recommend that you reserve extra time for the PRTG update. |
Tree version update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German and Dutch language files |

December 1st 2021 – Version 21.4.73.1656
New
Notifications
OPC UA |
You can now use OPC UA notifications to forward PRTG alerts to your northbound systems like SCADA, DCS, or any other system that has an OPC UA server. By creating an OPC UA notification template, you can build meaningful error messages that PRTG sends to your OPC UA server. This supports you in seeing and reacting on issues in your network infrastructure as fast as possible. |
Improved
Sensors
Business Process |
Requesting data of the Business Process sensor via the API now returns values in value_raw fields in a better consumable way. |
DNS v2 |
You can now define multiple filter values for the DNS v2 sensor to filter for more than one IP address, for example. |
Modbus sensors |
The sensor types Modbus RTU Custom and Modbus TCP Custom now provide a timeout setting. If the reply from the target device takes longer than the defined Receive Timeout (msec), the request will be aborted and the sensor stops trying to connect. |
Changed
Sensors
Lookups |
You can now easier identify sensors with a missing or broken lookup file. Sensors that have an issue with their lookups will change their status to warning with the message At least one channel uses a lookup that is not available or could not be loaded. (PE272) as of this version to indicate that the sensor cannot properly monitor. In previous versions, you only received a ToDo ticket in such cases but affected sensors kept their status. |
Microsoft 365 Service Status sensors |
The sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced support the new Microsoft 365 Service Health and Communications Graph API as of this version. This change is necessary to seamlessly continue monitoring your Microsoft 365 services because Microsoft soon will shut down the current API version that the sensors used until now. Important: Both sensors now require the API permission ServiceHealth.Read.All to be able to retrieve data from Microsoft Graph and continue monitoring. For details, please see the Knowledge Base article How do I obtain credentials and set permissions for the Microsoft 365 sensors? Please also note that the Microsoft 365 Service Status Advanced sensor cannot monitor subservices anymore and will show the message Channel is deprecated for affected channels. We will remove the channels in an upcoming PRTG version. |
Scanning interval |
We changed the default scanning interval for several newer sensor types that we introduced over the last couple of PRTG versions. |
Fixed
Sensors
Microsoft Azure Virtual Machine |
The Microsoft Azure Virtual Machine sensor now shows a down status with an appropriate error message if the target device is not reachable anymore, for example, due to changed credentials. In previous versions, the sensor incorrectly showed a misleading up status with 0 values in such cases. We also improved the general stability of the sensor. |
Fixed
WebGUI
Channel Unit Configuration |
The dropdown menu for the unit of Bytes (Bandwidth) in the Channel Unit Configuration settings is properly shown again. In Google Chrome and Edge, it was difficult to select the desired unit due to display issues in previous versions. |
Lab
Sensors
AWS v2 sensors |
We implemented various improvements for the experimental AWS v2 sensors.
|
AWS EBS v2 |
You can try out the experimental AWS EBS v2 (BETA) sensor as of this version and monitor the status and performance of an AWS EBS volume. |
FortiGate System Statistics |
You can try out the experimental FortiGate System Statistics (BETA) sensor with this version. The sensor monitors the system health of a Fortinet FortiGate firewall and shows CPU and memory usage, as well as uptime, session statistics, and conserve mode activity. |
Network Share |
You can try out the experimental Network Share (BETA) sensor with this version. The sensor monitors the number of files and folders on a network share via SMB or CIFS, as well as its size and the age of oldest and newest files. |
Redfish Power Supply |
You can try out the experimental Redfish Power Supply (BETA) sensor as of this version. The sensor monitors the status of the power supply of your servers, the power efficiency, and various other parameters. |
Lab
New UI
Initial alpha release |
We are working on a complete redesign of the PRTG web interface. The redesign is based on extensive user research and the feedback that we have received over the years. The user interface will be fully responsive and will follow the Web Content Accessibility Guidelines (WCAG). Although the new UI is still missing many features, we decided to release the alpha version to give you the opportunity to try out the new UI, and to gather feedback during the early development process. Read all about the new UI here: I want to use the new UI and new API. What do I need to know? |
Lab
New API
Initial alpha release |
Our new RESTful API will enable you to easily automate your monitoring and to integrate it with other tools. Our goal is to build a comprehensively documented RESTful API that is consistent across all endpoints. Although the new API is still missing many features, we decided to release the alpha version to give you the opportunity to try out the new API, and to gather feedback during the early development process. Read all about the new API here: I want to use the new UI and new API. What do I need to know? |
Lab
Multi-platform probe
Initial alpha release |
The new multi-platform probe will enable you to deploy PRTG probes on various platforms like Windows, Linux, and Docker. We are happy to now share the initial alpha version with you and gather your feedback during the early development process. You can already run a limited set of sensors on it but many features will follow later. Read all about the new multi-platform probe here: What is the Multi-Platform Probe and how can I use it? |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German and French language files |
Note
Sensors
Event Log (Windows API) |
The Event Log (Windows API) sensor will no longer work due to security changes from Microsoft and will be discontinued. For details, please see Event Tracing and Windows NTLM Elevation of Privilege Vulnerability. We recommend that you pause existing sensors to store historic data. To continue monitoring, use the WMI Event Log sensor. |

October 26th 2021 – Version 21.4.72.1649
Blog article
PRTG 21.4.72 with AWS Alarm v2 sensor and various fixes & improvements

Compared to the last releases of PRTG Network Monitor, this update does not contain many new sensors, but features several fixes and improvements. It comes with the experimental AWS Alarm v2...
Read the complete blog post here
Read the complete blog post here
Improved
Security
Server |
This version includes an important security update for the PRTG core server. An authenticated user with write access could leverage specifically crafted API calls to create an Execute Program notification template that runs an executable file that is vulnerable to a form of directory traversal. This can lead to a potential Remote Code Execution (RCE) by running an arbitrary file existing on the PRTG core server system under the use of the Security Context of the Core Server Service. (CVE-2021-42253)
Many thanks again to the anonymous reporter. |
Sensors |
We improved the parameter handling of several database sensors to prevent external tools from logging them. The change improves the security of the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, PostgreSQL, Oracle SQL v2, and Oracle Tablespace. |
Fixed
Sensors
Microsoft Azure SQL Database |
We hardened the detection mechanism of the database type when adding a new instance of the Microsoft Azure SQL Database sensor. The sensor showed a down status upon creation in previous versions if the database type had changed from single database to elastic pool or vice-versa. |
Microsoft Azure SQL Database |
You can now define a scanning interval for a running sensor that is lower than the initial scanning interval that was set when creating this sensor. This was not possible for several newer sensor types before this PRTG version. |
Fixed
Server
API |
Switching inheritance off and on with the setobjectproperty.htm API call works again. |
History |
Cloning a device now adds an entry to the History tab of the parent group on which the device clone is newly created. |
Probe connections |
Probes now automatically retry to connect to the PRTG server when their initial login to the server failed. This prevents certain cases where the sensors on the probe remained in the unknown status after starting the PRTG server. |
Stability |
We implemented several minor stability improvements for the PRTG core server. |
Startup |
We fixed the case where missing entries in custom language files prevented the PRTG core server from starting. |
Fixed
WebGUI
User accounts |
You can mark the passhash in your user account settings in Firefox again to easier copy and paste it. |
Lab
Sensors
AWS Alarm v2 |
You can try out the experimental AWS Alarm v2 (BETA) sensor as of this version and monitor your favorite metric and composite AWS alarms with this sensor type. |
AWS RDS v2 |
We implemented several minor improvements for the experimental AWS RDS v2 (BETA) sensor. |
HPE 3PAR Drive Enclosure |
We fixed an issue with the experimental HPE 3PAR Drive Enclosure (BETA) sensor that could not handle certain data that HPE 3PAR devices may return. The sensor showed a down status with a parsing error in such cases. |
HPE 3PAR Virtual Volume |
We added five new channels to the experimental HPE 3PAR Virtual Volume (BETA) sensor that show the full total of used and reserved space. We also renamed the channels User Space Total and Snapshot Space Total to User Space Reserved and Snapshot Space Reserved to better indicate what they monitor. The new channel names only apply to newly added instances of this sensor type. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German language file |

September 21st 2021 – Version 21.3.71.1416
Blog article
PRTG 21.3.71 with new IoT, AWS and Redfish sensors

Our latest version of Paessler PRTG Network Monitor is now available in the stable release channel.
Read the complete blog post here
Read the complete blog post here
New
Sensors
Beckhoff IPC System Health |
The new Beckhoff IPC System Health sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. It shows available memory, CPU load, the temperature of CPU and mainboard, as well as the status of the RAID controller. We initially released this sensor type as experimental sensor in PRTG 21.2.67. |
Modbus RTU Custom |
The new Modbus RTU Custom sensor connects to a Modbus RTU server and monitors up to five values returned by the device. With this sensor type, you can monitor, for example, temperature, humidity, and more inside a rack in your datacenter so that you can ensure your equipment operates within the defined ranges. We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions. |
Improved
Sensors
MQTT Subscribe Custom |
You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value with the MQTT Subscribe Custom sensor. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently. |
Improved
Server
API |
The API call api/health.json now additionally returns the number of State objects, which corresponds to the number of currently logged in PRTG user accounts. We also added api/health.json to the public API documentation in the PRTG user manual. |
Reports |
PRTG now generates your PDF and HTML reports much faster compared to previous versions. You will especially notice this performance improvement when running reports with a lot of sensors and historic data on large installations. |
Fixed
Sensors
Common SaaS |
The Twitter channel of the Common SaaS sensor now supports response code 426. In previous versions, the sensor occasionally showed a warning status with the message Twitter API not available - HTTP/1.1 426 Upgrade Required if Twitter returned this code. |
DNS v2 |
You can add the DNS v2 sensor via auto-discovery again. |
EXE/Script sensors |
We updated the sample PowerShell scripts that we deliver for EXE/Script sensors to work with the enabled PowerShell Security Enhancement setting. The scripts now use write-output instead of write-host. We also encourage you again to accordingly adapt your own scripts to write-output to successfully run your custom PowerShell sensors with enabled security enhancement. |
Flow and Packet Sniffer sensors |
PRTG now properly handles whitespaces in group names and captions when you change the default groups and channels for Flow and Packet Sniffer sensors (via CustomFlowRules.osr, for example). In previous version, whitespaces led to a disabled Save button on the Settings tab of Flow and Packet Sniffer sensors. |
HPE 3PAR sensors |
We fixed an issue with HPE 3PAR sensors that could cause the probe to stop monitoring if you had a certain number of running HPE 3PAR sensors on this probe. All sensors on the affected probe showed the unknown status in such cases. We also improved the stability of HPE 3PAR sensors in case of reconnects where the sensors previously were not able to recover from the down status in some cases. The issues affected the HPE 3PAR Common Provisioning Group sensor, as well as the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA). |
Modbus sensors |
We fixed connection issues of Modbus TCP Custom and Modbus RTU Custom sensors that appeared in the previous PRTG stable version 21.3.70. Modbus sensors were not able to connect to the target server if the initial attempt failed and showed a permanent down status with the error message The sensor could not retrieve data from the server or similar. |
NetApp LUN |
The NetApp LUN sensor now shows 0% bytes free if the used size exceeds the allocated size, just like the NetApp in its own interface. In previous versions, the sensor showed a completely incorrect value in such cases. |
VMware Virtual Machine (SOAP) |
Newly created VMware Virtual Machine (SOAP) sensors now have the Alarm when VM is powered off setting enabled by default. |
Sensor creation |
The progress bar in the Working... dialog window that appears when you start adding certain sensor types now also properly visualizes the progress for various sensor types that we implemented over the last couple of PRTG versions. |
Fixed
Security
User accounts |
Paused PRTG user accounts cannot resume other paused user accounts via the API anymore. |
Version number |
PRTG no longer displays the current version number in the footer of the startup screen in the web interface. This improves security by not providing attackers potentially relevant information on a page that does not require a login. |
Fixed
Server
Cluster |
Sensors on failover nodes in status Down (Acknowledged) show timestamps and names of the acknowledging user accounts in the sensor message again. |
User accounts |
User accounts that are member of an Active Directory or single sign-on user group now open the defined homepage of their primary user group when they log in for the first time. In previous versions, they always started on the default welcome page. |
Lab
Sensors
AWS ELB v2 |
We added several new sensor channels for various metrics of application and network load balancers to the AWS ELB v2 (BETA) sensor. |
AWS RDS v2 |
You can try out the experimental AWS RDS v2 (BETA) sensor as of this version. The sensor monitors various metrics of your RDS instances and will be the successor of the existing Amazon CloudWatch RDS sensor. |
Local Folder |
|
Redfish Virtual Disk |
You can try out the experimental Redfish Virtual Disk (BETA) sensor as of this version. The sensor monitors the virtual disks of your Redfish capable servers and shows capacity and status. |
REST Custom v2 |
The REST Custom v2 (BETA) sensor now supports XML in addition to JSON and you can use XPath to define the sensor channels. |
Improved
Various
Languages |
We updated the German language file and implemented some minor improvements for French and Russian. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |

August 17th 2021 – Version 21.3.70.1629
Blog article
New PRTG release 21.3.70 with new Azure, HPE, and Redfish sensors

Just a short while ago, I introduced you to PRTG Release 21.3.69, with a load of new sensors, and now the next version is ready for installation. And this version also comes with brand new stuff!
Read the complete blog post here
Read the complete blog post here
New
Sensors
HPE 3PAR Common Provisioning Group |
The new HPE 3PAR Common Provisioning Group sensor monitors the capacity of a common provisioning group (CPG) on an HPE 3PAR storage system. It shows the overall state of the CPG, as well as free, allocated, and used logical space, snapshot space, and user space. We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions. |
Microsoft Azure SQL Database |
The new Microsoft Azure SQL Database monitors metrics of an Azure SQL Database (single database or elastic pool) in a Microsoft Azure subscription. It can show, for example, CPU and disk usage, number of deadlocks, DTU and eDTU usage and limits, and sessions in percent. We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions. |
Microsoft Azure Storage Account |
The new Microsoft Azure Storage Account sensor monitors the storage account in a Microsoft Azure subscription and shows latency, traffic, and capacity metrics, as well as the number of request breakdowns. We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions. |
Improved
Sensors
Microsoft 365 sensors |
You can now create device templates that include the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced. This enables you to add these sensors via auto-discovery. |
Modbus TCP Custom |
We implemented session sharing for the Modbus TCP Custom sensor and the experimental Modbus RTU Custom sensor. Session sharing reduces the load on the monitored system compared to previous PRTG versions where each sensor created its own connection to the Modbus gateway. |
OPC UA Custom |
The OPC UA Custom sensor now supports up to 10 channels so that you can monitor up to 10 values returned by specific OPC UA node IDs with one sensor of this type. |
WMI Event Log |
The WMI Event Log sensor now supports filtering by multiple event IDs. |
Zoom Service Status |
You can now create device templates that include the Zoom Service Status sensor. This enables you to add sensors of this type via auto-discovery. |
Fixed
Sensors
MySQL (v1) |
Still existing instances of the deprecated sensor type MySQL (v1) work again and continue monitoring upon updating to PRTG 21.3.70 or later. In PRTG versions 21.2.68 and 21.3.69, they showed a down status with the error message parameter -sslmode is missing. Please note that we strongly recommend that you replace all sensors of the deprecated type MySQL (v1) with the MySQL v2 sensor. |
SNMP Custom Table |
Adding SNMP Custom Table sensors with an identification column other than table_index or ifindex properly works again. In previous versions, the sensors showed a down status after creation with error code PE247 in such cases. |
Fixed
Server
Active Directory |
We fixed an issue with the login of Active Directory user accounts. If the display name or full name of a user in the Active Directory contained certain special characters like, for example, ampersand (&), a newly introduced security mechanism blocked the login in the last PRTG version 21.3.69. This also affected PRTG user accounts with two or more consecutive whitespaces in login or display name. |
Cluster |
Failover nodes in a PRTG cluster now keep the password of the PRTG System Administrator user account when you have changed it. In previous versions, the administrator password on failover nodes always reverted to default upon updating the PRTG server. Important: The PRTG default login with password prtgadmin will not work on failover nodes anymore upon updating to PRTG 21.3.70 or later. Please use the PRTG Administration Tool on the failover node to generate a new password. See also the Knowledge Base article Change to requirements for login to the failover node. |
Device templates |
We fixed an issue with certain sensor types like the SNMP HPE ProLiant Memory Controller sensor that, if included, prevented a successful creation of device templates. The created template did not appear in the list of device templates in such cases. |
Single sign-on |
We fixed an issue with external callback URLs for the endpoint handling that included uppercase letters. In such cases, you could not login into PRTG via single sign-on and received the error message The URL you are using to connect to PRTG is not enabled for single sign-on. |
Time zones |
Status messages of down (acknowledged) and paused sensors now show the time zone of the user account instead of the server time. In the logs, the messages are displayed in server time. |
Fixed
WebGUI
Home page URL |
Home page URLs with URL parameters that you define for PRTG user groups work again. In previous versions, parameters were removed from the URL so that the you did not land on the defined home page when you logged in into the PRTG web interface. |
Internet Explorer |
Adding new notification triggers and displaying existing triggers in Internet Explorer 11 works again. |
Lab
Sensors
AWS EC2 v2 and AWS ELB v2 |
We added comprehensible region names to the channels of the experimental AWS EC2 v2 and AWS ELB v2 sensors. |
Local Folder |
We introduce the experimental Local Folder (BETA) sensor with this version. The sensor monitors the number of files and folders in a local folder on the probe device, as well as its size and the age of oldest and newest files. |
Redfish System Health |
You can try out the experimental Redfish System Health (BETA) sensor as of this version. With this sensor, you can monitor the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac. |
Improved
Various
Languages |
We updated and improved all language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |

July 6th 2021 – Version 21.3.69.1333
Blog article
New PRTG release 21.3.69 with new Veeam, AWS and Rittal sensors

This is a brand new PRTG version waiting for you. In release 21.3.69, you can expect the Veeam Backup Job Status Advanced Sensor, which goes from experimental state to normal operation. There are...
Read the complete blog post here
Read the complete blog post here
New
Sensors
Veeam Backup Job Status Advanced |
The new Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs on the Veeam Backup Enterprise Manager. The sensor monitors the status of the backup job, the duration, the time since the last run, and if the backup job is scheduled. We released this sensor type as experimental sensor in PRTG 21.1.65 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we resolved two more issue for this release.
|
Improved
Sensors
Dell EMC Unity Enclosure Health v2 |
The Dell EMC Unity Enclosure Health v2 sensor now can also monitor Power Consumption in a dedicated channel. |
Modbus TCP Custom |
|
MQTT Subscribe Custom |
The MQTT Subscribe Custom sensor now supports up to 10 channels so that you can monitor up to 10 values from a subscribed MQTT topic with one sensor of this type. |
SNMP sensors |
PRTG can now perform more SNMP v3 requests at the same time, so that monitoring with SNMP v3 sensors is more stable compared to previous versions. |
Improved
Security
Active Directory |
PRTG now validates all fields that are imported from Active Directory when creating a new user account to close a potential XSS vulnerability. (CVE-2021-29643) |
Fixed
Sensors
Microsoft Azure sensors |
We improved the stability of the Microsoft Azure sensors. In previous versions, the sensors had connection issues in some cases, which resulted in wrong down and warning states. |
DNS v2 |
The Records Resolved channel of the DNS v2 sensor correctly uses a lookup with the states yes and no again. Add the sensor anew to resolve the issue with the Records Resolved channel. |
Microsoft 365 Service Status sensors |
We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against unknown service states that Microsoft 365 may return. In such cases, the sensors previously showed a down status with the message error.generic[invalid map |
SNMP Printer |
We improved the stability of the SNMP Printer sensor. In rare cases, the sensor showed a down status with the message No such instance (SNMP error # 223) after some time when monitoring certain types of printers. |
Fixed
Server
API |
API calls for tables with content=probenodes return all probes again. |
Auto-Discovery |
Devices now keep their settings even after running an auto-discovery on this device. Previously, the first auto-discovery on a device occasionally overwrote your manually configured settings like names, icons, or tags. |
Graphs |
The graph on the 2 days tabs of sensors shows the correct downtime again. In previous versions, the 2 days tab showed a wrong downtime in various cases, for example, always 0% even if there was a downtime reported and correctly shown in the data table. The percentage values on the y-axis of 2 day graphs are also back again. |
Single sign-on |
Logging in with single sign-on now also works if you use an Azure AD group name (sAMAccountName) with upper-case letters as SSO Group Access Claim. We also fixed the misbehavior that PRTG logged out SSO user accounts after some time. |
Fixed
WebGUI
Maps |
We fixed a display issue on maps that affected channel gauges on View Map tabs. Sometimes, the gauge values of previously opened sensor pages erroneously appeared in gauge map objects instead of the real values until the page was refreshed. |
Lab
Sensors
AWS EC2 v2 |
You can try out the experimental AWS EC2 v2 (BETA) sensor as of this version. The sensor monitors the performance of an Amazon EC2 instance and will be the successor of the existing Amazon CloudWatch EC2 sensor.
Note: If you use the same IAM policy that you use for the Amazon CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG? |
AWS ELB v2 |
You can try out the experimental AWS ELB v2 (BETA) sensor as of this version. The sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor. |
HPE 3PAR sensors |
We implemented session sharing for the HPE 3PAR sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the HPE 3PAR system with every scan. |
REST Custom v2 |
We fixed the Custom Headers of the REST Custom v2 sensor. In the last PRTG version, sending custom HTTP headers did not work correctly. |
SNMP Rittal CMC III Hardware Status |
We introduce the experimental SNMP Rittal CMC III Hardware Status (BETA) sensor with this version. The sensor monitors the hardware status of a Rittal CMC III processing unit and shows the status of every attached external sensor. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated German language file, updated user manual |
Changed
Sensors
DNS sensor |
The DNS (v1) sensor is now deprecated as we previously announced. DNS (v1) sensors that you added in previous versions will continue to monitor after updating to PRTG 21.x.69, but you cannot add sensors of this type anew. Please use the new DNS v2 sensor instead. |
Note
Sensors
SNMP sensors |
In some cases, SNMP sensors show SNMP error 2011 after updating PRTG to version 21.3.69 with the message Could not create SNMP Session (-3000)-2011. The error may occur if the latest updates for the Visual C++ Redistributable Package are missing on the probe system. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/89831. |