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

July 6th 2021 – Version 21.3.69.1333

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.

Adding a new Veeam Backup Job Status Advanced sensor works more reliably now. In certain scenarios, you could not add the sensor and received the error message An error occurred. The queried field is empty.
We added the new lookup value None so that the sensor can now handle the combination job status idle and job result none. Previously, the sensor showed a down status with the error message An error occurred: Bad optional access in such cases.

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	You can now select single bits of input and holding registers to monitor them with the Modbus TCP Custom sensor. This is useful for monitoring Modbus devices that report the on/off status of several inputs as one register, for example. You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently. We also implemented these features for the experimental Modbus RTU Custom (BETA) sensor.
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 key].
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.

May 26th 2021 – Version 21.2.68.1492

Blog article

By Sascha Neumeier • Jun 7, 2021

PRTG version 21.2.68 includes Single Sign-On via Azure AD

…and lots of other interesting stuff! PRTG release 21.2.68 has been available in the stable release channel for a few days. With this version you can login to PRTG via Single Sign-On (SSO) using...
Read the complete blog post here

New

Login

Single sign-on

You can now login to PRTG via single sign-on (SSO). As of PRTG 21.2.68, you can use Azure Active Directory (Azure AD) as SSO provider in PRTG. After configuring Azure AD for PRTG, enable single sign-on in the PRTG system administration and create a user group that uses single sign-on integration. The members of this user group will then use SSO via Azure AD to login to PRTG.

For details about setup and configuration, see this Knowledge Base article. Please note that this feature is only available for PRTG on premises, not for Paessler PRTG Hosted Monitor.

New

Paessler PRTG Hosted Monitor

Regions

We added the cloud region US East for the hosting option of Paessler PRTG Hosted Monitor. Region transfers of instances between Europe and United States (and vice versa) are now possible. Please contact our support for according inquiries.

Improved

Sensors

Cloud HTTP v2 and Cloud Ping v2	We improved the stability of Cloud HTTP v2 and Cloud Ping v2 sensors, which will result in less sensor timeouts than in previous versions. The sensors now also continue monitoring and show data for available regions even if one or more region is not working, and we added a PRTG Cloud Response channel for each region that shows the current status of a region.
Dell EMC Unity v2 sensors	We implemented session sharing for the Dell EMC Unity v2 sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the Dell EMC system with every scan.
Modbus TCP Custom	You can now create device templates that include the Modbus TCP Custom sensor. This enables you to add sensors of this sensor type via auto-discovery.
MySQL v2	The MySQL v2 sensor now provides a dedicated setting for the SSL mode. The options you can choose are the same as the values of the MySQL sslmode parameter. Depending on your monitoring setup, for example with offline installations, you may have to change the setting for successful monitoring.

Improved

Server

HTTP requests

We upgraded the HTTP protocol that PRTG uses in HTTP POST requests to HTTP 1.1. PRTG uses POST requests at several places to call external endpoints. For example, this change affects the notification types email, push, and SMS. If required, you can still switch back to HTTP 1.0 in the according notification template settings.

Improved

Notifications

SMS delivery

We improved the usability of the SMS service provider setup, which will help you to more easily configure SMS notification delivery. All necessary fields now require you to fill them in before saving the settings to ensure you provide all necessary information. By default, the SMS configuration mode is now disabled if you have not had configured SMS delivery before.

Fixed

Sensors

EXE/Script sensors	EXE/Script and EXE/Script Advanced sensors now escape round brackets in the Parameters field to prevent potential code injection.
MQTT Statistics	We fixed an issue with the MQTT Statistics sensor that showed wrong data after some time of monitoring in certain cases.
NetFlow v9 and IPFIX sensors	We corrected the traffic calculation of NetFlow v9 and IPFIX sensors. The sensors reported too much traffic with certain combinations of flow fields.
VMware Host Hardware Status (SOAP)	The VMware Host Hardware Status (SOAP) sensor properly reports errors again. In previous versions, the sensor did not show an alert state if a warning state was already present.
Windows Updates Status (PowerShell)	The Windows Updates Status (PowerShell) sensor now properly applies the Port in SPN setting. In previous versions, the port was not correctly included in the SPN even if you enabled the setting.

Fixed

Server

API	We fixed an issue with API calls that returned no data in certain cases, for example, when querying System Information via /api/table.json.
Channel limits	You can define the same values for upper and lower sensor channel limits again.
Map Designer	We fixed an issue in the map designer that triggered an error dialog window with the message Error (Bad Request). Sorry, the selected object cannot be used here. This happened in the last PRTG version 21.2.67 when you tried to load the preview of an incompatible object type in the properties section of the map.
Probes	We implemented stability improvements for probe connections after a PRTG server restart, which will be especially helpful if you have many remote probes.

Lab

Sensors

REST Custom v2	You can try out the experimental REST Custom v2 (BETA) sensor as of this version. The sensor monitors the results of a JSON REST API call and will be the successor of the existing REST Custom sensor. We are looking forward to your feedback!
Microsoft Azure SQL Database	The experimental Microsoft Azure SQL Database (BETA) now shows correct channel names.

Improved

Various

Languages	We updated the German language file.
All parts of PRTG	Various other minor fixes and improvements, updated user manual

Note

Sensors

DNS sensor

We will discontinue the DNS sensor (v1) with the upcoming PRTG version 21.x.69. Running sensors of this type will still work for some more versions, but you will not be able to deploy them as of PRTG 21.x.69. If you use the sensor, we strongly recommend that you replace it with the superseding sensor type DNS v2 soon. If you encounter any remaining issues with the new DNS v2 sensor, please immediately contact us so that we can address them.

April 21st 2021 – Version 21.2.67.1562

Blog article

By Sascha Neumeier • May 3, 2021

We've released PRTG version 21.2.67 and updated our PRTG roadmap

PRTG 21.2.67 has been available in the stable release channel since last week. With this version, we released the probe-independent Core Health (Autonomous) sensor, as well as three new...
Read the complete blog post here

New

Server

Core Health (Autonomous) sensor

The new Core Health (Autonomous) sensor monitors your PRTG server and is automatically created on the new PRTG Core Server device when you install PRTG 21.x.67 or later. It shows the status of the PRTG core server and checks various parameters of the PRTG core server that have an impact on the stability of the system.

The sensor has the same functionality as the existing Core Health sensor but runs independently of the local probe. Because of this, the sensor still can monitor the status of the PRTG server if the probe is disconnected. This avoids situations that there is no health data for the PRTG server available when the local probe is disconnected so that efficient troubleshooting in case of server issues is still possible.

New

ITOps Board 2.11

Consolidated Components	The new Consolidated Components feature allows you to link together components that have common properties. This feature is helpful if you have components that are monitored by multiple source systems. For example, if a server is being monitored by multiple PRTG sensors, you can consolidate those sensors and the device into one component and designate it as a Computer in ITOps Board. You can then monitor a single computer with all its related sensors as one object.
SLA Reporting Enhancements	This release introduces the following enhancements to SLA reporting. The SLA chart for business services now displays uptime as well as downtime. The SLA table lists the components that contributed to downtime, and now shows both the start time and the end time of the outage that impacted the SLA. You can view which components contributed to downtime and choose to exclude specific outages from SLA calculations. For example, if a component was out of service due to maintenance, but maintenance mode was not scheduled, you can exclude that specific outage from the SLA calculations. You can add notes when you exclude an outage. You can generate and download a PDF report of SLA data for a business service.
Acknowledge Alerts	A new button on the Alerts page allows you to acknowledge an alert that has not yet been resolved. The button is available when you select one or more alerts and click the Action icon.
Google Analytics Option	Google Analytics has been added to this release to help us understand how you use the ITOps Board interface. This information will help us to improve future versions of the product. If you do not want to provide this information, you can disable Google Analytics in the installation wizard. After the installation is complete, administrators can enable or disable Google Analytics from the Settings \| General Settings page.

Improved

