SAV25 Data Systems

New PRTG Version Update


New Version Key Features

Improved Sensors


  • PRTG now saves the channel settings of newer sensor types (for example, MQTT sensors) into device templates. Sensors added via auto-discovery automatically apply the configuration and you will not have to manually change the channel settings anymore to keep a consistent monitoring.
  • You can now define include and exclude filters in custom device templates to limit which sensors are actually created during the auto-discovery when usually multiple sensors of the same type would be created (for example, create sensors only for specific drives or ports with a custom device template). For details, see the Knowledge Base article How can I include and exclude sensors from device templates? Note: This option is experimental and might not work properly in every case, so we would love to hear your feedback about it.
  • You can now add IMAP and POP3 sensors that use secured connections (IMAPS and POP3S) via auto-discovery. In previous versions, the auto-discovery only supported unsecured IMAP and POP3 connections.
  • You can now create device templates that include the following recently introduced sensor types to be able to add the sensors via auto-discovery: Dell EMC Unity Enclosure Health v2, Dell EMC Unity File System v2, Dell EMC Unity Storage Capacity v2, Dell EMC Unity Storage LUN v2, Dell EMC Unity Storage Pool v2, Dell EMC Unity VMware Datastore v2, Microsoft Azure Subscription Cost, Microsoft Azure Virtual Machine, Microsoft Azure SQL Database (BETA), Microsoft Azure Storage Account (BETA), OPC UA Server Status, OPC UA Certificate (BETA), OPC UA Custom (BETA)

Improved Notifications


We improved the content of History and Log entries for notification triggers. The entries appear much clearer now to enable you to more comprehensible see changes that added, modified, or removed triggers. We now also display the ID of each existing notification trigger on the notification trigger tabs so that you can better reference the history and log entries.

Thanks to these improvements, you will also easier understand which notification trigger was activated and why and where you configured the trigger.

Improved Server


PRTG is now always installed as 64-bit version if the operating system on which you run the installer is 64-bit, and only installed as 32-bit version if the operating system is 32-bit. PRTG will also install the 64-bit version when you update a PRTG instance that was originally installed as 32-bit version on a 64-bit operating system. Previously, PRTG only checked the available RAM on the server and always installed the 32-bit version whenever there was less than 6GB RAM, even on 64-bit systems.



We reduced the memory consumption of sustained API write calls, for example, when setting object properties via the API.



PRTG now more logically selects the browser on your system that works best with the web interface if you open it with the PRTG Network Monitor shortcut that is automatically created on the server where you install PRTG.

Improved Security


We hardened the log routines in setobjectproperty.htm API calls.



We improved the parameter handling of NetApp cDOT/ONTAP and VMware sensors to prevent external tools from logging them.



We fixed a potential XSS vulnerability on report.htm.

Changed Notifications


We removed all deprecated entries from the list of SMS service providers, which are the outdated BulkSMS endpoints. The removed entries automatically migrate to the corresponding new endpoints BulkSMS All regions (except South Africa) and BulkSMS South Africa with the update to this PRTG version.


For more information on Changed Notifications, read here.

Fixed Sensors


The Common SaaS sensor shows an Up status again if all monitored services are reachable. We had to update the URL that the Dropbox channel uses because Dropbox deprecated their old API. The channel could not reach Dropbox anymore so that the sensor showed a Warning status in default configurations the past few weeks.



  • Custom sensor messages delivered within the element are again displayed in sensor messages and logs of custom sensor types like, for example, HTTP Push Data Advanced.
  • We fixed the rare issue that sometimes custom sensors stopped working after an update due to unintentionally renamed custom sensor files on the probe system.


HTTP Push Data and HTTP Push Data Advanced sensors now keep and display their last value on device overview pages and map objects instead of showing No data after a scanning interval without a new value.



  • We fixed the auto-discovery of the SNMP Custom Table sensor that occasionally did not create new instances of the sensor in the previous PRTG version 20.4.64.
  • You can manually add SNMP Custom Table sensors using table_index as Identification Column again. In the previous PRTG versions 20.4.64 and, adding the sensor using table_index failed with the error message Sorry, the scan for available monitoring items has failed! TPaeInternalList.GetValues: List index out of bounds: [...].
  • The column headers of the table in the sensor settings are displayed again when manually adding the SNMP Custom Table sensor. In the previous PRTG versions 20.4.64 and, the table in the sensor settings had no column headers.


SNMP sensors now will continue to properly work if you change SNMP v3 settings in the Credentials for SNMP Devices section of the parent device or group. In previous versions, changing SNMP v3 settings or switching to SNMP v3 often resulted in a down status of the according SNMP sensors with the error message could not create snmp session -1114 -2011, which you could only resolve with a restart of the PRTG probe service.


For more information on Fixed Sensors, read here.

Fixed Server


Devices that you clone to a remote probe in a cluster are immediately synchronized to the failover node again. In previous versions, the failover node only showed the cloned device after a restart of the failover.



The status message of Down (Acknowledged) displays the PRTG server time again instead of just UTC.



We fixed a misbehavior that occurred after you have changed the login name of a PRTG user account. The old login name was not updated in the internal dictionary nor deleted after changing it so that a new user account with the same login name could not login due to wrong credentials. This could happen, for example, when you added an Active Directory user to replace a local user account with the same login name.



Remote probes that have special characters in their names automatically update and connect to the PRTG server again. In the previous PRTG version 20.4.64, characters like German umlauts or Japanese language characters in probe names prevented remote probes from automatically updating and required a manual update to connect.


For more information on Fixed Server, read here.

Note Sensors


We will discontinue the following sensor types with PRTG version 21.x.67 that we plan to release in Q2 2021. Running sensors of theses types will still work for some more versions, but you will not be able to deploy them as of PRTG 21.x.67. If you use these sensors, we strongly recommend that you replace them with the superseding sensor types soon. If you encounter any remaining issues with the new sensors, please immediately contact us so that we can address them.

  • Cloud HTTP and Cloud Ping: Please use the recently introduced Cloud HTTP v2 and Cloud Ping v2 sensors instead to monitor your web servers and devices with an enhanced feature set and state-of-the-art technologies.
  • REST Dell EMC sensors: Please use the recently introduced Dell EMC Unity v2 sensors instead to monitor your Dell EMC storage systems with an enhanced feature set and state-of-the-art technologies.

Note: With PRTG 21.x.65, we already deprecated the GitLab Build Status sensor. You cannot add this sensor type anymore.



Further in the future, we will discontinue the following sensor types and replace them. These sensors will continue to work as you are used to it until we have introduced full replacements for them. You will find more information about the future development of the sensors on our public roadmap. We would love to get your input for new versions of these sensors!

  • Amazon CloudWatch sensors
  • Docker Container Status
  • REST Custom



Update your PRTG now or submit a ticket to seek for help to update your PRTG!

© 2020 SAV25 DATA SYSTEMS | 146 West Ave, Quezon City, 1104 Metro Manila