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
Release Notes
for PRTG 20
Software versions in this channel are not
updated anymore.
Please consider upgrading to the latest "stable" version.
Please use the "Auto-Update" feature to update your PRTG installation
with the latest stable version:
In the PRTG web interface, navigate to Setup | Auto Update.
November 24th 2020 – Version 20.4.64.1402
Blog article
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.
|
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!
|
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 |
|
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.
|
Experimental Sensors |
We added two new experimental sensors that you can manually enable.
|
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
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.
|
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
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
|
Types |
API calls return type_raw without index again. For example, you will now receive |
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 |
|
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
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 |
|
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 |
|
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. |
July 7th 2020 – Version 20.3.60.1623
Blog article
By Sascha Neumeier • Jul 17, 2020
Some news about PRTG Network Monitor version 20.3.60
PRTG version 20.3.60 is available on the stable release channel since a few days ago! The new version contains 163 resolved issues, several security improvements, more options and improvements for...
Read the complete blog post here
Read the complete blog post here
New
PRTG hosted by Paessler
Multi-factor authentication |
You can now log in to my-prtg.com and your hosted PRTG instance with multi-factor authentication. Please see this KB article for more information on how to enable it. |
Custom lookups, MIBs, OIDlibs |
You can now have our support upload your custom MIBs, OIDlibs, lookups, and other custom PRTG files for you. The files will be persistently stored with your instance. Please contact our support team if you would like to upload and use some files of these types to use them with your hosted PRTG instance. |
Improved
Sensors
Amazon CloudWatch sensors |
We added the region Europe (Stockholm) (eu-north-1) to all Amazon CloudWatch sensors so that you are able to monitor AWS instances located there. |
VMware Host Hardware (WBEM) |
We added a lookup file for the Healthstate channel of the VMware Host Hardware (WBEM) sensor to visualize the health status in a more comprehensible way. Note: To apply the new lookup file prtg.standardlookups.esxelementhealthsensor.healthstate, you have to add running sensors of this type anew. |
WMI Disk Health and WMI Storage Pool |
We added the WMI Disk Health sensor to the standard auto-discovery, and the WMI Storage Pool sensor to the detailed auto-discovery. We also removed the beta status from both sensor types. They are now fully supported. Thank you for your feedback! |
Improved
Server
Active Directory |
We added a validation for domain controllers that you can individually define for the PRTG Active Directory integration since the last version 20.2.59. PRTG checks if the IP addresses and DNS names that you enter for primary and backup domain controllers exist and if the according host is a domain controller. If not, you will not be able to save your changes to the settings to avoid issues afterwards. |
Dependencies |
We improved the performance of the dependency calculation. This is especially noticeable when changing dependencies in larger PRTG installations with several thousands of sensors. PRTG now only uses potentially affected monitoring objects in the device tree to calculate dependencies, which significantly reduces the number of performed operations compared to the previous approach. Previously, all objects were considered for calculation, which could result in frequent Ajax timeouts on some large installations due to the huge number of operations. |
Licenses |
We improved the license information for PRTG Enterprise Monitor that appears on various places in PRTG to always provide you correct information about your license. |
Improved
Notifications
Amazon SNS |
|
SMS Delivery |
|
Notification Content |
We improved the handling of notifications that include certain characters like em dash (—) or non-breaking spaces (like in a resolved %history placeholder). In previous versions, notifications including such characters were not properly displayed. |
Improved
Security
Web Server |
|
Sensors |
Minor security fix for the VMware Virtual Machine (SOAP) sensor |
Fixed
Sensors
EXE/Script Advanced |
The meta-scan of EXE/Script Advanced sensor now supports the placeholders %device and %deviceid as described in the Knowledge Base article Using the Meta-Scan Functionality for EXE/Script Advanced Sensors. |
IMAP |
If you change the sensor behavior setting of a running IMAP sensor from the count or process emails option back to the default option Check connectivity only, do not process emails, the connectivity check will now also work without valid credentials. In previous versions, the sensor still used the authentication settings to connect to the mailbox in this case. |
NetApp I/O |
We improved the handling of very big values (64-bit unsigned integer) returned to the NetApp I/O sensor. In previous versions, the sensor showed 0 values in this case due to an issue with the internal value processing. |
SNMP Nutanix Hypervisor |
|
SSL Certificate |
The Days to Expiration channel of the SSL Certificate sensor now uses the hash sign (#) as unit. In previous versions, the channel had no unit. |
Lookups |
If you edit a lookup file that is used by a running sensor, the sensor will reflect the changes on the lookup without the need of a PRTG server restart again. The sensor will show the current status of the lookup file right after you reload the lookup files via the Administrative Tools in the PRTG System Administration. |
Performance Impact Bars |
|
Sensor Channels |
We fixed an issue with very small values (less than 0.0001) in sensor channels having the option to show all decimal places enabled. Sometimes the most significant digit in the channel value was missing in this case. |
Fixed
Server
Auto-Update |
We improved the stability of automatic PRTG updates. In certain cases, the PRTG auto-update did not successfully complete in previous versions and you had to manually install the new PRTG version. |
Passwords |
We fixed an issue with newly generated PRTG Administrator user passwords using the PRTG Administration Tool, for example, on failover nodes in a cluster. Please log in as PRTG Administrator user at least once after generating a new password and perform a proper server restart to ensure the password keeps working after another PRTG server restart. |
Reports |
Historic data reports for Sensor Factory sensors contain values again even if you select No Interval (Display Raw Data) as Average Interval. |
Fixed
Languages
French |
This version comes with the most current French language file again. In the previous PRTG version 20.2.59, we delivered an old French version by accident. Veuillez nous excuser pour la gêne occasionnée. |
Various |
We updated the German, Japanese, and Dutch language files. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
May 26th 2020 – Version 20.2.59.1689
Blog article
By Sascha Neumeier • Jun 10, 2020
PRTG Network Monitor 20.2.59 enhances IoT monitoring capabilities
A quick look at the calendar tells me that it's June 10, 2020. 90% of my colleagues (including myself) continue to work remotely from our homes. This is also reflected in the release 20.2.59 of...
Read the complete blog post here
Read the complete blog post here
New
Sensors
DNS v2 |
The new DNS v2 BETA sensor monitors a DNS server, resolves domain name records, and compares the records to a defined filter. It shows the response time of the DNS server and if records were resolved, the number of records, as well as the number of records matching the filter. With the help of this monitoring data, you can check if resolving a domain works, if the number of certain records changes, and if a certain record exists for a domain. In comparison to the already existing DNS sensor, the new DNS v2 sensor provides more features and works more reliable in certain configurations. For your convenience, the original DNS sensor will still work after the update to PRTG 20.2.59, as well as you can still add sensors of this type, but please note that we may deprecate the DNS sensor at some time in the future. Of course, we will inform you in time before the deprecation. |
MQTT Statistics |
The new MQTT Statistics BETA sensor monitors MQTT topics and shows related statistics of the broker, for example, the number of incoming messages from a subscribed topic and the received payload. With this new sensor type you can check if your IoT devices and the broker still send messages. We are looking forward to hearing your feedback about this new beta sensor! Please send your feedback to [email protected]. |
Changed
Sensors
MQTT Round Trip |
This version comes with a completely rewritten MQTT Round Trip BETA sensor. The new version of this sensor type replaces the original MQTT Round Trip BETA sensor. Any previously deployed MQTT Round Trip BETA sensors will immediately stop working upon updating to PRTG 20.2.59 or later because of the significant changes in the sensor implementation. You have to add the sensors anew after the update to continue your MQTT round trip monitoring. To keep historic data, you can pause existing instances of deprecated sensors. |
Improved
WebGUI
Maps |
We added new map objects for MQTT brokers. This enables you to create maps that visualize the status of your MQTT brokers on your dashboards so that you can identify the status right away. You find the new map objects in the map designer sections Default A and Default B. |
Improved
Sensors
Amazon CloudWatch sensors |
This version includes a minor security improvement for Amazon CloudWatch sensors. |
AWS Cost |
|
Windows Updates Status (PowerShell) |
We added an option to the Windows Updates Status (PowerShell) sensor settings that allows you to include the port number in the SPN (Service Principal Name) used for Kerberos authentication. Use Enable for the Include Port in SPN setting to apply the option. This option might help if your sensor monitors devices where an IIS service or similar is installed and the sensor did not work before. Because the new option is kind of experimental and we cannot say if it works in every case, we really would like to hear about your experience with it! Please send your feedback to [email protected]. |
Improved
Server
Active Directory |
You can now define how PRTG performs Active Directory queries, either by using the domain name or by using specific domain controllers. If you use Active Directory integration, you can choose the desired Domain Access option in the Core & Probe settings of PRTG. You can configure up to two domain controllers, a Primary Domain Controller and optionally a Backup Domain Controller. We also fixed some minor issues that affected the PRTG Active Directory integration. |
Geo Maps |
We improved the validation of coordinates that you enter into the Location (for Geo Maps) field. PRTG now checks if the geocode (longitude and latitude) is in a valid range and shows an error message if not, as well as PRTG tries to automatically correct invalid numbers. The improved validation will help to avoid issues when displaying geo maps. |
Probes |
|
Search |
We improved the stability of the PRTG search function and also fine-tuned the search results. For example, you will not receive a bunch of PRTG tickets anymore as search result when you search for more than one keyword. |
Toplists |
To improve performance and stability, PRTG now more efficiently handles data transmission to toplists and purging of toplists that are used by flow and packet sniffer sensors. |
Fixed
Sensors
SNMP Custom Table |
The SNMP Custom Table sensor correctly replaces OIDs in the sensor name with the value of the referenced column again. |
SSH Meminfo |
We fixed an issue with the SSH Meminfo sensor that occurred in the last PRTG version 20.2.58.1629 when target devices returned values in a certain notation. In this case, the sensor showed error PE094. |
WMI Disk Health |
The WMI Disk Health BETA sensor now supports blanks in the serial number of the monitored disk and continues monitoring this disk even after a PRTG server restart. In previous versions, PRTG removed the blanks upon restarting, so that the sensor was not able to identify the monitored disk anymore and showed an error message (PE016). We recommend that you update soon if you use this sensor type. In future PRTG versions, a seamless update of the sensor without having to add it anew might not be possible anymore because of the fix. |
Fixed
Server
Installer |
We hide the CLI window again that in the last version appeared during the Python installation step when installing or manually updating the PRTG server or a probe. |
PRTG Administration Tool |
We disabled the option to change the Path for probe data storage on the Probe Settings for Monitoring tab when you run the PRTG Administration Tool on the PRTG core server. Please use the option Local Storage of Data Files and Monitoring Database on the Core Server tab to change the path. In previous versions, having the option on both tabs available could be misleading and could result in unexpected behavior when changing the path on the probe settings tab. |
User Accounts |
You can change the settings of user accounts that you added via Add Multiple Users without restarting the PRTG server again. In previous versions, PRTG showed the error message The validation of the data you entered has failed. A user with this login name already exists. Login names have to be unique. in this case. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated German language file, updated user manual |
Note
Sensors
Npcap |
We added a registry key that allows you to individually prevent PRTG from installing Npcap on your PRTG probe machines. This might be necessary in certain scenarios to not interfere with other services. Please note that Packet Sniffer and Packet Sniffer (Custom) sensors need Npcap to monitor your traffic. For details, see the Knowledge Base article How can I disable the installation of Npcap before updating or installing PRTG? |
April 21st 2020 – Version 20.2.58.1629
Blog article
By Sascha Neumeier • May 14, 2020
PRTG version 20.2.58 includes PRTG Enterprise Console remover
I'm a bit late in introducing you to the most interesting features of PRTG version 20.2.58. The release has been available for download in the stable channel since the end of April, and you...
Read the complete blog post here
Read the complete blog post here
Improved
Server
Active Directory |
The PRTG active directory integration now supports LDAP over SSL (LDAPS). You can define to use SSL encryption as LDAP Transport Security in the Active Directory Integration section of your Core & Probes settings. Default is LDAP transport security without encryption. |
Improved
Languages
Japanese |
We completely revised the Japanese language version of PRTG. Thanks to significantly improved texts, the new Japanese version helps you to even better find your way in the PRTG web interface, makes your monitoring tasks easier, and you can enjoy your administrator life even more. If you speak Japanese, we highly recommend this update and trying out the new language file. |
All languages |
We also updated all other language files additionally to the completely revised Japanese version. |
Fixed
Sensors
Business Process (Processus métier) |
You can edit the channel definition settings of the Business Process (Processus métier) sensor again even when using the French language version of PRTG. In previous versions, a malformed link in the French language file made it impossible to add or change the channel definitions. |
HTTP sensors |
HTTP sensors properly support URLs that include a hash sign (#) again. In certain cases, when monitoring URLs that include the character sequence /#/, for example, HTTP sensors encoded the hash sign and showed error 404 (not found). |
HTTP Full Web Page |
The HTTP Full Web Page sensor supports URLs that include an equals sign (=) again. In previous versions, the sensor encoded the equals sign so that the sensor could not monitor the target URL and showed an error. We also increased the sensor message visibility to 255 characters and malformed results now show error PE132. |
Python Script Advanced |
You can install new packages in PRTG Python using pip or easy_install, for example, like normal again. In previous versions, you received an error message in such cases because the PRTG Python post-install script was not working when the base path included whitespaces, which is typically the case in PRTG Network Monitor installation paths. We also updated the Python distribution delivered with PRTG to version 3.7.7. |
SNMP Fujitsu System Health v2 |
We added the missing lookup file for the Redundancy Mode channel of SNMP Fujitsu System Health v2 BETA sensors that monitor the power supply redundancy status (default sensor name: iRMC Power Supply Redundancy: Status). The sensor channel shows a warning status if there is no redundancy, and an up status if there is a PSU redundancy, dual AC redundancy, or triple AC redundancy. |
SNMP Trap Receiver and Syslog Receiver |
SNMP Trap Receiver and Syslog Receiver sensors now purge their messages after 180 days if you select this option in the Purge Messages After settings. In previous versions, both sensor types already purged the messages after 120 days even if you had selected 180 days. |
SSH Meminfo |
The SSH Meminfo sensor now queries MemAvailable instead of MemFree from the target device to monitor the channels Available Memory and Percent Available Memory. This approach reflects the actual RAM usage of Linux systems in a better way and is aligned with the values that the SNMP Linux Meminfo sensor monitors. |
Custom advanced sensors |
We fixed an issue with custom advanced sensors that sometimes showed wrong values in tables (differing by 1 from the correct values) while showing correct values in the data graph. The issue was caused by the Decimal Places channel setting (the custom option worked correctly) and affected sensor types that use XML input like EXE/Script Advanced, Python Script Advanced, SSH Script Advanced, HTTP Push Data Advanced, HTTP IoT Push Data Advanced, HTTP Data Advanced, and REST Custom. |
Fixed
Server
Maps |
|
Probes |
Sensor requests will now be removed from the original probe when you move sensors (directly or via parent devices and groups) from one probe to another probe. In previous versions, the original probe kept on sending monitoring requests for the moved sensors until the requests were deleted by pausing and resuming the moved sensors or by a server restart. This resulted in unnecessary high CPU load on the probe systems. |
Reports |
Historic data reports for Sensor Factory sensors work more reliable now. Certain combinations of report interval and average interval resulted in empty reports in previous versions. |
Passhash |
The Generate new passhash function for PRTG user accounts on PRTG hosted by Paessler instances works again. In previous version, generating a new passhash resulted in an error and so was not possible. |
Note
Enterprise Console
Housekeeping |
We deliver the PRTG Enterprise Console Remover with this PRTG version. With this tool, you can simply uninstall the deprecated Enterprise Console from your server. You find it in your PRTG Network Monitor program folder, as well as there is a shortcut in the Windows Start Menu. |
Note
Sensors
MQTT Round Trip |
The upcoming PRTG version 20.2.59 will include a new, significantly changed MQTT Round Trip sensor. We already inform you now about the change because any previously deployed MQTT Round Trip BETA sensors will immediately stop working upon updating to PRTG 20.2.59 or later and you will have to add them anew. |
Improved
Various
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 Issues
SSH Meminfo sensor |
In certain monitoring scenarios, the SSH Meminfo sensor shows the error message The device you want to monitor is not compatible. The sensor cannot parse the reply data. (code: PE094) after updating to PRTG 20.2.58.1629. This is because the sensor does not support certain notations of the returned values that the sensor now queries. As workaround, you can use the SNMP Linux Meminfo sensor that is not affected by the issue and basically monitors the same values. Status: Resolved with PRTG 20.2.59.1689. |
April 1st 2020 – Version 20.1.57.1786
Blog article
By Sascha Neumeier • Apr 8, 2020
All you need to know about PRTG Release 20.1.57 (and some additional updates…)
It's not that long ago that I wrote about PRTG release 20.1.56 here in the blog. Due to the worldwide COVID-19 situation, I also got a bit confused regarding times and priorities. How we as a...
Read the complete blog post here
Read the complete blog post here
Fixed
Various
API |
Filtering by object ID (filter_obj) properly works again. In the previous PRTG version 20.1.57.1745, API calls using filter_obj returned an empty response file, which affected XML, JSON, and CSV. |
Auto-Discovery |
You can add WMI sensors with the PRTG auto-discovery again. In the previous PRTG version 20.1.57.1745, the auto-discovery for WMI sensors did not work and did not create the sensors. |
March 24th 2020 – Version 20.1.57.1745
Important
Security
Server |
This version includes an important security update for your PRTG core server. We recommend that you update as soon as possible. Please find more details in the email we sent to the email address provided in your license information. Note: You will only receive the email if your PRTG server is affected. The issue was found and reported during a penetration test done by a security researcher. Our thanks go to Nicolas Verdier from TEHTRIS (https://tehtris.com/). (CVE-2020-10374) |
Improved
Sensors
LDAP |
The LDAP sensor now supports LDAP over SSL (LDAPS). If you want to monitor your secured Active Directory server, choose the option Use LDAP over SSL for the sensor setting Connection Security in section LDAP Specific. LDAP without encryption is default. You can also define a custom port for the connection to the LDAP server or use the default port. |
VMware Host Hardware Status (SOAP) |
The VMware Host Hardware Status (SOAP) sensor now categorizes unknown states reported by the VMware host server as entity with its own sensor channel. You also have the sensor settings option to ignore unknown states so that they will not change the sensor status to warning nor appear in the sensor message. The setting Known Warnings is only purposed for warning states of the host server now. Because of this, you may encounter VMware Host Hardware Status (SOAP) sensors that show a new warning status after the PRTG update if the sensors receive unknown states. In this case, please change the Ignore Unknown States setting from the default option to Do not show unknown states if you do not want to have a warning status for unknowns. |
Improved
Server
Notifications |
We added a few more placeholders for notifications. You can use a new placeholder that only resolves to the current sensor status and additional placeholders for elapsed times since status updates.
|
Improved
WebGUI
Reports |
The column in the list of reports that shows the number of sensors included in the last run of a report now also updates if you run an HTML report. In previous version, only PDF reports were considered. We also renamed the column to # Sensors in last run to make it clearer what the numbers actually show. |
Security |
We updated the bootstrap.js plugin that we ship with PRTG because the previously used version 3.2.0 had an XSS vulnerability. (CVE-2019-8331) |
Fixed
Sensors
NetApp Volume |
We fixed an issue with the snapshot time calculation of the NetApp Volume BETA sensor. In certain cases, values of sensor channels like, for example, Latest snapshot and Oldest snapshot did not match the times displayed in the NetApp interface because the sensor mixed up the handling of UTC and local time. |
Sensor channels |
|
WMI sensors |
WMI sensors now show an according error message (PE069) if they do not find any items to monitor on the target device during the meta-scan on sensor creation. |
Fixed
Server
API |
When you use an API call that returns PRTG objects sorted by a numerical property like objid, the returned objects are now numerically sorted. In previous versions, the objects were alphabetically sorted. For example, as of the current PRTG version, IDs (objid) are sorted like [2419, 2470, 10359, 10360], where in previous versions the sorting was [10359, 10360,2419, 2470] in such a case. |
Cluster |
PRTG now shows a correct error message if you provided a wrong cluster access key and try to log in into the failover node so that you can easier help yourself. |
Licensing |
We fixed an issue with the PRTG PLUS license where, in certain cases, PRTG instances erroneously showed the message your license will expire in [x] days so that you had to manually reactivate the license each time this case occurred. |
Maps |
You can add custom background images to maps again. In the previous PRTG version 20.1.56, PRTG showed an internal server error when you selected a file as Custom Image to use as Background Image and tried to save the map settings. |
Memory Usage |
The PRTG server may consume less memory over time in certain monitoring scenarios. We also improved the memory usage of maps that include many historic graph images. |
Reports |
The default Security Context of a report is again the PRTG user account that creates the report. |
Timezones |
The default timezone for newly created user accounts and reports is the system timezone of the PRTG server again. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual including a style update |
Note
Sensors
Npcap |
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 0.9987. |
Beta sensors |
The following sensor types are not in beta status anymore and are now fully supported.
|
Note
Auto-Update
Windows Server 2008 R2 |
If your PRTG server or remote probes run on Windows Server 2008 R2, the PRTG auto-update may fail on these systems because of the Npcap update. The reason is a Windows Security dialog window that appears when trying to install Npcap and that interrupts the PRTG update process. We have also seen cases where the PRTG auto-update succeeded but Packet Sniffer sensors changed to down status (or unknown) with the message that the winpcap.dll is missing. The dialog window comes because of a renewed code signing certificate of the Nmap project (Insecure.Com LLC) and has to be confirmed before PRTG can proceed with the installation. Please manually run the latest PRTG installer on the PRTG server and the remote probe installer on remote probe systems or manually install Npcap if you use Windows Server 2008 R2 and confirm the dialog window. See also the Knowledge Base article PRTG update process is unsuccessful while trying to install Npcap. What can I do? |
Note
Known Issues
API |
Filtering by object ID (filter_obj) does not work in the current PRTG version 20.1.57.1745. API calls that use filter_obj return an empty response file (XML, JSON, CSV). Filtering currently only produces output if you change the parameter of filter_objid by left padding with zeros to length 10 (for example, 0000001002 for object ID 1002). Status: Resolved with PRTG 20.1.57.1786. |
Auto-Discovery |
The PRTG auto-discovery does not add WMI sensors in the current PRTG version 20.1.57.1745. Manually adding WMI sensors still works. Status: Resolved with PRTG 20.1.57.1786. |
February 25th 2020 – Version 20.1.56.1547
Blog article
By Sascha Neumeier • Mar 25, 2020
PRTG Release 20.1.56 comes with an AWS Cost Sensor (and other cool features)
Whew, what's the best way to start today? The stable release 20.1.56 of PRTG Network Monitor was released almost a month ago (which means that the next version, 20.1.57, will be online soon)....
Read the complete blog post here
Read the complete blog post here
New
Sensors
AWS Cost |
The new AWS Cost BETA sensor monitors the costs of your Amazon Web Services (AWS) account. It shows the total costs as well as a forecast of the total costs of your AWS account. You can optionally monitor additional types for costs and forecasts, like the cost types amortized and unblended costs, as well as the forecast types blended and net amortized costs, for example. The AWS Cost sensor will help you to keep an eye on your company AWS account's spending, as well on your single purpose AWS account's spending. If you set up channel limits, it can individually notify you if the costs become too high. |
Improved
WebGUI
Checkboxes |
We improved the appearance of checkboxes. You now find a standard checkbox icon everywhere in the PRTG web interface. In previous versions, PRTG used an individual icon in some sections, for example, in sensor lists, which made it unnecessarily difficult to immediately recognize its meaning. |
Sensors |
The performance impact bar that we added to sensor tabs in the last PRTG version 20.1.55 is now also available in several sensor lists. You can also directly open sensor lists sorted by performance impact from the main menu bar via Sensors | By Performance Impact and from the PRTG Status page, section Sensors by Performance Impact. The lists provide you a quick overview of the performance impact of all running sensors without having to individually look at each sensor, as well as the possibility to perform multi-edit on sensors with a certain impact, for example, to adjust scanning intervals and tweak the performance of PRTG. |
Improved
Server
Active Directory |
We improved the performance of Active Directory user connections to the PRTG server. In rare cases, nearly simultaneous logins and usage with Active Directory based user accounts from PRTG Desktop and PRTG mobile apps were quite slow when the last connections were longer ago. |
Cluster |
Sensors in status Down (Acknowledged) now also show the according sensor log message on cluster failover nodes. |
Notifications |
You can now use placeholders for tags in notifications. With %objecttags you get the tags of the sensor that triggers the notification, %parenttags resolves to all inherited tags, and %tags is for the sensor's tags plus all inherited tags. Using tags in your notifications enables you, for example, to automatically route notifications to the appropriate response teams based on included tags. See also the Knowledge Base article What placeholders can I use with PRTG? |
Password Recovery |
PRTG no longer sends redundant emails during the forgot password process. With the improvements in this context in previous versions, you already get the information from the removed emails in the PRTG web interface. |
Security |
If you change the password of your PRTG user account, the content of the fields Old Password, New Password, and Retype Password is now always masked when the change is written to a log file. If you entered a wrong old password in previous versions so that PRTG could not save the password change, the according error message was logged with the entered old, new, and retyped passwords in clear text on the PRTG server. |
Session Handling |
We implemented further improvements for the handling of user sessions. |
Fixed
Sensors
Cisco IP SLA |
The Cisco IP SLA sensor now even finds interfaces if the meta-scan (querying available interfaces on sensor creation) exceeds 9,000 SNMP requests so that you are able to create all possible instances of the sensor on a large target system. You can also individually define the interface range for the meta-scan of the Cisco IP SLA sensor in the SNMP Compatibility Options of the parent device with the options Start Interface Index and End Interface Index as of this version. |
NetApp SnapMirror |
We fixed an issue with the NetApp SnapMirror BETA sensor that you could not create in certain scenarios. PRTG expected a return field that did not exist in such cases, resulting in error messages like An item with the same key has already been added. or Error: Object reference not set to an instance of an object when trying to add the sensor. |
SIP Options Ping |
We fixed an issue with the SIP Options Ping sensor where in certain cases the authentication failed because of an incorrect realm sent by PRTG. |
SNMP Traffic |
The default primary channel of SNMP Traffic sensors is always the Total channel again. In previous version, SNMP Traffic sensors that you newly added to PRTG with at least one of the Additional Channels came with Traffic In as primary channel. |
VMware Datastore (SOAP) |
The auto-discovery can create VMware Datastore (SOAP) sensors again. This did not work with custom device templates in previous versions. |
Fixed
Server
Maps |
We fixed an issue with public maps that, in rare cases, caused very high CPU load on the server when viewing a public map with changed security context. |
Object Names |
Names of monitoring objects like, for example, sensors, devices, groups, are now properly displayed on the object's details page even if they contain the character sequence left square bracket and a ([a). In previous versions, the name was cut off at this position. |
Sensor Values |
We fixed a rounding issue were numbers close to 0 like 0.01 or -0.01 were mistakenly rounded to 0 in sensor messages instead of correctly showing the decimal places. |
Fixed
WebGUI
Cluster |
Switching the cluster node in map rotation works again. |
Graphs |
The values you enter into Vertical Axis Maximum and Vertical Axis Minimum in section Vertical Axis Scaling of channel settings now even take effect in graphs if you set the Display in percent of maximum option in the channel setting's Data section. |
Libraries |
|
Lookups |
We fixed some minor display issues of bitmask lookups on sensor pages. |
Changed
Sensors
Logging |
PRTG now stores sensor logs in the \Logs\sensors subfolder of your PRTG program data path when the debug option write result to disk is enabled in the sensor settings. By default, this is C:\ProgramData\Paessler\PRTG Network Monitor\Logs\Sensors. In previous versions, sensor logs were written to the folder \Logs (sensors). |
Improved
Various
All Parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German language file |
Note
Sensors
MQTT Round Trip |
We plan major changes to the MQTT Round Trip BETA sensor in an upcoming PRTG version. Once released, the changes will mean that any previously deployed sensors of this type will stop working and you will have to create them anew. We will inform you again as soon as the changes are included in a new PRTG version. |
Note
Known Issue
Maps: Background Image |
In the current version, you cannot add custom background images to maps. When you select a file as Custom Image to use as Background Image for a map and want to save the setting changes, PRTG will show an internal server error and saving is not possible. Status: Resolved with PRTG version 20.1.57.1745. |
January 22nd 2020 – Version 20.1.55.1775
Blog article
By Sascha Neumeier • Feb 7, 2020
First PRTG release in 2020 (20.1.55) contains sensors for Nutanix HCI
Since January 22nd, PRTG version 20.1.55 is available for download in our stable release channel. And once again, the new version has a lot of new features and improvements.
Read the complete blog post here
Read the complete blog post here
New
Sensors
SNMP Nutanix Cluster Health |
The new SNMP Nutanix Cluster Health BETA sensor provides an overview of your Nutanix cluster and shows the status of the cluster, as well as several performance metrics. Additionally to the quick status overview where you can see whether the cluster is started or stopped, for example, the new SNMP Nutanix Cluster Health sensors enables you to check I/O operations per second, used I/O bandwidth, and I/O latency with PRTG. |
SNMP Nutanix Hypervisor |
The new SNMP Nutanix Hypervisor BETA sensor monitors the health of your Nutanix cluster hypervisors. The sensor shows an overview of hypervisor performance metrics like CPU usage, traffic, and I/O data, as well as the number of active virtual machines on a node. |
Improved
Server
Access Rights |
We improved the performance of the access rights check. This will speed up the loading times of objects in PRTG for non-administrative user accounts after the login. In certain cases, loading all objects after the login took quite long for user accounts except for the PRTG system administrator. |
Login |
We modernized the password reset approach that consists of receiving a link by email from where you can set your new password. |
Probe Connections |
We improved the stability of probe connections to the PRTG server. After performance improvements for probe connections in PRTG version 19.2.50, some customers reported issues with the connection stability in certain scenarios. For example, probe reconnects could result in an error state in which the communication between PRTG core server and the probe did not succeed although the connection was established. This resulted in sensors in unknown status on this probe. To prevent such issues, PRTG now uses the unique GID of the probe to identify the probe node and management object and not the ID. Because of this, all GIDs must have a valid format. It is not possible anymore to define any string as probe GID. If you previously used an invalid GID, PRTG will automatically generate a new, valid GID for the probe. For more details, see the article The probe GID of my remote probe changed. What is the reason? in the Knowledge Base. |
Improved
WebGUI
Geo Maps |
If PRTG cannot retrieve data for geo maps when using the Google Maps API because of, for example, a wrong API key or unavailability of the service, PRTG now will show according information in the geo map section and logs to exactly tell you what went wrong. |
Reports |
We improved the appearance of reports that include data graphs. The height of main and monthly graphs is now consistent in all report templates that include graphs. In previous versions, graphs in "graphs only" report templates were very large, so we reduced their size to be able to display channel averages on the same page and so help you to get as much information as possible at a glance. |
Sensors |
You are now able to directly identify the impact on the PRTG system performance of a running sensor in its general information section. Each sensor shows the performance impact bar that you already know from the Add Sensor page on its overview tab, live data tab, and data by days tabs. This information will help you to easier decide about what sensor types to use and which scanning intervals to configure to get the best PRTG system performance possible. |
Improved
Security
Login |
We improved the handling of user sessions. |
WebGUI |
We fixed a potential XSS vulnerability of the PRTG web interface. |
Web Server |
This PRTG version comes with a more strict web server security by default to keep PRTG as secure as possible. TLS 1.2 will be the new default web server connection security. Note: The change may affect you if your PRTG users or third-party systems use outdated versions of browsers or PRTG mobile apps, the Enterprise Console, or old automation tools that interact with the PRTG API. You will receive a ToDo ticket in PRTG with further information. |
Changed
Sensors
Python Script Advanced |
This PRTG version includes a new Python distribution because of the end-of-life announcement for Python 3.4. We replaced the existing paepy library with the prtg library, following the definition of the other custom script advanced sensors. Please review the updated Python Script Advanced sensor example sensor_example.py under Custom Sensors\python in your PRTG program folder and make sure your custom Python scripts are compatible with Python 3.7 when you update PRTG. For more information, see the Knowledge Base article After updating to PRTG 20.1.55, my Python Script Advanced sensors are down. Note: You only need to consider the changes if you are using the Python Script Advanced sensor. PRTG also creates a ToDo ticket with further information for you in this case. |
REST Custom (Sigfox) |
We adjusted the default Sigfox templates for the REST Custom sensor to adapt the Sigfox v2 API. With this change we also combined the device state template (sigfox.device.template) and the token state template (sigfox.device.token.template) into one new template with different channels. Also, required lookup files are available again. Note: To apply these changes, please create a new REST Custom sensor with the template sigfox.device.template. REST Custom sensors that use the old templates will not work anymore. |
WMI Disk Health and WMI Storage Pool |
We implemented some cosmetic improvements for the beta sensors WMI Disk Health and WMI Storage Pool that we newly introduced in the last PRTG version 19.4.54. Note: With these improvements, we also changed the names of some WMI Disk Health and WMI Storage Pool sensor channels. This change may lead to duplicated channels on running instances of these sensor types after updating PRTG. Channels with an old name will not receive data anymore and cannot be deleted. Please add sensors with duplicated sensor channels anew. |
Changed
Geo Maps
Providers |
We removed the deprecated geographical map service provider CloudMade from PRTG. You cannot choose this provider anymore in section Geo Maps of the user interface settings in the PRTG system administration. If you had selected CloudMade before your PRTG update, the provider setting will be automatically changed to default. |
Fixed
Sensors
EXE/Script sensors |
We fixed an issue with encrypting passwords that contain certain special characters like the dollar sign ($). The issue affected EXE/Script and EXE/Script Advanced sensors. The dollar sign, for example, broke the encryption method, which resulted in a password being partly visible as clear text in the sensor log when you enabled the option Write EXE result to disk and used according placeholders in the parameters field. |
MQTT Round Trip |
|
NetFlow V9 |
We fixed an issue where in certain cases NetFlow V9 sensors did not display the traffic usage. This happened on specific configurations where empty IPv6 data in flow packets overwrote available IPv4 data, which resulted in missing information in the sensor. |
Sensor Factory |
The Sensor Factory sensor now properly shows values even if you perform calculations with sum channels (channel ID -1). In previous versions, values and unit did not match the source channels when summing up the total channels of SNMP Traffic sensors, for example. |
SIP Options Ping |
|
SMTP&IMAP Roundtrip |
The SMTP&IMAP Roundtrip sensor now automatically comes back after being down due to connection issues as soon as the connection is established again. In previous version, the sensor stopped working after connection interruptions like a firewall restart. |
SNMP Cisco System Health |
SNMP Cisco System Health sensors that you create via auto-discovery using the device template Cisco Device (Generic) now get only tags assigned that are suitable for the created sensor scope (for example, voltage, current, temperature). In previous versions, the automatically created sensors just got all Cisco system health tags assigned. |
SNMP Fujitsu System Health v2 |
The SNMP Fujitsu System Health v2 BETA sensor now updates the OID index if it changed (for example, after a restart of the target device) and the identifier still exists in the OID table. In previous versions, the sensor was not able to automatically repair the index if the OID table changed in a way that the OID index was not available anymore. This resulted in a down status with the sensor error message no such name, for example. |
SNMP HPE BladeSystem sensors |
We fixed a memory leak caused by running SNMP HPE BladeSystem Blade and SNMP HPE BladeSystem Enclosure System Health sensors. |
SSL Security Check |
The SSL Security Check sensor now actually uses the SOCKS proxy that you define in the Connection Specific settings of the sensor. In previous versions, the sensor just connected to the target host without using a proxy even if you defined one. |
Fixed
Server
Active Directory |
PRTG now automatically synchronizes user group memberships with the current status of a user account in the Active Directory. In previous versions, user accounts with changed Active Directory group memberships just remained in all user groups they have ever been members of. |
Auto-Discovery |
We improved the check for already existing devices so that the PRTG auto-discovery more reliably avoids creating duplicate devices for the same host. The fix applies in particular to cases where the host names of found devices only differ in uppercase and lowercase letters. |
Deleting |
You can directly delete devices from the device tree again even if they are paused by dependency. In previous versions, a device paused by dependency that you were trying to delete remained in the tree but only the sensors on the device were deleted. |
PRTG Status |
The PRTG Status page now lists sensors with a fixed scanning interval in the correct section of Sensors by Interval. This fix applies to Common SaaS and Windows Updates Status sensors, for example. |
Reports |
We fixed an issue with PDF reports that you could not generate anymore when using a symbolic link (symlink) or junction directory for the reports. The broken symlink functionality was also the reason that in some cases PDF reports did not work anymore after you have updated from a very old PRTG version to a current one. |
Search |
The search in PRTG works again even if you search for objects that include UTF-8 characters (for example, German umlauts or Russian or Japanese characters). In the last PRTG version 19.4.54, you did not get any search results in such a case. |
Sensor History |
The History tab of a sensor only shows entries for actual changes on sensor settings again. In previous versions, tags always showed up as changed in the history even if you only changed other sensor settings. |
Fixed
WebGUI
Automatic Logout |
PRTG user accounts that were automatically logged out from the PRTG web interface after being inactive for a certain time see the reason for being logged out on the login page again. You can define the automatic logout under Setup | User Interface with the setting Automatic Logout in section Website. |
Firefox ESR |
PRTG now correctly recognizes and handles Firefox Extended Support Release (ESR) versions as supported. If you access the PRTG web interface with Firefox ESR 68 or later, PRTG will not mistakenly show the warning message Sorry, your browser is not supported! anymore. |
Maps |
Maps now correctly display Korean characters like the timestamps in graphs that you show on a map. |
Schedules |
The Save button gets activated again if you uncheck a specific time via hour or weekday buttons in the time table of a schedule in your account settings. |
Improved
Various
All Parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated Dutch language file |
November 25th 2019 – Version 19.4.54.1506
Blog article
By Sascha Neumeier • Dec 2, 2019
PRTG Release 19.4.54 includes two brand-new sensors for disk and storage
A new PRTG release, new sensors and lots of new information for you. Take a look at version 19.4.54 together with me.
Read the complete blog post here
Read the complete blog post here
New
Sensors
WMI Disk Health |
The new WMI Disk Health BETA sensor monitors the health of virtual or physical disks on your Windows servers. It shows the operational and health status of a disk. It does not matter which disk type, the sensor works with all kinds like SSD, SATA, or SAS, for example. The WMI Disk Health sensor shows detailed information about the operational status like degraded or predictive failure in the sensor message. With this new sensor type, you will always have a quick and easy overview of the status of your disks. |
WMI Storage Pool |
The new WMI Storage Pool BETA sensor monitors a storage pool on your Windows servers. A storage pool consists of multiple disks and provides RAID functionality without real RAID hardware. This new sensor type shows the operational and health status of the storage pool, as well as free space, and provides detailed information about the operational status like stressed or relocating. With the new WMI Storage Pool sensor, you will always have an overview of the status of your storage pool. |
Important
Security
Server |
This version includes an important security update for your PRTG core server. We recommend that you update as soon as possible. Please find more details in the email we sent to the email address provided in your license information. Special thanks go to Aleksandr Melkikh from Positive Technologies for pointing us to the right direction. (CVE-2019-19119) |
Improved
Security
Access Rights |
Users with restricted access rights to sensors now only see a sensor's relationship in the Similar Sensors Overview if their user account has access to both related sensors. |
Sensors |
We fixed a potential Remote Code Execution (RCE) vulnerability of the HTTP Transaction sensor. (CVE-2019-11073) |
Server |
We fixed a potential Remote Code Execution (RCE) vulnerability of the PRTG core server. Many thanks to Sittikorn Sangrattanapitak - Cybersecurity Researcher, Nuttakorn Tungpoonsup & Ammarit Thongthua - Secure D Center Research Team, Secure D Center Co.,Ltd. for reporting the issue. |
Version Number |
PRTG does not show the current version number in HTTP headers anymore to improve security by not providing attackers potentially relevant information. For the same reason, the page footer of the web interface now only shows the version number on pages that require a logged in user account. |
Fixed
Sensors
MySQL v2 |
MySQL v2 sensors support user-defined variables in your SQL scripts again. This did not work in previous PRTG versions due to a change in the MySQL library, which added a new connection setting to allow user variables. The sensors showed the error message Fatal error encountered during command execution when running a SQL statement with user-defined variables. |
Port |
You can now also save the advanced Port sensor setting Goal into custom device templates. The goal of a Port sensor can be an open or closed port to define an up status. |
SNMP Library |
SNMP Library sensors again create each channel only once. If you selected more than 10 OIDs when adding the sensor in previous versions, the last channel of the sensor created for the first 10 OIDs was also created as first channel of the sensor added for the next 10 OIDs. |
Fixed
Server
Cluster |
Minor stability improvements for PRTG cluster installations |
Data Purging |
PRTG now correctly applies the data purging value for Historic Sensor Data even if you define a value that is greater than 1095 days (3 years). In previous versions, PRTG did not purge historic data anymore if you used a value above 1095 days. You can now define a maximum value of 9999 days. |
Overload Protection |
PRTG will only create one ToDo ticket and one log entry again when overload protection gets activated due to 100 failed logons since the last start of PRTG. In previous versions, PRTG was too noisy with an active overload protection, which could result in way too many tickets indicating that Web server is slowing down login attempts (Protective measure) in some cases. |
Reports |
|
Search |
The PRTG search function works properly again. In some cases, the search did not provide any results in previous PRTG versions and required a restart of the PRTG core server to work. |
Sensor Messages |
PRTG now correctly shows sensor messages in logs and notifications on status change (for example, due to a breached limit) even in certain corner cases. In previous versions, timing issues could result in logs and notifications just showing "OK" instead of the sensor message in such cases. |
Fixed
WebGUI
Libraries |
Libraries do not contain buttons to add devices, sensors, or to run an auto-discovery anymore. The buttons had no functionality anyway because libraries are designed for visualization, not interaction. |
Maps |
The object selector in the map designer to link a map object with an object from the device tree shows the whole tree again. In previous versions, objects at the bottom of the device tree were cut off so you could not select them. |
Multi-Edit |
You can see and change Sensor Display settings again when you open the settings of one or more sensors via multi-edit. |
Updating |
The auto-update confirmation dialog window now immediately reacts when you click the Yes, install update now button. |
Changed
API
JSON |
The value of the notifiesx_raw field returned by the API call api/table.json?content=sensorxref is never null now and always the same value no matter which language. In previous versions, notifiesx_raw could be empty as well. If you use external tools or scripts that use the PRTG API, please keep this change in mind and adjust them if necessary. |
Changed
WebGUI
Optional Downloads |
The PRTG web interface now also shows download links for PRTG Desktop on the Welcome page and under Setup | Optional Downloads on PRTG instances hosted by Paessler. Furthermore, we removed the PRTG Tools tab from the web interface section Setup | Optional Downloads. Of course, you still can download our free network tools on our website. |
Changed
Clients
Enterprise Console |
We no longer deliver the Enterprise Console with the PRTG installer. This change will not affect running Enterprise Console instances, but please note that they may stop working anytime in upcoming PRTG versions. We recommend that you switch to PRTG Desktop soon. Note: The Enterprise Console might not be able to automatically connect to the PRTG server anymore after you have updated to version 19.4.54 and you receive the error message Server runs incompatible software version. In this case, exit the Enterprise Console as well as the Windows tray and run the Enterprise Console again. If it still cannot connect, run PRTG Enterprise Console.exe with the ignore flag. For more information, see the Knowledge Base article Enterprise Console doesn't connect to PRTG core server anymore after updating PRTG. What can I do? Note: If you update from an older PRTG version, your Enterprise Console may show an error message asking you to update the Enterprise Console. This will fail because of the missing installer as of PRTG 19.4.54. For your convenience, you can still directly download the latest installer as well as the latest version of the Enterprise Console here and try to manually update: prtg_enterprise_console_54.zip If you want to update the Enterprise Console on the PRTG core server, extract PRTG Enterprise Console.exe into your PRTG Network Monitor program folder and run it. On other systems, you can just run PRTG_Enterprise_Console_Installer.exe to update. Please note that this is a workaround to keep the deprecated Enterprise Console running if mandatory and may not work in every case. |
Improved
Various
All Parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated language files |
Note
Sensors
Python Script Advanced |
PRTG version 20.1.55 that we will publish in January 2020 will include a new Python distribution because of the end-of-life announcement for Python 3.4. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.7 when you update to PRTG 20.1.55. You only need to consider the change if you are using the Python Script Advanced sensor. PRTG will also create a ToDo ticket with further information for you in this case. |
Note
Security
Web Server |
PRTG version 20.1.55 that we will publish in January 2020 will include a more strict web server security by default to keep PRTG as secure as possible. TLS 1.2 will be the new default web server connection security. The change may affect you if your PRTG users or third-party systems use outdated versions of browsers or PRTG mobile apps, the Enterprise Console, or old automation tools that interact with the PRTG API. You will receive a ToDo ticket in PRTG with further information. |
Note
Tools
PRTG Certificate Importer |
There is a new version of the PRTG Certificate Importer available since December 12, 2019. The new version is compatible with PRTG 19.4.54 and later. Installer and executable are now signed to confirm their integrity. Additionally, we introduced a new versioning system that follows the PRTG versioning, so the current version of the PRTG Certificate Importer comes with version number 19.4.54. For more details and to download it, please see PRTG Certificate Importer on our website. |
October 29th 2019 – Version 19.4.53.1912
Blog article
By Sascha Neumeier • Nov 11, 2019
PRTG Release 19.4.53 brings version 2 of the SNMP Fujitsu System Health Sensor
PRTG release 19.4.53 has been available in our stable channel for a few days now. Take some time and find out what's new in this version.
Read the complete blog post here
Read the complete blog post here
New
Sensors
SNMP Fujitsu System Health v2 |
The new SNMP Fujitsu System Health v2 BETA sensor monitors the status of a Fujitsu PRIMERGY server via iRMC. It might also work with the Fujitsu product lines PRIMEQUEST, ETERNUS, and CELSIUS if they have iRMC available. The sensor shows useful metrics for CPU usage, fans, memory modules, battery, and power supply of your Fujitsu servers. We are looking forward to hearing your feedback about this new beta sensor! Please send your feedback to [email protected]. Note: The new SNMP Fujitsu System Health v2 sensor replaces the original SNMP Fujitsu System Health BETA sensor and addresses the feedback we received from you about this sensor type. Please note that any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later. You need to add the new version of the sensor to continue monitoring your Fujitsu servers. To keep historic data, you can pause existing instances of deprecated sensors. |
Improved
Security
Login |
We improved the security of the password recovery function on the PRTG login page. PRTG will not provide any information about user accounts anymore when you request a new password. |
Sensors |
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic. The Npcap version (0.992) distributed with previous PRTG versions included a security issue with an ACE vulnerability (CVE-2019-11490). Note: Under certain circumstances, the PRTG update process may stop when trying to install Npcap and Windows shows the error message A LWF & WFP driver installation tool has stopped working. In this case, please manually stop npcapoem.exe (for example, via the Windows Task Manager) to continue the PRTG update process. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/86904. |
Fixed
Server
Active Directory |
PRTG automatically clears the cache for Active Directory integration again. In previous versions, the hourly clearing of the cache did not work so old passwords still worked after changing them until you logged in with the new password or manually cleared the cache. |
Cloning |
Clones of flow sensors (NetFlow, IPFIX, jFlow, sFlow) are now able to automatically receive data after you have resumed them. If you clone a flow sensor to the same probe, the clone will keep the IP selection as defined in the sensor settings to receive flow packets. If you clone a flow sensor to a different probe, the clone will receive flow packets on all available IP addresses of the probe by default. |
Dependencies |
You can save settings again even if PRTG detects an invalid Dependency Type on the same page, for example, if a sensor is not existing anymore that was selected as dependency type for the current object. In previous versions, you were not able to save the settings in this case—even if you just renamed the object—because data validation failed and you received the message Error (Bad Request) when saving. |
Device Tree |
We fixed an issue where the PRTG core server was not able to load the device tree anymore. This happened in rare cases if there were inconsistent or pending internal tree states. |
Logging |
We fixed an issue where PRTG did not correctly recognize the size of log files in corner cases. The issue could result in a steadily increasing log file size instead of making a copy and recreating the file, so that log files could still become very large in such cases. |
Notification Triggers |
We improved the performance of the Notification Triggers tab. Actions like adding or removing notification triggers provide feedback considerably faster than in the previous PRTG versions 19.3.51 and 19.3.52. |
PRTG Status |
The PRTG Status page shows the correct value for StateObjects again. |
Scanning Interval |
Objects now show the selected scanning interval even if you have deleted this interval from the Monitoring settings. |
Shutdown |
We improved the shutdown process of the PRTG core server. In certain cases, ending the dependency thread took very long. This could result in a failing automatic restart because the check for successful termination of the PRTG server service could not be performed in such cases. |
Fixed
WebGUI
Maps |
The map object Device Tree (S) now shows the correct color for the status Down (Acknowledged), just like all other device tree map objects. |
Tables |
We improved the layout of data tables on sensor overview pages by making the alignment of columns more consistent. The Channel column is always left-aligned as before, all other columns are now right-aligned. |
Improved
Various
All Parts of PRTG |
Various other minor fixes and improvements to all parts of PRTG, updated user manual, updated German language file |
Note
Sensors
Python Script Advanced |
PRTG version 20.1.55 that we will publish in January 2020 will include a new Python distribution because of the end-of-life announcement for Python 3.4. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.7 when you update to PRTG 20.1.55. You only need to consider the change if you are using the Python Script Advanced sensor. PRTG will also create a ToDo ticket with further information for you in this case. As of PRTG 20.1.55, the path that PRTG uses for Python is %programfiles%\PRTG Network Monitor\python3\ on 32-bit (x86) systems, and %programfiles(x86)%\PRTG Network Monitor\python3\ on 64-bit (x64) systems. |
Note
Clients
Enterprise Console |
We do not officially support the Enterprise Console with PRTG version 19.4.53 or later anymore. Please note that your Enterprise Console may stop working in upcoming versions without further notice due to changes to the PRTG server. Please use PRTG Desktop as successor of the Enterprise Console. |
October 10th 2019 – Version 19.4.52.3515
Fixed
Notifications
Summarized Notifications |
PRTG can send summarized notifications again. In previous PRTG versions 19.3.51 and 19.3.52, PRTG only sent the first notification but not the following summarization. The issue affected all notification summarization options of your notification templates. |
October 1st 2019 – Version 19.3.52.3502
Blog article
By Sascha Neumeier • Oct 9, 2019
All You Need to Know About PRTG Release 19.3.51 and 19.4.52
The PRTG release version 19.4.52 has been available for installation in the stable channel for a few days now. Maybe you already have the version in use, or you are planning the update. As regular...
Read the complete blog post here
Read the complete blog post here
New
Sensors
WMI Battery |
The new WMI Battery BETA sensor monitors status and available capacity of batteries that are connected to Windows devices. Additional channels of this new sensor type show voltage, time estimations until the battery is full or empty depending on the status charging or discharging, and an overall battery health value. The sensor makes it possible for you to see the level of batteries in your IT infrastructure at a glance. PRTG alerts you as soon as a battery threshold is breached. You can even generate reports to get to know how much time laptops spend charging, for example. Please note that the sensor is in beta status and only works if the required WMI battery classes are available on the monitored device. We welcome any feedback about the sensor and what you are trying to monitor. Please send your feedback to [email protected], thank you! |
Improved
WebGUI
Device Icons |
We added new device icons for several vendors. PRTG will automatically add suitable icons to devices detected via auto-discovery if possible. Of course, you can also manually select any device icon in the device settings, section Additional Device Information. The new set includes icons for the following vendors.
|
Improved
Sensors
SNMP Dell PowerEdge Physical Disk |
Newly added SNMP Dell PowerEdge Physical Disk sensors now include the enclosure ID in the sensor name if available. For example, a sensor name can be Physical Disk 1:0:0:16, where the first of four numbers is the enclosure ID (here: 1). If there is no enclosure ID available, there will be three numbers in the sensor name, for example, Physical Disk 0:0:16. This improvement will help you to easier find the disk you are looking for in PRTG. |
Fixed
Security
PRTG Core Server |
We fixed potential reflected XSS vulnerabilities with medium severity on the PRTG core server. The potential vulnerabilities affected tag filters, object IDs, and the contact support/feedback page. Please note that the fixed vulnerabilities required a logged in PRTG user account to be exploited. |
Sensors |
We fixed a potential Denial of Service (DoS) vulnerability of the HTTP Full Web Page sensor. Please note that the fixed vulnerability required a logged in PRTG user account with elevated rights to be exploited. (CVE-2019-11074) |
Fixed
Sensors
Event Log (Windows API) |
You can filter for more than two event IDs with the Event Log (Windows API) sensor again. In the previous version, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of more than 2 IDs. |
Exchange (PowerShell) sensors |
Exchange (PowerShell) sensors now correctly close the runspace. In previous versions, Exchange (PowerShell) sensors sometimes showed a down status with the error message Fail to create a runspace because you have exceeded the maximum number of connections allowed. The fix applies to all Exchange (PowerShell) sensor types, Exchange Backup (PowerShell), Exchange Database (PowerShell), Exchange Database DAG (PowerShell), Exchange Mail Queue (PowerShell), Exchange Mailbox (PowerShell), Exchange Public Folder (PowerShell). |
EXE/Script sensors |
EXE/Script and EXE/Script Advanced sensors again support the special characters round brackets "()", dot ".", and comma "," in the Parameters field. This allows you to pass arrays from the sensor to the script. |
Sensor Factory |
We fixed an issue where, in rare cases, modifying the spike filter in combination with Sensor Factory sensors caused issues with the PRTG core server, resulting in gray sensors, for example. |
SNMP Cisco System Health |
|
SNMP HPE BladeSystem sensors |
Channels of SNMP HPE BladeSystem Blade and SNMP HPE BladeSystem Enclosure System Health sensors will not be saved into custom device templates anymore. We changed it this way because dynamic sensor channels often lead to empty channels when they are created by custom device templates. |
SNMP Poseidon Environment |
You can add SNMP Poseidon Environment sensors again. The field validation in the settings when adding the sensor did not correctly work and prevented you from creating the sensor. |
SNMP Traffic |
|
SQL v2 sensors |
We fixed an issue with SQL v2 sensors where the impersonation with Windows or database credentials prevented the sensor to read the file with the SQL query if the impersonated user had no access to the query files. The error message in this case was Parameter -query is missing. The fix applies to the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, Oracle SQL v2, Oracle Tablespace, PostgreSQL. |
SSL Certificate |
The SSL Certificate sensor properly compares wildcard CN/SAN (Common Name/Subject Alternative Names) and SNI (Server Name Identification) again. In previous versions, the sensor showed a down status with the message CN/SAN do not match in this case. |
SSL Security Check |
If you create a device template that includes SSL Security Check sensors, running an auto-discovery with the template will now actually create SSL Security Check sensors. In previous versions, the auto-discovery erroneously added Port sensors in this case. |
Windows Updates Status (PowerShell) |
The Windows Updates Status (PowerShell) sensor will create more than one channel again if it can retrieve according data. The change will especially improve the sensor if the target device runs on Windows 10, Windows Server 2016, or later. |
SNMP sensors and System Information |
We implemented a minor stability improvement for the SNMP engine of PRTG. SNMP sensors as well as System Information tables retrieving data via SNMP can handle NUL in response strings again. For example, System Information tables showed the message Error: SNMPERR_GENERR (SNMP error #-1) with a timeout while waiting in WorkEnter in previous versions when receiving NUL strings. |
Optional Sensor Channels |
Sensors again only create optional channels if the channels are intended to be created. In the previous PRTG version 19.3.51, sensor types like, for example, SNMP Traffic and Ping erroneously created additional channels even if you did not select the according options in the Add Sensor dialog. |
Spike Filter |
Spike filters that you can optionally set apply to the tabs 30 days (Graph 2) and 365 days (Graph 3) again, as well as to historic data reports. In the previous PRTG version, the filter only worked for live data and the 2 days graph and table. |
Fixed
Notifications
Notification Delivery |
We removed the Test SMTP Settings button in the Notification Delivery settings on PRTG instances that are hosted by Paessler. As PRTG hosted by Paessler customer, you use the email infrastructure of Paessler so that testing the SMTP delivery settings is not necessary for you. |
Notification Templates |
PRTG user accounts with read/write rights and write or full access rights to a notification template can now change the user group as the recipient of an email, push, or SMS notification. Logged in read/write users can see and select all user groups they are member of, as well the currently selected user group in the Send to User Group field of a notification template. In the Send to User field, read/write users can see and select all user accounts from all user groups they are a member of, as well as the currently selected user account. |
SMS Notifications |
|
Fixed
Reports
PDF Layout |
We fixed an issue with PDF reports that erratically caused big gray boxes in generated reports. |
PDF Stability |
We implemented stability improvements for PDF reports with many sensors, especially regarding timeouts with the error message Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome. |
Fixed
Libraries
Node Types |
Libraries again only show a subtree if you select Show a subtree of the device tree in the library as Node Type for a library node. In previous versions, library nodes additionally showed an unordered list of sensors included in the subtree. |
Usability |
The buttons to collapse and expand library nodes are now also available in the smallest view (S). |
Fixed
Server
Data |
We fixed an issue where values of primary sensor channels with negative channel ID were not displayed in some data tables, for example, the Traffic Total channel of SNMP Traffic sensors (channel ID -1). The value of this channel was missing in headers of historic data reports and as Last Value in Cluster Node tables, for example, when set as primary channel in the last PRTG version. |
Logging |
|
Memory |
We fixed an issue where in certain cases the PRTG server showed a too high memory consumption on large installations with, for example, several thousand sensors. The PRTG server will also use less memory than before when cloning hundreds of objects in the device tree at the same time. |
PRTG Core Server |
We removed an unnecessary readlock on the PRTG server that could lead to a deadlock with an unintended PRTG server restart in rare cases. Another readlock we fixed was caused by calculations of the Sensor Factory sensor and could prevent the PRTG server to restart. |
PRTG GUI Starter |
Opening the PRTG web interface with the PRTG GUI Starter now also works if you have set the connection security of your web server to High security (TLS 1.1, TLS 1.2). The PRTG GUI Starter is only used if you open PRTG via the shortcut PRTG Network Monitor that is created by default on your server during the PRTG installation. |
Fixed
WebGUI
Dependencies |
It is not possible anymore to configure a sensor to be its own dependency. Having a sensor as its own dependency resulted in a situation where a sensor endlessly paused itself when it switched to a down status without the possibility to resume the sensor. |
Gauges |
The gauge of a sensor's primary channel now always shows the unit for the minimum value. In previous version, the unit for the minimum value was missing if the minimum was 0 and the channel had a custom unit. |
Multi-Edit |
You can now acknowledge one or more down states on the Alarms tab of probes using the multi-edit menu, as well as open the settings of one or more probes. |
Tables |
We fixed some layout issues of meta-scan tables in sensor settings so that especially large tables are displayed in a better way. |
Firefox |
Opening the context menu in the PRTG web interface via right-click now even works if you use Firefox on macOS. |
Internet Explorer 11 |
We fixed some more layout issues that occurred when accessing the PRTG web interface with Internet Explorer 11. For example, the Save button was cut off on some pages, the Hide and Show buttons for master dependencies in the dependencies graph were missing, and tickets sometimes occupied more space than given to them. |
Changed
Server
Probes |
Connecting remote probes now automatically downgrade to the correct version if the PRTG core server runs an older version than the probe. |
Tags |
It is not possible anymore to add the same tag to one object in PRTG more than once. |
User Accounts |
It is not possible anymore to create user accounts with a login name that includes the special characters " / \ [ ] : ; | = , + * ? > < Note: User accounts that already existed before the update to PRTG 19.3.51 and have a login name that includes one of the outlined special characters will still be able to login after the installation of version 19.3.51. However, affected user accounts will not be able to change and save their account settings without changing the login name. |
Improved
Various
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated German and Japanese language files |
Note
Sensors
SNMP Fujitsu System Health |
The upcoming PRTG version 19.4.53 will include a new, significantly improved SNMP Fujitsu System Health sensor. We already inform you now about the change because any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later and need to be added anew. |
Note
Outdated Windows Versions
Outdated Windows Versions |
It is not possible anymore to install PRTG on the outdated operating system Windows XP. This is a side-effect of changing the PRTG license check to a 64-bit binary. Please make sure you install PRTG on an officially supported operating system. |
Note
Known Issues
Summarized Notifications |
In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information. Status: resolved with PRTG 19.4.52.3515 |
September 10th 2019 – Version 19.3.51.2830
Improved
Sensors
Active Directory Replication Errors |
The Active Directory Replication Errors sensor now supports different Active Directory naming contexts. When you add the sensor, you can now choose between Configuration (default), Schema, DomainDnsZones, Domain, and ForestDnsZones as Naming Context to check your Windows Domain Controller for replication errors. In previous versions, the sensor always used Configuration as naming context. |
Improved
Notifications
Notification Delivery |
PRTG will now provide clearer communication in logs and tickets when an SMS notification fails due to a missing definition for an SMS provider in the Notification Delivery settings. |
Notification Triggers |
You can now directly create a new Notification Template while editing or defining a Notification Trigger without leaving the notification trigger tab. Click the plus symbol (+) in the dropdown list of a trigger to create a new notification template for the notification trigger. |
Improved
Server
Active Directory |
We improved the login process for Active Directory (AD) users by explicitly requesting read-only access. |
Device Templates |
If you create a new device template, you now only need to define a name for the template. You do not have to provide a file name anymore, PRTG will automatically create the corresponding template file with the extension .odt. |
PRTG Core Server |
Performance and memory footprint improvements for the PRTG core server, as well as several other improvements and fixes |
Reporter |
We added enhanced logging to the new reporter engine to be able to better help you in case of issues when generating reports. |
Improved
Security
Maps |
We fixed a potential XSS vulnerability in the context of maps. Thanks to Dmitry Galecha from Positive Technologies for reporting the issue. |
Notifications |
Passwords of Execute Program notifications, webhooks for Slack and Microsoft Teams notifications, as well as the AWS Secret Access Key of Amazon SNS notifications are now masked on the History tab of according notification templates in the PRTG web interface. Notification templates are only accessible for PRTG administrator users and read/write users with access rights for a particular notification template. We found the issue in internal tests, it was not public before. If your PRTG installation is affected, you will receive a Todo ticket in PRTG. Please follow the instructions there. |
Sensors |
Passwords of the following sensor types are now also masked in log files when you enable the debug option: FTP Server File Count, HTTP XML/REST Value, SIP Options Ping, Citrix XenServer Host, Citrix XenServer Virtual Machine, IPMI System Health |
Improved
Language Files
Language Files |
Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG. |
Fixed
Sensors
Event Log (Windows API) |
You can filter for two event IDs with the Event Log (Windows API) sensor again. In previous versions, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of IDs. Note: With this version, it is not possible to filter for more than two event IDs. We plan to fully support filtering for multiple IDs again for the next PRTG version 19.3.52. |
EXE-based Sensors |
Sensors that require .NET version 4.7.2 now actually show the required version number 4.7.2 in the error message if the .NET framework version 4.7.2 is not available on the probe system. The full error message is This sensor requires the .NET Framework version 4.7.2 (code: PE104) For more details, please see this Knowledge Base article. |
Flow Sensors |
It is possible again to clone flow sensors and devices on which flow sensors are running (for example, NetFlow sensors). In previous PRTG versions, you received Error (Not Found) when cloning flow sensors. Note: To receive data with a flow sensor clone, please open the Settings tab of the sensor and click Save. |
SNMP Traffic |
|
VMware Datastore (SOAP) |
The VMware Datastore (SOAP) sensor now also properly works if the name of the monitored datastore starts or ends with host. In previous version, the sensor showed a down status with the error message The object '[name]' has already been deleted or has not been completely created in such cases. |
Fixed
Probes
Memory Leak |
We fixed a small memory leak on the PRTG probe system. The memory leak was caused by SNMP sensors that use SNMP bulk walks with more than 20 channels. |
Probe Connections |
We improved the stability of remote probe connections to the PRTG server. In some scenarios, customers encountered frequent disconnects of remote probes with the previous PRTG version 19.2.50. Note: In certain cases, there may still occur issues with probe connections. We are working on further stability improvements for upcoming releases. |
Probe GID |
PRTG now always blocks connection attempts of deleted or rejected remote probes if there is an according entry in the Deny GID field of the Probe Connection Settings. The entry was not correctly saved in previous versions when using the French language file, Other language versions were not affected |
Fixed
Server
Cluster |
Sending support bundles from failover nodes works again. |
Dependencies |
We fixed an issue with dependencies where in certain cases devices and sensors did not resume automatically from paused by dependency. This happened, for example, after changing the dependency type from "Master object for parent" to "Use parent". |
Device Tools |
Opening the Service URL of a device via Device Tools now even works if the service URL contains an ampersand (&). |
Geo Maps |
Locations that you newly define for devices and groups in PRTG show up at the corresponding location in geo maps again. |
PRTG Core Server |
We fixed an issue with the PRTG core server that was not able to start and remained stuck in Loading Graph Cache if the configuration file contained an invalid speed trigger value. This happened in a few cases by error after cloning sensors with defined with speed triggers. |
Raw Data Buffer |
We fixed an issue that resulted in a full raw data buffer (see the according channel of the Core Health sensor) in certain scenarios with the previous PRTG version 19.2.50. This could happen, for example, when having many remote probes connected. The issue could also cause a loss of monitoring data with many sensors in unknown status. |
User Accounts |
It is possible again to change the settings of a user account at any time. Previous PRTG versions erroneously showed the error message A user with this login name already exists. Login names have to be unique. in certain cases when changing user settings. This especially happened for user accounts that you integrated via Active Directory. |
Fixed
WebGUI
Access Rights |
Primary groups of read/write user accounts in PRTG again automatically get write access to libraries, maps. reports, notification templates, and schedules that they create. This way, the new object remains visible after a page fresh for the user who created it. |
Breadcrumbs |
We implemented some minor improvements for the consistency of breadcrumbs and their translations. |
Contact Support |
PRTG user accounts with read/write rights can now also open the contact support form via Setup | Contact Support in the main menu bar. |
Dark Theme |
Historic data graphs keep their dark theme appearance again when you use the scroll and zoom buttons. |
Homepage URL |
Changing the PRTG Homepage URL in your account settings or via Make This My Homepage in the main menu bar on a PRTG hosted by Paessler instance now actually takes effect. |
Hover Popups |
|
Reports |
|
Search |
Text that you are searching for in PRTG is correctly displayed again even if your search contains special characters or whitespaces. Search results were not affected by the issue. |
Tags |
Tags can now contain certain special characters like ampersand (&) and percentage (%) without causing issues with the PRTG web interface when you filter for such a tag. |
Welcome Page |
The ticket count on the PRTG welcome page again shows the correct number of open tickets that are assigned to you. |
Fixed
Various
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual |
Changed
Sensors
Loopback Adapter |
PRTG will not install a loopback adapter as part of the Npcap library for Packet Sniffer sensors anymore. When enabled, the adapter could lead to unwanted side-effects on other services, for example, DHCP servers. |
Changed
Tree Version
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
Note
Known Issues
Enterprise Console |
The Enterprise Console will show two error messages when you close it: MM Operation after uninstall. and Runtime error 204 The messages do not have negative impact. You can ignore them and just close the message windows. Status: Will not be fixed. Please note that we will stop officially supporting the Enterprise Console with PRTG 19.4.53. Please use PRTG Desktop as successor of the Enterprise Console. |
Optional Sensor Channels |
Some sensor types create optional channels that were not intended to be created. For example, SNMP Traffic sensors create all channels from settings section Additional Channels even if they were not selected in the Add Sensor dialog. The Ping sensor creates channels for minimum and maximum ping time, as well as the packet loss channel, even if you select the option Send one single Ping when adding the sensor. The issue does not have functional impact as long as you do not set one of the erroneously created channels as primary channel. In this case, the sensor may switch to the unknown status. Please note that channels cannot be deleted anymore once they are created, so we recommend that you wait for the next PRTG version if you plan to add sensors of these types without optional channels. Status: resolved with PRTG 19.3.52.3502 |
Reports |
Big reports with thousands of sensors occasionally time out and are not successfully created. The message in this case is Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome Status: resolved with PRTG 19.3.52.3502 |
Spike Filter |
In the current version, the spike filter only applies to graphs and tables for live data and 2 days (Graph 1 in graph settings). It is not possible with PRTG 19.3.51 to remove spikes from graphs and tables for 30 days (Graph 2), 365 days (Graph 3), and historic data reports. Please note that this is a display issue, monitoring data is not affected. As soon as you update to a fixed version, all historic data will be correctly displayed again, respecting optionally set spike filters. Status: resolved with PRTG 19.3.52.3502 |
Summarized Notifications |
In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information. Status: resolved with PRTG 19.4.52.3515 |
Note
PRTG 19.3.51.2725
PRTG 19.3.51.2725 |
Please note that we took PRTG version 19.3.51.2725 (released on July 31) offline on August 5 as a precaution because some customers reported serious issues after the update to this version.
Affected customers reported 100% CPU load and many sensors in gray Unknown status due to a full graph cache recalculation that PRTG must do from time to time. We found the reason for the misbehavior and were able to resolve the issue. PRTG 19.3.51.2830 includes a fix for this, as well as three other fixes compared to 19.3.51.2725. If you are running the withdrawn version 19.3.51.2725, please update as soon as possible. |
Active Directory Replication Errors Sensor |
The Active Directory Replication Errors sensor now uses the naming context Configuration as default. This is also the naming context that the sensor used in previous version. With the support of different naming contexts introduced in PRTG 19.3.51.2725, the default was Domain, which, in certain cases, resulted in sensors of this type that did not find the replication neighbor anymore after the update. |
Auto-Discovery Groups |
Adding an auto-discovery group or editing the settings works properly again. In PRTG 19.3.51.2725, several IP selection methods caused an access violation when saving the settings. |
Updating |
We fixed an issue where, in rare cases, updating from older PRTG versions like, for example, 17.3.33, failed because of the tree version update in combination with certain history entries in the PRTG configuration file. |