Sensors

MQTT Subscribe Custom	The MQTT Subscribe Custom sensor can now show text messages from your IoT devices. Define the Sensor Message JSONPath in the sensor settings and always see the latest message from your system in the sensor message.
Zoom Service Status	We added the channel Webhooks to the Zoom Service Status sensor.

Improved

Security

User accounts

You can set the Homepage URL of a PRTG user account or user group only to web pages of your PRTG instance as of this version. External domains are not allowed anymore to prevent redirects to potentially malicious pages.

Note: Previously defined homepage URLs that violate this rule will prevent you from saving changes to affected user account or user group settings. Please change the homepage URL to a valid page in this case to be able to save the settings again.

Web server

Web pages in PRTG that do not require authentication like help and password recovery pages now return the X-Frame Options HTTP header DENY by default. This security improvement helps to prevent potential phishing attempts. Overriding the header value accordingly applies to these pages, see this Knowledge Base article.

Fixed

Sensors

Exchange (PowerShell) sensors	Exchange (PowerShell) sensors now work with the recent Microsoft Exchange Server security update KB5001779 from April 13, 2021. After applying the Exchange Server update, Exchange (PowerShell) sensors showed a down status with the error message The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details. This affected all Exchange (PowerShell) sensors. Exchange Backup (PowerShell) Exchange Database (PowerShell) Exchange Database DAG (PowerShell) Exchange Mail Queue (PowerShell) Exchange Mailbox (PowerShell) Exchange Public Folder (PowerShell)
Flow sensors	NetFlow, IPFIX, and jFlow sensors now properly ignore flow timestamps if you define 0 as Active Flow Timeout. Previously, this approach only worked in some cases while in other cases flows were disregarded when using 0 as active flow timeout, resulting in incorrect monitoring data. We hardened the flow sensors against unexpected data in received flows that some devices like, for example, Huawei routers may send. In rare cases where this happened, the flow sensors were not able to monitor any flow data and remained in unknown status.
HTTP Transaction	We fixed a memory leak that occurred when using the HTTP Transaction sensor in Alternate/Compatibility Mode.
OPC UA Custom	The OPC UA Custom sensor now supports Int64 values. In previous versions, the sensor showed a down status when reading a node with an Int64 data type.
SNMP Library	The SNMP Library sensor creates sensors and channels for all library OIDs that you select during sensor creation again. In previous versions, some sensor channels were missing after sensor creation if you selected more than one library OID from one category.
SNMP Trap Receiver and Syslog Receiver	You can now use angle brackets (<>) in the message filter of SNMP Trap Receiver and Syslog Receiver sensors.

Fixed

Server

Auto-Update	We improved the stability of auto-updates when PRTG updates to a 64-bit version from a 32-bit version. Previously, the auto-update sometimes failed in such cases and required a manual update.
Channel limits	You can save Limits in sensor channel settings again when using comma as decimal separator. In the previous PRTG version 21.1.66, you received the error message Internal Error: '[value]' is not a valid floating point value when you tried to save the channel settings in this case.
Cluster	Devices that you clone to a remote probe in a cluster are immediately synchronized to failover nodes again. In the previous PRTG version 21.1.66, failover nodes only showed the cloned device after a restart of the failover. Actions on notification contacts like creating, pausing, resuming, deleting are now immediately synchronized to failover nodes.
Gauges	Device overview tabs show gauges of sensors with a 5-star priority with a proper minimum/maximum value range again. In previous versions, the gauges only showed the value range 0 to 1000.
Search	The detailed search now properly works even if a search for objects with special characters returns more than 10 results. In previous versions, the More button that appears when more than 10 results are found opened an empty list of search results in such cases.
Startup	We fixed an issue with the PRTG server that could not start in rare cases due to language files being used by another process.
Toplists	We fixed the toplists of flow and packet sniffer sensors that only showed data for the most current toplist period in some cases.
User accounts	You cannot pause the default PRTG System Administrator (user ID 100) account with another administrator account anymore. In previous versions, this was temporarily possible until a server restart and could result in inconsistent behavior of PRTG.

Fixed

Notifications

Execute HTTP Action

HTTP notifications now use HTTP 1.1 by default to execute HTTP actions. In previous version, the HTTP version always fell back to 1.0, which could lead to issues with several notification targets like Atlassian Opsgenie, for example. If required, you can still switch back to HTTP 1.0 in the notification settings.

Fixed

System Information

Data	The System table on System Information tabs correctly displays MAC addresses again even if they are returned via SNMP. In previous versions, MAC addresses returned via SNMP were not readable.

Fixed

Reports

PDF reports

We fixed a layout issue that caused cut off graph legends with certain page format and orientation combinations in PDF reports.

Lab

Sensors

Beckhoff IPC System Health	We added the experimental Beckhoff IPC System Health (BETA) sensor. The sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. We are looking forward to your feedback!
HPE 3PAR sensors	You can try out the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA) with this version. Of course, your feedback is highly welcome! The HPE 3PAR Drive Enclosure (BETA) sensor monitors a drive enclosure of your HPE 3PAR storage system and shows status and temperature metrics. The HPE 3PAR Virtual Volume (BETA) 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.
PowerShell Security Enhancement	We fixed an issue with the parameter handling of custom EXE/Script sensors that occurred when the experimental feature PowerShell Security Enhancement was enabled. The issue could lead to non-functional EXE/Script sensors in some cases.
Veeam Backup Job Status Advanced	The experimental Veeam Backup Job Status Advanced (BETA) sensor can now monitor backup jobs on Hyper-V platforms. Previously, the sensor creation failed with the error message An error occurred. invalid map in such cases. We fixed an issue with the Status channel that incorrectly showed the status Not Run Yet for a backup job in certain cases.

Improved

Various

Languages	We updated the German language file.
All parts of PRTG	Various other minor fixes and improvements, updated user manual

Changed

Sensors and API

HTTP Push Data Advanced and HTTP IoT Push Data Advanced sensors

We fixed a typo in the Time Threshold (Minutes) property of HTTP Push Data Advanced and HTTP IoT Push Data Advanced sensors. The property is now correctly spelled timethreshold. If you modify or read out this property via the API (setobjectproperty.htm, getobjectproperty.htm), please change the misspelled timethreshhold to timethreshold if necessary.

Changed

Tree version

Tree version update

The configuration file of this version is not downwards compatible with previous PRTG versions.

Changed

Sensors

REST Dell EMC sensors

The REST Dell EMC sensors are now deprecated as we previously announced. REST Dell EMC sensors that you added in previous versions will continue to monitor after updating to PRTG 21.x.67, but you cannot add them anew. This affects the following sensor types.

REST Dell EMC Capacity
REST Dell EMC File System
REST Dell EMC LUN
REST Dell EMC Pool
REST Dell EMC System Health

Please use the new Dell EMC Unity sensors instead to monitor your Dell EMC Unity storage system.

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

Note

Known Issue

Map Designer

In the current PRTG version 21.2.67, object types in the Properties section of the Map Designer that are by design incompatible to the selected object in the Device Tree section return an error dialog window when loading the object preview. The message is Error (Bad Request). Sorry, the selected object cannot be used here. PRTG redirects you to the welcome page when you confirm the dialog window.

This happens, for example, when you select nothing, root, or a probe, group, or device in the device tree and hover your mouse over a live graph or gauge object in the properties section. Note that existing maps that already include an element that is empty due to incompatible object type will show the same error message and will not load.

Workaround: To add a live graph or gauge for a sensor, ensure you have selected the sensor in the device tree section (click the sensor in the device tree section to select it) before you choose an object in the properties section. If you have selected any other object in the device tree section than a sensor, avoid hovering incompatible object types like live graphs or gauges in the properties section.

Status: Resolved with PRTG version 21.2.68.1492.

March 23rd 2021 – Version 21.1.66.1664

Fixed

Probes and Sensors

SNMP v3

We fixed an issue that occurred in the context of sensors using SNMP v3 in the last PRTG version 21.1.66.1623. In several cases, a larger amount of SNMP v3 sensors running on one probe had unexpected impact on the probe health, which caused the sensors on this probe to stop monitoring and to show the unknown status.

March 8th 2021 – Version 21.1.66.1623

Blog article

By Sascha Neumeier • Mar 26, 2021

PRTG 21.1.66 is about OPC UA and improvements to existing sensors

Time for another new release of PRTG Network Monitor. Our latest PRTG version, 21.1.66, is ready for installation and is packed with several new features. That said, have you tried all the new...
Read the complete blog post here

New

Sensors

OPC UA Certificate

The new OPC UA Certificate sensor monitors the certificate of an OPC UA server and helps you to ensure a secure and consistent communication between the machines in your shop floor. We released this sensor type as experimental sensor in the last PRTG version and received valuable feedback that we now implemented to enhance the sensor based on your needs. The following additional features made it into this version.

We added the channel Self Signed that shows if the monitored certificate is self-signed or not.
The sensor shows the certificate thumbprint and the common name in the sensor message.

OPC UA Custom

The new OPC UA Custom sensor monitors the values returned by multiple nodes of an OPC UA server. We released this sensor type as experimental sensor in PRTG 20.4.63 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 added two more features for this release.

The sensor now automatically creates a lookup channel if the OPC UA server returns a Boolean value. By default, the channel will show a down status if the server returns the value 0 (false), and an up status if the server returns 1 (true).
The sensor can now read string nodes from an OPC UA server and display them in the sensor message. You can specify the node ID for the string in the sensor settings and use this feature to display serial numbers of connected modules or the like.

Improved

Sensors

DNS v2	You can now create device templates that include the DNS v2 sensor. This enables you to add sensors of this sensor type via auto-discovery.
Microsoft 365 Service Status Advanced	The Microsoft 365 Service Status Advanced sensor now shows in the sensor message whether an issue is an advisory or incident so that you can easily see the impact of an issue.
Packet Sniffer	We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 1.10. The new version includes several fixes and performance improvements compared to the previously delivered version 0.9987.
Windows Updates Status (PowerShell)	The Windows Updates Status (PowerShell) sensor can now monitor workgroup machines and target systems that are not in the same domain as the PRTG probe. You can define the required authentication method, Kerberos authentication or negotiation authentication, in the sensor settings.
WMI Battery	The WMI Battery sensor can now monitor the battery level of USB connected UPS so that you can ensure there is enough load in case of a power outage.

Improved

Server

User Accounts

PRTG now logs changes to user account passwords and shows which user account changed a password and when. You can view the changes on the History tab of a user account.

Improved

WebGUI

Add Sensor Dialog

Several more sensor types for which required credentials in the parent device settings are missing are now greyed out in the Add Sensor dialog. You cannot add the sensors without providing the credentials anymore. PRTG lists the credentials that you need to provide in this case for each sensor. This will help you to more flawlessly enhance your monitoring with new sensors. The change affects the recently introduced sensor families Dell EMC v2, Microsoft 365, Microsoft Azure, Veeam Backup, and HPE 3PAR (BETA).

Channel Limits

PRTG now validates the limits you enter in sensor channel settings. You cannot save invalid limit combinations anymore like, for example, a higher value for the lower error limit than for the lower warning limit. This will help you to avoid unexpected sensor behavior due to mistakenly defined limit configurations.

Improved

Security

Web Server

We fixed a vulnerability that enabled potential attackers to verify the existence of certain files on the file system of the web server of PRTG by invoking the screenshot functionality of PRTG with special crafted paths. (CVE-2021-27220)

Lab

Sensors

HPE 3PAR Common Provisioning Group	We added the channels Logical space free, User space free, and Snapshot space free to the HPE 3PAR Common Provisioning Group (BETA) sensor.
Microsoft Azure SQL Database	We improved the Add Sensor dialog of the Microsoft Azure SQL Database (BETA) sensor. The table where you select the databases you want to monitor when you add the sensor supports filtering and sorting by DTU and vCore, and you can see if a database belongs to an elastic pool and which one. Additionally, the elastic pool is added to the sensor name upon sensor creation.
Veeam Backup Job Status Advanced	We added the channels Last Job Run and Job Scheduled to the Veeam Backup Job Status Advanced (BETA) sensor. Because of the new channel, we also removed the setting Warn if the job is not scheduled, as well as we improved the help texts for the sensor and the names of lookup states.

Fixed

Sensors

Auto-Discovery	Auto-discovery on IPv6 devices works again. The sensors in according device templates are automatically created when you run the auto-discovery with a device template for an IPv6 device. In previous versions, it was not possible to add sensors via auto-discovery in this case. The standard device template UPS (Generic) now creates sensors with correct unit and scaling for the Current channels.
Dell EMC Unity v2 sensors	Dell EMC Unity v2 sensors now support multiple descriptions in the API response from the target device. Multiple descriptions can appear if there is an issue with a disk in a Dell EMC Unity storage system, for example. In this case, the sensors showed a down status in previous versions and created the log message The received value is an array instead of a single value. Dell EMC v2 sensors now show the correct value and all received descriptions in the sensor message in this case.
Dell EMC Unity VMware Datastore v2	You can now add Dell EMC Unity VMware Datastore v2 sensors to Dell storage systems even if there is a Veeam Backup plugin installed. In previous version, you could not add the sensor to such a device because the scan for available monitoring items failed with the error message An error occurred. (The queried field is empty.)
HTTP Transaction	The HTTP Transaction sensor now supports ports when using smart URL replacement. In previous versions, the sensor did not correctly fill in the parent device's IP address or DNS name if you defined a transaction URL only denoting the port number. The sensor showed a down status with the following message in this case: Failed to establish secure connection [Step 0] Socket Error # 11001 Host not found.
Microsoft 365 Service Status sensors	We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against some unexpected return values. We added a retry setting to avoid sensor errors due to empty responses that the Microsoft 365 API sometimes returns. The error message in such cases is An error occurred. API Response does not contain exactly one result for the workload [...]. We added support for a status return code that the sensors could not handle so far. The error message when the Microsoft 365 API returned such an unknown code was An error occurred. invalid map key.
Microsoft Azure Subscription Cost	We improved the handling of empty fields that Microsoft Azure sometimes returns to the Microsoft Azure Subscription Cost sensor. In previous versions, the sensor only showed a down status in such cases.
Modbus TCP Custom	The Modbus TCP Custom sensor now supports the unit ID 255, which is required for certain target devices. We also implemented the fix for the experimental Modbus RTU Custom (BETA) sensor.
NetFlow and IPFIX sensors	NetFlow and IPFIX sensors now show an expressive error message if one or more IP addresses that were previously selected for binding in the sensor settings are no longer available. This will help you to faster find the error source. The message in this case is The previously selected Network Adapter (with Address ('[IP]') could not be found, please change the sensor settings to an available IP address.
OPC UA sensors	We fixed the issue that some valid client certificates caused a BadCertificateUriInvalid error in OPC UA sensors. The OPC UA sensors could not connect to the target device in such cases due to a different application URI in certificate and sensor.
SNMP sensors	SNMP sensors now support very large values from the numeric SNMP data type Counter64 (unsigned 64-bit integer). In previous versions, SNMP sensors showed the error message [value] is not a valid integer value or wrong values if such a value was returned. The issue was reported by a customer for the SNMP Cisco CBQoS sensor but also affected other SNMP sensor types like SNMP custom sensors, for example.
VMware sensors	We fixed an issue with the session handling of VMware (SOAP) sensors. In the previous PRTG version 21.1.65, the issue caused the sensors to log in and log out on the target system with each sensor scan, which flooded the VMware logs, for example.

Fixed

Server

Cluster	We fixed a potential deadlock that appeared in very rare cases on cluster failover nodes when moving objects from the local probe to the cluster probe, which could crash the system. You can save changes to settings of objects on the cluster probe again. In the previous version 21.1.65, the Save button was always disabled, which made saving changes impossible.
License Activation	We fixed an issue that could prevent automatic license activation in proxy environments.
Notifications	We fixed an issue that prevented notifications from being sent out in rare cases.
Notification Templates	Pausing and resuming notification templates via the notification template list is logged on the History tab of a template again.
Reports	To avoid memory exhaustion, the maximum report interval is now limited to 500 days per report.

Fixed

Server and Probes

Stability

We fixed an issue that could cause instability of the PRTG server and probes in varying forms. This could happen in case of failing Execute Program notifications, failing EXE sensors, or failing script sensors, for example.

Fixed

WebGUI

Alarms as Gauges	We fixed an issue that caused the page Alarms \| Shows as Gauges to not show any sensor gauges. The page remained empty in previous PRTG versions if there was at least one sensor in Down (Acknowledged) status with a closing square bracket (]) at the end of the sensor's error message.
Device Tree	The device tree keeps collapsed and expanded states of all objects again when the page refreshes. In previous versions, all device tree objects were always expanded after a page refresh if you were logged in as read-only user or as read/write user with read access to an object.

Improved

Various

Languages	We updated the German language file.
All parts of PRTG	Various other minor fixes and improvements, updated user manual

Note

Known Issues

Channel Limits	You cannot save Limits in sensor channel settings when using comma as decimal separator. You will get the error message Internal Error: '[value]' is not a valid floating point value in the current PRTG version 21.1.66. Pre-existing limits are not affected and keep working. As a workaround, you can enter the closest integer value like, for example, 1 instead of 0,99 if applicable. The decimal comma is used in several European regions, for example. Status: We are working on a fix for the next PRTG version 21.x.67.
Microsoft 365 Service Status sensors	In some cases, the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced may show a down status after updating PRTG with the error message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. (code: PE270). To resolve the issue, please manually pause and resume affected sensors or restart the PRTG core server service under Setup \| System Administration \| Administrative Tools \| Restart PRTG Core Server Service.
OPC UA Server Status sensor	We strongly recommend that you add running OPC UA Server Status sensors anew after updating from a previous PRTG version for stability reasons. Although you will not directly encounter issues with the sensors, you may notice errors in the core.log file due to an update issue with the underlying functionality of this sensor type.

January 26th 2021 – Version 21.1.65.1767

Blog article

By Sascha Neumeier • Feb 8, 2021

PRTG 21.1.65 contains beta sensors for HPE, Azure, Veeam and OPC UA

The first stable release of 2021 for PRTG Network Monitor is here! By the way: PRTG release 21.1.65 is the 8th version in a row that our developers have programmed completely while working from home.
Read the complete blog post here

New

Experimental Features

Experimental Features	We added the option to enable experimental features in PRTG. Experimental features are still under development and not fully tested, but they are ready enough for you to try them out in a PRTG stable version. This makes it possible for you to already have a look at new upcoming features fresh from our labs without the need to install a PRTG canary version somewhere else, and you can provide us early feedback to enable us to learn from it before making a new feature available for all customers. You can only use an experimental feature if you explicitly enable the according option in the Experimental Features section in the PRTG web interface under Setup \| System Administration \| Monitoring. See also the Knowledge Base article Experimental Features in PRTG.
Beta Sensors	We introduce beta sensors as experimental feature with this PRTG version. As of now, you will only be able to add beta sensors and use them for monitoring if you enable the option in the experimental features section. The following beta sensors are new in this version. HPE 3PAR Common Provisioning Group: The HPE 3PAR Common Provisioning Group (BETA) sensor monitors a CPG of an HPE 3PAR storage system to help you ensure there is enough capacity available on your storage system. Microsoft Azure Storage Account: The Microsoft Azure Storage Account (BETA) sensor monitors your storage account in a Microsoft Azure subscription and shows latency, traffic, and capacity metrics. OPC UA Certificate: The OPC UA Certificate (BETA) sensor monitors the certificate of an OPC UA server and helps you to ensure a secure and consistent communication between the machines in your shop floor. Veeam Backup Job Status Advanced: The Veeam Backup Job Status Advanced (BETA) sensor monitors detailed information of a specific backup job that runs on the Veeam Backup Enterprise Manager. In previous PRTG versions, we already added the experimental sensor types Microsoft Azure SQL Database (BETA), Modbus RTU Custom (BETA), and OPC UA Custom (BETA). Together with the experimental features, we introduce the label NEW for sensor types that we recently added to PRTG and that are already available by default. Sensors with the NEW flag are fully supported and thoroughly tested, and you immediately see in the Add Sensor dialog that there are new sensors that can extend your monitoring. We transition all sensor types that we introduced with a BETA label in the last few PRTG versions to NEW so that you can simply continue your monitoring with these sensors. Older sensor types that still had the beta label are individually handled. We removed the flag for stable sensors and will discontinue and replace the others (see below for more information).
PowerShell Security Enhancement	The experimental feature PowerShell Security Enhancement hides PowerShell parameters that custom EXE/Script sensors use to avoid logging through external tools. This feature also reduces the resource usage of custom PowerShell sensors in certain cases and as such may improve their execution times.

Improved

Sensors

Auto-Discovery	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)
Dell EMC Unity v2 sensors	We added the Total Size channel to the recently introduced Dell EMC Unity sensor types Dell EMC Unity Storage Capacity v2, Dell EMC Unity File System v2, Dell EMC Unity Storage Pool v2, Dell EMC Unity Storage LUN v2, and Dell EMC Unity VMware Datastore v2. Thank you for your feedback that you need this channel for a comprehensive monitoring of your Dell EMC Unity storage systems.
MQTT sensors	You can now use single-level (+) and multi-level (#) wildcards for the Topic that you want to monitor with MQTT Round Trip, MQTT Statistics, and MQTT Subscribe Custom sensors. The MQTT Statistics sensor now monitors Active Topics in a dedicated channel and shows the number of unique topics which send data. This channel enables you be notified if less devices send data as planned.
OPC UA Server Status	All session related channels of the OPC UA Server Status sensor now use counter units (sessions per second #/s) to more comprehensible show if something unusual is going on.

Improved

Notifications

Notification Triggers

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

Installer	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.
Memory	We reduced the memory consumption of sustained API write calls, for example, when setting object properties via the API.
PRTG GUI Starter	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

API	We hardened the log routines in setobjectproperty.htm API calls.
Sensors	We improved the parameter handling of NetApp cDOT/ONTAP and VMware sensors to prevent external tools from logging them.
Web Server	We fixed a potential XSS vulnerability on report.htm.

Changed

Notifications

SMS Delivery

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.

If you have not manually changed the service provider to one of the new BulkSMS entries and tested the SMS delivery in previous versions, please check if PRTG still can send SMS messages after the update. The new BulkSMS endpoints use HTTPS (443) and as such you might need to adjust your firewall rules if you limit internet access from the PRTG server.

You can check your SMS delivery configuration and a successful delivery of SMS with the Test SMS Delivery button in the SMS Delivery settings. See the PRTG manual for details.

We also cleaned up the list of SMS service providers and only list the names of the providers now. You can still find endpoint, protocol, port, and additional information for each provider in the help box.

Fixed

Sensors

Common SaaS	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 Sensors	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 sensors	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.
Microsoft Azure Virtual Machine	We improved the scan for available virtual machines (meta-scan) when you add the recently introduced Microsoft Azure Virtual Machine sensor. Previously, you could not create the sensor if the response of the meta-scan included UTF-8 characters. You received the error message An error occurred. The received JSON data could not be parsed. in this case.
NetApp cDOT/ONTAP sensors	This version comes with several improvements and fixes for NetApp sensors that monitor NetApp cDOT or ONTAP storage aggregates by accessing the API via SOAP. In general, we improved the approach on how the sensor names are automatically created when you add a new NetApp sensor, as well as manually changed sensor names are now correctly applied. We also fixed the Timeout (Sec.) setting that always applied 60 seconds when you added the sensor, no matter which value you entered, and we removed the beta flag from NetApp sensors where it still was there. The following changes apply to specific NetApp sensors. NetApp Aggregate: Bytes free % is now the primary channel by default. This channel is more useful for most customers than the previous primary channel Files. NetApp LIF: The channels Data received and Data sent now correctly show counter values instead of the sum. NetApp NIC: We added the lookup status Not available to the Healthy channel to prevent KeyNotFoundException errors and renamed the states Yes and No to Healthy and Unhealthy. NetApp SnapMirror: Created sensors are now named according to the destination instead of source, following the NetApp standard. We also changed the Lag channel to not show all decimal places anymore by default but to use the automatic approach. NetApp Volume: Size free % is now the primary channel by default. This channel is more useful for most customers than the previous primary channel Snapshot reserve free %. We also fixed an issue that appeared due to number converting when snapshots were too old.
REST Custom	The REST Custom sensor now supports angle brackets (<>) in POST requests to be able to correctly send XML to the target device, for example.
SNMP Cisco ASA VPN Traffic	We fixed the Sensor Behavior setting of the SNMP Cisco ASA VPN Traffic sensor. The sensor shows the correct status again if no connection is active just as you have defined it in the sensor settings.
SNMP Custom Table	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 20.4.65.1667, 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 20.4.65.1667, the table in the sensor settings had no column headers.
SNMP v3 sensors	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.
Veeam Backup Job Status	We fixed the limits of the Job Runs Warning and Job Runs Failed channels of the recently introduced Veeam Backup Job Status sensor. The channels now only cause a warning or down status if there is at least one warning or failed job run. We also shortened the channel names and improved the sensor help to make clearer for you what and how this sensor monitors.

Fixed

Server

Active Directory	Active Directory integration now supports angle brackets (<>) in the access password if you use explicit credentials.
Cluster	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.
Down (Acknowledged)	The status message of Down (Acknowledged) displays the PRTG server time again instead of just UTC.
Login	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	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.
Various	We implemented several other minor fixes and improvements for the PRTG core server.

Fixed

WebGUI

Login

Nombre de inicio de sesión has the correct position on the Spanish login page again and does not overlay the input field anymore.

Improved

Various

Languages	We updated and improved all language files.
All parts of PRTG	Various other minor fixes and improvements, updated user manual

Note

Sensors

Discontinued Sensors with PRTG 21.x.67

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. (Update: Cloud HTTP and Cloud Ping sensors are not yet discontinued with PRTG 21.2.67 due to necessary stability improvements for the v2 sensors. We will discontinue both sensor types in another upcoming PRTG version.)
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.

Discontinued Sensors Forecast

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

November 24th 2020 – Version 20.4.64.1402

Blog article

By Sascha Neumeier • Dec 4, 2020

PRTG 20.4.64 includes native sensors for Veeam and Azure

PRTG Network Monitor release 20.4.64 is our 10th scheduled version this year, and it includes a lot of great stuff! PRTG 20.4.64 comes with three new sensor types, including the first one for...
Read the complete blog post here

New

Sensors

Dell EMC Unity Enclosure Health v2	The new Dell EMC Unity Enclosure Health v2 BETA sensor monitors the health of a disk-array enclosure (DAE) or a physical or virtual disk processor enclosure (DPE) on a Dell EMC storage system. It shows the health status and, depending on the target device, temperatures as well as the status of cooling modules, drives, storage processors, power supplies, and link control cards. This sensor will help you to ensure your Dell EMC Unity enclosure is always working as expected.
Microsoft Azure Subscription Cost	The new Microsoft Azure Subscription Cost BETA sensor monitors the cost in a Microsoft Azure subscription so that you can keep track of the overall expenses of your subscription. It shows the current and previous period cost, the cost forecast, user budgets, and the most expensive service by category.
Veeam Backup Job Status	The new Veeam Backup Job Status BETA sensor monitors the status of all backup job runs on the Veeam Backup Enterprise Manager in the last 24 hours. It shows the number of successful and failed job runs, running and finished job runs, job runs in warning states, and scheduled backup jobs. This sensor gives you a general overview of the status of your backup jobs so that you see the jobs which need your immediate attention at a glance.

Improved

Sensors

Modbus TCP Custom	Thanks to your feedback, we implemented several improvements for the Modbus TCP Custom BETA sensor that we introduced in the last PRTG version. We improved the usage of the sensor settings. We increased the range for register addresses. Register numbers can now start from 0. You can define a lower scanning interval than 60 seconds. The sensor log provides more information. We updated help texts and documentation. Important: After updating from PRTG 20.4.63 to 20.4.64 or later, you will have to add the sensor anew. Running Modbus TCP Custom sensors will show a down status after you have installed the update due to changes in our underlying Modbus monitoring configuration.
MQTT sensors	You can now create device templates that include the sensor types MQTT Round Trip, MQTT Statistics, and MQTT Subscribe Custom. You can use the device templates to add MQTT sensors via auto-discovery.
MySQL v2	The MySQL v2 sensor now supports authentication with caching_sha2_password on MySQL 8.0 and later. In previous versions, the sensor showed the error message Authentication method 'caching_sha2_password' not supported by any of the available plugin when you tried to monitor MySQL server version 8.0.
OPC UA Server Status	We further improved the OPC UA Server Status BETA sensor that we introduced in the last PRTG version. Thank you for your feedback! The sensor can now monitor session related metrics if diagnostics data is activated on the server, so that PRTG can notify you if there are too many ongoing sessions or the amount of timeout sessions increases. We added support for authentication with username and password, as well as you can use encryption and provide a certificate to authenticate the sensor against the OPC UA server. We improved the general performance of OPC UA sensors in this version by minimizing their network communication. We drastically reduced the amount of log entries that OPC UA sensors write into the probe.log file.
SSL Certificate	The SSL Certificate sensor has a new timeout setting for TCP read requests, which is useful if you monitor a slow server with the sensor.

Fixed

Sensors

Cisco IP SLA	Tag and Owner are now in the correct column when adding the Cisco IP SLA sensor. Furthermore, the sensor will not erroneously add a vendors_cisco tag to a device anymore when you run an auto-discovery and the discovered device is not a Cisco device.
Google Analytics	You can add Google Analytics sensors again. The sensor type needed a new OAuth verification by Google to be able to access data.
HTTP Push Data sensor	The HTTP Push Data Advanced sensor now applies the unit to a channel value if provided in the push message and as defined in the Channel Unit Configuration settings.
HTTP Transaction	Smart URL Replacement in the HTTP Transaction sensor now even works if you use the Alternate/Compatibility Mode as Monitoring Engine. In previous versions, the URL replacement only worked with the recommended default monitoring engine. Please note that support for ports in smart URL replacement when using the compatibility mode will only come with a later version.
SNMP Custom Table	We fixed an issue with SNMP Custom Table sensors that are created via auto-discovery. In certain cases, the sensors were created with invalid IDs and uncommon sensor names and immediately showed a down status after creation.
SQL v2 sensors	We fixed an issue with SQL v2 sensors that caused a down status with the message Error: An item with the same key has already been added because PRTG did not properly reset the parameters after a sensor timeout.
WMI sensors	The auto-discovery with template can add certain WMI sensors again. In previous versions, you could not add the sensor types WMI Exchange Server, WMI Sharepoint Process, and WMI Vital System Data v2 sensors, for example, by using an auto-discovery with template.

Fixed

Server

Active Directory	If you change the Login Name of an Active Directory user account in PRTG, it is not possible anymore to login with the changed login name because this user account does not exist in the Active Directory. The login with the original login name still works and will create a new Active Directory user account in PRTG. In previous version, the behavior in such cases was unreliable.
API	We fixed an issue with historic data queries via the PRTG API. In certain scenarios, the queries could take too much time since we improved the memory consumption of historic data queries in PRTG 20.1.57.
Config	We fixed a potential deadlock that could happen when PRTG saved the configuration, resulting in a server crash in rare cases.
Languages	The Local Probe now keeps its name after a server restart in Japanese, Russian, and Chinese language versions. In previous versions, the name of the probe was overridden by question marks (??) after a restart.
Login	We fixed an issue with the login of PRTG user accounts that occurred in rare cases when changing the password of a user who was logged in into PRTG Desktop at the same time. A re-login was not possible for some time in such cases.
Maps	We fixed a potential deadlock that could happen in rare cases when using the Map Designer. PRTG became unresponsive in such cases and required a server restart to work again.
Multi-Edit	You can edit the settings of multiple devices, groups, and probes at once again. In previous versions, multi-edit on these objects resulted in an error with the message The validation of the data you entered has failed when you saved your changes. Multi-editing limits of sensors now properly works for sensors with channels that display data in percent of the maximum value. In previous versions, the applied limit values were incorrect if two or more multi-edited channels had different maximum values.
Notification Templates	We removed some redundant entries from the History tab of notification templates that still appeared on 64-bit installations of PRTG.
Reports	Links to sensors and devices in PDF reports work again. In previous versions, the links included a wrong port and could not be opened.
Uninstall	We fixed an issue that prevented a clean uninstall of PRTG on Windows 10 Pro 64-bit instances.

Fixed

WebGUI

Libraries

You can collapse and expand library nodes again.

Fixed

System Information

Data	The System table on System Information tabs shows data for specific SNMP devices again. In previous versions, PRTG could not retrieve system information data from SNMP devices if an interface had multiple IP addresses. You received the message Error: duplicates not allowed in this case.

Fixed

PRTG for Android

Sorting

Sorting by status in the alarms section of PRTG for Android corresponds to the sorting in the web interface again if you connect your app to PRTG version 20.4.64 and later.

Note

Sensors

Beta Sensors

The following sensor types are not in beta status anymore and are now fully supported.

AWS Cost
Cloud HTTP v2
Cloud Ping v2
DNS v2
Microsoft 365 Service Status
Microsoft 365 Service Status Advanced
MQTT Round Trip
MQTT Statistics
SNMP Nutanix Cluster Health
SNMP Nutanix Hypervisor
SNMP Fujitsu System Health v2
WMI Microsoft SQL Server 2019
Zoom Service Status

Experimental Sensors

We added two new experimental sensors that you can manually enable.

Microsoft Azure SQL Database: The experimental Microsoft Azure SQL Database sensor monitors your Microsoft Azure SQL Database instances so that you are notified if there is an issue with your SQL instance. The sensor in the current experimental status has the known issue that the sensor will stop working as expected it if the database type changes or has changed from vCore to DTU or vice-versa. If you try out the sensor and encounter this issue, we would kindly ask you to contact us and provide the sensor logs if possible. This will help us to further develop the sensor.
Modbus RTU Custom: The experimental Modbus RTU Custom sensor monitors up to 5 values that your Modbus RTU device returns.

Improved

Various

All parts of PRTG

Various other minor fixes and improvements, updated user manual, updated German language file

Note

Known Issue

Remote Probes

Some customers reported connection issues of remote probes after the update to PRTG 20.4.64.1402. We found out that special characters in the name of a remote probe can prevent the probe from receiving the update and from connecting to the PRTG server. Characters that may cause this issue are, for example, German umlauts (ä, ö, ü) or Japanese language characters.

Workaround: To reconnect an affected remote probe in such a case, manually update the remote probe (download the remote probe installer from the web interface and run it on the remote probe system), or open the PRTG Administration Tool on the remote probe system and remove special characters from the name of the probe under probe settings until we can provide a fix.

October 29th 2020 – Version 20.4.63.1427

Fixed

Libraries

Library Filters

Filters in libraries properly work again. In the previous PRTG version 20.4.63.1412, filtering on a Linked Object did not work. A library node always showed all sensors of a PRTG instance that matched the filter, not only matching sensors of the linked object. Furthermore, Filter by Tags had issues with correct filtering so that the library node showed wrong or no sensors in some scenarios.

October 20th 2020 – Version 20.4.63.1412

Blog article

By Sascha Neumeier • Nov 6, 2020

5 brand-new sensors! PRTG Network Monitor 20.4.63 released

It was at the end of October when we released our PRTG Network Monitor Release 20.4.63 as a stable release. Some of you are probably already working with the latest version, all others can't wait...
Read the complete blog post here

New

Sensors

Dell EMC Unity VMware Datastore v2	The new Dell EMC Unity VMware Datastore v2 BETA sensor monitors a VMware datastore on your Dell EMC Unity storage system. With this sensor type, you can keep track of the free size of a VMware datastore on your Dell EMC storage, as well as you will always see the number of hosts, virtual machines, and virtual drives at a glance.
Microsoft Azure Virtual Machine	The new Microsoft Azure Virtual Machine BETA sensor monitors the status of a virtual machine in a Microsoft Azure subscription. Additionally to the overall status of a virtual machine, you can also monitor CPU usage as well as used and remaining CPU credits with this sensor. This will help you to act before your credits run out and the virtual machine stops.
Modbus TCP Custom	The new Modbus TCP Custom BETA sensor monitors values that your Modbus TCP server returns. With this new sensor type, you can keep an eye on your environment equipment like cooling units, power supply, backup generators, and temperature. This helps you to ensure your infrastructure always runs at its best.
OPC UA Server Status	The new OPC UA Server Status BETA sensor monitors status, uptime, and diagnostic information of your OPC UA server. With this new sensor type you can ensure your devices are available using OPC UA and your production processes run flawlessly. In this version, you can also try out an experimental OPC UA Custom sensor that you can manually enable. The sensor monitors multiple nodes of OPC UA servers and returns the contained values.
Soffico Orchestra Channel Health	The new Soffico Orchestra Channel Health BETA sensor monitors the availability of the Soffico Orchestra API and shows the status and overall number of successful and failed channel calls.

Improved

Sensors

Cloud HTTP v2	The Cloud HTTP v2 BETA sensor now supports Smart URL Replacement like other HTTP sensors. With this functionality, you can easier define custom URLs that you want to monitor with this sensor type.
Exchange (PowerShell) sensors	You can now monitor Exchange Server 2019 with all Exchange (PowerShell) sensors. The sensor types support all Exchange server versions as of 2010. Exchange Backup (PowerShell) Exchange Database DAG (PowerShell) Exchange Database (PowerShell) Exchange Mailbox (PowerShell) Exchange Mail Queue (PowerShell) Exchange Public Folder (PowerShell)
SNMP Cisco ASA VPN Connections	We improved the error handling of the SNMP Cisco ASA VPN Connections sensor. In cases where the requested OID of a channel is missing on the target device, the OID is now shown in the sensor message with according information and the sensor keeps its status. In previous versions, the sensor showed a down status with the error message "No such object" (SNMP error # 222) in such cases even if other channels were able to retrieve data.
SNMP Cisco ASA VPN Traffic	We added the option to monitor VPN connections that work with IKEv2 tunnels to the SNMP Cisco ASA VPN Traffic sensor. You can choose the new IKEv1 and IKEv2 option in the IKE Version Handling section of the sensor settings in this case. Note: This option is in beta status and might not work properly in every case, so we would love to hear your feedback about it. Please send it to [email protected].

Changed

Sensors

Microsoft 365 Service Status

Degraded services in the Microsoft 365 Service Status BETA sensor now result in a warning status instead of down by default. This change also corresponds to the status definition of degraded services in the Microsoft 365 Service Status Advanced BETA sensor, where degraded services were always defined as warning status.

Improved

Notifications

Notification Templates

We improved the content of the History tab for notification templates. The history of a notification template now only shows one entry per creation or modification and only the settings that were actually changed. The entries have a clearer wording aligned to other places in the web interface and referenced objects are written with both their name and ID. This will help you with tracking the creation and changes of a specific notification template.

Notification Triggers

You can now define if you want to inherit notification triggers from parent objects for new sensor types. Several sensor types that we added over the last few PRTG versions were missing the inherit option on their Notification Triggers tab and showed the message (Property not found) instead.

Improved

Server

Libraries

We slightly improved the performance of libraries by changing the approach of how libraries are calculated to event-based instead of doing regular polling. You will especially benefit from this improvement if you have libraries with a high amount of sensors.

Fixed

Sensors

Sensor Messages

Sensors now keep their messages even if you change a channel setting like limits or spike filter that causes a recalculation. In older PRTG versions, the current sensor message disappeared after such a change.

Sensor Statistics

Sensors now show a calculated value for uptime, downtime, and coverage in the general information section on a sensor's overview tab even if they never left the down status but receive values. This can be the case if limits are breached or lookup values cause the down status directly upon sensor creation. In older PRTG versions, sensors showed N/A for uptime, downtime, and coverage in such cases.

Fixed

Server

API

We fixed an inconsistency that appeared in the results of the column groupnum in getobjectstatus.htm API calls in certain cases. Depending on your device tree structure, the call sometimes returned incorrect values for the number of groups.

As of this version, groupnum always returns the correct number of subgroups if you perform the call for a specific group, and the number of all groups plus one for root if you perform the call for root (id=0) just as shown on the system status page.

Fixed

WebGUI

System Information

The column headers of tables on System Information pages are correctly displayed again.

Improved

Various

Language Files	We updated the German and Japanese language files.
All parts of PRTG	Various other minor fixes and improvements, updated user manual

Changed

Tree version

Tree version update

The configuration file of this version is not downwards compatible with previous PRTG versions.

Note

Known Issue

Libraries

We detected an issue with libraries in PRTG version 20.4.63.1412. Filtering on a Linked Object does not work. A library node will always show all sensors of a PRTG instance that match the filter, not only matching sensors of the linked object. Furthermore, Filter by Tags does not properly work.

If you actively use filtered libraries, especially in combination with notification triggers, we strongly recommend that you do not install PRTG 20.4.63.1412.

Status: Resolved with PRTG version 20.4.63.1427.

September 15th 2020 – Version 20.3.62.1397

Blog article

By Sascha Neumeier • Sep 28, 2020

Another 6 new sensor types in PRTG Network Monitor 20.3.62

After our last release in August with 5 brand new sensor types, PRTG version 20.3.62 again brings a lot of new features. Besides improvements in the context menu and a new notification method, we...
Read the complete blog post here

New

Sensors

Cloud HTTP v2	The new Cloud HTTP v2 BETA sensor monitors a web server and shows the loading times from different locations. It is the successor of the Cloud HTTP sensor introduced with PRTG 14.x.14 that we will deprecate and remove from PRTG in an upcoming version depending on your feedback for the new Cloud HTTP v2 sensor. The new sensor uses a new technology in the backend and comes with an enhanced feature set. For example, you can now individually define the regions that you want to use for the requests.
Cloud Ping v2	The new Cloud Ping v2 BETA sensor monitors the ping times to a device from different locations. It is the successor of the Cloud Ping sensor introduced with PRTG 14.x.14 that we will deprecate and remove from PRTG in an upcoming version depending on your feedback for the new Cloud Ping v2 sensor. The new sensor uses a new technology in the backend and comes with an enhanced feature set. For example, you can now individually define the regions that you want to use for the requests.
Dell EMC Unity File System v2	The new Dell EMC Unity File System v2 BETA sensor monitors a file system on a Dell EMC Unity storage system. It shows free size, allocated size, as well as size and number of snapshots. This new Dell EMC Unity storage sensor supports Unity OE API version 5 and later, which the existing REST Dell EMC File System BETA sensor is not capable of.
Dell EMC Unity Storage Capacity v2	The new Dell EMC Unity Storage Capacity v2 BETA sensor monitors a Dell EMC storage system and shows free size, used size, preallocated size, and subscribed size. This new Dell EMC Unity storage sensor supports Unity OE API version 5 and later, which the existing REST Dell EMC Capacity BETA sensor is not capable of.
Dell EMC Unity Storage Pool v2	The new Dell EMC Unity Storage Pool v2 BETA sensor monitors a storage pool on a Dell EMC Unity storage system. It shows the health status of the storage pool, as wells as several size metrics. This new Dell EMC Unity storage sensor supports Unity OE API version 5 and later, which the existing REST Dell EMC Pool BETA sensor is not capable of.
WMI Microsoft SQL Server 2019	You can now monitor your Microsoft SQL Server 2019 with PRTG! The new WMI Microsoft SQL Server 2019 BETA sensor monitors your database performance and shows values from SQL General Statistics, Access Methods, the Buffer Manager, the Memory Manager, the Locks Manager, and SQL Statistics.

New

Notifications

MQTT Messages

You can now connect PRTG to your MQTT broker and send (publish) messages with placeholders about alerts to a custom topic. Your MQTT infrastructure can then process the messages further.

Together with the three MQTT sensor types that we already released in previous versions, PRTG as an all-inclusive solution will help you to easier operate your MQTT infrastructure, day by day.

Improved

Server

Cluster

We improved the scope of read- and write-locks in PRTG cluster installations. This leads to a slightly better overall cluster performance in certain monitoring configurations.

Improved

WebGUI

Context menus

Context menus in the device tree now better reflect the actual access rights of a PRTG user account. Users with restricted permissions to an object (for example, users with read access to the object) can only click the menu items if they are allowed to perform the corresponding action.

Changed

API

Access rights	Querying access rights via the API as treejson now returns 0 for no rights 100 for read rights 200 for read/write rights In previous versions this was 0 for no rights and 1 for read/write rights. The change was necessary to improve the context menus regarding access rights (see above).
Types	API calls return type_raw without index again. For example, you will now receive device if you perform an according API call instead of device[1] as it was the case in previous versions.

Fixed

Sensors

Google Drive	You can add Google Drive sensors again. The sensor type needed a new OAuth verification by Google to be able to access data. Please note that the Google Analytics sensor is still in the re-verification process and still cannot be created.
SNMP Cisco CBQoS	The SNMP Cisco CBQoS sensor now supports the types tunnel(8) and wirelessInterface(9). In previous versions, created sensors of this type had incorrect names if tunnel or wireless interface were returned by the target device.
VMware Host Hardware Status (SOAP)	The VMware Host Hardware Status (SOAP) sensor now shows an appropriate warning message and instructions if no hardwareStatusInfo is available on the target device. In previous versions, the sensor showed no message in this case.
Zoom Service Status	The Zoom Service Status BETA sensor now supports the status Under Maintenance in all channels. We defined it as Warning status because the monitored Zoom service does not work as expected when it is under maintenance. The new status is necessary to reflect a change in the Zoom API, which recently resulted in an undefined lookup error in the Meeting Telephony Services channel.

Fixed

Server

Cluster

We improved the stability of PRTG cluster updates. In certain cases, it was not possible to update failover nodes due to a failing license check. PRTG showed a License invalid error message in such cases.
We fixed an issue with cluster installations where failover nodes could not properly load language and lookup files on startup when certain sensor types were running on the instance. The failover node did not work anymore in this case. The issue was caused by some of the new sensor types we introduced over the last couple of PRTG versions, for example, DNS v2, AWS Cost, and MQTT sensors.

Geo Maps

We fixed an issue with the automatic resolution of geo locations when adding a new remote probe. Windows systems with a language setting that does not use a point as decimal separator (for example, comma in German) resulted in an invalid format of the coordinates.

Improved

Various

Languages	We updated the German and Dutch language files, as well as we improved translations for Spanish, French, Russian, and Simplified Chinese in several places.
All parts of PRTG	Various other minor fixes and improvements, updated user manual

August 11th 2020 – Version 20.3.61.1649

Blog article

By Sascha Neumeier • Aug 24, 2020

PRTG Network Monitor 20.3.61 includes 5 brand new sensor types

Finally! Our latest PRTG version 20.3.61 has been available for download in the stable channel for a few days now, and the release is a blast! No less than 134 resolved issues including 5 new...
Read the complete blog post here

New

Sensors

Dell EMC Unity Storage LUN v2	The new Dell EMC Unity Storage LUN v2 BETA sensor monitors a LUN on a Dell EMC Unity storage system. It shows the health status of the LUN, as well as several size metrics. This new Dell EMC storage sensor also supports Unity REST API version 5 and later, which the existing REST Dell EMC LUN BETA sensor is not capable of.
Microsoft 365 Service Status	The new Microsoft 365 Service Status BETA sensor monitors the overall status of all services of a Microsoft 365 subscription. It shows the total number of operational services, degraded services, interrupted services, and services in warning status. With the help of this sensor type, you will always see the status of your Microsoft 365 services at a glance and can immediately step in before the workflow of your entire company is affected if there is an issue. See also the Knowledge Base articles How and where do I obtain credentials for Azure AD? and How do I set permissions for the Office 365 Management APIs? for more information on how to add the sensor.
Microsoft 365 Service Status Advanced	The new Microsoft 365 Service Status Advanced BETA sensor monitors the detailed status of all services of a Microsoft 365 subscription. With this sensor, you get a detailed status of all Microsoft 365 applications and products you are subscribed to like, for example, Microsoft Teams, Exchange Online, Skype for Business, OneDrive for Business, or Planner. You can individually define in the Add Sensor dialog which Microsoft 365 services you want to monitor and create a sensor for. See also the Knowledge Base articles How and where do I obtain credentials for Azure AD? and How do I set permissions for the Office 365 Management APIs? for more information on how to add the sensor.
MQTT Subscribe Custom	The new MQTT Subscribe Custom BETA sensor subscribes to an MQTT topic and monitors the returned values. It can show up to five numerical values from the received JSON data. Together with the MQTT Round Trip BETA and MQTT Statistics BETA sensors that we released in previous versions, you are now perfectly equipped for MQTT monitoring with PRTG.
Zoom Service Status	The new Zoom Service Status BETA sensor monitors the global status of each Zoom service. It shows the operational states of the services and according error messages if something went wrong. This new sensor type will help you to always know about the availability of Zoom to be able to immediately react if there is an issue, which is especially important if your company relies on remote work via Zoom.

Changed

Sensors

EXE/Script and EXE/Script Advanced

The EXE/Script sensor and the EXE/Script Advanced sensor now require PowerShell 3.0 on the probe and target system, as well as .NET 4.7.2 on the probe system.

MQTT Round Trip and MQTT Statistics

While implementing the new MQTT Subscribe Custom sensor, we also moved the Port setting for the connection to the MQTT broker from the sensor settings to the Credentials for MQTT settings on device, group, and probe level. This affects the existing MQTT Round Trip BETA and MQTT Statistics BETA sensors. Running instances of these sensor types will show a down status with error code PE270 after you have updated to PRTG 20.3.61.

If you use the default port 1883 for MQTT connections, please manually re-scan your MQTT sensors to bring them up again. If you use another port for MQTT connections, please change the port in the Credentials for MQTT settings of the MQTT sensors' parent device (or on group or probe level if you inherit the settings) and re-scan the sensors.

Improved

Sensors

Core Health	The Core Health sensor shows more information about the health of the PRTG core server. It now monitors the number of Notifications in Send Queue, the Number of State Objects, and the number of Probe Messages per Second in 3 new channels. The additional information will help us to better help you if you encounter issues with your PRTG installation.
DNS v2	The DNS v2 BETA sensor now fully supports devices with FQDN or host names. In previous versions, the sensor occasionally was only able to monitor devices that have an IP address defined in the settings.
MQTT sensors	We introduced connection sharing for MQTT sensors. The sensors now open only one connection per broker URL, so in general less clients will be connected to the broker. We improved the error handling of MQTT sensors. For example, the MQTT Round Trip v2 BETA sensor now shows a down status if there are wrong or missing entries in the Client Authentication settings.

Improved

Server

Auto-Discovery	You can now see in the device tree if an auto-discovery for a device is in queue. In this case, the device will show the message Auto-Discovery pending, for example, when there already run auto-discoveries on 10 devices at the same time.
Notification Delivery	You can now also test the configuration of your fallback SMTP relay server in the Notification Delivery settings. PRTG will try to send a test e-mail to both SMTP relay servers if you click Test SMTP Settings and adds an according entry to Logs \| System Events \| Notification Related.

Fixed

Sensors

NetApp Volume	The NetApp Volume BETA sensor can now handle big return values. In previous versions, the sensor showed a down status because a conversion error if, for example, there were snapshots older than a few years on the volume.
SSH Meminfo	The SSH Meminfo sensor is now DASH compatible and can monitor Ubuntu devices again. The SSH Meminfo sensor can now also monitor target systems where /proc/zoneinfo information is not available.

Fixed

Server

Pause	Sensors now resume monitoring after your defined timespan elapsed even if you paused them indefinitely first. In previous versions, the sensors indefinitely kept the paused by user status in such cases.
Reports	We fixed an issue where in rare cases historic data reports for Sensor Factory sensors still did not contain values if you selected No Interval (Display Raw Data) as Average Interval after the initial fix in the last PRTG version.
Time zones	Time zones that you individually define for reports or other PRTG user accounts are saved and correctly applied again.
Various	Several other fixes and improvements for the PRTG server.

Improved

Various

All parts of PRTG

Various other minor fixes and improvements, updated user manual, updated language files (German, Spanish, Portuguese, and French)

Note

PRTG hosted by Paessler

PRTG 20.3.61.1663

PRTG version 20.3.61.1663 that we rolled out on PRTG hosted by Paessler includes the same changes as PRTG 20.3.61.1649. Additionally, it is now possible to use the beta sensor types AWS Cost, DNS v2, MQTT Round Trip, and MQTT Statistics on hosted instances, as well as the sensor types that we newly introduced with PRTG 20.3.61.

Previous Versions
and other Release Channels

This third party content uses Performance cookies. Change your Cookie Settings or

load anyways

*This will leave your Cookie Settings unchanged.

Release notes for the "stable" release channel

July 6th 2021 – Version 21.3.69.1333

New

Sensors

Veeam Backup Job Status Advanced

Improved

Sensors

Dell EMC Unity Enclosure Health v2

Modbus TCP Custom

MQTT Subscribe Custom

SNMP sensors

Improved

Security

Active Directory

Fixed

Sensors

Microsoft Azure sensors

DNS v2

Microsoft 365 Service Status sensors

SNMP Printer

Fixed

Server

API

Auto-Discovery

Graphs

Single sign-on

Fixed

WebGUI

Maps

Lab

Sensors

AWS EC2 v2

AWS ELB v2

HPE 3PAR sensors

REST Custom v2

SNMP Rittal CMC III Hardware Status

Improved

Various

All parts of PRTG

Changed

Sensors

DNS sensor

May 26th 2021 – Version 21.2.68.1492

Blog article

PRTG version 21.2.68 includes Single Sign-On via Azure AD

New

Login

Single sign-on

New

Paessler PRTG Hosted Monitor

Regions

Improved

Sensors

Cloud HTTP v2 and Cloud Ping v2

Dell EMC Unity v2 sensors

Modbus TCP Custom

MySQL v2

Improved

Server

HTTP requests

Improved

Notifications

SMS delivery

Fixed

Sensors

EXE/Script sensors

MQTT Statistics

NetFlow v9 and IPFIX sensors

VMware Host Hardware Status (SOAP)

Windows Updates Status (PowerShell)

Fixed

Server

API

Channel limits

Map Designer

Probes

Lab

Sensors

REST Custom v2

Microsoft Azure SQL Database

Release notes
for the "stable" release channel