Please consider these versions as "beta". They have been thoroughly tested in our labs, but there may still be limitations in certain monitoring configurations. Please do not use this version on live systems on which you have to rely on!
Please use the "Auto-Update" feature to update your PRTG installation with the latest preview version: In the PRTG web interface, navigate to Setup | Auto Update.
Download PRTG · Manual: "Software Auto-Update" · Other Release Channels
PRTG Core server |
We fixed an issue where PRTG ran into deadlocks in certain cases as of PRTG 24.1.94.1393, resulting in high CPU load and server crashes and restarts. This issue was more likely to happen if you ran aggregation type sensors, like Sensor Factory sensors, for example. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.94.1397
|
Maps |
We fixed an issue where the access of a public map resulted in the error message Map refresh failed when you updated to the previous PRTG preview version 24.1.94.1355. The workaround was to log in with an administrative user account. Public map access will now work again without an active user session when the map is configured for public access. |
PRTG application server |
We fixed an issue where running the PRTG application server caused a higher CPU load on the relevant system in the previous PRTG preview version 24.1.94.1355. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.94.1393
|
Languages |
We updated the German and Spanish language files. |
Sensors |
The behavior of the Environment setting was changed for the EXE/Script and EXE/Script Advanced sensors to prevent remote code execution for Batch (.bat) scripts. Thanks to IT Matters Most GmbH who made us aware of that vulnerability and which can be tracked under CVE-2024-28055. Please note that this change might cause your running custom scripts to fail as it is no longer possible to use the environment variables placeholders in the Parameters setting for Batch (.bat) scripts anymore. |
Webserver |
We hardened PRTG against possible Cross-Site Scripting attacks via User Agent in the browser. |
Single Sign-on |
We improved the Single Sign-on handling for PRTG user integration in Microsoft Azure AD to support the Microsoft Graph API for paging when a user is assigned to more than 100 groups. Previously, the issue occurred in certain cases that a user with Microsoft Azure AD integration could not log in to PRTG via Single Sign-on when he was assigned to more than 100 groups. Due to limitations in the Access Token concerning the group memberships we need to switch to Microsoft Graph API for paging what was not yet supported by PRTG. The user would then receive the message that the login has failed. In the Core.log you could also find this error message for the user login: is no member of SSO groups allowed by PRTG. You can configure the Group Claim Retrieval for Access token or GraphQL in the Single Sign-on settings. |
Multi-edit |
You will now be able to save the settings for all your selected sensors when you use the multi-edit function. This did not work properly before in the previous PRTG versions in certain cases. Saving the value Maximum (Mbit/s) for the channel Traffic Total when you have selected several SNMP Traffic sensors would only work for the first sensor in the list, not for all sensors that you selected via multi-edit. |
Notification trigger |
We fixed an issue for notification triggers, that is Speed, Volume and Threshold trigger where added values in the PRTG web UI would not be saved correctly in certain cases. It could happen that after you have entered for example a valid value for bit/second in the Speed trigger under Notification Triggers, that the value was saved afterwards with 0 or even an invalid float value. We also fixed this issue for the PRTG App for desktop. |
Remote probes |
We fixed an issue where not all probe Settings were displayed in the previous PRTG versions when you installed a new remote probe on your system. When you have added a remote probe successfully and opened the probe Settings tab you could see that, for example, the Credentials for Cisco Meraki were missing. |
PRTG Administration Tool |
We fixed an issue where the PRTG Administration Tool could not be opened on a remote probe with a 64-bit operating system in the previous PRTG preview version 24.1.93.1655. You would receive an error message Load of logging dll PaeAdvLog.dll failed with error code: The specified module could not be found in this case. The workaround was to open the PRTG Administration Tool directly from the folder as 32-bit version. The PRTG Administration Tool will now start correctly as 32-bit version when you open it on a remote probe with a system running on 64-bit. Please note that when you update from preview version 24.1.93.1655 to this version, the folder C:\Program Files (x86)\PRTG Network Monitor*\64bit still exists. We will deliver a fix for this issue with upcoming PRTG versions. |
Oracle SQL v2 |
We fixed an issue for the Oracle SQL v2 sensor that reported an error The type initializer for OracleInternal.Common.ProviderConfig threw an exception when Oracle Data Access Components (ODAC) was installed on the system where also the sensor was added, e.g. on a remote probe. The sensor then went into an error state in this case because one of the Oracle assembly references did not match. |
Sensor logs |
The Result of Sensor.txt file will now be updated again when you have activated the Store result option for Debug Options in the sensor Settings. Updating the Result of Sensor.txt file did not work anymore in the previous PRTG versions for certain sensor types. This issue affected sensor types like Traceroute Hop Count sensor, Windows Print Queue sensor and Active Directory Replication Errors sensor, for example. |
SNMP Memory sensor |
We fixed an issue for the SNMP Memory sensor that reported the error message (value)' is not a valid integer value in certain cases. The issue occurred because certain devices falsely returned counter values instead of integer values for the storage size in the OID 'hrStorageSize' (1.3.6.1.2.1.25.2.3.1.5) what the sensor then could not process correctly. |
Access rights |
You can now acknowledge alarms with your read-only user in the PRTG App for Desktop when you have set the according rights for that user in the PRTG web interface before. Previously, when you have created a read-only user in PRTG and afterwards added additional rights Allow user to acknowledge alarms to that user, the settings would not automatically be updated when the user was logged in to the PRTG App for Desktop. As a workaround, you had to restart the Core server or the user had to log in to PRTG App for Desktop again. |
Auto-Discovery |
We fixed an issue where the execution of an auto-discovery with device template on the PRTG App for Desktop produced an access denied message in the CoreWebServer.log. |
PRTG application server |
You will notice a higher CPU utilization on your system when you run the PRTG application server and when you update to this PRTG preview version 24.1.94.1355. As a workaround, please try to run your PRTG installation without the PRTG application server service. We will provide a fix for this issue in the upcoming PRTG versions. |
Maps |
Public map access reports the error message Map refresh failed when you update to this preview version 24.1.94.1355 and when you open a map that is configured for Allow public access in the map settings. You will have to log in with an administrative user account for an active user session to view a map with public access on this preview version. We are currently working on a fix for this issue. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.94.1355
|
Probe Adapter |
With this PRTG version we introduce a new Multi-Platform Probe Connection Health (Autonomous) sensor that will inform you of the NATS server connection with your Multi-Platform probe and is created automatically when you have activated Allow multi-platform probe connections in the Core & Probes settings of your PRTG installation. The sensor comes with the channel NATS Connection state that has the lookup values Disabled, Connected and Disconnected. When you have disabled the setting for Allow multi-platform probe connections the sensor will display an according error message and return the value Disabled. Please note that the sensor is in BETA status but you do not need to enable the BETA feature in order to get this sensor created. This sensor type only concerns the connection between Probe Adapter and NATS server. |
Multi-Platform Probe Connection settings |
We added the NATS Connection Security toggle in the Multi-Platform Probe Connection Settings to explicitly set the security schema used.
The configuration for connecting the PRTG core server to a NATS server has changed. The schema is now an explicit toggle instead of encoded into the NATS URL. The NATS URL setting was changed to NATS Server Host, which is made up of the hostname and port of the NATS Server. After this update, the NATS Server Host setting will be reset to the default localhost:23561 value and users will need to reconfigure their NATS server. Important for PRTG Hosted Monitor: This setting is not visible for PRTG Hosted Monitor instances. Customers will be informed separately, as soon as the multi-platform probe can be used with PRTG Hosted Monitor. |
API |
|
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
PRTG configuration file |
Credentials like passwords in the PRTG configuration file are now masked when you use the option Include configuration file (contains passwords) for Send Logs to Paessler in the PRTG Administration Tool in order to send a support bundle. When you have a larger configuration file, e.g. 355 MB and run the PRTG Administration Tool as a 32 bit version, you will receive a message that PRTG was not able to hide encrypted passwords in the configuration file. The same behavior applies when you want to send a support bundle with a broken configuration file. You will then be asked if you still want to include the configuration file containing passwords or not. Please note that currently is not possible to start the Administration Tool for a Remote Probe running on a 64-bit operating system. As a workaround go to the Program Files (x86) folder, open the PRTG Network Monitor folder, and run the 32-bit version of the Administration tool. We will deliver a fix for this issue in the upcoming PRTG versions. |
Webserver |
|
Logging |
You will now see a log entry in the History tab of a device when you have enabled or disabled the inheritance of an object. For example, if you enable the Inherit From feature toggle for Credentials for Windows Systems, it will be logged as Credentials for Windows Systems: Inherited in the History tab of the device. |
Discontinued sensors with PRTG 24.1.94 |
With this version we discontinue the below already deprecated sensors:
For further information about sensor deprecation and discontinuation in general as well as successor sensors and sensor alternatives please see our Knowledge Base articles: What do deprecation and discontinuation in the context of sensors mean? and What sensors are deprecated and what are their successors or alternatives? |
VMware Datastore (SOAP) sensor |
We changed Bytes (File) to Bytes (Disk) in the Channel Unit Configuration of the VMware Datastore (SOAP) sensor to better match the size of datastores. Please note that this change will come into effect only when you add this sensor type as new and does not affect any existing sensors. |
HTTP Transaction sensor |
We fixed an issue for the HTTP transaction sensor that could not access a target URL anymore in certain cases and reported the error message String not found in the previous PRTG version, or when you changed to Compatibility engine in the sensor settings the error message was Object reference not set to an instance of an object. |
Memory |
We fixed an issue that could cause a higher memory consumption especially on the Multi-Platform Probe when you ran MQTT sensors and OPC UA sensors on your system. We therefore also updated our MQTT library to version 1.3.13 what patches several issues. |
Microsoft Azure SQL Database sensor |
Your Microsoft Azure SQL Database sensor will now report an according sensor message when the monitored single database or elastic pool is in a different state then Online or Ready. Previously, the sensor reported an error message The queried field "average,count,maximum,minimum,total" is empty. when, for example, the queried database was in status Paused. |
QoS (Quality of Service) One Way sensor |
The QoS (Quality of Service) One Way sensor now no longer displays any IP address in the Quality of Service Measurement section for Target Probe when you are about to create this sensor type. Previously, the sensor displayed 127.0.0.1 for the local probe what did not reflect the actual probe ID being used. |
Sensor message |
We fixed an issue where in certain cases the message reported by the sensor suddenly displayed only OK after some time. In these cases the message of the sensor was reverted from the original to OK when the message sent from Probe to Core contained an empty string for some reason. The issue occurred for sensor types like WMI Custom String sensor, SNMP Custom String sensor and REST Custom v2 sensor. |
Sensor settings |
We fixed an issue that occurred for certain sensor types, like the SNMP Custom v2 sensor, where an additional text overlapping the help box was displayed in the section for Schedules, Dependencies and Maintenance Window. Additionally the default dates for Maintenance Begins and Maintenance Ends were not displayed correctly. |
SNMP HPE ProLiant Physical Disk Sensor |
We fixed an issue for the SNMP HPE ProLiant Physical Disk Sensor that reported an error Disk: Required field, not defined when you added multiple disks where at least one disk was defective, e.g. did not report serial number and model values. As a result, the sensor could not be created and additionally the PRTG configuration file could also no longer be saved. You will now be able to save your PRTG configuration file again even if your SNMP HPE ProLiant Physical Disk sensor includes a defective disk. |
Windows Print Queue sensor |
We fixed an issue for the Windows Print Queue sensor that did not report the correct sensor message when monitored printers were offline or paused. The sensor wrongly reported the status message up in these cases. |
API |
We fixed an issue where in certain cases API calls to PRTG failed with the error Unauthorized although the API token was valid. For example, when you use the API endpoint /api/table.json to reach PRTG with a valid created API key, it could happen that the call resulted in an Unauthorized message. |
Notifications |
We fixed an issue for sms notifications that were cut off in the text when you used certain special characters, like for example ampersand &. |
Maps |
|
Proxy server |
You can now use Probe Transfer and Configuration Viewer in the PRTG App for Desktop when you have configured a proxy server under Probe Connection Settings in your PRTG installation. In the previous PRTG versions, the remote probe would not connect to the server if you enabled the Probe Transfer feature and if you had a proxy server configured on your PRTG installation. The beta feature Template Transfer for custom device templates from one PRTG server to another will now work as well with a configured proxy server. |
Access Rights |
We fixed an issue for Paessler PRTG Hosted Monitor where you could not change the Inherit From option for Access Rights when you right clicked on a probe in order to edit access rights from the menu. Instead of the Inherit From option you would see the message You need full access rights to view or edit access rights for this object. although you were logged in with a user that has administrative rights. |
Find duplicates |
We fixed an issue for the Find Duplicates feature on /api/findduplicates.htm. Previously, if you selected the option Find Duplicates from the device Context menu the result you would have received was empty. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.93.1655
|
Probe adapter |
You will now need to configure the probe adapter connection to the NATS server through the PRTG web interface. You can set up your probe adapter configuration in the Core & Probes tab of the System Administration in the Multi-Platform Probe Connection Settings section. In this section you can choose the Multi-Platform Probe Connections, add a NATS Server URL, NATS Server Name, NATS Password, choose the NATS Server Certificate Authority Handling and finally choose the Connection Log Level where you can define the log severity level to determine which logs appear in the probe adapter log file. For this field you can choose one of the options offered from a dropdown menu: Error, Warning, Info (default), Debug, Trace. |
API |
|
PRTG application server |
We fixed an issue for the PRTG application server that ran into panic mode when you ran a mini probe on your PRTG installation, for example a Python Mini Probe or a PRTG Mobile Probe for Android. The created panic log would display the error panic: runtime error: invalid memory address or nil pointer dereference in these cases. |
Device settings |
You can now configure and manage your Credentials for Windows Systems in the device settings in the new UI and also via API v2. This enables you to use sensors on your device which require windows authentication, like WMI sensors. The available fields are Domain or Computer Name, User Name and Password. You can also see and manage the Inherit From toggle and enable or disable it. The windows credentials will also be visible in the new UI when you set them via APIv2 PATCH request on the endpoint /api/v2/devices/{id}. Additionally you are now able to edit the following device settings in the new UI and APIv2: Credentials for VMware/XenServer, Credentials for AWS, Credentials for Script Sensors, Advanced Network Analysis. |
Mobile view |
We improved the navigation in the mobile view for the new UI. When you click on the menu icon it opens a drawer from the left hand side. The drawer remains open during navigation and you can close it with the x button. Additionally, when you select home in the side bar, you will see links to the sections Welcome and Quickstart. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Sensor Languages |
We updated the Spanish language files for certain selected sensor types. |
SNMP Trap Receiver and Syslog Receiver |
We fixed an issue where the messages for the Syslog Receiver sensor and the SNMP Trap Receiver sensor were not displayed in the Messages and Sensor Overview tab after updating to the previous PRTG Preview version 24.1.92.1496. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.92.1545
|
Languages |
We updated the German and Spanish languages files. |
Cisco Meraki sensors |
The Cisco Meraki License sensor monitors Meraki licenses of an organization and the Cisco Meraki Network Health sensor monitors the health of Cisco Meraki network devices. Both sensor types use the Cisco Meraki Dashboard API. We released these sensor types as experimental sensors with PRTG version 22.1.74.1869. |
FortiGate VPN Overview sensor |
This sensor monitors VPN connections of your Fortinet FortiGate firewall. The sensor shows the number of connected SSL clients, as well as the number of both up and down IPsec tunnels. We released this sensor type as experimental sensor with PRTG version 22.1.74.1869. |
HTTP v2 sensor |
This sensor allows you to send a HTTP request (HEAD, GET or POST) and use placeholders, similar to the REST Custom v2 sensor. We released this sensor type as experimental sensor with PRTG version 22.4.81.1532. |
Local Folder sensor |
The Local Folder sensor monitors a local folder on a probe system. We released this sensor type as experimental sensor with PRTG version 21.3.70.1629. |
Network Share sensor |
The Network Share sensor monitor a Server Message Block (SMB) or Common Internet File System (CIFS) network share. We released this sensor type as experimental sensor with PRTG version 21.4.73.1656. |
Ping v2 sensor |
The Ping v2 sensor comes with a new setting Inverted Error Status different to its predecessor. If you select Enable for this new setting, the sensor shows a Down status if the target device is reachable. The Ping v2 sensor supports IPv6. We released this sensor type as experimental sensor with PRTG version 22.4.81.1532. |
Redfish Virtual Disk sensor |
This sensor monitors the virtual disks of your Redfish capable servers and shows capacity and status. We introduced this sensor type as experimental sensor with PRTG version 21.3.71.1416. |
SNMP Uptime v2 |
This sensor type comes with the same basic settings as the already existing SNMP System Uptime sensor including the additional Data Source setting under the section SNMP Uptime Specific, where you can select the object identifier (OID) the sensor gets its uptime from. The Data source is also depicted in the sensor status. We released this sensor type as experimental sensor with PRTG version 23.2.84.1566. |
Soffico Orchestra Scenario sensor |
This sensor monitors the status of processes within an Orchestra scenario. Please note that this sensor requires a Soffico license and as of Orchestra 4.8.2.5. We released this sensor type as experimental sensor with PRTG version 23.4.90.1299. |
API Keys |
We improved the creation of API keys via API call requests to match the given access rights. Previously, it was possible to create an API key for a read/write user with the parameter accesslevel_new=full via GET request, although the user only has write access at the most according to the API key access rights settings. The Access Level for the created API key then wrongly displayed full access. |
Web interface |
We fixed an issue where an authenticated attacker could craft a specific request against the editlicense.htm endpoint and change the license of PRTG partially affecting the availability of PRTG. The severity is 4.3-Medium and calculated as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L. |
Historic Data reports |
We fixed an issue for historic data reports that displayed not all or additional hours in the Date Time table when the user has set a different time zone under My Account in the PRTG Web Interface. For example, when your time zone in your account was set to (UTC -6:00) and you ran a historic data report for 12 hours, the report would in this case substract the hours in the Date Time table from the UTC time zone set under your account. |
Logging |
We fixed an issue where in certain cases the Core.log reported the following errors failed loading MQTT transport library: The specified module could not be found or failed loading OPC transport library: The specified module could not be found. Sending test OPCUA Publish notifications or MQTT test notifications also resulted in an access violation in these cases. The issue occurred in the previous Preview version 23.4.91.1566 because internal notification dependency was updated to use a higher OpenSSL version then the PRTG installer provided. |
Lookups |
We fixed an issue for lookup files where changes were not reflected in the web interface when you changed values in lookup files after OID library creation. Changes to lookup values were only displayed after a complete PRTG core server restart. The issue affected for example the SNMP Library sensor, but also other sensors that come with value lookups and appeared only for the first modification in the lookup file. |
Maps |
We fixed an issue for public maps where the map access failed with the error message Map refresh failed in certain cases. The issue occurred for read-only users that had Read Access to a public map in the according PRTG User Group but different security contexts, for example No Access, for objects in a public map. Public maps are now displayed for read-only users but only show the objects the read-only users have access to according to the security context. |
AWS RDS v2 sensor |
Your AWS RDS v2 sensors now display the correct values for the channel Database Connections again. The sensors displayed a wrong amount of connections in the mentioned channel with PRTG stable version 23.4.90.1299 since the sensors pulled the metric for 'SUM' and not 'AVG' (average) for Database Connections. |
Add sensor |
We fixed an issue for certain sensors on addsensor.htm that could be added although the device or group to which you want to add these sensor types did not have corresponding credentials. When you tried to add an AWS sensor, for example, to a device without Credentials for AWS, you received an error message Sorry, the scan for available monitoring items has failed! The AWS sensors will now be displayed as inactive on addsensor.htm with a hint that valid credentials are needed when you try to add them to a device without Credentials for AWS. This issue was also fixed for the Local Folder sensor (BETA) and the Network Share sensor (BETA). |
Device tree |
We fixed an issue that occurred when you renamed a device or group via context menu in the device tree that contained Credentials for Microsoft 365. The error message was The validation of the data you entered has failed and settings could not be saved when you tried to rename the device or group with right click on edit and rename. The issue also occurred when you tried to edit the access rights in the device tree in these cases. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.92.1496
|
Second beta release |
The Multi-Platform Probe enables you to deploy probes on platforms not supported by the Remote Probe, including various Linux distributions and ARM hardware.
In this latest release, we provide TLS support, ensuring a secure and encrypted connection to the NATS server. Additionally, we've included a user-friendly setup wizard for the NATS server, streamlining the installation and configuration process. For more information about the Multi-Platform Probe please see our Knowledge Base article: What is the Multi-Platform Probe and how can I use it? For detailed release notes please see our Knowledge Base article: What are the release notes for the Multi-Platform Probe? |
Script v2 sensor |
We improved the security for the usage of Python scripts with the Script v2 sensor. All PYTHON* environment variables that might be set, like PYTHONPATH or PYTHONHOME, will be ignored when you execute scripts with the Script v2 sensor by using the parameter -E. This parameter prevents that a different e.g. PYTHONPATH is set and that Python scripts with potential security issues are run in the Python script directory. |
SNMP Uptime v2 |
We fixed an issue for the SNMP Uptime v2 (BETA) sensor that displayed wrong values in the Live Data section of the sensor in the System Uptime channel. The issue occurred when you added the sensor to your PRTG local probe, however, it displayed the correct values when you have added it to your Multi-Platform Probe. |
Mobile view |
We introduced a new header for PRTG in mobile view where the menu is positioned on the top left side. The parent breadcrumb will be displayed on the top right side. The main page title Home was removed. |
Web interface |
|
API |
|
PRTG application server |
|
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Webserver Security |
CVE-2023-51630 - ZDI-CAN-21182: An XSS vulnerability was identified through the htmclass parameter in the error.htm in PRTG 23.4.90.1299 and earlier versions where an attacker could bypass the authentication by creating a malicious link and luring a PRTG user with an active session to click it. The severity of this vulnerability is high and received a score of 8.8, (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
For further information, please refer to ZDI-24-073 and CVE-2023-51630 We would like to thank n1nj4sec for working with Trend Micro Zero Day Initiative and responsibly reporting this vulnerability. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 24.1.91.1583
|
Webserver |
We fixed a reflected XSS vulnerability which allowed JavaScript injection. The severity is 6.1-Medium and calculated as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. |
Notifications |
We added the option for SNMP Trap notifications to include the sensor ID that triggers the notification in the trap message. If you select the option Include sensor ID in the Send SNMP Trap notification template, PRTG will send it on the OID 1.3.6.1.4.1.32446.1.1.5. Previously, parsing the sent trap messages was not possible for certain third party systems due to the missing option. |
Update to OpenSSL 1.1.1w |
To ensure secure communication furthermore we updated to the OpenSSL version 1.1.1w. |
Contact Support |
You can now send support bundles with the Contact Support option when you have configured a proxy server in the PRTG Core & Probes settings. Important: The issue still appears in the Paessler PRTG app for desktop. |
Change Password |
You will now receive a proper error message Error (Bad Request) again when you enter an invalid (old) password under My Account in your Account Settings. In the previous PRTG version there was a log entry in the Core webserver log Error: The validation of the data you entered has failed, but no corresponding error message in the web interface. The issue occurred when you selected the option Specify a new password and entered an invalid Old password. |
Device List |
We fixed an issue that caused the inheritance to be disabled for all settings of a device if you changed settings in the Device List before. The issue occurred when you selected several devices in the Device List via Settings option in the multi-edit and saved the changes. The settings of the devices where you made the changes for were set to disabled in the Inherit From toggle. |
Libraries |
We fixed an issue for an unauthorized Ajax error that occurred in certain cases in the CoreWebServer.log instead of displaying the correct error message Your user account is not allowed to access this information. The issue happened when you were logged in with a user account whose assigned user group has write permissions on a library but who is not allowed to access user information when you clicked on the Security Context link for the user to see the User Account Settings. |
Maps |
You can again change the background image of a Map in the Map Settings. If you changed the background image of your map and saved the changes, the map would still display the old image as the new one was saved under an incorrect map ID in the previous PRTG version. |
Reports |
You can now sent reports by email again for scheduled reports in the Report Schedule setting. Previously, when the report schedule sent out an email to a configured email address or PRTG user group you would receive an access violation in the Core.log and in certain cases also the message Error sending Report Email. The issue occurred if you selected a schedule for a report in the Report Schedule setting with Target Email Address and/or Email to User Group. |
PRTG Installer |
We fixed an issue where PRTG stored the data for the Installation Path in the same folder as for the Data Path when you selected to run the PRTG installer in the Custom mode for fresh installations since PRTG version 23.3.88. The issue happened when you changed the Data Path directory in the path field directly. |
Scanning Interval |
We fixed an issue where you could not save your Scanning Intervals in certain cases when you used a regular interval and a UTC interval with the same unit. For example, if you entered 4h and @UTC 4:00 at the same time in the Available Intervals section you would receive a validation error upon saving your changes. |
Remote Probes |
Your remote probes that you have deleted from the device tree will no longer appear on your PRTG Status Page under the Probes and Database Objects sections, or in the information returned when you execute a query on PRTG Health System Information via an API call /api/health.json?. In the previous PRTG version, a deleted remote probe would still be displayed on the mentioned sections with the status disconnected. |
AWS sensors |
We fixed an issue that caused the environment variable AWS_EC2_METADATA_DISABLED to be leaked into the environment of other sensors. For example, it did not work in cases when you had PRTG installed on an AWS environment and ran a script with a Python Script sensor that pulled credentials from an API although the role on AWS allowed PRTG to authenticate with an AWS SDK. The environmental variable was set to AWS_EC2_METADATA_DISABLED=TRUE in this case. |
Veeam Backup Job Status Advanced sensor |
Your Veeam Backup Job Status Advanced Sensor is now able to display the correct value for the channel Job Scheduled when the scheduled job has been disabled. The channel Job Scheduled will now display the value No where previously the channel would have displayed the value Yes. For more information please see our Knowledge Base article:https://kb.paessler.com/en/topic/89136 . |
Historic Data Tooltip |
TWe fixed an issue where a second tooltip icon with tooltip text was displayed in the section Percentile Handling in the Historic Data Tab of a sensor. You could observe this behavior when you selected the radio button for Show Percentiles. The second tooltip would be displayed for Percentile Averaging Interval. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.4.91.1566
|
Redfish Virtual Disk sensor |
The Redfish Virtual Disk sensor (BETA) is now able to handle disks that have one of the following states: Enabled, StandbySpare, InTest, Starting, Quiesced, Updating and Qualified. Previously, the sensor could handle only the state Enabled and would display the status offline for all other states. |
API |
|
Devices |
|
Security |
We fixed an issue where it was possible to escalate privileges for API-Keys. |
Web Interface |
|
All parts of PRTG |
Various other minor fixes and improvements. |
Sensor Languages |
We updated the German and Spanish language files for certain selected sensor types. |
Microsoft Azure |
You can now add the following sensor types to your device template when you select the function Create Device Template in the device tree: Microsoft Azure SQL Database sensor, Microsoft Azure Subscription Cost sensor, Microsoft Azure Virtual Machine sensor and Microsoft Azure Storage Account sensor. This enables you to create these sensors afterwards with the option Run Auto-Discovery with Template. Please note that these sensor types require an Azure custom role with specific permissions. For more information please see our Knowledge Base article: https://kb.paessler.com/en/topic/88625. |
Access rights |
We fixed an issue that affected the creation of Reports, Notification Templates and Schedules when you were logged in as a user with read/write access. When you were logged in as a read/write user, you would get an Unauthorized ajax error when you tried to create a Report, Notification Template or Schedule. However, the creation was successful in the background and visible to PRTG users with administrative rights afterwards. |
API Keys |
We fixed an issue where the created API key for an active directory user was still valid for a certain period of time even though the active directory user was deleted. Previously, when you created a new user in your active directory and connected it with your PRTG installation and also created an API key for this user, the API key would still be valid for a while even the login credentials were not when you deleted the user afterwards. The API key is now promptly invalid like the credentials when you delete the user from your active directory. |
Reports |
You can now create Historic Data Reports in the Historic Data tab for sensors as .csv file format again with the setting for show percentiles activated. Previously, the historic data report would run into an Ajax Error: timeout when you selected the format .csv file and additionally selected the radio button for show percentiles. |
Microsoft 365 Mailbox sensor |
|
OPC UA Server Status sensor |
We fixed an issue for the OPC UA Server Status sensor that reported the following error message in certain cases: The sensor could not connect to the OPC UA server (BadConnectionClosed). The issue occurred because the endpoint selection changed with an update of the library open62541 that is used by OPC UA. |
Windows IIS 6.0 SMTP Received, Windows IIS 6.0 SMTP Sent |
We renamed the sensor types Windows IIS 6.0 SMTP Received sensor to Windows SMTP Service Received sensor and Windows IIS 6.0 SMTP Sent sensor to Windows SMTP Service Sent sensor to meet the technical requirements. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.4.90.1279
|
Local Folder Sensor and Network Share Sensor |
You can now add the sensor types Local Folder Sensor (BETA) and Network Share Sensor (BETA) to your device template when you select the function Create Device Template in the device tree. This enables you to create these sensors afterwards with the option Run Auto-Discovery with Template. |
Script v2 sensor |
You can now create the Script v2 sensor (BETA) when you execute the Run Auto-Discovery with Template function on a device. The sensor will be created only when you have Python installed on the probe system. |
SNMP Disk Free v2 |
We fixed an issue for the SNMP Disk Free v2 (BETA) that displayed wrong values in certain cases when you updated to PRTG version 23.3.88.1393. The issue occurred in cases when you monitored disks with a larger volume. The sensor then reported wrong values like 0% for the percentage channel Free Space and went into error status. Additionally, the absolute values in the channel Total were displayed as negative. The issue happened because the value calculation in the sensor was exceeded by the large values and the sensor could not handle the value overflow correctly. |
Channels |
We fixed an issue for the Last Value column in the new UI that displayed 0% as difference value. The Last Value column now no longer show a difference value of '0' in the sensor channel list when the value is 0% as difference between Warning Limit and Last Value. |
Device Settings |
You can now search for device tags by adding the tag you want to search for, to the search field in the Device Settings tab. |
All parts of PRTG |
Various other minor fixes and improvements. |
Sensor Languages |
We updated the Chinese, German, French, Japanese, Portuguese, Russian and Dutch language files for certain selected sensor types. |
Webserver |
We fixed a path traversal vulnerability in the PRTG Webserver that could be leveraged without authentication. The vulnerability can be tracked under CVE-2023-45858. More information will be available as part of a staged disclosure process, for updates please see our Knowledge Base article https://kb.paessler.com/en/topic/91880. |
Installer |
We fixed an issue where the last PRTG Preview version 23.4.89.1500 could not be installed successfully in rare cases. You could see the error log entry with the message Verify Error (could not initialize openSSL Library) in the PRTG Server Install Log in this case. The issue could happen if you had no vcruntime140.dll for C++ runtimes installed which is required by the PRTG installer due to an internal change within PRTG Preview version 23.4.89.1500. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.4.89.1539
|
Languages |
We updated the Dutch languages files. |
Forgot Password |
The reset token in the link for setting a new password is now masked in the CoreWebServer.log. It was logged in a readable format before when you clicked on the link for setting a new password with the forgot password option. |
Exchange Database DAG (PowerShell) sensor |
Your Exchange Database DAG (PowerShell) sensor now recognizes newer versions of Exchange Server (>2019) and can distinguish between versions i.e 2010, 2013, 2016 and 2019. Previously the sensor recognized the Exchange Server 2019 version as an older version and tried to use this information, resulting in a Warning status for the Active Copy Channel with the message Could Not Read Activation Preference. |
EXE sensors |
We updated our database connectors for certain EXE sensor types, e.g. Oracle SQL v2 sensor, MySQL v2 sensor and PostgreSQL sensor. Previously, the connection to the corresponding databases failed due to required encryption ciphers that did not match. |
Proxy Settings |
We improved the following sensor types to support the Proxy Settings in the device settings so they are able to use a HTTP proxy server when you have set up one in the device settings:
|
OPC UA Custom sensor |
Your OPC UA Custom sensor now supports more data types, that means enums and single values from array-valued variables. Previously, the sensor supported only string, Boolean, and numeric variables. |
Soffico Orchestra sensors |
You can now create device templates that include the sensor types Soffico Orchestra Channel Health sensor and Soffico Orchestra Scenario sensor (BETA). This enables you to add these sensors via auto-discovery. |
MySQL v2 |
With this PRTG version the MySQL v2 sensor does not support the integrated Windows authentication for MySQL anymore due to a license change in the database connector. The sensor will request the Windows password and username instead. |
Scanning Interval |
We fixed an issue for certain selected sensor types that caused the previously set scan interval to be ignored and always run for the default value of 60 seconds. In addition, the interval information was not added to the sensor log in cases where the |
Map rotation |
Public map rotation is now working again as expected. Previously, if you used the public map rotation feature without login credentials required, only the first map would be displayed or the other maps would be displayed as blank pages instead. |
AWS sensors |
We implemented various improvements for the AWS v2 sensors:
|
EXE sensors |
We fixed an issue for certain EXE sensor types, such as the ADO SQL v2 sensor, where the parsing for arguments failed when the Connection String in the Database Specific setting contained a linebreak. The sensor reported a down status with the message Invalid Authorization Specification in these cases. |
Microsoft Azure sensors |
We generally hardened the approach how Microsoft Azure sensors retrieve data to avoid gaps in the sensor data. |
MySQL v2 |
We fixed an issue for the MySQL v2 sensor where the executed SQLV2.exe client tool reported an error with the message Parameter -sslmode is missing. With PRTG version 21.2.68.1492 we introduced a dedicated setting for the SSL mode; however, this setting was initially only implemented for the Command Line Interface. The options you could choose are the same as the values of the MySQL sslmode parameter. |
Netflow sensors |
We fixed an issue for certain Flow sensors, like the NetFlow v9 sensor or IPFIX sensor, that led to access violations in certain cases when the data flow contained fields with variable length. |
SNMP HPE ProLiant Memory Controller sensor |
We fixed an issue for the HPE ProLiant Memory Controller sensor that in some cases could not be created on a HPE ProLiant Gen10 server when the device type was 1 (other) in the given OIDs. An error with the message The sensor could not find any matching data on the monitored device occurred in these cases during sensor creation. |
SMTP sensor |
We fixed an issue for the SMTP sensors where the HELO ident that you configured in the Authentication setting of the sensor was ignored and instead e.g. the default hostname of the probe was used. This issue affected the SMTP sensor, SMTP&POP3 Round Trip sensor and the SMTP&IMAP Round Trip sensor. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.4.89.1500
|
SNMP Traffic v2 sensor |
Your SNMP Traffic v2 sensor now includes the tag snmp in the default tags that are automatically predefined in the Basic Sensor Settings when you add the sensor. |
Soffico Orchestra Scenario sensor |
You can try out our experimental Soffico Orchestra Scenario sensor that we introduce with this PRTG version. This sensor monitors the status of processes within an Orchestra scenario. The sensor comes with the channels Aborted Count, Downtime, Finished Count, Paused Count, Running Count and Warning Count. Please note that this sensor requires a Soffico license and as of Orchestra 4.8.2.5. |
API v2 |
We added a new parameter purpose to the /schemas/{kind} endpoint that supports the values create (for POST), update (for PATCH) or read (for a GET endpoint). The endpoint returns the appropriate schema for a given purpose. |
PRTG application server |
|
Device settings |
|
Maps |
We fixed an issue that occurred when you deleted devices that were included in a map. Previously after you deleted devices in the new UI that were included in a publicly accessible map you would receive the warning message Monitoring might be incomplete or inaccurate due to fundamental problems in your PRTG installation! Click here for more information! when you opened the map then in the classic UI. In addition, the Core Health sensor displayed a down status with the error message Free Physical memory is below error limit of x in Free Physical Memory. The public access page for the map was also not accessible and reported the error Map Refresh Failed in these cases. |
URL parameter |
|
All parts of PRTG |
Various other minor fixes and improvements. |
Languages |
We updated the Chinese, French, Japanese, Portuguese, Russian language files. |
Sensor Languages |
We updated the Spanish language files for certain selected sensor types. |
Error messages |
PRTG shows the error dialog Error (Bad Request) in the web interface again when you attempt to save invalid changes to settings. Previously, the error description was not displayed. The page reloaded without any indication when you tried to save your changes with invalid settings. The error was only logged in CoreWebServer.log. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.3.88.1385
|
PRTG application server |
The CPU usage of the PRTG application server is on normal level again. In the previous PRTG 23.3.88 preview versions, it caused unnecessary high CPU load on the server. |
Remote probe update |
We hardened the mechanism for the automatic update of remote probes in PRTG with this PRTG version. Previously, sometimes remote probes required a manual update after you auto-updated your PRTG server with a new version due to a connection issue. Please note that this change will take effect when you update from PRTG 23.3.88 to the following version, not immediately after updating to this PRTG version. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.3.88.1359
|
Languages |
We updated the German and Spanish language files. |
AWS EC2 v2 and AWS RDS v2 sensors |
Your AWS EC2 and AWS RDS v2 sensors will show a warning message if the limit of the channel CPU Credit Balance limit has less than 1 credit available. Previously the sensors were showing an error status. Please note that this change applies only when you add this sensor type as new sensor. |
MQTT Subscribe Custom sensor |
We added two new options in the MQTT Specific settings of the MQTT Subscribe Custom sensor for a better message handling. The option Add duration since last message will set a threshold alarm that will notify you when no message was received. Previously, the sensor went into unknown status before when no message was received in the scan interval. This default behavior will remain if the setting for Add duration since last message is not enabled. The option Retain last sensor value keeps the last message on the live charts and allows you to monitor specific JSON values of the payload. |
SNMP Buffalo TS System Health Sensor |
Your SNMP Buffalo TS System Health sensor is now able to display an additional status for the channel Firmware Update Available. Previously, the status was not included in the lookup file and therefore displayed an error with the message undefined lookup value (3) when the value 3 was sent to the sensor. The value 3 in this case represents the status latest. |
Cluster Setup |
We fixed an issue that caused the Failover node to become unreachable when you added a new contact to the Notification Contacts settings of the Master node. |
Dependencies |
We fixed an issue where dependent objects, like sensors and devices, were not paused if the configured master sensor went into error status due to exceeded limits. When you configured the sensor under Dependency Type as Master sensor for parent then the issue occurred in rare cases when the sensor was not saved to the device tree while the limit status changed. The issue only affected newly created sensors. |
Libraries |
You can now create libraries again when you are logged in as a user with read/write access. This did not work before in the previous PRTG version 23.3.86.1520 when you were logged in as a read/write user that has full access in the according user group. You would get an Unauthorized ajax error message for adding a new library before. |
Notifications |
|
Probe connection |
We fixed an issue where in certain cases the probe service stopped working and caused the probe to disconnect from the PRTG core server. The probe service then reported a high CPU usage in these cases and sometimes access violations were logged in the PRTG probe.log additionally. The issue was probably caused by the DNS v1 sensor that we declared as deprecated with PRTG version 21.3.69.1333 and which was replaced with its successor DNS v2 sensor. For more information about deprecated sensor types and their alternatives please see our Knowledge Base article: https://kb.paessler.com/en/topic/89505. |
Scanning Interval |
We fixed an issue in the Monitoring settings for the Scanning Intervals section. You can now enter multiple scanning intervals again with the format of Coordinated Universal Time (UTC) points, like @ UTC hh:mm , hh:mm. Previously intervals with the "@ UTC" format were treated as duplicates and the entries could not be saved. Please note that you have to enter different time periods in the scanning intervals when you add multiple intervals in the UTC format. Note:The input validation still incorrectly fails when you add a UTC at a full hour that is already set as hourly scanning interval. For example, @ UTC 06:00 fails to save when there is already a scanning interval with 6h while @ UTC 06:01 would work in this case. |
Add sensor |
We fixed an issue for certain sensor types that ran into the error no available in the Specific settings of the sensor during sensor creation. The issue happened when a timeout value higher than 300 was set in the registry for the initial sensor scan when you added the sensor. Sensor types affected were Microsoft 365 Service Status Advanced, Veeam Backup Job Status Advanced sensor, for example. |
Beckhoff IPC System Health sensor |
The Beckhoff IPC System Health sensor now supports IPv6 as IP Version connection that you can configure in the Basic Device Settings under IP version of the monitored device. The sensor appeared under Sensor types that are not IPv6 compatible in the previous PRTG versions due to a missing compatibility flag in the sensor library. |
Custom sensor channel names |
We fixed an issue for custom sensor types, like the HTTP Push Data Advanced sensor, where channels were created as duplicate when there was a trailing whitespace behind the relevant channel name. The issue occurred after a PRTG core server restart. The whitespace was removed and since it did not match the previous channel name, the sensor would create a duplicate. |
HTTP sensors |
We fixed the handling of HTTP methods that are returned after a redirect to follow the Post/Redirect/Get (PRG) pattern. This prevents the contents of the original POST to be resubmitted by redirecting the client to another location. If you select the Request Method POST, for example, under the HTTP Specific settings of the sensor, then the first request will use this method. If a request is redirected, all further requests will use GET. Redirects of requests that use GET and HEAD will continue to use GET and HEAD, respectively. This change affects all HTTP based sensor types, like the HTTP sensor and HTTP Advanced sensor. |
Microsoft Azure |
Your Microsoft Azure sensors now query data in a slightly longer time span to make sure data is returned from Microsoft Azure and that every time stamp is considered. Previously, it could happen that Azure did not return any value when the queried time span was too close to the present as it would query only the most recent one and not also the latest data.
Note: The Microsoft Azure SQL Database sensor will throw an exception in case no result is returned from timeseries. Microsoft Azure Storage Account and Microsoft Azure Virtual Machine sensors return default value = 0 in case no result is returned from timeseries. |
NetApp I/O v2 sensor |
We fixed an issue for the NetApp I/O v2 sensor that occurred with the ONTAP version update to 9.12.1P3. Due to changes in the API, the sensor received additional unexpected information which resulted in an error with the message The queried field "value" is empty for NetApp Cluster systems. |
OPC UA sensors |
We fixed an issue for OPC UA sensors that could run into a memory leak on the probe system causing the probe service to stop. The issue occurred only in certain cases when you ran a large number of OPC UA sensors, like OPC UA Certificate sensor, OPC UA custom sensor and OPC UA Server Status sensor with a short scan interval. |
Redfish System Health sensor |
We fixed an issue for the Redfish System Health sensor that in certain cases reported an error when the monitored device did not sent a Thermal service. The sensor ran into an exception and reported the error message No 'Thermal' service found in Redfish chassis. The channel for Thermal Status will now report the status Offline/Absent when there is no Thermal data sent by the monitored device. The channel for Thermal Status will not be created if the target system does not support this service determined with the first scan. |
SNMP Cisco System Health sensor |
We fixed an issue for the SNMP Cisco System Health sensor that resulted in sensor logs that were written into the \Logs\sensors folder when you have selected the option Discard result in the Debug options of the sensor. The sensor kept overwriting the log files in this case when the store result option was disabled. Additionally, the sensor disabled the option Store result automatically after writing log files and reset it to Discard result. We also fixed this behavior so that you can now edit the options again manually. |
SNMP Custom String sensor |
We fixed an issue for the SNMP Custom String sensor where the parameter for the setting Interpret Result As was always set to the String (default) option, regardless of the option you set before. This issue occurred when the sensor was used in a device template. |
SNMP Nutanix Hypervisor sensor |
Your SNMP Nutanix Hypervisor sensor will display the speed in the column Last Value (speed) for Bytes Received when you update to this PRTG version. In the previous PRTG versions, the Last Value (speed) for Bytes Received was missing and had the unit Megabyte instead of Mbits configured. |
Cloning sensors |
We have fixed an issue that prevented a sensor from being cloned to more than one device. The same issue would also occur if you tried to clone another sensor to another device after the first clone attempt. In both cases you would receive an error message stating Invalid operation. You can now clone a sensor (or different sensors) to more than one device. |
Comments |
We fixed an issue that prevented you from saving new or edit existing comments in the Comment tab of a device or a sensor. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.3.88.1319
|
HTTP v2 |
We improved the handling of HTTP requests for the HTTP v2 (BETA) sensor to follow the Post/Redirect/Get (PRG) pattern. |
REST Custom v2 sensor |
We fixed an issue for the channel setting Custom Unit in the REST Custom v2 sensor that was displayed even if you selected a different unit than custom. The field will now be displayed only when you have selected Custom (default) for the relevant channel as unit before. |
PRTG application server |
|
Device Tree |
We fixed an issue that resulted in a missing cloned group in the new UI tree when you have cloned the group before in the classic UI and removed one device from the cloned group afterwards. Instead of only missing the deleted device in the new UI the whole group was gone in these cases. |
Web Interface |
We improved the navigation behavior of cards on the device and sensor overview pages. |
All parts of PRTG |
Various other minor fixes and improvements. |
Sensor Languages |
We updated the Spanish and German language files for certain selected sensor types. |
Security |
Your API Keys are no longer logged in a readable format in the CoreWebServer.log when you have created an API key and executed an API call request with it. The issue only occurred for the Log in Debug Level. |
Microsoft 365 Mailbox sensor |
You can now filter emails that match a defined regular expression. The new filter filters email whose Subject, From or Body fields match the defined regular expression. You can set the new option under the Microsoft 365 Settings. Important: The regular expressions filter will result in the Down status if there are more than 10,000 emails in the mailbox folder you want to monitor. This is because the regular expression filter is applied after the emails are retrieved from the API. The larger the volume of emails, the greater the impact on performance. Enable the Filter by Age setting or use a non-regular expression filter in addition to the regular expression filter to reduce the number of emails. |
Notifications |
We fixed an issue that prevented notification templates from being edited within the notification trigger tab. |
PRTG Administration Tool |
You can now enter a folder path with a folder that contains ANSI-characters, like umlauts or accents, in the PRTG Core Server Tab of the PRTG Administration Tool. Please note that this change does not work for unicode characters, like the Cyrillic language. If you select a folder path that contains non-ANSI characters or if you enter a folder path name with such in the field for Local Storage of Data Files and Monitoring Database, then an according error message will be displayed. |
PRTG Installer |
During PRTG installation, when the license server is unreachable due to connection or license expiration issues, the following error message will be displayed: Either the license server is not available because you are offline, or you cannot use the current version of installer because your license has expired. Please check your connection or log into the Paessler shop, make sure your maintenance contract is active and restart the installer. Previously, the installation displayed an error with the message that the license is invalid or that maintenance has expired. |
Single Sign-on |
We fixed an issue where in rare cases the execution of the button Test Single Sign-On Authorization Endpoint led to an access violation. This issue occurred only in very rare cases if your Application (Client) ID for loading the configuration contained a blank space at the end. |
User groups |
We fixed an issue for user groups that had the setting Allow user group members to create certain sensors only enabled. When you created a user group with the mentioned setting and did not select any sensor types in the list, then all the sensor types would be selected after a PRTG core server restart for this user group. |
HL7 sensor |
We fixed an issue for the HL7 sensor in the settings for Message Header where the Default message header was overwritten in certain cases. The issue happened when you entered data for the setting Override message header but you activated the radio button for Default message header afterwards. In those cases, the sensor always took the override parameters instead of the selected default headers from the script. |
HTTP Push Data |
Your HTTP Push Data sensors will show again their values in the Last Value column of the channel list of the sensor as well as in the channel gauges of the sensor Overview tab. The Last Value column did not display any data before in the previous PRTG versions for the HTTP Push Data sensor, HTTP Push Data Advanced sensor and HTTP IoT Push Data Advanced sensor. |
SNMP sensors |
Your SNMP Disk Free and SNMP Memory sensors now display valid values for monitored disks with a larger size >16 terabyte and memory storage >2 terabyte again. In the previous PRTG versions, these sensor types displayed random values or reported an error code 2003. |
SSL sensors |
We fixed an issue for the SSL Security Check sensor and SSL Certificate sensor that did not work anymore when a SOCKS proxy server for sensor connection was used in the previous PRTG versions. The sensors reported an error with the message The connection has dropped (PE039) in these cases. |
Probe Transfer |
We fixed an issue where the transfer of your probes to another server may have failed in certain cases and resulted in a deadlock with the previous PRTG versions. With PRTG version 23.2.84.1566 we announced that you can find the Probe Transfer feature for PRTG Desktop under Probe Connection Settings in the PRTG setup and that it is no longer available in the Experimental Features section. |
PRTG application server |
The application server may be down in certain cases when you update to this PRTG preview version 23.3.87.1579. You can see this with the Application Server Health (Autonomous) sensor that shows a down status. As a workaround, please restart your PRTG core server to make the application server go up again. We will deliver a fix for this issue in the upcoming PRTG versions. Solved with Preview PRTG 23.3.88.1319 |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.3.87.1579
|
Device settings |
We fixed an issue where it was not possible to pause a device via API with /api/v2/devices/40/pause. |
API Keys |
You can now create, read, update and delete API-Keys with HTTP requests via PRTG API v2. For example, a POST request to users/{id}/api-key will create an API key with name, description and access level properties for the user. For more information about how to use HTTP requests in the PRTG API v2 concerning API keys please see our updated Knowledge Base article: https://kb.paessler.com/en/topic/90008. |
Device Settings |
|
REST Custom v2 |
We improved the handling for JSON-path expressions in the REST Custom v2 sensor that in some cases could not be mapped if there were boolean strings with true and false. The mapping now works for counter and integer Value Type in the Channel Settings of the sensor with a given JSONPath/XPath. |
SNMP Traffic v2 |
You can try out the experimental SNMP Traffic v2 sensor. The SNMP Traffic v2 sensor monitors bandwidth and traffic on a device via the Simple Network Management Protocol (SNMP). This sensor type has the same basic settings as its predecessor and comes with the additional channels Broadcasts In (number of incoming broadcast packets), Broadcasts Out (number of outgoing broadcast packets), Multicasts In (number of incoming multicast packets), and Multicasts Out (number of outgoing multicast packets). This sensor is not affected by the following SNMP compatibility options set in the parent device: Port Name Template, Port Name Update, Port Identification, Start Interface Index, and End Interface Index. |
All parts of PRTG |
Various other minor fixes and improvements. |
Sensor Languages |
We updated the Dutch language files for certain selected sensor types. |
PRTG installer |
We fixed an issue for the PRTG installer when you selected to run it in the Custom installation mode. The issue occurred in the previous Preview version 23.2.86.1462 for fresh PRTG installations and when you used the default data path C:\ProgramData\Paessler\PRTG Network Monitor here. In this case you could not proceed on to the next installation step and the PRTG installer reported an error message The Setup program cannot access the selected data path. Check your Windows access rights or select a different directory. |
User accounts |
We fixed an issue that resulted in an automatically created new user group when you have added a new user account in the previous Preview version 23.2.86.1462. This user group was also wrongly assigned as Primary Group to the user. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.3.86.1515
|
Languages |
We updated the German and Spanish language files. |
Vulnerabilities |
|
Sensor Security |
We fixed a vulnerability that could enable an authenticated and authorized malicious user to write an arbitrary file on the probe system. The issue affected the exe sensors FTP Server File Count sensor and HTTP XML/REST Value sensor. The vulnerabilities can be tracked under CVE-2023-22631 and CVE-2023-22632. For further information please also see our Knowledge Base article: https://kb.paessler.com/en/topic/91756 |
PRTG installer |
The PRTG installer now validates the access to the selected Installation Path and Data Path on PRTG installation in the Custom mode and resets the path to its default when it is not accessible. Previously, the installation displayed a fatal error with the message PRTG Webserver could not be started properly when the installer failed to write into the path due to access restrictions. |
Notifications |
We fixed an issue for the HTTP notification type when it contained reserved special characters, such as hash symbols (#), in the placeholders of the URL which you can add in the Execute HTTP Action section. The URL string was cut off after the hash symbol in these cases. |
Object naming |
We fixed an issue on group, sensor, device and notifications level that led to several issues in the web interface when you entered an URL as name of the relevant object. |
HL7 sensor |
We fixed an issue for the HL7 sensor that went into error status with the message Error caused by lookup value 'No' in channel 'Message Control ID OK' (AE:102 Data type error) after running for a certain period of time. The issue was located in the current date and time of the timestamp. |
HPE 3PAR |
We fixed an issue that happened within the parsing of the output for the commands executed by the HPE 3PAR drive enclosure sensor. The sensor then reported the error message Invalid response structure encountered, some data is missing for HPE Primera systems in certain cases. |
HTTP Advanced |
Your HTTP Advanced sensors now can use custom headers again when you have defined them in the setting for Use Custom HTTP Headers of the sensor settings. Previously, the custom headers were ignored and overwritten with a default value. We therefore also fixed an issue with the default HTTP headers where the wrong response format, e.g. XML instead of JSON, was returned in certain cases. |
NetApp SnapMirror v2 |
Your NetApp SnapMirror v2 sensor is now able to display a correct status for the channel Transfer Status when the reverse lookup value is insync for Snapmirror continuous protections. Previously, the sensor reported an error with the message The following reverse lookup value is invalid: insync. in this case. |
NetFlow |
We fixed an issue for the NetFlow v5 sensor where the values for Inbound and Outbound Interface were set to 16 bit instead of 32 bit in certain cases. |
OPC UA Sensors |
|
Windows MSMQ Queue Length sensor |
Your Windows MSMQ Queue Length sensors will now run again when you update to this PRTG version. These sensor types did not work anymore with PRTG version 23.1.82.2175 and reported an error with the message Queuename not found on specified machine in certain cases. The issue occurred on remote systems with a MSMQ service running that could not be queried. |
Libraries |
You currently cannot add a library with a user account that has read/write access when you update to this PRTG Preview version. When you are logged in as a read/write user that has full access in the according user group you will get an Unauthorized ajax error message for adding a new library. As a workaround, please use an admin user account instead. We will deliver a fix for this issue in the upcoming PRTG versions. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.2.86.1462
|
Cisco Meraki |
We fixed an issue for the Cisco Meraki License Sensor and Cisco Meraki Network Health Sensor that went into an error status when PRTG was updated to version 23.2.84.1566 with the message The sensor could not get a response from the server. 0 (). schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). |
HTTP v2 |
To make it more clear, we have renamed the setting from Timeout (sec.) to Timeout per Request (sec.) in the HTTP Specific settings of the sensor. |
SNMP Uptime v2 |
We fixed an issue for the SNMP Uptime v2 sensor that reported the following error in certain cases: Could not resolve OID for 'iso.org.dod.internet.mgmt.mib-2.host.hrSystem.hrSystemUptime.0'. Either the required MIB file was not found or the name is invalid. The issue occurred only when you have added the sensor to a remote probe. |
Script v2 |
We fixed an issue for the Script v2 sensor where the path to the Script folder was broken. The issue was fixed for the path on Microsoft Windows operating systems. |
Web Interface |
|
All parts of PRTG |
Various other minor fixes and improvements. |
Access Keys |
We fixed an issue for Probe and PRTG application server access keys that were encrypted with Preview version 23.2.85.1310 what led to a corrupted PRTG configuration file in certain cases. The issue occurred only when you had more than one access keys and only when you executed a second core server restart after the update to Preview version 23.2.85.1310. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.2.85.1327
|
Forgot Password |
Read-only users that do not have the permission to change their password will now receive an email again with the information Subject: Password Reset Failed: Please contact your PRTG administrator. Password Reset Failed: Not allowed. Read-only users without permission to change their password did not receive this email in the previous PRTG version before with the Forgot password? option on the PRTG login page. |
PRTG Configuration file |
Access keys for Probe and PRTG application server are now encrypted in the PRTG configuration file. The mentioned access keys were displayed in a readable format in the previous PRTG versions. |
DNS v2 sensor |
We fixed an issue for the DNS v2 sensor where the character escaping for curly brackets } in the Filter Value did not work properly. The sensor displayed the error message regex_error(error_brace): The expression contained mismatched { and }. |
Microsoft Azure Storage Account Sensor |
We fixed an issue for the Microsoft Azure Storage Account sensor's channel, Used Capacity , which was previously recording 0 values. With this fix the sensor returns the average values. |
OPC UA Server Status sensor |
The OPC UA Server Status sensor now supports Client Keys with a 4096 bit length for OPC Client Certificates. In previous PRTG versions, the sensor reported an error when a private key with a length other then 2048 bits was used. |
Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor |
We fixed an issue for the Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized |
PRTG for Android and iOS Mobile App |
We fixed an issue where the login for non admin user accounts did not work anymore when PRTG was updated to version 23.2.84.1566. The issue occurred for both manual and QR code login. The workaround was to log in with an admin user account. |
PRTG Desktop Probe Transfer |
The transfer of your probes to another server may fail in certain cases and will result in a deadlock. We are currently analyzing the issue. With PRTG version 23.2.84.1566 we announced that you can find the Probe Transfer feature for PRTG Desktop under Probe Connection Settings in the PRTG setup and that it is no longer available in the Experimental Features section. |
Access Keys |
If you have more than one access keys in your list for remote probe connections, after updating to PRTG Preview version 23.2.85.1310, the configuration will retain only the first key entry and any other key gets deleted or overwritten. We are currently analyzing the issue and we will deliver a fix for this issue in the upcoming PRTG versions. Note: Existing configurations fail after a second core restart after the update. Solved with Preview PRTG 23.2.85.1327 |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.2.85.1310
|
HTTP v2 |
We improved the HTTP v2 sensor to be more compliant with its predecessors HTTP and HTTP Advanced sensor concerning the redirect handling. The HTTP v2 sensor now comes with the new Setting Maximum number of Redirects that is by default set to 16. You can use a value of 0 if you do not want the sensor to follow any redirects. |
SNMP Disk Free v2 |
You can try out the experimental SNMP Disk Free v2 sensor that was rewritten to work on the Multi-Platform Probe. The SNMP Disk Free sensor monitors the free disk space on a logical disk via the Simple Network Management Protocol (SNMP). This sensor type has the same basic settings as its predecessor and comes with the channels Free Space (bytes), Free Space (%) and Total Space (bytes). |
PRTG application server |
We fixed an issue that prevented logging in after an automatic logout, for example after a timeout, logout in a different tab or when the PRTG application server was disconnected. |
Device settings |
|
Web Interface |
We fixed an issue that resulted in not keeping the zoomed-out position of a graph of a device or sensor overview in down or warning status after the automatic refresh. |
All parts of PRTG |
Various other minor fixes and improvements. |
Security |
We fixed an issue for Microsoft 365 credentials that were displayed in a readable format in the Core Log. The issue only occurred for the Log in Debug Level. |
IPMI System Health sensor |
We fixed an issue that appeared in the IPMI System Health sensors that caused increased mutex timeouts. |
German and Spanish |
We updated the German and Spanish language files. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.2.84.1562
|
By Michael Becker • Jun 9, 2023
NetApp v2 |
The new NetApp v2 sensors NetApp Aggregate v2, NetApp I/O v2, NetApp LIF v2, NetApp LUN v2, NetApp NIC v2, NetApp Physical Disk v2, NetApp SnapMirror v2 Sensor, NetApp System Health v2 and NetApp Volume v2 support the new ONTAP REST API as of ONTAP 9.6. We first introduced the new NetApp v2 sensors as experimental with PRTG version 22.3.79.2108 since NetApp delivers a new RESTful API for ONTAP based storage systems and former ONTAPI will reach end of availability soon. We received valuable feedback and in addition to the functionality that the sensor already had in the last PRTG version, we resolved one more issue for this release.
Note: Your running NetApp v1 sensors will no longer work when you update to ONTAP version 9.13.1. We already announced the deprecation of NetApp v1 sensors with PRTG version 23.2.83.1760. |
SNMP v3 |
PRTG now supports the following encryption methods for SNMP v3 communication in the Credentials for SNMP Devices settings: AES192 and AES256 (Advanced Encryption Standard), SHA-224, SHA-256, SHA-384 and SHA-512 (Secure Hash Algorithms). Previously we only supported AES128 for encryption. |
PRTG status page |
We hardened PRTG against possible data extraction from instances on the PRTG status page. |
Sensor Security |
We improved the sensor types SMTP&POP3 Round Trip sensor, SMTP&IMAP Round Trip sensor and SMTP sensor which were not compliant to the Internet Message Format RFC 2822. Outgoing emails from PRTG to your (SMTP) server will no longer set a Message-ID field itself, but let the remote server add it. This applies to any other mail client. |
Map Layout |
You can now enter only valid pixel sizes for Map Width and Map Height in the Map Layout settings that range from 1 (min.) to 2147483647 (max.). Before it was possible to enter and save large numbers without limitation or negative numbers with the result that the map was not working afterwards. |
Scanning Interval |
We fixed an issue in the Monitoring settings for the Scanning Intervals section. In previous PRTG versions you could enter and save an already existing scanning interval to Available Intervals with the same or with a different unit. For example, if you had a scanning interval of 60s you could add 60s as interval again or equivalent to it 1m. |
Security |
We fixed an issue for Microsoft 365 credentials that were displayed in a readable format in the Core Log. The issue only occurred for the Log in Debug Level. |
Docker Container Status |
Your Docker Container Status sensors work properly again. In the previous PRTG version 23.2.83 they ran into an error with the message bad certificate in some cases. |
Filtering and libraries |
Filter by type option in the main menu bar and in libraries now properly works for all sensors. Filtering by certain sensor types previously showed no sensors directly after PRTG updates and only after a server restart. |
IPMI System Health sensor |
We fixed an issue that appeared in the IPMI System Health sensors that caused increased mutex timeouts. |
PRTG default SSL certificate |
We created a new PRTG default SSL certificate since the one in use will expire soon. The new certificate will be automatically set only if you make a fresh PRTG installation and not upon updating
PRTG. If you have already installed PRTG you need to manually update it. For more details, please see our Knowledge Base article https://kb.paessler.com/en/topic/283. |
Probe Transfer |
You can now find the feature Probe Transfer in the Probe Connection Settings as it has left the Experimental Features section in the PRTG setup. This feature allows PRTG Desktop to access the configuration files of your probes to transfer a probe to another server. You still need to enable the feature first for your server in the Probe Connection Settings. |
PRTG Mobile Apps and PRTG Desktop |
The login, via QR code and manually, to your PRTG Android and iOS App and the PRTG Desktop is currently not working for non admin user accounts when your PRTG is updated to version 23.2.84.1566. As a workaround, please use an admin user account instead. We will deliver a fix for this issue with an upcoming PRTG version. Solved with PRTG 23.3.86.1520 |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.2.84.1562
|
Cisco Meraki |
We added a new setting Meraki Dashboard API EndPoint in the section Credentials for Cisco Meraki devices. With this field you can define your API endpoint for the sensor types Cisco Meraki License (BETA) and Cisco Meraki Netwok Health (BETA) after unlocking it. The setting resolves any issues on a device or group level where the API url has an extension other than .com. |
REST Custom v2 |
|
SNMP Custom v2 |
You can try out the experimental SNMP Custom v2 sensor that we have rewritten to work on the Multi-Platform Probe. This sensor type comes with the same basic settings as the already existing SNMP Custom sensor. The SNMP Custom sensor monitors a single parameter that is returned by a specific object identifier (OID). The experimental SNMP custom v2 sensor will use both OID and MIB files.For more information about MIBs and how to use them please see our Knowledge Base article:https://kb.paessler.com/en/topic/91688. |
SNMP Uptime v2 |
You can try out the experimental SNMP Uptime v2 sensor that we have rewritten to work on the Multi-Platform Probe. This sensor type comes with the same basic settings as the already existing SNMP System Uptime sensor including the additional Data Source setting under the section SNMP Uptime Specific, where you can select the object identifier (OID) the sensor gets its uptime from. The Data source is also depicted in the sensor status. |
Script v2 |
We improved the Script v2 sensor to use a new JSON schema format. The sensor executes a Python script that returns data in JSON format and shows the exit code. This way you can create your own custom script sensors that may not be available in PRTG by default. Additionally the Type field in the sensor Settings has a new option Lookups. When you use lookups for Script Specific Type you need to set the lookup_name as property which defines the used lookup file. The Script v2 sensor now also supports unit kinds for the Type field that determine how a value is interpreted and therefore displayed. Kind can be custom, count, percent, for example. We also updated and improved the example scripts that are available during sensor creation. For available example scripts and how to use them, see the Knowledge Base article https://kb.paessler.com/en/topic/91349. |
Device Settings |
|
Web Interface |
|
All parts of PRTG |
Various other minor fixes and improvements. | Languages |
We updated the Chinese, Dutch, French, German, Japanese, Portuguese, Russian and Spanish language files. |
By Michael Becker • Apr 26, 2023
Device icon |
PRTG now validates the value of a device icon to avoid the risk of modifying it to possibly enter arbitrary content into the style tags when loading the Cascading Style Sheets (CSS) for the relevant page. (CVE-2022-35739) For more information please see our Knowledge Base article: https://kb.paessler.com/en/topic/91149. |
PRTG Login Page |
We improved the wording of an error message text on the login page that displayed sensitive information. The error message occurred in cases when users of an Active Directory group that was not part of a PRTG user group used wrong login credentials and it displayed the information no corresponding Active Directory Security group was found. The error message now displays Your login has failed. Please contact your administrator. |
Web server |
We hardened PRTG against a possible Cross-Site Scripting (XSS) attack where a malicious actor could trick a victim into running injected javascript code over a manipulated link. |
Notification Delivery |
With PRTG version 23.2.83 we now support TLS 1.3 in the Notification Delivery settings for the Delivery Mechanism Use one SMTP relay server (recommended in LANs/NATs). If you select this option, TLS 1.3 will additionally be displayed for the SSL/TLS Method radio group. |
Reports |
We updated our reporting engine to the Chromium version 89. This update will improve the rendering of PDF reports that did not work in certain cases before. Chromium will create temporary files under %TEMP%/prtg_reporter that will be removed when the PDF report creation is finished. |
Update to OpenSSL 1.1.1t |
To ensure secure communication furthermore we updated to the OpenSSL version 1.1.1t. We now support TLS 1.3 in the connection security settings for High, Default and Weakened security connection in the Probe Connection settings and PRTG Web Server settings. Important: Please note concerning your running HTTP sensors that we do not support any cryptographically broken ciphers for outgoing HTTP connections anymore with this update to OpenSSL 1.1.1t due to security reasons. This concerns the encryption methods MD5, DES, RC4. If you run any HTTP sensors for devices that do not offer any ciphers supported by OpenSSL 1.1.1t anymore, the sensors may run into an error with the message ssl3_read_bytes:sslv3 alert handshake failure. For further information about the high security standards of PRTG please see our Knowledge Base article: https://kb.paessler.com/en/topic/61108. |
HPE 3PAR Drive Enclosure |
We improved our HPE 3PAR Drive Enclosure sensors that in certain cases returned an error with the message An error occured. For more information, check the \Logs\sensors subfolder of the PRTG data directory on the probe system. If you have not enabled debug options, activate Store result under Debug Options in the settings of the sensor, rescan, and check the \Logs\sensors subfolder of the PRTG data directory on the probe system. showcage: invalid option -d. The issue occurred because the sensor uses the option showcage -d in the API what could not be processed by the Primera system, which instead uses the option showcage -all. |
Microsoft Azure Subscription Cost |
We updated our Microsoft Azure Subscription Cost sensors so that they now support the new Azure billing model from Microsoft. Before, the sensor returned an error in the result of sensor log with the message No billing periods found. Cannot continue since there are no individual billing periods anymore in the new Azure billing model and it uses invoices for calendar months instead. |
Sensor security TLS connection |
With the update of OpenSSL we also improved certain sensor types that now support TLS 1.3 connection security:
|
Sensor security digital signature |
We improved several sensor types by signing them digitally with Secure Hash Algorithms sha256. In the previous PRTG version, these sensor types failed in certain cases when an AV scanner detected the unsigned .exe files as insecure. Sensor types improved, for example, are as follows: FTP Server File Count sensor, Windows MSMQ Queue Length sensor, Ping Jitter sensor, Windows Print Queue, Traceroute Hop Count sensor, HTTP XML/REST Value sensor. |
Microsoft 365 Mailbox sensor |
We fixed an issue for the Microsoft 365 Mailbox sensor that could not match emails when you used special (non-ASCII) characters in the filter options Filter by 'subject' with Contains all or Contains any, for example words with accents like "é". The issue was located in the library used by the sensor where URL encoding did not work properly. |
Notifications |
We fixed an issue where subjects in email notifications could not be displayed correctly in certain cases in previous PRTG version 23.1.82.2175 and 23.1.82.2074. The issue occurred in cases when you used diacritics or umlauts in the subjects of email notifications. |
PRTG Core server |
We fixed an issue for the PRTG core server that caused high CPU usage in certain cases. The reason for this were connection threads in the background that were not terminated. |
Reports |
You can now generate PDF reports again when you are logged in via single-sign on. We first introduced this feature for single-sign on with PRTG version 22.2.77.2204, yet it did not work anymore in the previous PRTG version. The PDF report only displayed the text Unauthorized instead of the report data. |
Python Script Advanced |
With PRTG version 23.2.83 we deliver a new Python distribution. Python distribution 3.9.13 includes security patches and several other improvements. Please make sure your custom Python scripts are compatible with Python version 3.9.13. You only need to consider the change if you are using the Python Script Advanced Sensor. |
PRTG application server ports |
The new UI and PRTG API v2 will now be served under port 1616 (HTTPS) or 1615 (HTTP). We exchanged the old configured ports HTTPS 8443 and HTTP 8080 because we experienced issues in certain cases that the PRTG application server could not start. Please ensure that these ports are not blocked by your firewall and be sure to update any bookmarks and hardcoded URLs. The Open new UI button in the classic UI will be updated automatically. |
Discontinued NetApp Sensors with upcoming PRTG versions |
With PRTG version 23.2.83 you will receive a to do ticket for your NetApp sensors that you still can add but they will no longer work when you update to ONTAP 9.13.1. NetApp ONTAPI will no longer be available by the end of July and NetApp delivers a new RESTful API (ONTAP REST API) for ONTAP based storage systems. With PRTG version 22.3.79.2108 we introduced new NetApp v2 (BETA) sensors that support ONTAP 9.6 and higher. Please also see our Knowledge Base article for more information: https://kb.paessler.com/en/topic/90198 |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.1.83.1742
|
Docker Container Status |
Your Docker Container Status sensors may run into an error with the message bad certificate when you update to this PRTG version 23.2.83. We are currently analyzing the issue.
Solved with PRTG 23.2.84.1566 |
Cache recalculation |
The update to this PRTG version will in most cases immediately cause a cache recalculation upon starting the PRTG server. While PRTG is usable during the cache recalculation, it will considerably consume more hardware resources like CPU and memory. Depending on your monitoring configuration, you may encounter negative effects on the performance of PRTG during this process. We recommend that you reserve extra time for the PRTG update. |
NetApp SnapMirror v2 |
You will now receive the NetApp SnapMirror v2 sensor as a result when you add a sensor to a device on the Add sensor page. The sensor did not appear before when you searched for NetApp sensors and the radio button for Storage and File server was active. |
REST Custom v2 |
|
Redfish |
You will now receive results for Redfish sensors when you add a sensor from a device and search for the term Fujitsu on the Add sensor page /addsensor.htm. The sensors listed are Redfish Power Supply sensor (NEW), Redfish System Health sensor (NEW) and Redfish Virtual Disk sensor (BETA). |
PRTG Probe adapter |
With this PRTG version we deliver the DLL file for the PRTG probe adapter by default with the PRTG installer, to make the setup and the use of the Multi-Platform Probe easier. For more information about the Multi-Platform Probe please see our Knowledge Base article: https://kb.paessler.com/en/topic/90140 |
Controls |
|
Device Settings |
|
Web Interface |
|
API |
We improved the order of the settings of objects for the experimental section experimental/devices/ID/settings with the most used and most important settings at the top. |
Licenses |
You can now run the PRTG application server and activate the new UI with a PRTG Enterprise license. This did not work before in the previous PRTG version when you used a PRTG Enterprise license. The error message returned was The functionality of your PRTG installation is currently limited. License is inactive. |
PRTG application server |
|
All parts of PRTG |
Various other minor fixes and improvements. | Languages |
We updated the German and Spanish language files. |
Security |
We updated the ITOps to version 3.7.2 to fix an improper access control in the API which could have led to unwanted data leakage (CVE-2023-29488). |
By Michael Becker • Mar 1, 2023
OPC UA sensors |
The OPC UA Certificate, OPC UA Custom and OPC UA Server Status sensor types now support insecure connections to your OPC UA server with username and password authentication. Note that if you use this configuration, your data including passwords will be transmitted unencrypted. Thank you for your feedback that the ability to monitor devices with such configurations is needed in several use cases. |
Sensors |
Additionally to the Exchange PowerShell, Citrix and EXE sensors in Paessler PRTG version 22.3.79, we also improved the method of password transmission for the following sensor types:
|
Vulnerability |
We fixed a vulnerability that affected certain exe sensors. We thank the reporter who brought this vulnerability to our attention. |
Updates |
PRTG now uses HTTPS by default when downloading new software versions for the PRTG auto-update. |
SMTP&POP3 Round Trip |
We fixed an issue with the SMTP&POP3 Round Trip sensor that did not report an error if no email was found in the relevant mailbox. The issue was caused by the sensor matching any email on the mail server. |
SSL Certificate |
The SSL Certificate sensor works with a Virtual Host (SNI Name) again even if the SNI name does not contain a dot (.). In previous versions, the sensor showed a down status with the error message Connection reset by peer (socket error # 10054) if the SNI name had no dot. For example, the sensor still worked as expected with example.com but not with example as SNI name. Additionally, the SSL Certificate sensor now supports domains that contain an umlaut (like ü or ä) in the name. |
Access rights |
Read-only users can change their password by themselves again if the PRTG System Administrator enables the option Allow user to change the account password in their user account settings. |
PRTG Core Server |
We fixed an issue where in some cases certain licensee names caused the service for the PRTG core server to stop. The issue occurred during the license activation process. |
Remote probes |
The automatic update of a large number of remote probes to the latest PRTG version properly works again. In previous versions, remote probes required a manual update after 20 automatically updated remote probes. |
Tutorials |
You can now watch again the PRTG Tutorial: Creating Maps on the PRTG Welcome page. The link did not work anymore in the previous versions. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 23.1.82.2026
|
Stability |
The new UI is now stable enough to be activated on production systems. Previously, we recommended that you activate the new UI only in test environments. When you activate it, you can use it side-by-side with the classic UI. Please note that the new UI and PRTG API v2 are still in an ongoing development process and that several features are missing. For further information about features, requirements and known issues for PRTG API v2 and the new UI please see our Knowledge Base article: I want to use the new UI and API v2. What do I need to know? |
HTTP v2 |
|
Ping v2 |
The Response Time channel is now set as the primary channel for the Ping v2 sensor if you created the sensor with Inverted Error Status disabled and multiple pings. The sensor still shows the Status channel as the primary channel if you enabled the Inverted Error Status feature when creating the sensor. |
Script v2 |
You can try out the experimental Script v2 sensor that also works on the Multi-Platform Probe. The sensor executes a Python script that returns data in JSON format and shows the exit code. This way you can create your own custom script sensors that may not be available in PRTG by default. For available example scripts and how to use them, please see the Knowledge Base article: https://kb.paessler.com/en/topic/91349 |
Controls |
|
Mobile View |
The mobile view now shows channels with unknown lookup states. |
Channels |
We fixed an issue in the sensor graphs section to avoid the risk of possible cross-site scripting (XSS) attacks. |
Security |
We fixed an issue for sensor channel values that were sometimes displayed in too large numbers. |
Web Interface |
|
Devices |
|
Sensors |
We fixed an issue in the experimental section for the settings endpoints /experimental/sensors/ID/settings and /experimental/devices/ID/settings. The settings were returned empty after you created a device or sensor. |
Channels |
We renamed the scale field in the payload of channels to scaling and improved the description. |
Web Interface |
We fixed an issue for sensor channel values that were sometimes displayed in too large numbers. |
All parts of PRTG |
Various other minor fixes and improvements. |
Languages |
We updated the German and Spanish language files. |
By Michael Becker • Dec 14, 2022
FTP sensors |
We fixed an issue for FTP sensors that in some cases displayed the error message Start SSL negotiation command failed. (SSL/TLS not available). The issue occurred in cases when a connection with a TLS-only port was established. |
HPE 3PAR Drive Enclosure |
We fixed an issue for the HPE 3PAR Drive Enclosure sensor that in some cases showed an error during the sensor creation process. The error message displayed was The queried field 'FormFactor' is empty. |
HTTP Push Data |
We fixed an issue for the HTTP Push Data sensor that showed an access violation error with the message Failed to handle request. Sensors that were affected are HTTP Push Data sensor, HTTP Push Data Advanced Sensor and HTTP IoT Push Data Advanced sensor. The issue occurred in cases when you used the port 5051 for HTTPS connection with TLS. |
MQTT Subscribe Custom |
We fixed an issue for the MQTT Subscribe Custom sensor that returned the error message The received JSON data could not be parsed. This happened in cases when the JSON string could not be parsed completely due to additional characters. |
Zoom Service Status |
The channels of your Zoom Service Status sensors will now be displayed correctly again. Regions have been introduced by Zoom recently and components have the same naming as regions, that is why channels in the Zoom Service Status sensor were displayed multiple times in the previous PRTG version. To monitor the Zoom groups and components you have to add the Zoom Service Status sensor again. You will also receive a to do ticket for this sensor type with further information. |
CPU usage |
We fixed an issue that occurred with Paessler PRTG version 22.4.80.1553 for denied remote probes that caused high CPU usage in the core server of PRTG. If you had IP addresses of remote probes in the Deny IP Addresses filter under Core & Probes this would lead to an increase in the CPU load as the issue was in the communication for disconnected connections to the core server of PRTG. |
PRTG Administration Tool |
You can now send logfiles to Paessler again from the PRTG Administration Tool in the tab Logs and Info via button Send Logs to Paessler. |
Security |
We fixed an issue in the tag handling system regarding tag parameters to avoid the risk of a possible Cross Site Scripting (XSS) attack. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 22.4.81.1504
|
Discontinued Sensors with PRTG 22.4.81 |
With PRTG version 22.4.81 we discontinue the following sensor types: Dropbox sensor, Google Drive sensor, Google Analytics sensor, Microsoft OneDrive sensor. These sensor types were announced as deprecated with PRTG version 22.3.78.1873. If you run any of these sensor types they will show a down status when you update your PRTG installations to version 22.4.81. You can pause existing sensors afterwards but you will not be able to deploy them anymore. For further information about sensor deprecation and discontinuation in general as well as successor sensors and sensor alternatives please see our Knowledge Base articles: What do deprecation and discontinuation in the context of sensors mean? and What sensors are deprecated and what are their successors or alternatives? Note: We also announced the deprecation for the Amazon CloudWatch sensors with PRTG 22.3.78.1873 and that they will be discontinued with PRTG 22.4.81. However, since these sensor types still have a high utilization rate we will postpone their discontinuation until further notice. |
HTTP v2 |
You can try out the experimental HTTP v2 (BETA) sensor that we introduce with this PRTG version. This sensor allows you to send a HTTP request (HEAD, GET or POST) and use placeholders, similar to the REST Custom v2 sensor. |
Ping v2 |
You can try out the experimental Ping v2 (BETA) sensor that we introduce with this PRTG version. This sensor keeps the basic ping settings to send one single ping or send multiple ping requests and comes with a new setting Inverted Error Status. If you select Enable for this new setting, the sensor shows a Down status if the target device is reachable. Note: This setting is currently only available during sensor creation, however, you can change the relevant lookup in the reachable channel afterwards to disable the Inverted Error Status. Multi-Platform Probe: Both HTTP v2 sensor and Ping v2 sensor work with the multi-platform probe that we first mentioned in the PRTG 21.4.73.1656 release notes when the multi-platform probe started its initial alpha phase. For more information please see our Knowledge Base article: https://kb.paessler.com/en/topic/90140 |
Sensors |
|
Channels |
|
Web Interface |
|
API |
|
PRTG application server |
We improved stability and performance of the PRTG application server. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German and Spanish language files. |
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Preview 22.4.80.1542
|
Connection |
We fixed an issue for probes that in some cases were disconnected due to a false connect timeout value. The issue occurred when you updated to the previous preview version 22.3.80.1498. |
All languages |
We updated and improved all language files. |
By Michael Becker • Nov 21, 2022
Installer |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 22.4.80.1553
Preview 22.3.80.1498
They will be documented in the release notes also for future versions. These hashvalues confirm the integrity of the PRTG installer and that it originates from a trusted source. |
Microsoft 365 Service Status Advanced |
We improved the filtering process of issues from the Graph API for the Microsoft 365 Service Status Advanced sensor. |
Redfish Power Supply |
Your Redfish Power Supply sensors now handle null values correctly and work again as expected. In some cases, the sensor failed with the following error message displayed in the Result of Sensor Log: The queried field Status.Health has an unknown value: The following reverse lookup value is invalid: . Valid reverse lookup values are: Critical, OK, Offline, Warning. |
Veeam Backup Job Status |
We fixed an issue for the Veeam Backup Job Status sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized due to a missing slash sign in the /api/sessionMngr/? API call. |
Cloud HTTP sensor, Cloud Ping sensor |
With PRTG version 22.3.80 we discontinue the Cloud HTTP sensors and Cloud Ping sensors, for which you received a to do ticket for with PRTG 22.3.78.1873. If you run Cloud HTTP sensors and Cloud Ping sensors on your PRTG installation they will be paused automatically to preserve the sensor history. These sensor types will be replaced with their successor versions Cloud HTTP v2 sensor and Cloud Ping v2 sensor when updating to PRTG version 22.4.80. Please also see our Knowledge Base article about the migration of the Cloud sensors: https://kb.paessler.com/en/topic/91091 |
NetApp System Health v2 |
We fixed an issue for the NetApp System Health v2 sensor (BETA) that in some cases displayed the error message The following reverse lookup value is invalid: multi_path_ha. The issue was caused by a missing status in the relevant lookup file. |
NetApp v2 sensors |
|
Port v2 |
You can try out the experimental Port v2 sensor (BETA) that combines the features of the Port sensor and Port Range sensor. The sensor comes with the channels Maximum Connect Time, Open Ports, Closed Ports and Errors and will send you alerts depending on your settings about open or closed ports. Note: If you use a larger port range in the Port List of the sensor Settings, the sensor may remain in the unknown status for an uncertain period of time since it performs a scan for each port. To avoid this condition, please increase the Scanning Interval of the sensor. |
Sensors |
|
API |
|
API Keys |
You can now use API keys, that you can generate in the PRTG web interface under My Account in the Setup menu in the API keys tab, for the new API. With the API key you can authenticate yourself in the new API without implementing login credentials in a script or integration. The API keys can also be used once for endpoints in the Swagger UI for each Swagger session and they will be sent automatically afterwards with each request. |
Documentation |
We improved the documentation. |
PRTG application server |
The application server now handles errors correctly when a webserver cannot be created. |
Discontinued Sensors with PRTG 22.x.81 |
With this version we inform you again about the deprecation of the following sensor types, for which you will receive a to do ticket for: Google Drive sensor, Microsoft OneDrive sensor, Dropbox sensor and Google Analytics sensor. Running sensors of these types will still work, but you will not be able to deploy them anymore. We already announced the deprecation of the mentioned sensor types with PRTG 22.3.78.1873, as well as of Amazon CloudWatch sensor, Cloud HTTP sensor and Cloud Ping sensor. As of PRTG version 22.x.81 that we plan to release in Q4 2022, all these sensor types will be discontinued and stop working. For further information about sensor deprecation and discontinuation in general please see our Knowledge Base article: https://kb.paessler.com/en/topic/90680 |
Microsoft 365 Mailbox |
The Microsoft 365 Mailbox sensor currently cannot match emails when you use special (non-ASCII) characters in the filter options Filter by 'subject' with Contains all or Contains any, for example words with accents like "é". This issue is located in the library where URL encoding does not work properly. As a workaround, you can manually URL encode those parts you want to have URL encoded. We will deliver a fix for this issue in the upcoming PRTG versions. Solved with PRTG 23.2.83.1760 |
PRTG Administration Tool |
You currently cannot send logfiles from the tab Send Logs to Paessler via PRTG Administration Tool. Sending logfiles results in an error with the message Error connecting with SSL. As a workaround, please use the Contact Support option in the PRTG web interface that can be found in the Setup menu. We will deliver a fix for this issue in the upcoming PRTG versions. Solved with PRTG 22.4.81.1532 |
Security |
PRTG is currently affected by a CSS vulnerability with low severity (CVE-2022-35739). For more information please see the Knowledge Base article: https://kb.paessler.com/en/topic/91149 Solved with PRTG 23.2.83.1760 |
Zoom Service Status |
Some zoom components that belong to regions in the Zoom Service Status sensor will be displayed as channels multiple times. Regions have been introduced by Zoom recently and components have the same naming as regions. The Zoom Service Status sensor is not updated yet to use the Zoom structure for components. We are currently working on a fix for this issue. Solved with PRTG 22.4.81.1532 |
Cache recalculation |
The update to this PRTG version will immediately cause a cache recalculation upon starting the PRTG server. While PRTG is usable during the cache recalculation, it will considerably consume more hardware resources like CPU and memory. Depending on your monitoring configuration, you may encounter negative effects on the performance of PRTG during this process. We recommend that you reserve extra time for the PRTG update. |
Tree version update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated and improved all language files. |
German and Spanish |
We updated the German and Spanish language files. |
Public maps |
You can access public maps without login again. This did not work in the previous preview version 22.3.79.2073. |
NetFlow sensors |
NetFlow sensors show available IP addresses on which PRTG listens to NetFlow packets again. This was not always the case in the previous preview version 22.3.79.2073. |
SNMP v3 sensors |
We removed the update of the net-snmp library again, as well as the enhanced authentication methods and encryption types for SNMP v3. Sensors that use SNMP v3 caused increased memory usage in the previous preview version 22.3.79.2073 due to a memory leak in the updated library. |
By Michael Becker • Sep 30, 2022
FortiGate System Statistics sensor |
The new FortiGate System Statistics sensor monitors the system health of a Fortinet FortiGate firewall via the Representational State Transfer (REST) application programming interface (API). We released this sensor type as experimental sensor with PRTG version 21.4.73.1656. |
Microsoft 365 Mailbox sensor |
The Microsoft 365 Mailbox sensor monitors a Microsoft 365 mailbox. We introduced this sensor type as experimental sensor with PRTG version 22.3.78.1873 and implemented several improvements since then.
|
API |
With PRTG version 22.3.79 you can create and manage API Keys for any PRTG User. The API Key can then be used as a parameter in any call instead of the username and password (or passhash) to interact with PRTG's HTTP API. The syntax for using the API Key looks as follows: &apitoken=myapitoken.You can find the new Tab API Keys on the Setup page under Account Settings and under System Administration in the User Accounts settings. |
Modbus sensors |
You can now add up to ten Modbus values for the Modbus TCP Custom sensor and Modbus RTU Custom sensor in the Modbus Channel Specific settings to monitor your metrics. |
NetFlow sensors |
The sensor types NetFlow v5, NetFlow v9, and their custom variants are now able to listen for UDP packets on IPv6 addresses. |
Sensor Security |
We improved the method of password transmission for the Exchange PowerShell, Citrix and EXE sensor types to make them more secure. The transmission happened in cleartext format before and is now encrypted so that the passwords are no longer visible in Windows Event Log or Task Manager. Improved sensor types are as follows:
|
Script sensors |
We added a new section Credentials for Script Sensors for placeholders in the sensor Settings where you can enter your credentials as parameters and which are displayed as masked. The following sensors support the new placeholders %scriptplaceholder1 up to %scriptplaceholder5: EXE/Script sensor, EXE/Script Advanced, SSH Script sensor, SSH Script Advanced sensor, Python Script Advanced sensor. You can use the new placeholders in the parameter field for Command-line Parameters. |
Server |
We updated our OpenSSL libraries to version 1.0.2ze that patches the CVE-2022-1292 vulnerability. The c_rehash script does not properly sanitise shell metacharacters to prevent command injection, where attackers could execute arbitrary commands with the privileges of the script. |
EXE/Script sensors |
With PRTG Version 22.3.79 you won't be able to use DLL files as sensors anymore. We removed this feature for EXE/Script sensor and EXE/Script Advanced sensor in the Sensor Settings for the EXE/Script function since it will be deprecated. |
AWS Cost sensor |
The AWS Cost sensor now correctly calculates the forecast values again in the given forecast channels. |
Core Health (Autonomous) |
|
FTP sensor |
We fixed an issue for the FTP sensor where in some cases the sensor displayed the error message OK (530 - Login incorrect.) but nevertheless stopped working. You can now use the FTP sensor again even if it cannot log on to the FTP server because of a wrong password. The error message shows that the credentials are incorrect but the sensor remains in the up status. |
HTTP sensors |
|
HTTP Transaction |
We fixed an issue for the HTTP Transaction sensor where HTTP requests did not work anymore because the sensor created a new Result of Sensor logfile with every scan and exceeded the Windows character limit at some point. The sensor now uses the initial logfile again. |
Microsoft Azure Virtual Machine |
Your Microsoft Azure Virtual Machine sensor now displays all existing virtual machines from your Azure environment in the list. The list only showed 50 virtual machines even if there were more available. |
NetApp LUN |
We fixed an issue with the NetApp LUN sensor where in certain cases the sensor showed the message error and stopped working due to LUN data that could not be found. |
SSL Certificate |
The SSL Certificate sensor now also works when monitoring endpoints that require client authentication. In previous versions, the sensor showed a down status with the error message Error getting certificate information: Not Connected in such cases. |
Sensor creation |
PRTG now aborts the scan for available monitoring items and shows a suitable error message in the Add Sensor dialog if the target URL is invalid or the target device does not respond. In previous versions, the meta-scan when adding a sensor never finished and the dialog window got stuck in such cases. |
Login |
Failed login attempts are now logged again in the WebServer.log. In the previous PRTG versions, the failed login attempts were not listed anymore to comprehend why Overload Protection is active. For more information about Overload Protection please see our Knowledge Base article: https://kb.paessler.com/en/topic/25523 |
Memory usage |
We fixed several smaller memory leaks on the PRTG server. |
Security |
We fixed an issue for SSL passwords in the Core Activation Log that were displayed in a readable format and that are now masked again. The issue only appeared for the Log in Debug Level. |
Start-up |
We improved the underlying process of restarting and updating the PRTG server. In previous versions, a check for CSRF tokens could possibly interfere with the server start. |
Contact Support |
We replaced the old link for our Contact Support options on the pages Help and Support Center and Change License Key in PRTG with the new one redirecting to our Helpdesk portal. |
Cisco Meraki sensors |
The experimental sensor types Cisco Meraki License BETA and Cisco Meraki Network Health BETA now include the organization name in the instance name so that you can easily recognize to which organization the Meraki sensor refers to. |
FortiGate VPN Overview sensor |
We fixed an issue for the FortiGate VPN Overview sensor where VPN tunnels were shown as down even if the tunnels were up, due to a not linked dial-up entry for the parent link. |
NetApp v2 sensors |
You can try out the experimental sensor types NetApp Aggregate v2 (BETA), NetApp LIF v2 (BETA), NetApp NIC v2 (BETA), NetApp Physical Disk v2 (BETA), NetApp I/O v2 (BETA), and NetApp LUN v2 (BETA) that support the new ONTAP REST API as of ONTAP 9.6. We introduce new NetApp sensors based on REST API as with ONTAP 9.6 NetApp delivers a new RESTful API for ONTAP based storage systems. Note: You must have ONTAP REST API version 9.11 or higher to see two additional channels, Battery State and Storage Configuration, that we introduced with NetApp System Health v2 sensor. You also need ONTAP REST API version 9.11 or higher to create an NetApp I/O v2 sensor. |
Controls |
|
Errors |
We updated several error messages. They now contain more information about the corresponding objects and details about the failed object actions. |
Sensors |
You can now update the acknowledge message and the duration until which a sensor stays in the Down (Acknowledged) status. |
Web interface |
|
Web interface |
|
Documentation |
We improved the documentation. |
PRTG application server |
|
Languages |
We updated the German and Spanish language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
By Michael Becker • Aug 17, 2022
AWS RDS v2 sensor |
The new AWS RDS v2 sensor monitors the performance of an RDS database instance via the AWS API and will be the successor of the Amazon CloudWatch RDS sensor. We released this sensor type as experimental sensor with PRTG 21.3.71.1416. |
IMAP & POP3 Roundtrip sensors |
We updated the defaults for Transport-Level Security in the sensor Connectivity settings. The new default port for IMAP sensor and SMTP&IMAP Round Trip sensor will be port 993. For POP3 sensor and SMTP&POP3 Round Trip sensor it will be port 995. These sensor types now use Enforce Transport Level Security as default in the Connectivity settings. |
AWS EC2 v2 sensor |
You can add the AWS EC2 v2 sensor again as expected even if some services in a region cannot be accessed. In rare cases the sensor failed with the error message You are not authorized to perform this operation. |
Cloud v2 sensors |
|
FTP sensor |
We fixed an issue for the FTP sensor that failed in certain configurations after updating to the last PRTG version 22.2.77.2204. The issue occurred when the sensor tried to connect during the authentication step and therefore the sensor came up with the error message Start SSL negotiation command failed. (SSL/TLS not available). |
HTTP Advanced sensor |
You now receive a proper error message for your HTTP and HTTP Advanced sensor when the Proxy server requires credentials in the Proxy Settings for HTTP Sensors. |
HTTP Apache sensor |
We fixed an issue where HTTP Apache sensors consumed to much memory, resulting in a memory leak on the PRTG probe system. |
Redfish System Health sensor |
You now receive a proper error message for your Redfish System Health sensor when a drive of an according controller does not report back. Before, the sensor only reported that the request had failed. |
SSH sensors |
To increase our support for older SSH systems, we extended our list of encrypted algorithms for the SSH sensors. Affected sensors, like the SFTP Secure File Transfer Protocol sensor, ran into an error when, for example, the SSH server for Windows did not support secure algorithms. Your SSH sensors will now work again as expected. You can find a list of supported SSH algorithms here in our Knowledge Base article: https://kb.paessler.com/en/topic/90689. |
SNMP Fujitsu System Health v2 sensor |
In certain cases, the SNMP Fujitsu System Health v2 sensor could not be created via auto-discovery device template. Adding the sensor with auto-discovery now works again as expected. |
WMI Vital System Data Sensor |
You can add the WMI Vital System Data Sensor again as expected. The sensor now correctly reports Bytes Received and Bytes Sent in the appropriate channels, these values were previously inverted. Only new created sensors were affected by this issue. |
API |
|
Stability |
We fixed an issue that led to access violations in the Core.log when objects in PRTG were deleted while auto-discovery was running. |
Passwords |
We fixed an issue in the CoreWebServer.log that contained readable passwords and passhashes. This occurred only in cases when the login with password or passhash failed. |
Common SaaS sensor |
We removed the Common SaaS sensor from the auto-discovery as it will be discontinued in upcoming PRTG releases. The sensor is no longer created during initial and manually triggered auto-discovery. |
Python Script Advanced |
PRTG Version 22.2.77.2204 broke compatibility with pip.exe install (to install Python packages). With this PRTG release we have removed support for this command to prevent unexpected errors. As of now the only supported way of installing a Python package to use Python Script Advanced sensor is python.exe -m pip install |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
FortiGate VPN Overview sensor |
We improved the experimental FortiGate VPN Overview sensor concerning data that is received from the FortiGate API. |
Microsoft 365 Mailbox sensor |
You can try out the experimental Microsoft 365 Mailbox sensor that we created to be ahead of the deprecation for basic authentication. The Microsoft 365 Mailbox sensor authentication option is based on OAuth2. Microsoft is retiring basic authentication starting in October and IMAP and POP3 including Roundtrip sensors will stop working accordingly. We are looking forward to receive your early feedback for the experimental Microsoft 365 Mailbox sensor that you can send to [email protected]. |
NetApp |
For the NetApp System Health v2 sensor and NetApp Volume v2 sensor we made the User Name in the settings for Credentials for NetApp visible, it was masked before. Due to this change you need to pause, resume and rescan these NetApp Beta sensors manually to make them work again. |
Controls |
The refresh timer on the bottom of the new PRTG web interface is now part of the tab index again and can be focused via keyboard navigation as expected. |
Device tree |
We have added a new resizable split-screen mode for the device tree. |
Device list |
Sorting items by probe name or location now correctly takes empty fields into account again. |
Sensors |
|
Web interface |
|
Documentation |
We improved the documentation. |
PRTG application server |
|
Swagger UI |
We updated Swagger UI to the latest stable version to close a potential XSS vulnerability. |
All parts of PRTG |
Various other minor fixes and improvements, updated German and Spanish language files, updated user manual. |
Discontinued Sensors with PRTG 22.x.81 |
We announce the deprecation of the following sensor types that you will receive a to do ticket for: Amazon CloudWatch sensors, Dropbox sensor, Google Drive sensor, Google Analytics sensor, Microsoft OneDrive sensor, Cloud HTTP sensor, Cloud Ping sensor. We will discontinue these sensor types with PRTG version 22.x.81 that we plan to release in Q4 2022. Running sensors of these types will still work for some more versions, but you will not be able to deploy them anymore. For further information about sensor deprecation and discontinuation in general please see our Knowledge Base article: https://kb.paessler.com/en/topic/90680. |
Gitlab Build Status sensor |
With this version we discontinue the already deprecated Gitlab Build Status sensor. The sensor was deprecated with PRTG 21.1.65.1767 and will now no longer provide any data. You will as well receive a notification with further instructions if you run this sensor. |
Microsoft 365 Service Status sensor |
Your Microsoft 365 Service Status sensors and Microsoft 365 Service Status Advanced sensors will run into an error with the message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. (code: PE270) when updating to this PRTG version. You need to pause and resume these sensor types to make them work again. |
Map backgrounds, Device templates |
Your additionally added map backgrounds and device templates are available again on Paessler PRTG hosted monitor installations. |
All languages |
We updated and improved all language files. |
Memory usage |
We fixed an issue that appeared in the previous preview version 22.2.77.2033 where PRTG probes showed too high memory usage under specific conditions, resulting in a memory leak on the PRTG probe system. Please note that with certain configurations memory usage still might be a bit higher than in previous versions. |
Cluster |
PRTG System Administrator user accounts can open and edit settings under Setup on cluster failover nodes again. In the previous preview version 22.2.77.2033, PRTG System Administrator users could not open the setup pages on a failover node and received the error message Read-only user accounts are not allowed to access this web page. |
Single sign-on |
Single sign-on correctly validates the used PRTG license again. This did not properly work in the previous preview version 22.2.77.2033. |
By Michael Becker • Jul 4, 2022
Elasticsearch Upgrade |
ITOps Board has been updated to use Elasticsearch 7.17.0. |
New SLA Report |
This release introduces a new PDF report for SLA availability statistics across multiple business services. The report allows you to view SLA statistics on a weekly or a monthly basis, and contains the following information: Report summary, combined SLA statistics, individual SLA statistics. |
Enhancements to Boards |
The Boards page has been enhanced to improve loading time and provide additional page view and filtering options. You can now choose to show a maximum number of boards on the page; you can reduce the page load time by decreasing the number of boards to show. The Filters panel contains the following page view and filtering options: Display Top, Visualize by, Sort by, Display Board States, Health Rollup Types, Exclude Child Boards, Display Boards with. |
Maps |
We added a validation for the image upload in maps that minimizes a potential risk in uploading files with arbitrary content. |
Command line parameters |
We added the command line parameters /datadir and /snmpCommunityStrg to change the PRTG data path and the SNMP community string at first installation via command line. |
Python Script Advanced |
With PRTG version 22.2.77 we deliver a new Python distribution. Python distribution 3.9.12 includes security patches, for example CVE-2021-3177, and several other improvements, as well as we renamed the Python helper library from prtg to paesslerag_prtg_sensor_api. After installing PRTG version 22.x.77, PRTG creates a ticket that informs you about the Python update. Please make sure your custom Python scripts are compatible with Python version 3.9.12. You only need to consider the change if you are using the Python Script Advanced Sensor. For more information, see our Knowledge Base article https://kb.paessler.com/en/topic/90484. |
Auto-Discovery |
We fixed an issue that occurred for several newer sensor types during auto-discovery. The sensors could not be added if an additional scan for a scheduled auto-discovery was carried out, however, it worked for the first scan. One affected sensor was, for example, the Veeam Backup Job Status Advanced sensor. The auto-discovery options now work again as expected. |
Channels |
Newer sensor types that previously displayed bandwidth measurements in Bytes only now take the configured channel unit configuration for Bytes (Bandwidth) into account. We fixed this behavior for sensor types like Amazon CloudWatch, WMI Logical Disk v2, and WMI Physical Disk v2. Also newer sensor types now include channel unit configuration like AWS EBS v2 and AWS RDS v2, as well as custom sensor types like the EXE/Script Advanced sensor. |
HTTP sensors |
We fixed an issue where the option for SNI inheritance did not work correctly for affected sensor types HTTP sensor, HTTP Advanced sensor and HTTP Data Advanced sensor. Note: If you use the option Inherit SNI from parent device for the mentioned sensor types, you need to enter the IP address as host name in the parent device settings. Otherwise your sensors may run into the error with the message Error connecting with SSL. |
Microsoft Azure SQL Database |
The Microsoft Azure SQL Database sensor is now able to monitor databases with umlauts in the name string. |
Modbus sensors |
We improved the connection stability of Modbus RTU Custom and Modbus TCP Custom sensors. In certain cases, the Modbus sensors switched between warning and up status and returned an unknown error. |
Redfish sensors |
We improved the handling of optional fields in the Redfish System Health sensor and Redfish Virtual Disk (BETA) sensor to avoid an unnecessary warning status. In such cases, the sensors went into a warning status with the message Error: The queried field "Status.State" is empty. |
SNMP sensors |
We fixed an issue that occurred in very rare cases when adding SNMP Traffic or other SNMP sensors ran into a timeout. The sensors could not be added successfully. This affected, for example, certain Cisco, Arista, and Fortinet devices. |
SSL Security Check |
SSL Security Check sensors now correctly show the message Weak Protocols Available if TLS 1.1 is accepted. |
VMware Host Performance (SOAP) |
The VMware Host Performance (SOAP) sensor now correctly displays watt as unit of the Power channel. Previously, the sensor showed a hashtag (#) instead. |
Configuration |
We fixed an issue for notifications where in rare cases missing lookup files caused the notification delivery for PRTG to stop working. |
Notifications |
We fixed an issue for notifications that stopped working in some cases due to unavailable lookups that create a todo ticket. |
Reports |
You can now generate PDF reports when you are logged in via single sign-on. This was not supported before. |
Cisco Meraki Network Health |
We hardened the process of adding the Cisco Meraki Network Health (BETA) sensor. |
PowerShell Security Enhancement |
We improved the experimental PowerShell Security Enhancement feature for EXE/Script sensors that in some cases caused executed scripts to return 0 as a value. As a consequence, custom EXE/Script PowerShell sensors did not work anymore when you enabled the feature. |
REST Custom v2 |
|
Web interface |
|
Device tree |
We added buttons that allow you to collapse and expand the device tree. |
Navigation |
|
Controls |
We fixed a bug that caused an unknown error when an object was deleted while it was opened by another user. |
Filters |
|
PRTG application server |
|
Languages |
We updated and improved all language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
StartTLS connectivity |
For sensors using the StartTLS option Use transport-level security if available using StartTLS (default) in the Connectivity settings, you have to select Use transport-level security if available or better Enforce transport-level security if they use a TLS only port (which is 993 for IMAP or 995 for POP3). If a setting with StartTLS option is used, on a TLS only port in this case, the sensors now correctly try to connect to the server unencrypted first and may run into a timeout. Affected sensors are, for example, IMAP sensor, POP3 sensor, SMTP&IMAP Roundtrip sensor, SMTP&POP3 Roundtrip sensor. |
Access rights |
Read-only users that have the option set for Allow user to change the account password under User Accounts on the Setup page, can currently not change their password in this version. The password needs to be changed by the administrator in these cases. |
HTTP Apache sensors |
The sensor types HTTP Apache ModStatus PerfStats and HTTP Apache ModStatus Totals may cause increased memory usage on the probe system in this version. Please increase the scanning interval of HTTP Apache sensors on your probe or reduce the number of running HTTP Apache sensors until the next PRTG version is available if too much memory is consumed. |
Microsoft Azure SQL Database |
The Microsoft Azure SQL Database sensor works again. Due to a change in the Azure API, the sensor recently showed a down status with the error message The queried field "average" is empty. on all instances. |
Languages |
We updated the German and Spanish language files. |
By Michael Becker • May 9, 2022
Okta |
You can now use Okta as provider for single sign-on (SSO) to login to PRTG with multi-factor authentication. Okta is the second SSO provider that you can integrate to PRTG. Azure Active Directory (Azure AD) is available since PRTG 21.2.68. You can choose the SSO provider that you work with in the system administration of PRTG and configure the settings for your SSO access. Please note that this feature is only available for Paessler PRTG Network Monitor, not for Paessler PRTG Hosted Monitor. |
AWS Alarm v2 |
The new AWS Alarm v2 sensor monitors your favorite metric and composite AWS alarms and will be the successor of the existing Amazon CloudWatch Alarm sensor. |
AWS EBS v2 |
The new AWS EBS v2 sensor monitors the status and performance of an AWS EBS volume and will be the successor of the existing Amazon CloudWatch EBS sensor. |
AWS EC2 v2 |
The new AWS EC2 v2 sensor monitors the performance of an Amazon EC2 instance and will be the successor of the existing Amazon CloudWatch EC2 sensor. Note: If you use the same IAM policy that you use for the Amazon CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG? |
AWS ELB v2 |
The new AWS ELB v2 sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor. |
HPE 3PAR Drive Enclosure |
The new HPE 3PAR Drive Enclosure sensor monitors a drive enclosure of your HPE 3PAR storage system and shows status and temperature metrics. |
HPE 3PAR Virtual Volume |
The new HPE 3PAR Virtual Volume sensor monitors a virtual volume of your HPE 3PAR storage system and shows the status as well as used and free space on the volume. |
Redfish Power Supply |
The new Redfish Power Supply sensor monitors the status of the power supply of your servers, the power efficiency, and various other parameters. |
Redfish System Health |
The new Redfish System Health sensor monitors the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac. |
SNMP Rittal CMC III Hardware Status |
The new SNMP Rittal CMC III Hardware Status sensor monitors the hardware status of a Rittal CMC III processing unit and shows the status of every attached external sensor. |
Modbus sensors |
Modbus RTU Custom and Modbus TCP Custom sensors now support connection sharing for multiple unit IDs on the same device. Previously, connection sharing only worked for a single unit ID on a device, so that you could only create a few Modbus sensors until the maximum number of allowed sessions was reached. |
MySQL v2 |
The MySQL v2 sensor now supports MariaDB version 10.6 as we updated the MySQL data library that PRTG uses to version 8.0.28. |
PostgreSQL |
The PostgreSQL sensor now supports TLS 1.2 connections as we updated the Npgsql library that the PostgreSQL sensor uses to monitor your database to version 6.0.3. |
SSH sensors |
We updated the SSH library that SSH sensors use to monitor the target devices. The update improves the security of SSH sensors. |
Sensor security |
We updated the logging library log4net that several sensor types use to version 2.0.14 to improve the security of PRTG. Affected sensor types are DICOM sensors, Exchange Mailbox (PowerShell), HL7, NetApp (cDOT/ONTAP) sensors, Windows Update Status (PowerShell), SQL v2 sensors. |
Microsoft Azure SQL Database |
The Microsoft Azure SQL Database sensor works again. Due to a change in the Azure API, the sensor recently showed a down status with the error message The queried field "average" is empty. on all instances. |
Veeam Backup Job Status Advanced |
The Veeam Backup Job Status Advanced sensor now supports the status Postprocessing and shows more expressive error messages in many cases instead of just Reason: Unknown. or The queried field "Reason" is empty. |
XML |
The View as XML button returns data again when you generate the XML from a sensor's Logs tab, for example. |
Cisco Meraki Network Health |
The experimental Cisco Meraki Network Health (BETA) sensor now supports the uplink status not connected. |
NetApp Volume v2 |
You can try out the experimental NetApp Volume v2 (BETA) sensor that supports the new ONTAP REST API as of ONTAP 9.6 and will be the successor of the existing NetApp Volume sensor. |
Administration |
You can now globally hide the “Activate New UI And New API (Alpha)” banner in PRTG. For more information, see the Knowledge Base: https://kb.paessler.com/en/topic/90566. |
Improvement |
We reduced the installation size of the new PRTG web interface. |
Objects |
Objects that were moved or cloned now receive a correct update of their path. |
PRTG application server |
We fixed an issue that caused a start loop of the PRTG application server when the default port was blocked. |
Performance |
We have increased the performance of the PRTG application server. |
All parts of PRTG |
Various other minor fixes and improvements, updated German and Spanish language files, updated user manual |
Python Script Advanced |
PRTG version 22.2.77 that we will publish in June 2022 will include a new Python distribution. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.9 when you update to PRTG 22.2.77. You only need to consider the change if you are using the Python Script Advanced sensor. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/90484. |
Signature |
In certain cases, the PRTG core server does not start anymore after updating to PRTG 22.2.76 and the log file core.log contains the message
You can resolve the issue by adding the trusted root certificate for timestamp signature. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/90610. |
Server |
This version includes an important security update for your PRTG core server. We updated the OpenSSL library that PRTG uses to version 1.0.2zd, which patches the recently disclosed OpenSSL vulnerability CVE-2022-0778. For more information, see the Knowledge Base: https://kb.paessler.com/en/topic/90462. We recommend that you update as soon as possible. Note: Under certain circumstances, the PRTG core server could not successfully start after updating to version 22.1.75.1569 or 22.1.75.1588. We fixed the issue with PRTG 22.1.75.1594. |
All languages |
We updated and improved all language files. |
Data tables |
Data table pages on sensor data tabs appear in the correct order with newest entries on the first page again. In the last preview version 22.1.75.1521, the order of the data table pages was reversed. |
Performance |
We fixed an issue that resulted in degraded performance of the PRTG application server on larger installations, which was also noticeable with longer loading times when using the new user interface with the last preview version 22.1.75.1521. |
By Michael Becker • Mar 28, 2022
Server |
PRTG now sanitizes channel names to close a potential XSS vulnerability. (CVE-2021-42695) |
Packet Sniffer |
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 1.60. The new version includes several fixes and improvements compared to the previously delivered version 1.10. If you encounter issues with your Packet Sniffer sensors after the update, please see the Knowledge Base article https://kb.paessler.com/en/topic/86904 |
Single sign-on |
|
HTTP Push Data Advanced |
We improved the stability of the HTTP Push Data Advanced sensor. In previous versions, the sensor occasionally showed a down status with the error message could not bind socket after some time. The issue appeared in cases when there were more than one sensor of this type running. |
Microsoft Azure sensors |
Microsoft Azure sensors now can handle all name strings as specified in the Resource name rules by Microsoft. In previous versions, the Microsoft Azure SQL sensor, for example, could not handle whitespaces in elastic pool names and showed HTTP error 400 after creation. |
SQL v2 sensors |
SQL v2 sensors show data table values in the sensor message again if you enable the Use Data Table Value in Sensor Message setting. In previous versions, the defined value of the data table was missing in the message of the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, PostgreSQL, and Oracle SQL v2. |
Syslog Receiver |
We improved the reliability of the Syslog Receiver sensor in case of probe restarts to reduce issues with blocked ports. |
Historic data |
You can generate historic data files in XML and CSV format via the web interface again. In the previous version, running historic data reports for sensors did not work via the web interface and returned an Unauthorized error if the file format was XML or CSV. |
Stability |
This version comes with a number of stability improvements for the PRTG core server. |
Cisco Meraki sensors |
|
NetApp System Health |
You can try out the experimental NetApp System Health (BETA) sensor that supports the new ONTAP REST API as of ONTAP 9.6 and will be the successor of the existing NetApp System Health sensor. |
Redfish sensors |
We implemented several improvements for the experimental Redfish sensors.
|
REST Custom v2 |
You can now define up to 5 individual placeholders for the experimental REST Custom v2 (BETA) sensor in the Credentials for REST API settings of devices. You can use the placeholders, as well as newly introduced placeholders for credentials, in the Request URL, POST Body, and Custom Header fields of the REST Custom v2 sensor. PRTG does not display the corresponding values in the sensor log nor in the sensor settings. |
Device list |
You can now select the Device List view to see all devices on root group, probes, or groups. |
Web interface |
|
Controls |
The Open new UI button in the classic PRTG web interface in German language no longer causes the global sensor status symbols to overlap the search box. |
Tables |
We updated the style of linked sensor names in tables. |
POST Requests |
We increased the maximum size of the request body of POST requests to 15 kB. |
Sensors |
|
Certificates |
The PRTG application server does not use a hard-coded fallback certificate anymore. If the PRTG application server cannot load the provided certificate, it stops the startup process. |
Performance |
We have increased the performance of the PRTG application server. |
Documentation |
We improved the documentation. |
Probe transfer |
We improved the stability of the probe transfer when transferring large probe configuration files. |
Languages |
We updated and improved all language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
By Michael Becker • Feb 7, 2022
Server |
We hardened PRTG against Cross Site Request Forgery (CSRF) attacks. This prevents changes to PRTG via web forms not originating from PRTG that attackers may use to trick PRTG users into performing requests with the user account's context. (CVE-2021-34547) Note: API calls now always explicitly require credentials even if the user account is currently logged in in PRTG. Otherwise, PRTG will return Unauthorized. If you have issues with saving changes to settings, clear your browser cache with CTRL+F5 after updating and opening the PRTG web interface because we also updated the JavaScript version with this security improvement. |
AWS Cost |
You can now create device templates that include the AWS Cost sensor. You can use the device templates to add AWS Cost sensors via auto-discovery. |
DNS v2 |
|
Veeam Backup Job Status Advanced |
|
Oracle Tablespace |
We changed the name of the Database Size channel of the Oracle Tablespace sensor to Tablespace Size. Tablespace Size is the correct naming because this is what the channel monitors. The same is for the Tablespace Size on Disk channel that we accordingly changed as well. |
SSL Security Check |
We changed the TLS 1.1 (Strong) channel of the SSL Security Check sensor to TLS 1.1 (Weak). This means that the sensor will now show a warning status if the target device accepts TLS 1.1 connections. We also changed the TLS 1.2 (Perfect) channel to TLS 1.2 (Strong), which comes without a changed behavior for the sensor status. |
Channel Unit Configuration |
We changed the default channel units for probes, group, devices and sensors. New PRTG installations and newly created probes, group, devices, and sensors with turned off inheritance now have the following units defined by default as you can check in the Channel Unit Configuration settings.
|
SNMP Cisco CBQoS |
Running an auto-discovery with a device template that includes SNMP Cisco CBQoS sensors now successfully adds sensors of this type. In previous versions, this did not work due to incorrect entries for this sensor type in created device templates and the sensors were not added. |
API |
Filtering in table API calls returns only exact matches again. In previous versions, the filter also returned objects if it matched their prefixes. |
Cluster |
PRTG properly synchronizes the settings of notification templates from the master node to failover nodes again. In previous versions, defined settings of newly created notification templates were not taken over on failover nodes, which could result in notifications not being sent from a failover. |
Down (Acknowledged) |
The sensor message of sensors in Down (Acknowledged) status shows the original error message again. The error message was missing for acknowledged sensors in previous versions. |
Installation |
The command line parameter /LANG for the language used in PRTG works again when installing PRTG via command line as specified in the Knowledge Base article What command line codes and exit codes can I use with Paessler setups? You can now even use /LANG for silent installations. In previous version, PRTG was always installed with the default English language file when using the command line for setup. |
Libraries |
We fixed the channel selection of notification triggers in cloned libraries. In previous versions, you could not select a sensor channel in the settings of speed, threshold, and volume triggers if the library was a clone. |
Limits |
You can save changes to sensor channels again even if another channel of the same sensor has the setting Enable alerting based on limits with no defined limits activated. In previous versions, the input validation failed in such cases and you received an Error (Bad Request) dialog window with the message The validation of the data you entered failed. You have set Alerting to limit-based, but have entered no limit value. |
Cisco Meraki License |
You can try out the experimental Cisco Meraki License (BETA) sensor as of this version and monitor the status of your Meraki licenses. It shows days to expiration, license model, and license count. |
Cisco Meraki Network Health |
You can try out the experimental Cisco Meraki Network Health (BETA) sensor as of this version and monitor the health of Cisco Meraki network devices. |
FortiGate VPN Overview |
You can try out the experimental FortiGate VPN Overview (BETA) sensor as of this version and monitor VPN connections of your Fortinet FortiGate firewall. The sensor shows the number of connected SSL clients, as well as the number of both up and down IPsec tunnels. |
REST Custom v2 |
|
Context menus |
You can now open the corresponding context menu if you right-click linked objects or headers. |
Devices |
You can now sort sensor lists based on the time since the last scan. |
Notifications |
Line breaks in notifications no longer break up single words. |
Sensors |
Sensors now immediately display measurements after the start of the PRTG application server regardless of the sensor’s scanning interval. |
Documentation |
We improved the documentation. |
PRTG application server |
|
Sensor Factory |
The channels of the Sensor Factory sensor receive measurements as expected again. |
Channels |
Channels that are created after the first sensor scan work as expected again. |
Supported platforms |
The multi-platform probe now supports ARM based systems with either ARMv7 or aarch64 architecture. This enables you to deploy your probe on systems like Raspberry Pi, AWS EC2 with Graviton CPU, and NAS systems, for example. See the Knowledge Base for more details: What is the Multi-Platform Probe and how can I use it? |
Probe transfer |
You can now allow PRTG Desktop to access the configuration files of your probes to transfer a probe to another server. You find the setting Probe Transfer in the Experimental Features section of the PRTG web interface. |
Cache recalculation |
The update to this PRTG version will immediately cause a cache recalculation upon starting the PRTG server. While PRTG is usable during the cache recalculation, it will considerably consume more hardware resources like CPU and memory. Depending on your monitoring configuration, you may encounter negative effects on the performance of PRTG during this process. We recommend that you reserve extra time for the PRTG update. |
Tree version update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German and Dutch language files |
German and French |
We updated the German and French language files. |
SSL Certificate |
The SSL Certificate sensor properly compares common name (CN)/alternative names (SAN) and address/SNI again. This did not work in the previous PRTG preview versions 21.4.73.1545 and 21.4.73.1581. |
FortiGate System Statistics |
You can now actually add the FortiGate System Statistics (BETA) sensor. In the previous preview version 21.4.73.1545, the sensor was missing in the Add Sensor dialog. |
Welcome page |
Overview and reference links on the welcome page now open the correct pages. |
By Michael Becker • Dec 6, 2021
OPC UA |
You can now use OPC UA notifications to forward PRTG alerts to your northbound systems like SCADA, DCS, or any other system that has an OPC UA server. By creating an OPC UA notification template, you can build meaningful error messages that PRTG sends to your OPC UA server. This supports you in seeing and reacting on issues in your network infrastructure as fast as possible. |
Business Process |
Requesting data of the Business Process sensor via the API now returns values in value_raw fields in a better consumable way. |
DNS v2 |
You can now define multiple filter values for the DNS v2 sensor to filter for more than one IP address, for example. |
Modbus sensors |
The sensor types Modbus RTU Custom and Modbus TCP Custom now provide a timeout setting. If the reply from the target device takes longer than the defined Receive Timeout (msec), the request will be aborted and the sensor stops trying to connect. |
Lookups |
You can now easier identify sensors with a missing or broken lookup file. Sensors that have an issue with their lookups will change their status to warning with the message At least one channel uses a lookup that is not available or could not be loaded. (PE272) as of this version to indicate that the sensor cannot properly monitor. In previous versions, you only received a ToDo ticket in such cases but affected sensors kept their status. |
Microsoft 365 Service Status sensors |
The sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced support the new Microsoft 365 Service Health and Communications Graph API as of this version. This change is necessary to seamlessly continue monitoring your Microsoft 365 services because Microsoft soon will shut down the current API version that the sensors used until now. Important: Both sensors now require the API permission ServiceHealth.Read.All to be able to retrieve data from Microsoft Graph and continue monitoring. For details, please see the Knowledge Base article How do I obtain credentials and set permissions for the Microsoft 365 sensors? Please also note that the Microsoft 365 Service Status Advanced sensor cannot monitor subservices anymore and will show the message Channel is deprecated for affected channels. We will remove the channels in an upcoming PRTG version. |
Scanning interval |
We changed the default scanning interval for several newer sensor types that we introduced over the last couple of PRTG versions. |
Microsoft Azure Virtual Machine |
The Microsoft Azure Virtual Machine sensor now shows a down status with an appropriate error message if the target device is not reachable anymore, for example, due to changed credentials. In previous versions, the sensor incorrectly showed a misleading up status with 0 values in such cases. We also improved the general stability of the sensor. |
Channel Unit Configuration |
The dropdown menu for the unit of Bytes (Bandwidth) in the Channel Unit Configuration settings is properly shown again. In Google Chrome and Edge, it was difficult to select the desired unit due to display issues in previous versions. |
AWS v2 sensors |
We implemented various improvements for the experimental AWS v2 sensors.
|
AWS EBS v2 |
You can try out the experimental AWS EBS v2 (BETA) sensor as of this version and monitor the status and performance of an AWS EBS volume. |
FortiGate System Statistics |
You can try out the experimental FortiGate System Statistics (BETA) sensor with this version. The sensor monitors the system health of a Fortinet FortiGate firewall and shows CPU and memory usage, as well as uptime, session statistics, and conserve mode activity. |
Network Share |
You can try out the experimental Network Share (BETA) sensor with this version. The sensor monitors the number of files and folders on a network share via SMB or CIFS, as well as its size and the age of oldest and newest files. |
Redfish Power Supply |
You can try out the experimental Redfish Power Supply (BETA) sensor as of this version. The sensor monitors the status of the power supply of your servers, the power efficiency, and various other parameters. |
Initial alpha release |
We are working on a complete redesign of the PRTG web interface. The redesign is based on extensive user research and the feedback that we have received over the years. The user interface will be fully responsive and will follow the Web Content Accessibility Guidelines (WCAG). Although the new UI is still missing many features, we decided to release the alpha version to give you the opportunity to try out the new UI, and to gather feedback during the early development process. Read all about the new UI here: I want to use the new UI and new API. What do I need to know? |
Initial alpha release |
Our new RESTful API will enable you to easily automate your monitoring and to integrate it with other tools. Our goal is to build a comprehensively documented RESTful API that is consistent across all endpoints. Although the new API is still missing many features, we decided to release the alpha version to give you the opportunity to try out the new API, and to gather feedback during the early development process. Read all about the new API here: I want to use the new UI and new API. What do I need to know? |
Initial alpha release |
The new multi-platform probe will enable you to deploy PRTG probes on various platforms like Windows, Linux, and Docker. We are happy to now share the initial alpha version with you and gather your feedback during the early development process. You can already run a limited set of sensors on it but many features will follow later. Read all about the new multi-platform probe here: What is the Multi-Platform Probe and how can I use it? |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German and French language files |
Event Log (Windows API) |
The Event Log (Windows API) sensor will no longer work due to security changes from Microsoft and will be discontinued. For details, please see Event Tracing and Windows NTLM Elevation of Privilege Vulnerability. We recommend that you pause existing sensors to store historic data. To continue monitoring, use the WMI Event Log sensor. |
Server |
An authenticated user with write access could leverage specifically crafted API calls to execute an arbitrary file on the PRTG core server system under the identity of the PRTG core server service. (CVE-2021-42253) |
By Michael Becker • Nov 8, 2021
Server |
This version includes an important security update for the PRTG core server. An authenticated user with write access could leverage specifically crafted API calls to create an Execute Program notification template that runs an executable file that is vulnerable to a form of directory traversal. This can lead to a potential Remote Code Execution (RCE) by running an arbitrary file existing on the PRTG core server system under the use of the Security Context of the Core Server Service. (CVE-2021-42253)
Many thanks again to the anonymous reporter. |
Sensors |
We improved the parameter handling of several database sensors to prevent external tools from logging them. The change improves the security of the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, PostgreSQL, Oracle SQL v2, and Oracle Tablespace. |
Microsoft Azure SQL Database |
We hardened the detection mechanism of the database type when adding a new instance of the Microsoft Azure SQL Database sensor. The sensor showed a down status upon creation in previous versions if the database type had changed from single database to elastic pool or vice-versa. |
Microsoft Azure SQL Database |
You can now define a scanning interval for a running sensor that is lower than the initial scanning interval that was set when creating this sensor. This was not possible for several newer sensor types before this PRTG version. |
API |
Switching inheritance off and on with the setobjectproperty.htm API call works again. |
History |
Cloning a device now adds an entry to the History tab of the parent group on which the device clone is newly created. |
Probe connections |
Probes now automatically retry to connect to the PRTG server when their initial login to the server failed. This prevents certain cases where the sensors on the probe remained in the unknown status after starting the PRTG server. |
Stability |
We implemented several minor stability improvements for the PRTG core server. |
Startup |
We fixed the case where missing entries in custom language files prevented the PRTG core server from starting. |
User accounts |
You can mark the passhash in your user account settings in Firefox again to easier copy and paste it. |
AWS Alarm v2 |
You can try out the experimental AWS Alarm v2 (BETA) sensor as of this version and monitor your favorite metric and composite AWS alarms with this sensor type. |
AWS RDS v2 |
We implemented several minor improvements for the experimental AWS RDS v2 (BETA) sensor. |
HPE 3PAR Drive Enclosure |
We fixed an issue with the experimental HPE 3PAR Drive Enclosure (BETA) sensor that could not handle certain data that HPE 3PAR devices may return. The sensor showed a down status with a parsing error in such cases. |
HPE 3PAR Virtual Volume |
We added five new channels to the experimental HPE 3PAR Virtual Volume (BETA) sensor that show the full total of used and reserved space. We also renamed the channels User Space Total and Snapshot Space Total to User Space Reserved and Snapshot Space Reserved to better indicate what they monitor. The new channel names only apply to newly added instances of this sensor type. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German language file |
German, French, Russian |
We updated the German language file and implemented some minor improvements for French and Russian. |
Microsoft Azure Subscription Cost |
The Microsoft Azure Subscription Cost sensor works again. In the previous PRTG preview version 21.3.71.1360, the sensor showed a down status with the error message An error occurred. Request failed: HTTP request was not successful: 400: Bad Request. |
Modbus sensors |
We fixed connection issues of Modbus TCP Custom and Modbus RTU Custom sensors that appeared in the previous PRTG stable version 21.3.70. Modbus sensors were not able to connect to the target server if the initial attempt failed and showed a permanent down status with the error message The sensor could not retrieve data from the server or similar. |
By Sascha Neumeier • Oct 4, 2021
Beckhoff IPC System Health |
The new Beckhoff IPC System Health sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. It shows available memory, CPU load, the temperature of CPU and mainboard, as well as the status of the RAID controller. We initially released this sensor type as experimental sensor in PRTG 21.2.67. |
Modbus RTU Custom |
The new Modbus RTU Custom sensor connects to a Modbus RTU server and monitors up to five values returned by the device. With this sensor type, you can monitor, for example, temperature, humidity, and more inside a rack in your datacenter so that you can ensure your equipment operates within the defined ranges. We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions. |
MQTT Subscribe Custom |
You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value with the MQTT Subscribe Custom sensor. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently. |
API |
The API call api/health.json now additionally returns the number of State objects, which corresponds to the number of currently logged in PRTG user accounts. We also added api/health.json to the public API documentation in the PRTG user manual. |
Reports |
PRTG now generates your PDF and HTML reports much faster compared to previous versions. You will especially notice this performance improvement when running reports with a lot of sensors and historic data on large installations. |
Common SaaS |
The Twitter channel of the Common SaaS sensor now supports response code 426. In previous versions, the sensor occasionally showed a warning status with the message Twitter API not available - HTTP/1.1 426 Upgrade Required if Twitter returned this code. |
DNS v2 |
You can add the DNS v2 sensor via auto-discovery again. |
EXE/Script sensors |
We updated the sample PowerShell scripts that we deliver for EXE/Script sensors to work with the enabled PowerShell Security Enhancement setting. The scripts now use write-output instead of write-host. We also encourage you again to accordingly adapt your own scripts to write-output to successfully run your custom PowerShell sensors with enabled security enhancement. |
Flow and Packet Sniffer sensors |
PRTG now properly handles whitespaces in group names and captions when you change the default groups and channels for Flow and Packet Sniffer sensors (via CustomFlowRules.osr, for example). In previous version, whitespaces led to a disabled Save button on the Settings tab of Flow and Packet Sniffer sensors. |
HPE 3PAR sensors |
We fixed an issue with HPE 3PAR sensors that could cause the probe to stop monitoring if you had a certain number of running HPE 3PAR sensors on this probe. All sensors on the affected probe showed the unknown status in such cases. We also improved the stability of HPE 3PAR sensors in case of reconnects where the sensors previously were not able to recover from the down status in some cases. The issues affected the HPE 3PAR Common Provisioning Group sensor, as well as the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA). |
Modbus sensors |
We fixed connection issues of Modbus TCP Custom and Modbus RTU Custom sensors that appeared in the previous PRTG stable version 21.3.70. Modbus sensors were not able to connect to the target server if the initial attempt failed and showed a permanent down status with the error message The sensor could not retrieve data from the server or similar. |
NetApp LUN |
The NetApp LUN sensor now shows 0% bytes free if the used size exceeds the allocated size, just like the NetApp in its own interface. In previous versions, the sensor showed a completely incorrect value in such cases. |
VMware Virtual Machine (SOAP) |
Newly created VMware Virtual Machine (SOAP) sensors now have the Alarm when VM is powered off setting enabled by default. |
Sensor creation |
The progress bar in the Working... dialog window that appears when you start adding certain sensor types now also properly visualizes the progress for various sensor types that we implemented over the last couple of PRTG versions. |
User accounts |
Paused PRTG user accounts cannot resume other paused user accounts via the API anymore. |
Version number |
PRTG no longer displays the current version number in the footer of the startup screen in the web interface. This improves security by not providing attackers potentially relevant information on a page that does not require a login. |
Cluster |
Sensors on failover nodes in status Down (Acknowledged) show timestamps and names of the acknowledging user accounts in the sensor message again. |
User accounts |
User accounts that are member of an Active Directory or single sign-on user group now open the defined homepage of their primary user group when they log in for the first time. In previous versions, they always started on the default welcome page. |
AWS ELB v2 |
We added several new sensor channels for various metrics of application and network load balancers to the AWS ELB v2 (BETA) sensor. |
AWS RDS v2 |
You can try out the experimental AWS RDS v2 (BETA) sensor as of this version. The sensor monitors various metrics of your RDS instances and will be the successor of the existing Amazon CloudWatch RDS sensor. |
Local Folder |
|
Redfish Virtual Disk |
You can try out the experimental Redfish Virtual Disk (BETA) sensor as of this version. The sensor monitors the virtual disks of your Redfish capable servers and shows capacity and status. |
REST Custom v2 |
The REST Custom v2 (BETA) sensor now supports XML in addition to JSON and you can use XPath to define the sensor channels. |
Languages |
We updated the German language file and implemented some minor improvements for French and Russian. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
By Sascha Neumeier • Aug 31, 2021
HPE 3PAR Common Provisioning Group |
The new HPE 3PAR Common Provisioning Group sensor monitors the capacity of a common provisioning group (CPG) on an HPE 3PAR storage system. It shows the overall state of the CPG, as well as free, allocated, and used logical space, snapshot space, and user space. We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions. |
Microsoft Azure SQL Database |
The new Microsoft Azure SQL Database monitors metrics of an Azure SQL Database (single database or elastic pool) in a Microsoft Azure subscription. It can show, for example, CPU and disk usage, number of deadlocks, DTU and eDTU usage and limits, and sessions in percent. We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions. |
Microsoft Azure Storage Account |
The new Microsoft Azure Storage Account sensor monitors the storage account in a Microsoft Azure subscription and shows latency, traffic, and capacity metrics, as well as the number of request breakdowns. We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions. |
Microsoft 365 sensors |
You can now create device templates that include the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced. This enables you to add these sensors via auto-discovery. |
Modbus TCP Custom |
We implemented session sharing for the Modbus TCP Custom sensor and the experimental Modbus RTU Custom sensor. Session sharing reduces the load on the monitored system compared to previous PRTG versions where each sensor created its own connection to the Modbus gateway. |
OPC UA Custom |
The OPC UA Custom sensor now supports up to 10 channels so that you can monitor up to 10 values returned by specific OPC UA node IDs with one sensor of this type. |
WMI Event Log |
The WMI Event Log sensor now supports filtering by multiple event IDs. |
Zoom Service Status |
You can now create device templates that include the Zoom Service Status sensor. This enables you to add sensors of this type via auto-discovery. |
MySQL (v1) |
Still existing instances of the deprecated sensor type MySQL (v1) work again and continue monitoring upon updating to PRTG 21.3.70 or later. In PRTG versions 21.2.68 and 21.3.69, they showed a down status with the error message parameter -sslmode is missing. Please note that we strongly recommend that you replace all sensors of the deprecated type MySQL (v1) with the MySQL v2 sensor. |
SNMP Custom Table |
Adding SNMP Custom Table sensors with an identification column other than table_index or ifindex properly works again. In previous versions, the sensors showed a down status after creation with error code PE247 in such cases. |
Active Directory |
We fixed an issue with the login of Active Directory user accounts. If the display name or full name of a user in the Active Directory contained certain special characters like, for example, ampersand (&), a newly introduced security mechanism blocked the login in the last PRTG version 21.3.69. This also affected PRTG user accounts with two or more consecutive whitespaces in login or display name. |
Cluster |
Failover nodes in a PRTG cluster now keep the password of the PRTG System Administrator user account when you have changed it. In previous versions, the administrator password on failover nodes always reverted to default upon updating the PRTG server. Important: The PRTG default login with password prtgadmin will not work on failover nodes anymore upon updating to PRTG 21.3.70 or later. Please use the PRTG Administration Tool on the failover node to generate a new password. See also the Knowledge Base article Change to requirements for login to the failover node. |
Device templates |
We fixed an issue with certain sensor types like the SNMP HPE ProLiant Memory Controller sensor that, if included, prevented a successful creation of device templates. The created template did not appear in the list of device templates in such cases. |
Single sign-on |
We fixed an issue with external callback URLs for the endpoint handling that included uppercase letters. In such cases, you could not login into PRTG via single sign-on and received the error message The URL you are using to connect to PRTG is not enabled for single sign-on. |
Time zones |
Status messages of down (acknowledged) and paused sensors now show the time zone of the user account instead of the server time. In the logs, the messages are displayed in server time. |
Home page URL |
Home page URLs with URL parameters that you define for PRTG user groups work again. In previous versions, parameters were removed from the URL so that the you did not land on the defined home page when you logged in into the PRTG web interface. |
Internet Explorer |
Adding new notification triggers and displaying existing triggers in Internet Explorer 11 works again. |
AWS EC2 v2 and AWS ELB v2 |
We added comprehensible region names to the channels of the experimental AWS EC2 v2 and AWS ELB v2 sensors. |
Local Folder |
We introduce the experimental Local Folder (BETA) sensor with this version. The sensor monitors the number of files and folders in a local folder on the probe device, as well as its size and the age of oldest and newest files. |
Redfish System Health |
You can try out the experimental Redfish System Health (BETA) sensor as of this version. With this sensor, you can monitor the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac. |
Languages |
We updated and improved all language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
By Sascha Neumeier • Jul 16, 2021
Veeam Backup Job Status Advanced |
The new Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs on the Veeam Backup Enterprise Manager. The sensor monitors the status of the backup job, the duration, the time since the last run, and if the backup job is scheduled. We released this sensor type as experimental sensor in PRTG 21.1.65 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we resolved two more issue for this release.
|
Dell EMC Unity Enclosure Health v2 |
The Dell EMC Unity Enclosure Health v2 sensor now can also monitor Power Consumption in a dedicated channel. |
Modbus TCP Custom |
|
MQTT Subscribe Custom |
The MQTT Subscribe Custom sensor now supports up to 10 channels so that you can monitor up to 10 values from a subscribed MQTT topic with one sensor of this type. |
SNMP sensors |
PRTG can now perform more SNMP v3 requests at the same time, so that monitoring with SNMP v3 sensors is more stable compared to previous versions. |
Active Directory |
PRTG now validates all fields that are imported from Active Directory when creating a new user account to close a potential XSS vulnerability. (CVE-2021-29643) |
Microsoft Azure sensors |
We improved the stability of the Microsoft Azure sensors. In previous versions, the sensors had connection issues in some cases, which resulted in wrong down and warning states. |
DNS v2 |
The Records Resolved channel of the DNS v2 sensor correctly uses a lookup with the states yes and no again. Add the sensor anew to resolve the issue with the Records Resolved channel. |
Microsoft 365 Service Status sensors |
We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against unknown service states that Microsoft 365 may return. In such cases, the sensors previously showed a down status with the message error.generic[invalid map |
SNMP Printer |
We improved the stability of the SNMP Printer sensor. In rare cases, the sensor showed a down status with the message No such instance (SNMP error # 223) after some time when monitoring certain types of printers. |
API |
API calls for tables with content=probenodes return all probes again. |
Auto-Discovery |
Devices now keep their settings even after running an auto-discovery on this device. Previously, the first auto-discovery on a device occasionally overwrote your manually configured settings like names, icons, or tags. |
Graphs |
The graph on the 2 days tabs of sensors shows the correct downtime again. In previous versions, the 2 days tab showed a wrong downtime in various cases, for example, always 0% even if there was a downtime reported and correctly shown in the data table. The percentage values on the y-axis of 2 day graphs are also back again. |
Single sign-on |
Logging in with single sign-on now also works if you use an Azure AD group name (sAMAccountName) with upper-case letters as SSO Group Access Claim. We also fixed the misbehavior that PRTG logged out SSO user accounts after some time. |
Maps |
We fixed a display issue on maps that affected channel gauges on View Map tabs. Sometimes, the gauge values of previously opened sensor pages erroneously appeared in gauge map objects instead of the real values until the page was refreshed. |
AWS EC2 v2 |
You can try out the experimental AWS EC2 v2 (BETA) sensor as of this version. The sensor monitors the performance of an Amazon EC2 instance and will be the successor of the existing Amazon CloudWatch EC2 sensor.
Note: If you use the same IAM policy that you use for the Amazon CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG? |
AWS ELB v2 |
You can try out the experimental AWS ELB v2 (BETA) sensor as of this version. The sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor. |
HPE 3PAR sensors |
We implemented session sharing for the HPE 3PAR sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the HPE 3PAR system with every scan. |
REST Custom v2 |
We fixed the Custom Headers of the REST Custom v2 sensor. In the last PRTG version, sending custom HTTP headers did not work correctly. |
SNMP Rittal CMC III Hardware Status |
We introduce the experimental SNMP Rittal CMC III Hardware Status (BETA) sensor with this version. The sensor monitors the hardware status of a Rittal CMC III processing unit and shows the status of every attached external sensor. |
All parts of PRTG |
Various other minor fixes and improvements, updated German language file, updated user manual |
DNS sensor |
The DNS (v1) sensor is now deprecated as we previously announced. DNS (v1) sensors that you added in previous versions will continue to monitor after updating to PRTG 21.x.69, but you cannot add sensors of this type anew. Please use the new DNS v2 sensor instead. |
SNMP sensors |
In some cases, SNMP sensors show SNMP error 2011 after updating PRTG to version 21.3.69 with the message Could not create SNMP Session (-3000)-2011. The error may occur if the latest updates for the Visual C++ Redistributable Package are missing on the probe system. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/89831. |
German |
We updated the German language file. |
Sensor settings |
We fixed an issue with sensor channel limits that caused an error when you tried to save sensor or channel settings. You could not save the settings of a sensor if you previously configured a floating value in the channel limits of this sensor. Depending on the current page in PRTG, the error message in this case was Error (Bad Request) Internal error: [value] is not a valid floating point value or There was a problem... PRTG Network Monitor has encountered a problem. Your last request could not be processed properly. The issue occurred in the previous preview version 21.2.68.1433. |
By Sascha Neumeier • Jun 7, 2021
Single sign-on |
You can now login to PRTG via single sign-on (SSO). As of PRTG 21.2.68, you can use Azure Active Directory (Azure AD) as SSO provider in PRTG. After configuring Azure AD for PRTG, enable single sign-on in the PRTG system administration and create a user group that uses single sign-on integration. The members of this user group will then use SSO via Azure AD to login to PRTG. For details about setup and configuration, see this Knowledge Base article. Please note that this feature is only available for PRTG on premises, not for Paessler PRTG Hosted Monitor. |
Regions |
We added the cloud region US East for the hosting option of Paessler PRTG Hosted Monitor. Region transfers of instances between Europe and United States (and vice versa) are now possible. Please contact our support for according inquiries. |
Cloud HTTP v2 and Cloud Ping v2 |
We improved the stability of Cloud HTTP v2 and Cloud Ping v2 sensors, which will result in less sensor timeouts than in previous versions. The sensors now also continue monitoring and show data for available regions even if one or more region is not working, and we added a PRTG Cloud Response channel for each region that shows the current status of a region. |
Dell EMC Unity v2 sensors |
We implemented session sharing for the Dell EMC Unity v2 sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the Dell EMC system with every scan. |
Modbus TCP Custom |
You can now create device templates that include the Modbus TCP Custom sensor. This enables you to add sensors of this sensor type via auto-discovery. |
MySQL v2 |
The MySQL v2 sensor now provides a dedicated setting for the SSL mode. The options you can choose are the same as the values of the MySQL sslmode parameter. Depending on your monitoring setup, for example with offline installations, you may have to change the setting for successful monitoring. |
HTTP requests |
We upgraded the HTTP protocol that PRTG uses in HTTP POST requests to HTTP 1.1. PRTG uses POST requests at several places to call external endpoints. For example, this change affects the notification types email, push, and SMS. If required, you can still switch back to HTTP 1.0 in the according notification template settings. |
SMS delivery |
We improved the usability of the SMS service provider setup, which will help you to more easily configure SMS notification delivery. All necessary fields now require you to fill them in before saving the settings to ensure you provide all necessary information. By default, the SMS configuration mode is now disabled if you have not had configured SMS delivery before. |
EXE/Script sensors |
EXE/Script and EXE/Script Advanced sensors now escape round brackets in the Parameters field to prevent potential code injection. |
MQTT Statistics |
We fixed an issue with the MQTT Statistics sensor that showed wrong data after some time of monitoring in certain cases. |
NetFlow v9 and IPFIX sensors |
We corrected the traffic calculation of NetFlow v9 and IPFIX sensors. The sensors reported too much traffic with certain combinations of flow fields. |
VMware Host Hardware Status (SOAP) |
The VMware Host Hardware Status (SOAP) sensor properly reports errors again. In previous versions, the sensor did not show an alert state if a warning state was already present. |
Windows Updates Status (PowerShell) |
The Windows Updates Status (PowerShell) sensor now properly applies the Port in SPN setting. In previous versions, the port was not correctly included in the SPN even if you enabled the setting. |
API |
We fixed an issue with API calls that returned no data in certain cases, for example, when querying System Information via /api/table.json. |
Channel limits |
You can define the same values for upper and lower sensor channel limits again. |
Map Designer |
We fixed an issue in the map designer that triggered an error dialog window with the message Error (Bad Request). Sorry, the selected object cannot be used here. This happened in the last PRTG version 21.2.67 when you tried to load the preview of an incompatible object type in the properties section of the map. |
Probes |
We implemented stability improvements for probe connections after a PRTG server restart, which will be especially helpful if you have many remote probes. |
REST Custom v2 |
You can try out the experimental REST Custom v2 (BETA) sensor as of this version. The sensor monitors the results of a JSON REST API call and will be the successor of the existing REST Custom sensor. We are looking forward to your feedback! |
Microsoft Azure SQL Database |
The experimental Microsoft Azure SQL Database (BETA) now shows correct channel names. |
Languages |
We updated the German language file. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
DNS sensor |
We will discontinue the DNS sensor (v1) with the upcoming PRTG version 21.x.69. Running sensors of this type will still work for some more versions, but you will not be able to deploy them as of PRTG 21.x.69. If you use the sensor, we strongly recommend that you replace it with the superseding sensor type DNS v2 soon. If you encounter any remaining issues with the new DNS v2 sensor, please immediately contact us so that we can address them. |
EXE/Script sensors |
As of PRTG 21.2.68, the experimental setting PowerShell Security Enhancement is enabled by default if you update PRTG from version 20.4.64 or previous to 21.2.68 or later and on new installations. If you encounter custom EXE/Script sensors in down status with, for example, error code PE231 or PE233 after the update, please check the according PowerShell scripts and replace write-host with write-output where applicable. If this does not help or is not applicable, you can still disable the PowerShell Security Enhancement setting again under Setup | System Administration | Monitoring, section Experimental Features. Please contact us in such cases to help us resolving remaining issues with this security enhancement. |
Exchange (PowerShell) sensors |
Exchange (PowerShell) sensors now work with the recent Microsoft Exchange Server security update KB5001779 from April 13, 2021. After applying the Exchange Server update, Exchange (PowerShell) sensors showed a down status with the error message The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details. This affected all Exchange (PowerShell) sensors.
|
IPMI System Health |
The IPMI System Health sensor works again. After updating to the last PRTG preview version 21.2.67.1531, sensors of this type showed a down status with the error message No "result" or "error" in XML response. |
SNMP sensors |
SNMP community strings remain as defined again when updating PRTG. The update to the last PRTG preview version 21.2.67.1531 overwrote SNMP community strings with the default value (public) so that SNMP sensors stopped working after the update if you used another SNMP community string. |
German |
We updated the German language file. |
By Sascha Neumeier • May 3, 2021
Core Health (Autonomous) sensor |
The new Core Health (Autonomous) sensor monitors your PRTG server and is automatically created on the new PRTG Core Server device when you install PRTG 21.x.67 or later. It shows the status of the PRTG core server and checks various parameters of the PRTG core server that have an impact on the stability of the system. The sensor has the same functionality as the existing Core Health sensor but runs independently of the local probe. Because of this, the sensor still can monitor the status of the PRTG server if the probe is disconnected. This avoids situations that there is no health data for the PRTG server available when the local probe is disconnected so that efficient troubleshooting in case of server issues is still possible. |
Consolidated Components |
The new Consolidated Components feature allows you to link together components
that have common properties. This feature is helpful if you have components that are
monitored by multiple source systems. For example, if a server is being monitored by multiple PRTG sensors, you can consolidate those sensors and the device into one component and designate it as a Computer in ITOps Board. You can then monitor a single computer with all its related sensors as one object. |
SLA Reporting Enhancements |
This release introduces the following enhancements to SLA reporting.
|
Acknowledge Alerts |
A new button on the Alerts page allows you to acknowledge an alert that has not yet been resolved. The button is available when you select one or more alerts and click the Action icon. |
Google Analytics Option |
Google Analytics has been added to this release to help us understand how you use the ITOps Board interface. This information will help us to improve future versions of the product. If you do not want to provide this information, you can disable Google Analytics in the installation wizard. After the installation is complete, administrators can enable or disable Google Analytics from the Settings | General Settings page. |
MQTT Subscribe Custom |
The MQTT Subscribe Custom sensor can now show text messages from your IoT devices. Define the Sensor Message JSONPath in the sensor settings and always see the latest message from your system in the sensor message. |
Zoom Service Status |
We added the channel Webhooks to the Zoom Service Status sensor. |
User accounts |
You can set the Homepage URL of a PRTG user account or user group only to web pages of your PRTG instance as of this version. External domains are not allowed anymore to prevent redirects to potentially malicious pages. Note: Previously defined homepage URLs that violate this rule will prevent you from saving changes to affected user account or user group settings. Please change the homepage URL to a valid page in this case to be able to save the settings again. |
Web server |
Web pages in PRTG that do not require authentication like help and password recovery pages now return the X-Frame Options HTTP header DENY by default. This security improvement helps to prevent potential phishing attempts. Overriding the header value accordingly applies to these pages, see this Knowledge Base article. |
Exchange (PowerShell) sensors |
Exchange (PowerShell) sensors now work with the recent Microsoft Exchange Server security update KB5001779 from April 13, 2021. After applying the Exchange Server update, Exchange (PowerShell) sensors showed a down status with the error message The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details. This affected all Exchange (PowerShell) sensors.
|
Flow sensors |
|
HTTP Transaction |
We fixed a memory leak that occurred when using the HTTP Transaction sensor in Alternate/Compatibility Mode. |
OPC UA Custom |
The OPC UA Custom sensor now supports Int64 values. In previous versions, the sensor showed a down status when reading a node with an Int64 data type. |
SNMP Library |
The SNMP Library sensor creates sensors and channels for all library OIDs that you select during sensor creation again. In previous versions, some sensor channels were missing after sensor creation if you selected more than one library OID from one category. |
SNMP Trap Receiver and Syslog Receiver |
You can now use angle brackets (<>) in the message filter of SNMP Trap Receiver and Syslog Receiver sensors. |
Auto-Update |
We improved the stability of auto-updates when PRTG updates to a 64-bit version from a 32-bit version. Previously, the auto-update sometimes failed in such cases and required a manual update. |
Channel limits |
You can save Limits in sensor channel settings again when using comma as decimal separator. In the previous PRTG version 21.1.66, you received the error message Internal Error: '[value]' is not a valid floating point value when you tried to save the channel settings in this case. |
Cluster |
|
Gauges |
Device overview tabs show gauges of sensors with a 5-star priority with a proper minimum/maximum value range again. In previous versions, the gauges only showed the value range 0 to 1000. |
Search |
The detailed search now properly works even if a search for objects with special characters returns more than 10 results. In previous versions, the More button that appears when more than 10 results are found opened an empty list of search results in such cases. |
Startup |
We fixed an issue with the PRTG server that could not start in rare cases due to language files being used by another process. |
Toplists |
We fixed the toplists of flow and packet sniffer sensors that only showed data for the most current toplist period in some cases. |
User accounts |
You cannot pause the default PRTG System Administrator (user ID 100) account with another administrator account anymore. In previous versions, this was temporarily possible until a server restart and could result in inconsistent behavior of PRTG. |
Execute HTTP Action |
HTTP notifications now use HTTP 1.1 by default to execute HTTP actions. In previous version, the HTTP version always fell back to 1.0, which could lead to issues with several notification targets like Atlassian Opsgenie, for example. If required, you can still switch back to HTTP 1.0 in the notification settings. |
Data |
The System table on System Information tabs correctly displays MAC addresses again even if they are returned via SNMP. In previous versions, MAC addresses returned via SNMP were not readable. |
PDF reports |
We fixed a layout issue that caused cut off graph legends with certain page format and orientation combinations in PDF reports. |
Beckhoff IPC System Health |
We added the experimental Beckhoff IPC System Health (BETA) sensor. The sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. We are looking forward to your feedback! |
HPE 3PAR sensors |
You can try out the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA) with this version. Of course, your feedback is highly welcome!
|
PowerShell Security Enhancement |
We fixed an issue with the parameter handling of custom EXE/Script sensors that occurred when the experimental feature PowerShell Security Enhancement was enabled. The issue could lead to non-functional EXE/Script sensors in some cases. |
Veeam Backup Job Status Advanced |
|
Languages |
We updated the German language file. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
HTTP Push Data Advanced and HTTP IoT Push Data Advanced sensors |
We fixed a typo in the Time Threshold (Minutes) property of HTTP Push Data Advanced and HTTP IoT Push Data Advanced sensors. The property is now correctly spelled timethreshold. If you modify or read out this property via the API (setobjectproperty.htm, getobjectproperty.htm), please change the misspelled timethreshhold to timethreshold if necessary. |
Tree version update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
REST Dell EMC sensors |
The REST Dell EMC sensors are now deprecated as we previously announced. REST Dell EMC sensors that you added in previous versions will continue to monitor after updating to PRTG 21.x.67, but you cannot add them anew. This affects the following sensor types.
|
Map Designer |
In the current PRTG version 21.2.67, object types in the Properties section of the Map Designer that are by design incompatible to the selected object in the Device Tree section return an error dialog window when loading the object preview. The message is Error (Bad Request). Sorry, the selected object cannot be used here. PRTG redirects you to the welcome page when you confirm the dialog window. This happens, for example, when you select nothing, root, or a probe, group, or device in the device tree and hover your mouse over a live graph or gauge object in the properties section. Note that existing maps that already include an element that is empty due to incompatible object type will show the same error message and will not load. Workaround: To add a live graph or gauge for a sensor, ensure you have selected the sensor in the device tree section (click the sensor in the device tree section to select it) before you choose an object in the properties section. If you have selected any other object in the device tree section than a sensor, avoid hovering incompatible object types like live graphs or gauges in the properties section. Status: Resolved with PRTG version 21.2.68.1492. |
German |
We updated the German language file. |
VMware sensors |
We fixed an issue with the session handling of VMware (SOAP) sensors. In the previous PRTG version 21.1.65, the issue caused the sensors to log in and log out on the target system with each sensor scan, which flooded the VMware logs, for example. |
Stability |
We fixed an issue that could cause instability of the PRTG server and probes in varying forms. This could happen in case of failing Execute Program notifications, failing EXE sensors, or failing script sensors, for example. |
By Sascha Neumeier • Mar 26, 2021
OPC UA Certificate |
The new OPC UA Certificate sensor monitors the certificate of an OPC UA server and helps you to ensure a secure and consistent communication between the machines in your shop floor. We released this sensor type as experimental sensor in the last PRTG version and received valuable feedback that we now implemented to enhance the sensor based on your needs. The following additional features made it into this version.
|
OPC UA Custom |
The new OPC UA Custom sensor monitors the values returned by multiple nodes of an OPC UA server. We released this sensor type as experimental sensor in PRTG 20.4.63 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we added two more features for this release.
|
DNS v2 |
You can now create device templates that include the DNS v2 sensor. This enables you to add sensors of this sensor type via auto-discovery. |
Microsoft 365 Service Status Advanced |
The Microsoft 365 Service Status Advanced sensor now shows in the sensor message whether an issue is an advisory or incident so that you can easily see the impact of an issue. |
Packet Sniffer |
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 1.10. The new version includes several fixes and performance improvements compared to the previously delivered version 0.9987. |
Windows Updates Status (PowerShell) |
The Windows Updates Status (PowerShell) sensor can now monitor workgroup machines and target systems that are not in the same domain as the PRTG probe. You can define the required authentication method, Kerberos authentication or negotiation authentication, in the sensor settings. |
WMI Battery |
The WMI Battery sensor can now monitor the battery level of USB connected UPS so that you can ensure there is enough load in case of a power outage. |
User Accounts |
PRTG now logs changes to user account passwords and shows which user account changed a password and when. You can view the changes on the History tab of a user account. |
Add Sensor Dialog |
Several more sensor types for which required credentials in the parent device settings are missing are now greyed out in the Add Sensor dialog. You cannot add the sensors without providing the credentials anymore. PRTG lists the credentials that you need to provide in this case for each sensor. This will help you to more flawlessly enhance your monitoring with new sensors. The change affects the recently introduced sensor families Dell EMC v2, Microsoft 365, Microsoft Azure, Veeam Backup, and HPE 3PAR (BETA). |
Channel Limits |
PRTG now validates the limits you enter in sensor channel settings. You cannot save invalid limit combinations anymore like, for example, a higher value for the lower error limit than for the lower warning limit. This will help you to avoid unexpected sensor behavior due to mistakenly defined limit configurations. |
Web Server |
We fixed a vulnerability that enabled potential attackers to verify the existence of certain files on the file system of the web server of PRTG by invoking the screenshot functionality of PRTG with special crafted paths. (CVE-2021-27220) |
HPE 3PAR Common Provisioning Group |
We added the channels Logical space free, User space free, and Snapshot space free to the HPE 3PAR Common Provisioning Group (BETA) sensor. |
Microsoft Azure SQL Database |
We improved the Add Sensor dialog of the Microsoft Azure SQL Database (BETA) sensor. The table where you select the databases you want to monitor when you add the sensor supports filtering and sorting by DTU and vCore, and you can see if a database belongs to an elastic pool and which one. Additionally, the elastic pool is added to the sensor name upon sensor creation. |
Veeam Backup Job Status Advanced |
We added the channels Last Job Run and Job Scheduled to the Veeam Backup Job Status Advanced (BETA) sensor. Because of the new channel, we also removed the setting Warn if the job is not scheduled, as well as we improved the help texts for the sensor and the names of lookup states. |
Auto-Discovery |
|
Dell EMC Unity v2 sensors |
Dell EMC Unity v2 sensors now support multiple descriptions in the API response from the target device. Multiple descriptions can appear if there is an issue with a disk in a Dell EMC Unity storage system, for example. In this case, the sensors showed a down status in previous versions and created the log message The received value is an array instead of a single value. Dell EMC v2 sensors now show the correct value and all received descriptions in the sensor message in this case. |
Dell EMC Unity VMware Datastore v2 |
You can now add Dell EMC Unity VMware Datastore v2 sensors to Dell storage systems even if there is a Veeam Backup plugin installed. In previous version, you could not add the sensor to such a device because the scan for available monitoring items failed with the error message An error occurred. (The queried field is empty.) |
HTTP Transaction |
The HTTP Transaction sensor now supports ports when using smart URL replacement. In previous versions, the sensor did not correctly fill in the parent device's IP address or DNS name if you defined a transaction URL only denoting the port number. The sensor showed a down status with the following message in this case: Failed to establish secure connection [Step 0] Socket Error # 11001 Host not found. |
Microsoft 365 Service Status sensors |
We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against some unexpected return values.
|
Microsoft Azure Subscription Cost |
We improved the handling of empty fields that Microsoft Azure sometimes returns to the Microsoft Azure Subscription Cost sensor. In previous versions, the sensor only showed a down status in such cases. |
Modbus TCP Custom |
The Modbus TCP Custom sensor now supports the unit ID 255, which is required for certain target devices. We also implemented the fix for the experimental Modbus RTU Custom (BETA) sensor. |
NetFlow and IPFIX sensors |
NetFlow and IPFIX sensors now show an expressive error message if one or more IP addresses that were previously selected for binding in the sensor settings are no longer available. This will help you to faster find the error source. The message in this case is The previously selected Network Adapter (with Address ('[IP]') could not be found, please change the sensor settings to an available IP address. |
OPC UA sensors |
We fixed the issue that some valid client certificates caused a BadCertificateUriInvalid error in OPC UA sensors. The OPC UA sensors could not connect to the target device in such cases due to a different application URI in certificate and sensor. |
SNMP sensors |
SNMP sensors now support very large values from the numeric SNMP data type Counter64 (unsigned 64-bit integer). In previous versions, SNMP sensors showed the error message [value] is not a valid integer value or wrong values if such a value was returned. The issue was reported by a customer for the SNMP Cisco CBQoS sensor but also affected other SNMP sensor types like SNMP custom sensors, for example. |
VMware sensors |
We fixed an issue with the session handling of VMware (SOAP) sensors. In the previous PRTG version 21.1.65, the issue caused the sensors to log in and log out on the target system with each sensor scan, which flooded the VMware logs, for example. |
Cluster |
|
License Activation |
We fixed an issue that could prevent automatic license activation in proxy environments. |
Notifications |
We fixed an issue that prevented notifications from being sent out in rare cases. |
Notification Templates |
Pausing and resuming notification templates via the notification template list is logged on the History tab of a template again. |
Reports |
To avoid memory exhaustion, the maximum report interval is now limited to 500 days per report. |
Stability |
We fixed an issue that could cause instability of the PRTG server and probes in varying forms. This could happen in case of failing Execute Program notifications, failing EXE sensors, or failing script sensors, for example. |
Alarms as Gauges |
We fixed an issue that caused the page Alarms | Shows as Gauges to not show any sensor gauges. The page remained empty in previous PRTG versions if there was at least one sensor in Down (Acknowledged) status with a closing square bracket (]) at the end of the sensor's error message. |
Device Tree |
The device tree keeps collapsed and expanded states of all objects again when the page refreshes. In previous versions, all device tree objects were always expanded after a page refresh if you were logged in as read-only user or as read/write user with read access to an object. |
Languages |
We updated the German language file. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
Channel Limits |
You cannot save Limits in sensor channel settings when using comma as decimal separator. You will get the error message Internal Error: '[value]' is not a valid floating point value in the current PRTG version 21.1.66. Pre-existing limits are not affected and keep working. As a workaround, you can enter the closest integer value like, for example, 1 instead of 0,99 if applicable. The decimal comma is used in several European regions, for example. Status: We are working on a fix for the next PRTG version 21.x.67. |
Microsoft 365 Service Status sensors |
In some cases, the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced may show a down status after updating PRTG with the error message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. (code: PE270). To resolve the issue, please manually pause and resume affected sensors or restart the PRTG core server service under Setup | System Administration | Administrative Tools | Restart PRTG Core Server Service. |
OPC UA Server Status sensor |
We strongly recommend that you add running OPC UA Server Status sensors anew after updating from a previous PRTG version for stability reasons. Although you will not directly encounter issues with the sensors, you may notice errors in the core.log file due to an update issue with the underlying functionality of this sensor type. |
All Languages |
We updated and improved all language files. |
Microsoft Azure and HPE 3PAR sensors |
You can add all Microsoft Azure sensors again in this version, as well as existing Microsoft Azure sensors continue to monitor. The fix also makes the newly introduced HPE 3PAR Common Provisioning Group (BETA) sensor available if you enable experimental sensors. In the previous preview version 20.4.65.1667, the sensor modules for Azure and HPE 3PAR sometimes were not loaded on PRTG startup so that you could neither add them nor continue monitoring with already existing sensors of these types. |
SNMP Custom Table |
|
By Sascha Neumeier • Feb 8, 2021
Experimental Features |
We added the option to enable experimental features in PRTG. Experimental features are still under development and not fully tested, but they are ready enough for you to try them out in a PRTG stable version. This makes it possible for you to already have a look at new upcoming features fresh from our labs without the need to install a PRTG canary version somewhere else, and you can provide us early feedback to enable us to learn from it before making a new feature available for all customers. You can only use an experimental feature if you explicitly enable the according option in the Experimental Features section in the PRTG web interface under Setup | System Administration | Monitoring. See also the Knowledge Base article Experimental Features in PRTG. |
Beta Sensors |
We introduce beta sensors as experimental feature with this PRTG version. As of now, you will only be able to add beta sensors and use them for monitoring if you enable the option in the experimental features section. The following beta sensors are new in this version.
We transition all sensor types that we introduced with a BETA label in the last few PRTG versions to NEW so that you can simply continue your monitoring with these sensors. Older sensor types that still had the beta label are individually handled. We removed the flag for stable sensors and will discontinue and replace the others (see below for more information). |
PowerShell Security Enhancement |
The experimental feature PowerShell Security Enhancement hides PowerShell parameters that custom EXE/Script sensors use to avoid logging through external tools. This feature also reduces the resource usage of custom PowerShell sensors in certain cases and as such may improve their execution times. |
Auto-Discovery |
|
Dell EMC Unity v2 sensors |
We added the Total Size channel to the recently introduced Dell EMC Unity sensor types Dell EMC Unity Storage Capacity v2, Dell EMC Unity File System v2, Dell EMC Unity Storage Pool v2, Dell EMC Unity Storage LUN v2, and Dell EMC Unity VMware Datastore v2. Thank you for your feedback that you need this channel for a comprehensive monitoring of your Dell EMC Unity storage systems. |
MQTT sensors |
|
OPC UA Server Status |
All session related channels of the OPC UA Server Status sensor now use counter units (sessions per second #/s) to more comprehensible show if something unusual is going on. |
Notification Triggers |
We improved the content of History and Log entries for notification triggers. The entries appear much clearer now to enable you to more comprehensible see changes that added, modified, or removed triggers. We now also display the ID of each existing notification trigger on the notification trigger tabs so that you can better reference the history and log entries. Thanks to these improvements, you will also easier understand which notification trigger was activated and why and where you configured the trigger. |
Installer |
PRTG is now always installed as 64-bit version if the operating system on which you run the installer is 64-bit, and only installed as 32-bit version if the operating system is 32-bit. PRTG will also install the 64-bit version when you update a PRTG instance that was originally installed as 32-bit version on a 64-bit operating system. Previously, PRTG only checked the available RAM on the server and always installed the 32-bit version whenever there was less than 6GB RAM, even on 64-bit systems. |
Memory |
We reduced the memory consumption of sustained API write calls, for example, when setting object properties via the API. |
PRTG GUI Starter |
PRTG now more logically selects the browser on your system that works best with the web interface if you open it with the PRTG Network Monitor shortcut that is automatically created on the server where you install PRTG. |
API |
We hardened the log routines in setobjectproperty.htm API calls. |
Sensors |
We improved the parameter handling of NetApp cDOT/ONTAP and VMware sensors to prevent external tools from logging them. |
Web Server |
We fixed a potential XSS vulnerability on report.htm. |
SMS Delivery |
We removed all deprecated entries from the list of SMS service providers, which are the outdated BulkSMS endpoints. The removed entries automatically migrate to the corresponding new endpoints BulkSMS All regions (except South Africa) and BulkSMS South Africa with the update to this PRTG version. If you have not manually changed the service provider to one of the new BulkSMS entries and tested the SMS delivery in previous versions, please check if PRTG still can send SMS messages after the update. The new BulkSMS endpoints use HTTPS (443) and as such you might need to adjust your firewall rules if you limit internet access from the PRTG server. You can check your SMS delivery configuration and a successful delivery of SMS with the Test SMS Delivery button in the SMS Delivery settings. See the PRTG manual for details. We also cleaned up the list of SMS service providers and only list the names of the providers now. You can still find endpoint, protocol, port, and additional information for each provider in the help box. |
Common SaaS |
The Common SaaS sensor shows an Up status again if all monitored services are reachable. We had to update the URL that the Dropbox channel uses because Dropbox deprecated their old API. The channel could not reach Dropbox anymore so that the sensor showed a Warning status in default configurations the past few weeks. |
Custom Sensors |
|
HTTP Push Data sensors |
HTTP Push Data and HTTP Push Data Advanced sensors now keep and display their last value on device overview pages and map objects instead of showing No data after a scanning interval without a new value. |
Microsoft Azure Virtual Machine |
We improved the scan for available virtual machines (meta-scan) when you add the recently introduced Microsoft Azure Virtual Machine sensor. Previously, you could not create the sensor if the response of the meta-scan included UTF-8 characters. You received the error message An error occurred. The received JSON data could not be parsed. in this case. |
NetApp cDOT/ONTAP sensors |
This version comes with several improvements and fixes for NetApp sensors that monitor NetApp cDOT or ONTAP storage aggregates by accessing the API via SOAP. In general, we improved the approach on how the sensor names are automatically created when you add a new NetApp sensor, as well as manually changed sensor names are now correctly applied. We also fixed the Timeout (Sec.) setting that always applied 60 seconds when you added the sensor, no matter which value you entered, and we removed the beta flag from NetApp sensors where it still was there. The following changes apply to specific NetApp sensors.
|
REST Custom |
The REST Custom sensor now supports angle brackets (<>) in POST requests to be able to correctly send XML to the target device, for example. |
SNMP Cisco ASA VPN Traffic |
We fixed the Sensor Behavior setting of the SNMP Cisco ASA VPN Traffic sensor. The sensor shows the correct status again if no connection is active just as you have defined it in the sensor settings. |
SNMP Custom Table |
|
SNMP v3 sensors |
SNMP sensors now will continue to properly work if you change SNMP v3 settings in the Credentials for SNMP Devices section of the parent device or group. In previous versions, changing SNMP v3 settings or switching to SNMP v3 often resulted in a down status of the according SNMP sensors with the error message could not create snmp session -1114 -2011, which you could only resolve with a restart of the PRTG probe service. |
Veeam Backup Job Status |
We fixed the limits of the Job Runs Warning and Job Runs Failed channels of the recently introduced Veeam Backup Job Status sensor. The channels now only cause a warning or down status if there is at least one warning or failed job run. We also shortened the channel names and improved the sensor help to make clearer for you what and how this sensor monitors. |
Active Directory |
Active Directory integration now supports angle brackets (<>) in the access password if you use explicit credentials. |
Cluster |
Devices that you clone to a remote probe in a cluster are immediately synchronized to the failover node again. In previous versions, the failover node only showed the cloned device after a restart of the failover. |
Down (Acknowledged) |
The status message of Down (Acknowledged) displays the PRTG server time again instead of just UTC. |
Login |
We fixed a misbehavior that occurred after you have changed the login name of a PRTG user account. The old login name was not updated in the internal dictionary nor deleted after changing it so that a new user account with the same login name could not login due to wrong credentials. This could happen, for example, when you added an Active Directory user to replace a local user account with the same login name. |
Remote Probes |
Remote probes that have special characters in their names automatically update and connect to the PRTG server again. In the previous PRTG version 20.4.64, characters like German umlauts or Japanese language characters in probe names prevented remote probes from automatically updating and required a manual update to connect. |
Various |
We implemented several other minor fixes and improvements for the PRTG core server. |
Login |
Nombre de inicio de sesión has the correct position on the Spanish login page again and does not overlay the input field anymore. |
Languages |
We updated and improved all language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
Discontinued Sensors with PRTG 21.x.67 |
We will discontinue the following sensor types with PRTG version 21.x.67 that we plan to release in Q2 2021. Running sensors of theses types will still work for some more versions, but you will not be able to deploy them as of PRTG 21.x.67. If you use these sensors, we strongly recommend that you replace them with the superseding sensor types soon. If you encounter any remaining issues with the new sensors, please immediately contact us so that we can address them.
|
Discontinued Sensors Forecast |
Further in the future, we will discontinue the following sensor types and replace them. These sensors will continue to work as you are used to it until we have introduced full replacements for them. You will find more information about the future development of the sensors on our public roadmap. We would love to get your input for new versions of these sensors!
|
German |
We updated the German language file. |
OPC UA sensors |
We improved the stability of the OPC UA Server Status BETA sensor and the experimental OPC UA Custom sensor. In the previous preview version 20.4.64.1362, OPC UA sensor scans with longer scanning intervals often failed after the first successful scan due to interference with the internal connection timeout. |
Graph Display |
Primary channels in live and historic data graphs have a line again and do not only show the colored background anymore as in the previous preview version 20.4.64.1362. |
By Sascha Neumeier • Dec 4, 2020
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. |
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. |
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. |
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. |
Libraries |
You can collapse and expand library nodes again. |
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. |
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. |
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.
|
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German language file |
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. |
Language Files |
We updated the German and Japanese language files. |
SNMP Custom Table |
We fixed an issue with SNMP Custom Table sensors that were not properly created in some cases because of incorrectly retrieved identifiers. The issue appeared in the previous PRTG 20.4.63 preview versions and affected the manual adding of the sensors as well as adding them via auto-discovery. |
Startup |
We fixed an issue that could prevent PRTG from starting with the last preview version 20.4.63.1395. Libraries without filter caused a loop so that the start of PRTG got stuck after loading the config. |
By Sascha Neumeier • Nov 6, 2020
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. |
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]. |
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. |
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. |
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. |
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. |
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. |
System Information |
The column headers of tables on System Information pages are correctly displayed again. |
Language Files |
We updated the German and Japanese language files. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
Tree version update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
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. |
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. |
Various |
We updated the German and Dutch language files, as well as we improved translations in several places in the Spanish and French files. |
Cluster |
PRTG correctly shows the Down (Partial) status again. In the previous PRTG 20.3.62 preview versions, the status incorrectly showed up even if a sensor was down on all cluster nodes, as well as it did not show up if a sensor was up on at least one cluster node. |
Cluster |
We fixed an issue with cluster installations where failover nodes could not properly load language and lookup files on startup when certain sensor types were running on the instance. The failover node did not work anymore in this case. The issue was caused by some of the new sensor types we introduced over the last couple of PRTG versions, for example, DNS v2, AWS Cost, and MQTT sensors. |
By Sascha Neumeier • Sep 28, 2020
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. |
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. |
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. |
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. |
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 |
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. |
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. |
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 |
By Sascha Neumeier • Aug 24, 2020
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. |
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. |
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 |
|
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. |
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 |
|
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. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated language files (German, Spanish, Portuguese, and French) |
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. |
Password Recovery |
You can set a new password again using the Forgot password? option on the login page of the PRTG web interface. This did not work in the previous PRTG preview version 20.2.60.1535. |
Public Maps |
Maps with Public Access that you open without being logged in into PRTG are displayed again. You were not able to see the content of public maps in the previous PRTG preview version 20.2.60.1535. |
PRTG Status |
Synchronization statistics about configuration requests on the PRTG Status page are available again. They were not visible in the previous PRTG preview version 20.2.60.1535. |
Stability |
We fixed an access violation that appeared in the context of notifications in the previous PRTG preview version 20.2.60.1535. |
German and Japanese |
We updated the German and Japanese language files. |
By Sascha Neumeier • Jul 17, 2020
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. |
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! |
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. |
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. |
Web Server |
|
Sensors |
Minor security fix for the VMware Virtual Machine (SOAP) sensor |
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. |
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. |
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. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
Probes |
We fixed an issue with the "burst mode" for probe reconnects that we introduced with the last preview version 20.2.59.1579. If a probe disconnected and reconnected again during active burst mode, the probe did not show monitoring data until you manually triggered a scan. |
MQTT sensors |
The MQTT credentials settings on device, group, and probe level used by MQTT Round Trip BETA and MQTT Statistics BETA sensors are now also available on remote probes. |
German |
We updated the German language file. |
By Sascha Neumeier • Jun 10, 2020
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]. |
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. |
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. |
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]. |
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. |
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. |
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. |
All parts of PRTG |
Various other minor fixes and improvements, updated German language file, updated user manual |
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? |
By Sascha Neumeier • May 14, 2020
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. |
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. |
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. |
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. |
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. |
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. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
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. |
Server |
This version includes a security update for your PRTG core server. (CVE-2020-10374) |
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) |
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. |
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.
|
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) |
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. |
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. |
All parts of PRTG |
Various other minor fixes and improvements, updated user manual including a style update |
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.
|
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? |
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. |
Languages |
Updated German language file |
Security |
Minor security improvement in the context of PRTG user accounts |
Access Rights |
Access rights for the device tree in PRTG Desktop work again so that you can view information about objects like devices, groups, and probes if your user account has sufficient permissions. This did not work if you connected PRTG Desktop to the previous PRTG preview version 20.1.56.1498 due to a change to the access rights system. |
Logging |
Writing individual log files for the sensor types SNMP Fujitsu System Health v2, SNMP Nutanix Cluster Health, and SNMP Nutanix Hypervisor works again when you enable the debug option Write sensor result to disk. This did not work in the previous PRTG preview version 20.1.56.1498. |
By Sascha Neumeier • Mar 25, 2020
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. |
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. |
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. |
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. |
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. |
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. |
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). |
All Parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated German language file |
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. |
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. |
SNMP Fujitsu System Health v2 |
We fixed an issue with access violations in the sensor message for SNMP Fujitsu System Health v2 Sensor that occurred when updating to PRTG 19.4.55.1720. Only already existing sensors were affected and stopped working after updating. |
Access Rights |
Objects like groups or devices are now displayed when they are added by a non-administrative user account that has read/write access. Before the fix the added objects were only visible to other users in the same group in the previous preview version 19.4.55.1720. |
Probe Connections |
You do not need to approve Mini Probes again that are already running when you update to the latest PRTG preview version 20.1.55.1749. The mini probes required a re-approval when updating to the previous preview version 19.4.55.1720. |
By Sascha Neumeier • Feb 7, 2020
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
All Parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated Dutch language file |
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) |
HTTP Sensors |
HTTP sensors only show one URL field in the HTTP Specific settings again. In the previous PRTG preview version 19.4.54.1455, the field appeared twice in the settings of sensor types like HTTP and HTTP Advanced. |
Failover |
We fixed a potential issue with data synchronization to failover nodes that appeared in the last PRTG preview version 19.4.54.1455. |
By Sascha Neumeier • Dec 2, 2019
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. |
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) |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
All Parts of PRTG |
Various other minor fixes and improvements, updated user manual, updated language files |
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. |
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. |
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. |
Sensor Creation |
You can add sensor types with a fixed minimum scanning interval again. In the previous preview version 19.4.53.1869, the creation of such sensors failed. Affected sensor types were the Amazon CloudWatch sensors, Cloud Ping and Cloud HTTP, Common SaaS, Dropbox, Google Analytics, Google Drive, Microsoft OneDrive, and Windows Updates Status (PowerShell). |
Stability |
We fixed an access violation that was thrown when opening the Run Now tab of a report in the previous preview version 19.4.53.1869. |
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. |
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. |
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. |
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. |
All Parts of PRTG |
Various other minor fixes and improvements to all parts of PRTG, updated user manual, updated German language file |
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. |
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. |
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. |
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. |
Logs |
The Sensor Factory sensor writes less log messages than in the previous PRTG preview version and behaves as before again. Two lines of INFO logs for each sensor scan was a bit too much and unnecessarily filled up the PRTG core server log depending on your Sensor Factory sensor usage scenario. |
By Sascha Neumeier • Oct 9, 2019
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! |
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.
|
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. |
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) |
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. |
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 |
|
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. |
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). |
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. |
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. |
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. |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated German and Japanese language files |
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. |
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. |
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 |
Access Rights |
User accounts with restricted access rights to the device tree cannot see groups and devices anymore they are not allowed to. In the last 19.x.51 preview versions there was an issue concerning access rights. |
Access Rights |
The current preview version 19.3.51.2712 comes with an issue that affects access rights. User accounts with restricted access rights to the device tree can see groups and devices they are not allowed to. The sensor level is not affected by the issue. Status: Resolved with PRTG 19.3.51.2722 |
Language Files |
Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG. |
WMI Free Disk Space (Multi Disk) |
The WMI Free Disk Space (Multi Disk) sensor will not create channels for drives without values for free space and bytes anymore. In previous PRTG 19.2.51 preview versions, the sensor erroneously created a channel for the A:\ drive, for example, when selecting All disks during sensor creation (including sensors created by auto-discovery). This resulted in newly added WMI Free Disk Space (Multi Disk) sensors that did not recover from the unknown status. |
Cluster |
|
Devices |
Overview tabs of devices show data tables and sensor gauges again even if newly added sensors have not yet received data. In previous PRTG 19.2.51 preview versions, sensors were only shown on the tab when the newly added sensors had received data at least once. |
Device Tree |
PRTG will completely show the device tree again after expanding and collapsing parts of it. In the previous PRTG 19.2.51 preview versions, parts of the tree just vanished in this case until a page reload. This was already partially fixed in preview version 19.2.51.2561. |
Memory |
We fixed several minor and one bigger memory leaks on the PRTG core server that occurred in previous PRTG 19.2.51 preview versions. |
Notifications |
|
Probes |
|
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 also caused a loss of monitoring data with many sensors in unknown status. |
Sensors |
We fixed an issue that caused access violations on the PRTG server in previous PRTG 19.2.51 preview versions when there were running sensors without a primary channel. |
User Rights |
PRTG user accounts with restricted access rights can see the number of sensors by status on the welcome page again, as well as the global sensor status bar, of course only for sensors they have access to. In previous PRTG 19.2.51 preview versions, the numbers were not visible for read/write users, for example. |
DHCP |
The DHCP sensor works again. It showed a down status with an access violation in the sensor message in the previous preview version. |
SNMP Library |
You can add SNMP Library sensors again. This did not properly work in the previous preview version. |
Dependencies |
Dependencies properly work again with devices created via auto-discovery. Paused by dependency did not work for such devices when the master dependency was down in the previous preview version. |
Device Tree |
PRTG will completely show the device tree again after expanding and collapsing parts of it. In the previous preview version, parts of the tree just vanished in this case until a page reload. |
Sensors |
Sensors always have data tables again. In the previous preview version, data tables were not rendered in certain cases. This also lead to failing API calls when requesting data from running 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. |
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. |
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. |
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 |
Language Files |
Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG. |
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. |
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 |
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. |
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. |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual |
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. |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
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 |
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. |
Cluster |
We improved the stability of PRTG when adding remote probes to failover nodes in a cluster. In previous PRTG 19.2.50 preview versions, this action could cause several access violations. |
PRTG Core Server |
We improved the stability of PRTG core server restarts. In previous PRTG 19.2.50 preview versions, this action could cause several access violations in certain cases because running threads from the previous PRTG process were not properly stopped. |
DHCP |
We fixed an issue with the DHCP sensor that appeared in previous 19.2.50 preview versions of PRTG due to the activation of the Npcap Loopback Adapter (Packet Sniffer sensors use the Npcap library as of this version). In certain cases, the sensor showed a timeout error after updating to PRTG preview version 19.2.50 although there was a valid DHCP available. It is now also possible to monitor multiple DHCP servers in different networks. The DHCP sensor will send the data packets only via the selected NIC to monitor the DHCP server. If there is no DHCP server available in the specified network, for example, if the NIC has a link-local address, the sensor will time out as expected. |
Cluster |
|
License |
Activating and deactivating a license in offline installations works again. In the previous preview version 19.2.50.2778, clicking according buttons did not take effect due to an access violation. |
PRTG Core Server |
We fixed an issue with the message handler of the PRTG core server that could result in access violations. |
Windows IIS Application |
We changed the name of the new sensor channel that we introduced in PRTG 19.2.50 to Uptime (because it did not really show system uptime). The new channel Status has now its own lookup file with the states Running and Stopped. |
By Sascha Neumeier • May 28, 2019
MQTT Round Trip |
This PRTG version comes with the new MQTT Round Trip sensor! You can now monitor the availability of an MQTT broker to ensure your IoT devices can deliver their data at all times. Use the MQTT Round Trip sensor to check if a connection to the broker can be established, if the broker accepts messages via publish, if the broker forwards a message to a matching subscriber, and measure either the connection times or the round trip time from publishing a message until receiving it back on a subscribed topic. The sensor shows the message round trip time, the round trip status, the publisher connection time, and the subscriber connection time in different sensor channels. Keep a close eye on your IoT infrastructure - with PRTG and the new MQTT Round Trip sensor! |
DHCP |
You can now monitor multiple DHCP servers in different networks. The DHCP sensor will send the data packets only via the selected NIC to monitor the DHCP server. If there is no DHCP server available in the specified network, for example, if the NIC has a link-local address, the sensor will time out as expected. |
FTP Server File Count |
The FTP Server File Count sensor now supports TLS 1.2 connections. |
Oracle SQL |
We updated the Oracle library that Oracle SQL v2 and Oracle Tablespace sensors use to monitor your Oracle databases. We have seen that both sensor types cause less CPU load on the PRTG probe system compared to previous versions when using the updated library. |
VMware Host Hardware Status (SOAP) |
You can now define Known Warnings and Known Errors in the settings of the VMware Host Hardware Status (SOAP) sensor that include angle brackets (<>) to ignore messages that include such characters. |
VMware Host Performance and VMware Virtual Machine (SOAP) |
The sensor types VMware Host Performance (SOAP) and VMware Virtual Machine (SOAP) can now inherit the Channel Unit Configuration settings from the parent device. Please note that this still is not possible for certain units like bandwidth, for example. |
Windows IIS Application |
We added two new channels to the Windows IIS Application sensor. The channels show status and system uptime of a monitored web service. If the web service is not available, the sensor will show a down status. |
Amazon SNS Notifications |
The Location setting of the notification method Send Amazon Simple Notification Service Message now shows all available SNS locations in a dropdown list instead of a bullet list for a better usage of the available space. |
Execute Program |
Notifications that execute programs now show a meaningful message in notification related logs instead of an access violation if the defined credentials are incorrect. |
Notification Templates |
On the Notification Templates tab in your account settings, you can now directly test an existing template, pause or resume it, and open a list of objects that use the template. The functionalities are accessible in the notification templates table without the need of using the multi-edit menu. |
Notification Triggers |
Notification templates that you select for a notification trigger now show the actions they perform with an according icon in the dropdown before the template name. |
SMS Notifications |
|
Multi-Edit |
|
Reports |
We changed the rendering engine for PDF reports. PRTG now uses Chromium instead of the deprecated PhantomJS to be able to generate PDF reports in a more reliable way. Screenshots that you generate for the support bundle also use Chromium now. Known issue: Please ensure port 9222 is not blocked on the PRTG core server system to generate PDF reports and screenshots. This only affects PRTG version 19.2.50. |
Tags |
Clicking a tag in the settings of a Notification Template or Map now opens a list with all accordingly tagged objects. |
Cluster |
We slightly improved the cluster performance. |
Probe Connections |
We slightly improved the performance of probe connections by introducing a threadpool instead of using two dedicated threads for each probe. You will especially notice the improvement if you have many remote probes connected. |
Packet Sniffer |
Packet Sniffer and Packet Sniffer (Custom) sensors now use the Npcap library instead of the deprecated WinPcap to monitor your traffic. Note: If you need to downgrade from PRTG 19.2.50 or later to a PRTG version 19.2.49 or previous for some reason, please first stop the PRTG services and manually uninstall Npcap before you install an older PRTG version. |
Loopback Adapter |
PRTG now installs a loopback adapter as part of the Npcap library for Packet Sniffer sensors.
Note: If your remote probe runs additional services, for example a DHCP server, this adapter might have an effect on these services. If you experience issues, we recommend that you disable the adapter. This will not affect PRTG. |
Device Icons |
We replaced the previous SVG device icons with new TinySVG 1.2 compliant icons. |
Cisco IP SLA |
PRTG will not create an instance of the Cisco IP SLA sensor for an OID anymore if the target device does not return values for this OID. In such cases, the Cisco IP SLA sensor immediately showed a down status with the message No such object (SNMP error # 222) after sensor creation in previous versions. |
HTTP |
The auto-discovery creates working HTTP sensors again even if the target device only runs on HTTP (ports 80, 8080). In previous versions (since PRTG 18.3.42), the auto-discovery only created properly working HTTP sensors for HTTPS devices (port 443). |
HTTP Advanced |
The HTTP Advanced sensor can monitor a website over a proxy server with basic access authentication (HTTP) now. In previous versions, it returned an error with the message Unauthorized (HTTP error # 401) when using a proxy. |
IMAP |
We improved the message filtering of the IMAP sensor. In previous versions, the IMAP sensor only recognized the content types text/html and text/plain if the attributes were written in lowercase. Depending on the configuration of your email server, they can be written in different casing, so that the sensor could not find matching messages. This will now work. |
NetApp NIC |
NetApp NIC BETA sensors that you add to a NetApp cDOT or ONTAP with a version earlier than 9.2 will not create the Healthy channel anymore. NetApp versions previous to 9.2 do not return according data so the Healthy channel just remained empty after sensor creation. |
Sensor Factory |
We fixed several issues with the Sensor Factory sensor. Reports and graphs now include all data without gaps that occurred in certain cases, and the error handling as well as the no data behavior realize your defined options more reliably. |
SNMP Cisco System Health |
PRTG again only creates one instance of an SNMP Cisco System Health sensor per selected item in the Add Sensor dialog. In browsers other than Chrome (for example, Firefox and Internet Explorer 11), each selected measurement of the SNMP System Health sensor was added twice in previous versions. |
SNMP Custom Table |
The column headers in the Table Specific settings in the Add Sensor dialog of the SNMP Custom Table sensor are now always aligned with their columns so you can easier identify which data belongs to which column. In previous versions, the column headers did not scroll sideways with the table content. |
SNMP Windows Service |
The table of Windows services in the Add Sensors dialog of the SNMP Windows Service sensor has now paging so you do not have to scroll down through all the services anymore. |
WMI Microsoft SQL Server |
We removed the obsolete setting SQL Server Version from the sensor types WMI Microsoft SQL Server 2017, WMI Microsoft SQL Server 2016, WMI Microsoft SQL Server 2014, WMI Microsoft SQL Server 2012, WMI Microsoft SQL Server 2008, WMI Microsoft SQL Server 2005. |
Images |
We fixed an issue with images in PRTG that were not correctly loaded (for example, graphs in reports) when the port to publish PRTG via NAT or on a load balancer did not match the port of the web server. |
Search |
We fixed an access violation that appeared in certain cases on the PRTG core server and resulted in a malfunctioning PRTG search, not returning any search results. |
Dark Theme |
|
Dropdown Menus |
Entries in dropdown menus are better readable again. In previous versions, some dropdown menus like, for example, the report templates list appeared with blurred section headings in Google Chrome. |
Graphs |
Zoomed graphs automatically refresh their data again, as well as the according page footer shows up again. You can open a zoomed graph via the button Zoom graph in new window on several pages in the PRTG web interface. |
Maintenance Window |
If a sensor, device, group, or probe has the inheritance of the Schedules, Dependencies, and Maintenance Window setting enabled, PRTG will not validate the values (for example, start and end time of the maintenance window) anymore when you click Save. In case of enabled inheritance, the settings on this device tree level are inactive anyway. The previous behavior resulted in unnecessary error messages in certain cases. |
Mobile Android Probe |
We removed the last remaining links from the PRTG web interface that lead to the download page of PRTG Mobile Probe for Android. The app is not official supported and was removed from the Google Play Store some months ago. |
Multi-Edit |
The multi-edit menu is always available now if you have selected at least one item in a list (for example, a list of devices, sensors, reports, maps, libraries). In previous versions, the menu disappeared after cancelling the delete dialog while one or more items were still selected. |
Page Refresh |
The pause and resume buttons for the automatic page refresh in the page footer now always show the correct status, indicating if a click will pause or resume the refresh countdown. |
Quick Ranges |
We improved the filtering with quick range buttons, for example, for logs. The filters now better correspond to what the buttons say. |
Reports |
Data table entries in reports with a downtime greater than 0% are highlighted in red color again. We also improved the layout of reports with very long names and report related pages. |
Search |
The item count selector on the detailed search page now shows the current number of shown results per page without hovering over the selector. |
Smart Setup |
If you skip single steps or the the whole introduction, the setup assistant on a new PRTG installation will keep your decision and does not show up unwanted anymore. |
User Rights |
Only PRTG user accounts with administrative rights can download remote probes now. Read/write users and read-only users do not have the option anymore to open the Remote Probe Installer tab under Setup | Downloads and Tools, nor have the permission to do so on other places in the PRTG web interface. Read-only rights for remote probe downloads also apply to failover nodes in a PRTG cluster. |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual |
Report Period in Chrome |
In the current version, manually defining a date range (Period) with Start Date and End Date is not possible if you access the Report page with Google Chrome and your currently logged in PRTG user account uses the date format DD.MM.YYYY (24h or AM/PM). The date validation fails in this case. Workaround: Because the issue only exists in Chrome, you can use another browser like Firefox, Internet Explorer 11, or Edge to manually define a report period. Another option is to temporarily change the Date Format of your PRTG user account to MM/DD/YYYY or YYYY-MM-DD (24h or AM/PM). You can do so under Setup | Account Settings | My Account, section Web Interface. |
Dependencies |
We fixed another issue with dependencies where pausing by dependency did not work as expected in certain cases. If a sensor is set as master dependency, the sensor shows a down status in case of an error again instead of a paused status as it sometimes happened in PRTG 19.1.48. |
Down (Acknowledged) |
PRTG shows the user account who acknowledged the down status of a sensor again. As usual, the name will appear in the message as well as in the log of a sensor in status Down (Acknowledged). In PRTG version 19.1.48, the name of the acknowledging user account was missing. |
Unknown Status |
We fixed an issue where the system time of PRTG probe and server ran out of synchronization, which could result in grey sensors (for example, Ping sensors) in PRTG 19.1.48. You also might have noticed the issue if you use the WMI UTC Time sensor that showed a steadily increasing value in the Difference channel (time difference between PRTG system time and monitored device), which is also fixed with this new PRTG version. |
German |
We updated the German language file. |
By Sascha Neumeier • Apr 23, 2019
PRTG Desktop |
The PRTG Desktop client is now fully integrated in PRTG! You can directly open the download page from the PRTG web interface under Setup | Downloads and Tools | Desktop Client Apps or via the automatically created shortcut Get PRTG Desktop on the system you run your PRTG server and install the app on your desired system. PRTG Desktop is a new native PRTG application that runs on supported Windows and macOS systems. Use PRTG Desktop to completely control one or more PRTG installations with one app and show data of all your independent PRTG core servers including PRTG hosted by Paessler. The integrated tray tool will notify you whenever PRTG discovers issues in your network. You can also import server connections from the Enterprise Console. For more information and a direct download link, see the PRTG Desktop app webpage. |
EXE-Based Sensors |
PRTG now requires .NET version 4.7.2 installed on all computers running a probe for all sensor types that require the .NET framework. You will receive a ToDo ticket in PRTG for each affected probe if .NET 4.7.2 is missing. You will not be able to add .NET sensors anymore in this case and running .NET sensors will show a down status with error code PE104 after you have installed the PRTG update. For more details, please see this Knowledge Base article. |
SNMP HP and SNMP HPE Sensors |
We updated the names of several sensor types to reflect differences between devices from Hewlett Packard Inc. and Hewlett Packard Enterprise. Except for the SNMP HP LaserJet Hardware sensor, all former SNMP HP sensors have now a leading SNMP HPE in the sensor name. Please note that we already updated the device icons in PRTG version 18.2.41. There are no functional changes. |
JSON |
JSON output from the PRTG API now returns all fields as string values as long as the textraw format is not used for the field, even if a field was returned as integer until now. For example, priority in table.json is now returned as string instead of integer. |
Active Directory |
We improved the performance of Active Directory group synchronization when PRTG Active Directory accounts are members of two or more PRTG Active Directory user groups. You will especially perceive the improvement if you use PRTG apps to access PRTG. |
Tags |
We improved the way PRTG handles tags in the background, providing more consistency, stability, and a slightly improved performance for tag usage. |
PRTG Core Server |
Several other minor performance improvements |
SNMP Synology Logical Disk |
We added 9 new states to the standard lookup file of the SNMP Synology Logical Disk sensor, so your are now able to monitor all possible states of your Synology RAID. |
Windows Process |
The Windows Process sensor now supports 64-bit processes and accurately monitors processes that use more than 4 GB RAM (private bytes). |
API |
We fixed a potential DoS vector in the PRTG API. |
Sensors |
We improved the input validation of port fields in sensors settings. The fix closes a potential attack vector for malicious activities like Remote Code Execution (RCE). The issue was reported by Anton Vaychikauskas and Dmitry Galecha from Positive Technologies, thank you! (CVE-2018-19204) |
WebGUI |
We fixed some potential XSS vulnerabilities in the PRTG web interface. Thanks to the usd Bug Bounty Team (CVE-2018-14683), as well as Anton Vaychikauskas and Dmitry Galecha from Positive Technologies for reporting the issues! |
Cloud HTTP and Cloud Ping |
It is not possible to add Cloud HTTP or Cloud Ping sensors to IPv6 devices anymore because they do not support IPv6 and just showed an error message in this case. |
Sensor Factory |
Gauges of Sensor Factory sensors are now properly shown even if you use certain special characters in the channel definition. |
Auto-Discovery |
The PRTG auto-discovery adds found devices exactly written as they are named in the DNS, considering upper and lower case. In previous versions, PRTG erroneously added devices only in lower case. |
Cluster |
The Master Heartbeat now also works on failover nodes that become the current master. The file you choose via the PRTG Administration Tool on the failover server will be executed every 5 minutes as expected. |
Dependencies |
We fixed another issue with dependencies where pausing by dependency did not work as expected in certain cases. If a sensor is set as master dependency, the sensor shows a down status in case of an error again instead of a paused status as it sometimes happened in PRTG 19.1.48. |
Device Tree |
The group in the device tree that is automatically created when adding a new PRTG user group now always has the same name as the user group with an attached home (for example, New User Group home), even if the user group was created while adding a new user account. The group part of the name was missing in the device tree group in such cases. |
Down (Acknowledged) |
PRTG shows the user account who acknowledged the down status of a sensor again. As usual, the name will appear in the message as well as in the log of a sensor in status Down (Acknowledged). In PRTG version 19.1.48, the name of the acknowledging user account was missing. |
Logging |
The logging level in configuration files is now case insensitive for easier usage. |
Maps |
The History tab of maps now always contains an entry with the date the map was created. In previous versions, the entry disappeared as soon as 100 history entries were reached. |
Probes |
Your Python processes on PRTG probe systems will now continue running when you update your probes. In previous versions, updating probes resulted in terminating all Python processes on the machine because the updater did not check which process runs python.exe. |
Server Startup |
We fixed an issue with custom toplist fields where the check for the status of the target data structure was missing when PRTG upgrades the field declaration due to a change in PRTG version 18.4.47. Depending on when the custom field was created, the start of the PRTG core server could have been blocked by the issue. The error message that appeared in the PRTG core server log or when trying to start the server via the PRTG Administration Tool was TPaeInternalList.SetData: Col index out of bounds: 3(2) |
Unknown Status |
We fixed an issue where the system time of PRTG probe and server ran out of synchronization, which could result in grey sensors (for example, Ping sensors) in PRTG 19.1.48. You also might have noticed the issue if you use the WMI UTC Time sensor that showed a steadily increasing value in the Difference channel (time difference between PRTG system time and monitored device), which is also fixed with this new PRTG version. |
Cluster |
|
Dark Theme |
We improved the readability of notification template names when editing notification triggers in the dark theme. |
Dependencies Graph |
The dependencies graph now properly displays select dependencies that were not shown in certain cases. |
Device Tree |
|
HTML Email Notifications |
We improved the readability of HTML email notifications that contain SNMP Trap or Syslog messages resolved from the placeholders %traperrors, %trapmessages, %trapwarnings, %syslogerrors, %syslogmessages, %syslogwarnings |
Maintenance Window |
Minor usability improvements for the maintenance window setting in the PRTG device tree |
Management Tab |
We fixed a layout issue on the Management tab where the device tree showed too much whitespace between devices in browsers other than Chrome. |
Reports |
Reports now show an according message when there are no sensors included in the report instead of showing just an empty page. |
System Information |
|
Toplists |
Layout improvements for the time-range selector on toplist pages |
Welcome Page |
Read/write users and read-only users can now stay on the PRTG welcome page without receiving the message Error (Bad Request). Sorry, your user account is not allowed to access this information. because of erroneously trying to retrieve license information. |
Languages Files |
Major update of the Dutch language file, especially more consistency in terminology, and updated German language file |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual |
Memory Leak |
Please note that we took PRTG version 19.1.49.1916 (released on March 19) offline on March 21. The PRTG core server included a memory leak in version 19.1.49.1916. Depending on your monitoring scenario, this could lead to critical memory consumption on your PRTG server. The new PRTG version 19.1.49.1966 includes a fix for the memory leak. If you are running the withdrawn version 19.1.49.1916, please update as soon as possible. |
PRTG Core Server |
We fixed an issue that occurred in the previous preview version when PRTG was accessing historic data. This could result in deadlock events, followed by restarts of the PRTG server. |
Memory Leak |
We fixed several minor memory leaks and a bigger one on the PRTG probe system. The memory leaks were caused by SNMP monitoring and resulted in steadily increasing memory usage on affected probe systems in the previous preview version. |
Meta-Scan |
The meta-scan of SNMP Windows Service and SNMP Fujitsu System Health BETA sensors works properly again. In the previous preview version, the sensors did not find all available services and counters on sensor creation. |
Login |
We fixed a reflected XSS vulnerability on the login page of the PRTG web interface. Special thanks to Damian Schwyrz for reporting the issue! |
Historic Data |
The Sensor Status History section in HTML reports generated via a sensor's Historic Data function shows each entry only once again. In the last preview version, each status change erroneously appeared several times. |
Probes |
We fixed an issue with probe requests that were lost when the probe reconnected, which resulted in grey sensors (status unknown) on affected probes because they did not receive data. We also fixed scan thread timeouts that occurred in the context of System Information, which could result in unwanted probe restarts. |
PRTG Core Server |
We fixed an issue that lead to an access violation when deleting a sensor from PRTG. |
Maps |
Public maps that contain the Data Tables map object Alarms (gauges) work again. In the previous preview version, such maps constantly reloaded when accessed without login. |
SNMP HP BladeSystem Enclosure System Health |
SNMP HP BladeSystem Enclosure System Health sensors will show an error with the message Duplicates not allowed after the update to PRTG version 19.1.48.2868 in certain cases. We recommend that you wait with the update of your PRTG installation until we publish a fix for the issue if you are using SNMP HP BladeSystem Enclosure System Health sensors. Status: resolved with PRTG 19.1.48.2891 |
Sensor Graphs |
After updating to PRTG version 19.1.48.2868, historic data graphs will not show data in a few cases. This happens due to an issue with the PRTG graph data cache recalculation. If you are affected, please don't panic, your data is not lost. We will provide a fix for the issue as soon as possible and your data will be shown again. Status: resolved with PRTG 19.1.48.2876 |
SNMP Linux Disk Free |
SNMP Linux Disk Free sensors will show an error with the message List index out of bounds (0) after the update to PRTG version 19.1.48.2868 when monitoring certain Linux distributions. Affected are, for example, Debian 6, Debian 7, CentOS 6, Mandriva Linux 7.2 Odyssey, Ubuntu 12.04. Please note that these are affected distributions from which we only know right now. We are currently working on a fix and recommend that you wait with the update of your PRTG installation until we publish it if you are using SNMP Linux Disk Free sensors. Status: resolved with PRTG 19.1.48.2876 |
Lookups |
We added two new standard lookup files to PRTG that reflect the Boolean values 1 (true) and 0 (false). Use prtg.standardlookups.boolean.statetrueok as lookup if you want to have an up status for true (returned 1), use prtg.standardlookups.boolean.statefalseok if you want to have an up status for false (returned 0). |
SNMP HP ProLiant System Health |
We added the lookup status noPowerInput(17) to the standard lookup file prtg.standardlookups.hp.powersupplystatus of the SNMP HP ProLiant System Health sensor. The sensor will now show an according down status if your target device returns this value. |
SNMP Sensors |
We changed the method that SNMP sensors use on creation to search for available monitoring items on the target device ("meta-scan"). SNMP sensors will now use GETBULK requests during meta-scan instead of GETNEXT. With SNMP GETBULK, the sensors request 10 OIDs at a time by default, which leads to performance improvements in comparison to GETNEXT that requests only 1 OID at a time. The change also affects the System Information feature, so that the DDoS protection of QNAP devices should report alerts less often because of PRTG. Note: Only SNMP v2c and SNMP v3 support GETBULK, for SNMP v1 you still have to use GETNEXT. You can change the setting in the SNMP Compatibility Options of the target device in PRTG, section Walk Mode. |
PRTG Core Server |
This version includes various minor and major performance improvements, especially for the handling of a lot of remote probes. We also improved the scalability of the server with CPU cores and memory, the server startup times, and the post-processing of configuration changes (special thanks to electromichi for pointing us to this issue!). |
Maps |
The Top 10 lists Longest System Uptime and Shortest System Uptime are now available as map objects. |
Notification Delivery |
You can now directly test your SMTP and SMS settings on the Notification Delivery tab to check immediately if your settings work without changing pages and losing your context. Just click the button Test SMTP Settings or Test SMS Settings and see if your delivery settings work. |
Object History |
The object history of a notification template now indicates if settings of this template have been changed, Also, resuming an object like a sensor or device from paused status appears in the object history as of this version. |
Business Process |
Saving the settings of a Business Process sensor is now also possible when you only remove an object from the channel definition because the Save button is now active after the change. Also, when deleting an object from the channel definition, all objects are still shown and not only the first 7 entries so that you can easier delete more than 1 object. |
File and Folder |
File sensors and Folder sensors now use a negative value to indicate when the timestamp of a modified file is in the future. This approach will prevent the sensors from showing false warnings in such scenarios. |
File Content |
You can now add File Content sensors with the auto-discovery using your own device template. In previous versions, PRTG erroneously added File Content sensors as File sensors to newly created device templates, so that an auto-discovery with this device template only added File sensors. |
IMAP |
You can now use the setting Check connectivity only, do not process emails without providing credentials for the monitored mailbox. Credentials are not required in this scenario but were requested when you have manually added the sensor in previous versions. |
Sensor Factory |
The Sensor Factory sensor handles angle brackets (<>) in the channel definition in a better way now. The sensor overview tab will not appear broken anymore if you use these characters, but please note that the sensor gauge still will not look perfect in such cases. |
SNMP Cisco System Health |
The SNMP Cisco System Health sensor now shows a down status with error code PE268 if the sensor runs against an invalid OID. The sensor will show a down status with error code PE269 if there are one or more channels for which the sensor cannot query data. In previous versions, the sensor status was not expressive enough in such cases because it only showed unknown (gray color) or up with empty channels. |
SNMP IBM System X System Health |
We fixed the appearance of the gauge for the Overall Status channel of the SNMP IBM System X System Health sensor. The gauge did not properly appear because the sensor used a unit type not supported by lookups. The sensor now also shows the return message if the target device returned an invalid value (sensor value -1). Important: To apply the fix, please add the sensor anew. |
SNMP Linux Disk Free |
The SNMP Linux Disk Free sensor now creates channels for all disks on the target device. In previous versions, the sensor stopped searching for available disks during sensor creation as soon as there was a missing OID in the index table and so did not create channels for each disk on the target system. |
SNMP Synology Logical Disk |
The SNMP Synology Logical Disk sensor is now able to recognize when the order or name of a volume changes. In previous versions, it was possible that the sensor monitored an incorrect volume in such cases, which resulted in wrong monitoring data. |
Windows Updates Status (PowerShell) |
We fixed an issue with the Time since last update channel of the Windows Updates Status (PowerShell) sensor that still showed incorrect values in certain use cases after the improvements in the previous PRTG version 18.4.47. |
Login |
|
Reports |
We removed PRTG credentials (login name and passhash) from the URL of HTML reports that appeared in certain cases. |
Auto-Discovery |
We fixed an issue with the custom meta-scan that you can use with the auto-discovery but did not work as expected in certain cases. Please note that this functionality is still not officially supported. |
Installer |
PRTG now correctly switches from the 32-bit version to 64-bit after a server restart when the machine on which PRTG runs upgraded from less to more than 6GB RAM. This did not work in previous versions when a server restart was pending (status "PendingReboot") because of some Windows update or similar. |
Logging |
Several fixes and improvements for the logging framework |
PRTG Administration Tool |
If you change the Local Storage of Data Files and Monitoring Database folder on the Core Server tab in the PRTG Administration Tool, PRTG will also restart the local PRTG probe service along with the PRTG core server service now to immediately apply the changes. This is necessary to write data into the correct folder. |
Server Startup |
We fixed an issue that occurred when adding or editing a Sensor Factory sensor using Internet Explorer 11 or Edge. In this case, some control characters were wrongly added to the PRTG configuration file, which resulted in a failing start of the PRTG server. The error message in this case was: Sorry, could not start PRTG Core Server (Web server) [...] Formula empty. |
Updating from Version 18.1.37 or Older |
Direct updates from PRTG version 18.1.37 and previous versions to the current PRTG version 19.1.48 do work. It was not possible to directly update from these older versions to the previous PRTG version 18.4.47 because the PRTG server was not able to start in this case. |
Slack and Teams |
Slack and Microsoft Teams notifications now recognize line breaks within placeholders and show the whole content in a received notification. |
Teams |
The message when pausing a monitoring object like a sensor for 60 minutes via a received notification in Microsoft Teams now correctly is Paused via Microsoft Teams. In previous versions, PRTG showed the wrong pause message Paused via Slack. |
Dark Theme |
|
Graphs |
|
Maps |
|
Multi-Edit |
|
Sensor Gauges |
Sensor channels that show data as percentage now show gauges with minimum 0% and maximum 100% by default and appropriately display set limits. |
Tables |
Improved table layout and usage on various places, for example:
|
Tickets |
|
Top 10 Lists |
Top 10 lists of sensors will not show sensors without current last value anymore. |
Various |
This version includes dozens of other minor fixes and improvements for the PRTG web interface. This will remarkably improve your overall experience with PRTG! The fixes and improvements affect the following parts of the web interface, among others.
|
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files |
EXE-based Sensors |
Future versions of PRTG will need .NET version 4.7.2 installed on all computers running a probe for all sensor types that require the .NET framework. You will receive a ToDo ticket in PRTG for each affected probe after each probe update if .NET 4.7.2 is missing. For more details, please see this Knowledge Base article. |
PRTG Core Server |
We fixed an issue with the PRTG core server. In certain cases, the issue lead to access violations in the PRTG server system that could result in issues with sending notifications or unexpected server restarts with sensors in unknown status. |
PRTG GUI Starter |
We fixed several issues with the PRTG GUI Starter. It will work more reliable now. |
WMI Sensors |
You can now add the sensor types Windows Physical Disk I/O, WMI Exchange Server, WMI Exchange Transport Queue, WMI Logical Disk I/O, and WMI Vital System Data (V2) using the auto-discovery. The auto-discovery could not successfully add these sensor types in previous versions. |
Language Files |
Major update for all language files! |
Security |
We fixed a possible XSS vulnerability. |
Server Startup |
We fixed an issue with the flowid field in toplists of NetFlow sensors that could result in an exception during the startup of the PRTG server. The PRTG server did not start in such cases. |
Device Templates |
The sensor requirements for the .NET framework are correctly checked again in the PRTG auto-discovery, as defined in the applied device template. In the last preview version, .NET sensors were always created, no matter if the .NET version on the probe system matched the required version. |
Lookups |
Lists of lookup files are sorted alphabetically again when you select value lookups for a sensor channel. IDs of lookups are also loaded case insensitively again to prevent issues when you override default lookups with customs lookups. |
Sensor Factory |
PRTG correctly calculates historic data of the Sensor Factory sensor again. In the last preview version, live data was used to calculate historic data instead of averages. This resulted in wrong values. |
Notification Triggers |
This version includes some fixes for the appearance of the new notification template filter on the notification triggers tab that we introduced in the last PRTG preview version. |
Enterprise Console |
The Enterprise Console loads and displays all pages again. In the last PRTG preview version, the Enterprise Console was not able to load several pages. |
Updating from version 18.1.37 or older |
Please note that direct updates from PRTG version 18.1.37 and previous versions to the current PRTG version 18.4.47 do not work. Please wait with an update of your PRTG instance if you are currently running 18.1.37 or an older version until we publish PRTG 19.1.48. This version will include a fix for the issue. If you update from PRTG 18.1.37 or previous, the PRTG server will not be able to start. It will show an access violation in this case. If you are affected by the issue, please contact our technical support team. Status: resolved with PRTG 19.1.48.2868 |
Notifications |
|
Maps |
We improved the readability of map objects with status-related background colors. |
PRTG Core Server |
Several performance and stability improvements for the PRTG core server |
Graphs |
We updated the engine that PRTG uses to create data graphs. Thanks to the updated graphs engine, stacked graphs look better now! |
Logging |
This version includes some more improvements for the logging framework. |
HTTP Push Data Advanced |
The HTTP Push Data Advanced now supports UTF-8 characters in the |
SNMP Trap Receiver |
The SNMP Trap Receiver sensor now supports several modes for bindings that you can use with the syntax bindings[oid,value,mode]. Mode can be:
|
Windows Updates Status (PowerShell) |
We changed the approach of the Windows Updates Status (PowerShell) sensor to avoid down states that are not meaningful enough. As of the current PRTG version, the sensor will always create the channel Time since last update. All other channels only show up if the sensor can retrieve according data. Furthermore, the channel value is more accurate now. |
PRTG Core Server |
We fixed an issue with the PRTG core server. In certain cases, the issue lead to access violations in the PRTG server system that could result in issues with sending notifications or unexpected server restarts with sensors in unknown status. |
PRTG GUI Starter |
We fixed several issues with the PRTG GUI Starter. It will work more reliable now. |
Security |
We fixed a possible XSS vulnerability. |
Server Startup |
We fixed an issue with the flowid field in toplists of NetFlow sensors that could result in an exception during the startup of the PRTG server. The PRTG server did not start in such cases. |
Channels |
|
Event Log (Windows API) |
The Exclude Filter of the Event Log (Windows API) sensor now correctly disregards all events that you have added to the filter, for example, event IDs. |
Flow Sensors |
Stability improvements for the sensor types IPFIX, NetFlow V5, NetFlow V9, and sFlow: The fields FlowID, InboundInterface, and OutboundInterface in custom toplists are now stored with their field ID. In previous versions, they were stored as index, which could lead to issues when the list of fields changed. |
Lookups |
Lists of lookup files are sorted alphabetically again when you select value lookups for a sensor channel. IDs of lookups are also loaded case insensitively again to prevent issues when you override default lookups with customs lookups. | Sensor Factory |
PRTG correctly calculates historic data of the Sensor Factory sensor again. In the last preview version, live data was used to calculate historic data instead of averages. This resulted in wrong values. |
SNMP Custom String Lookup |
We fixed an issue with device templates that include an SNMP Custom String Lookup BETA sensor. When running an auto-discovery with the template, PRTG created an unused channel that was not defined for the sensor. |
SNMP sensors |
SNMP sensors that support this functionality now only replace text within square brackets in the sensor name if the text is an OID or a defined variable. All other text will appear in the sensor name as it is. |
SNMP Trap Receiver |
The SNMP Trap Receiver sensor now properly handles quotation marks (") in the filter for bindings and can find strings that contain quotation marks. |
UPS Health (Generic) Template |
The device template UPS Health (Generic) now also supports Tripp Lite UPS, so running an auto-discovery with the template will create suitable sensors for your Tripp Lite UPS. |
WMI Sensors |
You can now add the sensor types Windows Physical Disk I/O, WMI Exchange Server, WMI Exchange Transport Queue, WMI Logical Disk I/O, and WMI Vital System Data (V2) using the auto-discovery. The auto-discovery could not successfully add these sensor types in previous versions. |
Amazon SNS |
We updated the signature version of Amazon SNS notifications to Signature Version 4, so it is now possible to send SNS notifications from AWS regions that only support this signature version like, for example, Canada (Central) (ca-central-1). |
SMS |
Using the placeholders %SMSNUMBER and %SMSTEXT in the path of custom URLs for SMS notifications works again. Due to an encoding issue, the placeholders only worked in the query string of a URL since PRTG version 18.3.43 and you received an unknown protocol error if your custom SMS provider requires number and text as part of the path. |
Credentials |
We disabled the browser auto-complete of login and password fields in authentication sections of several sensor types (for example, HTTP Advanced and IMAP sensors). If you have saved your PRTG login credentials in your browser, your browser will not automatically fill in the credentials into PRTG settings sections anymore. |
Tables |
Paging on large tables and the selection of table items in the Add Sensor dialog works properly again. In previous versions, only sensors selected on the current table page were created. |
Various |
Several other minor fixes and improvements for the PRTG web interface |
XML |
We fixed an issue with invalid XML returned by the PRTG API. For example, if a sensor included non-XML compliant characters in the sensor or log message and you requested the sensor via the PRTG API, this resulted in an error with the message cannot convert value. |
Language Files |
Major update for all language files! |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual |
.NET Version |
Please note that we will upgrade our system requirements for the .NET framework in upcoming versions. Sensors that require the .NET framework will need at least .NET version 4.7.2 on all computers running a probe in the next PRTG version 19.1.48 that we plan to release in the first quarter of 2019. |
Icons |
We fixed an issue with icons that were not correctly loaded throughout the web interface in certain cases after installing the update to PRTG preview version 18.4.46.1638. The icons only were correctly loaded after clearing the browser cache. |
Support Bundle |
Screenshots in the support bundle are rendered and sent again. In the last PRTG preview version 18.4.46.1638, the screenshot function did not work. |
Lookups |
We fixed an issue with the PRTG server where access violations regarding lookups resulted in missing channels of some sensors. This only happened under certain circumstances. |
Enterprise Console |
The Enterprise Console loads and displays all pages again. In the last PRTG preview version 18.4.46.1638, the Enterprise Console was not able to load several pages. |
PRTG Status |
You can now see the names of all PRTG user accounts that are currently logged in to your PRTG instance! Open the PRTG System Status page in the web interface via the main menu (Setup | PRTG Status) and look at section Software Version and Server Information. There is the new entry Active User Sessions that shows all currently logged in PRTG users. |
Remote Probes |
Remote probes now always keep their defined names. In certain cases, the name of a remote probe changed to the host name after manually updating the probe. |
PRTG Server |
This version includes several stability and performance improvements for the PRTG server. For example, we dramatically improved the startup time especially with bigger configuration files, we reduced the memory usage of the core server after startup and after the configuration was saved, and we improved the performance of the website response a little. |
Web Server Connections |
The PRTG web server will now keep the option that you defined as IP address for the web server even if no IPs were found on the stack after a PRTG core server restart. In certain cases, usually after Windows updates, this resulted in the error No IPs could be found on the stack - reverting web server to local host after the core server started and the web server connection setting permanently switched to localhost. |
Amazon CloudWatch |
We added the new regions US East (Ohio), EU (Paris), and Asia Pacific (Osaka-Local) to all Amazon CloudWatch sensors. You can use the new regions with the sensor types Amazon CloudWatch Alarm, Amazon CloudWatch EBS, Amazon CloudWatch EC2, Amazon CloudWatch ElastiCache, Amazon CloudWatch ELB, Amazon CloudWatch RDS, Amazon CloudWatch SNS, Amazon CloudWatch SQS. |
SNMP System Uptime |
We improved the fallback mechanism of the SNMP System Uptime sensor. The sensor uses the hrSystemUptime OID to retrieve the uptime value and uses sysUpTimeInstance as fallback if hrSystemUptime is not available (see also this article). If both are not available, the sensor will show a down status until at least one uptime OID is available. If both are available again, the sensor will use the preferred hrSystemUptime. In previous versions, the sensor used the fallback sysUpTimeInstance in this case. |
JSON |
PRTG now returns strings from _raw columns surrounded by quotation marks ("") when you request JSON output, numbers still will be returned without quotation marks. In previous versions, quotation marks were missing for strings, which resulted in some issues because this was not common JSON. Please adapt your usage scenario of the PRTG API if necessary. Example: "uptimetime":"642 d","uptimetime_raw":55492731 |
XML |
The PRTG API now returns the correct response content-type header text/xml when you request XML output. In previous versions, the content-type was erroneously set to text/html. |
Amazon CloudWatch Alarm |
The Amazon CloudWatch Alarm BETA sensor now shows all configured alarms in the Add Sensor dialog. In previous version, some alarms were missing and could not be selected for monitoring. |
Debug Options |
We fixed an issue with the debug option Write sensor result to disk. In certain cases, some sensors continued writing the log files although the option was turned off again with "Discard sensor result". |
DHCP |
The DHCP sensor now correctly applies changes to settings. In previous versions, the check for server IP or client IP was still applied if you switched the option to Don't check but kept the entries in the include or must not include fields. |
DICOM Bandwidth |
The DICOM Bandwidth BETA sensor now shows the correct C-STORE size and correctly calculates the bandwidth usage of sent files. |
SNMP NetApp Network Interface |
The SNMP NetApp Network Interface sensor now applies the Unit for Bytes (Bandwidth) that you selected in the Channel Unit Configuration settings of the sensor's parent device. In previous versions, the sensor always showed traffic in MByte/s. |
SNMP Traffic |
We fixed an issue with SNMP Traffic sensors that were not addable to Cisco devices if selected additional channels were not available. PRTG showed the SNMP error #2003 in this case. |
SSH Script and SSH Script Advanced |
We fixed an issue with the search for scripts when adding an SSH Script or SSH Script Advanced sensor. The sensors were not able to find scripts and show them in the Add Sensor dialog when having certain localizations on target systems, for example, Italian. |
WMI HDD Health |
We fixed an issue with the WMI HDD Health sensor that occurred when parsing the instance name. The sensor returned an error message like "The query was not syntactically valid." if the WMI property InstanceName included certain characters. |
IE11 and Edge |
Saving changes on setting pages when using Internet Explorer 11 or Edge is possible again. In the previous PRTG version 18.4.45, clicking save resulted in a saving window that did not disappear and the settings could not saved. |
Various |
Several minor fixes for the PRTG web interface |
Lookups |
We fixed an issue with the PRTG server where access violations regarding lookups resulted in missing channels of some sensors. This only happened under certain circumstances. |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual (including API documentation for System Information), updated language files |
Trial Installation |
If you download a PRTG trial version from paessler.com and run the installer on a fresh machine, you will not have to manually enter trial key and license name anymore. |
Flow Sensors |
We fixed an issue with flow sensors. If received flow packets were too big, it was possible that they dropped. In this case, you encountered an increased value of the Probe Health sensor's Lost Flow Packets channel. This issue especially affected IPFIX sensors monitoring a Sophos UTM after an update of the target device. |
HTTP IoT Push Data Advanced |
The HTTP IoT Push Data Advanced sensor on PRTG hosted by Paessler instances works again. |
Language |
This version includes a substantial update of the German language file. |
License Update |
Updating license information in the PRTG web interface works fine again. In the last preview version, a saving window appeared and did not automatically disappear when updating the license. |
Reports |
When saving a new report, the Select Sensors Manually tab will automatically open again so that you are able to immediately add sensors to the report. In the last preview version, you mistakenly landed on the Run Now tab after saving. |
Notifications |
When you are on the Notification Triggers tab in the device tree, you can now directly open a dialog window to edit a selected Notification Template. This way you stay on the same page if you want to change the properties of a notification, so you do not have to leave the current context or lose settings that you already changed on the triggers tab. |
Status Donuts |
The legends of status donuts on the PRTG Welcome page and on map objects are now interactive. Click a status icon to directly open a list of sensors filtered by this status! |
Oracle Sensors |
The sensor types Oracle SQL v2 and Oracle Tablespace now support secure connections to your database system and are compatible with Oracle network encryption. |
Encryption |
The encryption method that PRTG uses now supports unicode (UTF-8 characters), for example, in fields for passwords, comments, and for the payload of HTTP notifications. In previous versions, the characters were converted to question marks (??) as soon as they were written to the configuration file (for example, after server restarts). |
Logging |
This version includes some minor improvements for the new logging framework introduced in PRTG 18.3.43. |
Common SaaS |
You can now define the inheritance of Notification Triggers of the Common SaaS sensor. In previous versions, the message (Property not found) was displayed instead of the settings. |
Flow Sensors |
We fixed an issue with flow sensors. If received flow packets were too big, it was possible that they dropped. In this case, you encountered an increased value of the Probe Health sensor's Lost Flow Packets channel. This issue especially affected IPFIX sensors monitoring a Sophos UTM after an update of the target device. |
HTTP IoT Push Data Advanced |
The HTTP IoT Push Data Advanced sensor on PRTG hosted by Paessler instances works again. |
Sensor Factory |
The Sensor Factory sensor will now notify you with an error message if the sensor could not created due to a syntax error in the channel definition. In previous versions, you might not have noticed it when the sensor creation failed. |
SNMP Library |
PRTG creates tickets again to notify you about newly created lookups when adding SNMP Library sensors. |
Add Sensor Dialog |
The Cancel button in the SNMP Help and WMI Help dialogs that you can open when adding according sensor types fails now works as expected and closes the dialog window without getting stuck. |
Map Designer |
The scissor symbol in the Map Designer to drop connection lines is available again. |
Maps |
We fixed an issue with maps that were added to the Home menu using a 5-stars priority and contained a sunburst element. The sunburst was not shown on such "home" maps. We also further improved the appearance of status background colors. |
Reports |
When selecting sensors manually in the report settings, the channels will now keep their selection even if you change the order of selected sensors. In previous version, the channel selection was reset when moving sensors. |
Sensor Gauges |
Sensor gauges are now properly displayed when the sensor is paused. In previous versions, the gauges erroneously still showed values and remained green when the sensor, device, or group was paused for x minutes. |
Sensor Lists |
Mini graphs in sensor lists are immediately displayed again and do not require a page refresh anymore. |
Similar Sensors |
Similar sensors will not show up anymore on a sensor's overview tab if you have disabled the functionality. |
System Administration |
Settings on PRTG system administration pages in the PRTG web interface that require a server restart to apply now are only saved if you confirm the server restart when saving changes to the settings. If you cancel the restart when PRTG asks for it, the settings will not be saved. This new behavior will prevent some unwanted side-effects that sometimes occurred when cancelling the restart. |
Tables |
More improvements for tables:
|
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
Flow Sensors |
We fixed an issue with xFlow sensors that occurred in PRTG 18.3.43. In certain configurations, the sensor types NetFlow V5, NetFlow V5 (Custom), NetFlow V9, NetFlow V9 (Custom), jFlow V5, jFlow V5 (Custom), sFlow, sFlow (Custom), IPFIX, IPFIX (Custom) did not receive data anymore after you have updated to PRTG version 18.3.43. They turned gray and showed the message "No data received since x minutes." in this case. |
Web Server Starter |
We fixed a timing issue that resulted in failing automatic starts of the web server in certain cases. |
Port Fallback |
We fixed an issue with the URL of the PRTG web interface. The URL was incorrect in case of forwarding to an SSL fallback port. |
Various |
Minor PRTG internal improvements |
Dependencies Graph |
The dependencies graph correctly shows dependencies again. In previous versions, the graph erroneously showed every dependent object as deleted. The functionality of dependencies was not affected by the issue. |
Device Tree |
Moving devices and groups to other groups via the right-click context menu in the device tree properly works again. You will stay on the current page after the moving action and PRTG will not mistakenly redirect you to an error page anymore. |
Maps |
We fixed an issue with the Map Designer that affected the previous preview version 18.3.44.1971. Object names appeared as "not found" in the Map Designer when moving an object from the device tree on the left onto the map and replacing it with a status icon from the right. |
Auto-Discovery |
We fixed some internal errors that occurred during auto-discovery in certain cases. |
Logging |
We fixed an issue with the new logging framework. The issue prevented PRTG from writing web server logs in certain cases. |
Connections |
You can now block TLS 1.0 connections for the PRTG web server. You can also explicitly define a security level for probe connections. With the high security option for web server connections, only TLS 1.1 and TLS 1.2 connections are allowed for clients, whereas default security additionally allows TLS 1.0. You can define the Connection Security level for the web server in the User Interface settings, section Web Server. With the high security option for probe connections, only TLS 1.2 connections are allowed for PRTG remote probes, whereas default security additionally allows TLS 1.1. If you update from an older PRTG version to the current PRTG version and your remote probes cannot connect anymore, you can temporarily allow TLS 1.0 and SSL V3 connections as well until all probes are updated. You can define the Connection Security level for probe connections in the Core & Probes settings, section Probe Connection Settings. By default, all PRTG installations are set to default security that allows TLS 1.0, TLS 1.1, and TLS 1.2 for web server connections and TLS 1.1 and TLS 1.2 for probe connections. Note: If you have set a registry key in previous PRTG versions to override the SSL version and cipher of PRTG web server connections, the High security setting will override the registry key setting and only TLS 1.1 and TLS 1.2 will be allowed. If you select the Default security setting, the registry key will override the default security setting and the connection security that you have defined in the registry will apply. |
Core Health |
The Core Health sensor has a new channel Configuration Last Saved that will warn you if PRTG was not able to save the configuration for 26 hours. |
NetApp Sensors |
|
Notifications |
The "clear condition" for the State Trigger now denotes more clearly in which cases the rule will apply. |
Reports |
A report can be run another time when changing Run Report settings without reloading the page. |
User Group Settings |
Improved performance for loading Active Directory groups on the setting pages of PRTG user groups |
API |
The API call /getobjectproperty.htm now supports subnodes like, for example, channels, notification triggers, and notification contacts. For example, the call /api/getobjectproperty.htm?id= |
Auto-Discovery |
|
Maintenance |
This version comes with a major maintenance increment including multiple changes in all areas of the PRTG core server. The changes lead to minor performance improvements on resource allocation within the data layer of the core server and reduction of file access while serving html pages on the web server. |
Security |
We fixed the field type of the proxy port field of HTTP sensors and several cases that potentially allowed a malicious administrative user to download content into the filespace of the PRTG probe system. The fixes of these minor issues improve the overall security of PRTG. Special thanks to Anton Vaychikauskas and Dmitry Galecha for finding and sharing the issues! |
Shutdown |
Improved shutdown procedure of the PRTG server |
Exchange (Powershell) Sensors |
Stability improvements for Exchange (Powershell) sensors |
NetApp NIC |
The NetApp NIC BETA sensor now shows correct traffic values. |
NetFlow v9 |
NetFlow v9 sensors now correctly handle IPv6 flows instead of just showing 0.0.0.0 for IP addresses. |
Sensor Factory |
|
sFlow |
We fixed an issue with sFlow sensors that did not properly process very high traffic values of inbound and outbound interfaces. |
SNMP Sensors |
|
SNMP Traffic |
The quick action buttons Select all connected interfaces and Select all disconnected interfaces when adding the SNMP Traffic sensor work again. |
SSL Certificate |
The SSL Certificate sensor now compares the SAN/CN and the device name in a case insensitive way as defined by the RFC. The fix will prevent the sensor from showing false positives when monitoring a certificate. |
VMware Datastore (SOAP) |
We changed the handling of regional system settings on the Windows system that runs the PRTG probe service with the VMware Datastore (SOAP) sensor. If the decimal symbol defined in the system settings differed from the decimal separator defined by Windows regional settings (for example, comma in number formats but dot via the region format), disk space values were not correctly shown in previous versions. |
Windows IIS Application |
We fixed an issue with the Windows IIS Application sensor that, in certain cases, resulted in sensor errors after restarting the PRTG server or monitored devices. |
Windows Updates Status (Powershell) |
Stability improvements for the Windows Updates Status (Powershell) sensor |
Internet Explorer 11 |
Checkboxes in live graphs are correctly displayed again in Internet Explorer 11. |
Maps |
We did some minor improvements for the layout of device tree map objects and the appearance of status background colors. |
Reports |
We fixed an issue where volume showed incorrect first and last values in historic data reports if the interval of the report was set too close to the scanning interval of the sensor. |
Security |
The re-auth dialog on settings pages now appears more reliably and always asks to re-enter credentials after 15 minutes. |
Tables |
Layout fixes for tables on various places throughout the web interface |
Ticket Notification Template |
You can properly edit the last line in the Content field of the Assign Ticket notification template again. Clicking the last line will not mistakenly set the default content anymore. |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files |
WebGUI |
In the last preview version, context menus did not properly work in some cases. We fixed this. |
Logging |
Some fixes for the new logging framework |
Enterprise Console |
Starting a standalone Enterprise Console works again. In the last preview version of PRTG, the Enterprise Console only could be started on the PRTG server itself. |
Languages |
We updated the language files for German and Dutch. |
By Sascha Neumeier • Aug 31, 2018
NetFlow Sensors |
In certain configurations, NetFlow sensors do not properly work with the current PRTG versions 18.3.43.2317 and 18.3.43.2323. If an installation is affected, the sensor types NetFlow V5, NetFlow V5 (Custom), NetFlow V9, and NetFlow V9 (Custom) do not receive data anymore after you have updated to the current PRTG version. They will turn gray and show the message "No data received since x minutes." in this case. The issue does not affect every configuration, but we strongly recommend that you do not install the update if you use NetFlow sensors. We are currently working on a fix with high priority. Please bear with us! |
HTTP IoT Push Data Advanced |
The new HTTP IoT Push Data Advanced BETA sensor displays data from XML encoded messages that are pushed via an HTTP request to the PRTG server, including PRTG hosted by Paessler instances. It works very similar to the HTTP Push Data Advanced sensor, but we adapted the concept so that you can now push your messages to the hosted probe of PRTG hosted by Paessler. This is especially useful in the context of Internet of Things (IoT), for example, if you want to monitor your Sigfox infrastructure. |
NetApp SnapMirror |
The NetApp SnapMirror BETA sensor has a new channel that shows the end timestamp of the last transfer. Furthermore, you can now add a NetApp SnapMirror BETA sensor even if there exist relationships that have the same source, which resulted in an error when trying to add the sensor in previous versions. |
Notifications |
We improved the wording of notifications and notification triggers to help you to better distinguish between the different parts of the PRTG notification system.
|
Notification Triggers |
You can now use Up and Unknown states with the State Trigger. |
SMS Delivery |
Whitespaces in custom URLs for SMS delivery will now be automatically URL encoded. Important: If you have manually encoded the whitespaces with %20 in previous PRTG versions, you will have to replace %20 with whitespaces for working custom SMS notifications after updating to PRTG 18.3.43. |
SMTP Relay Server |
It is not possible anymore to explicitly set SSL V2 for SMTP delivery of notifications when using an SMTP relay server. The SSL method will be automatically set to SSL V2 or V3 after updating to PRTG 18.3.43 if you had selected SSL V2 before. |
Logging |
We massively improved the logging framework of PRTG to be able to even better support you if you have issues with PRTG. This includes the option to log unusual events (unusual detection) and a change of the logging directory structure (invalidated CVE-2018-17887). |
Search |
We improved the search speed in the manual that is delivered with your PRTG installation. |
Main Menu |
If you use more than 1,000 tags in your PRTG installation, the main menu (Sensors | By Tag) of the PRTG web interface will not show your tags anymore to improve the performance. You will see an according note in this case and you can still use tags, for example, for filtering and searching. |
Maps |
You can now control the color mode of public maps via the security context of the map. The public map either uses the light theme or the dark theme depending on the user account that you choose in the map setting Security Context and Color Mode. The Color Mode that this user account has set in the account settings will apply to the public map. |
Passhash |
PRTG user accounts that were added via Active Directory can now show their passhash in their account settings. |
NetApp System Health |
The NetApp System Health sensor now shows the usable spare size and the spare disk count 0 if a NetApp node has no spare disks instead of showing an error. |
sFlow and sFlow (Custom) |
We improved the handling of incorrectly reported "sample pool" values that caused 0 values for traffic. |
SNMP Fujitsu System Health |
We fixed an issue that caused SNMP Fujitsu System Health BETA sensors to show an unknown status (gray) in certain cases after running a while. We also fixed minor memory leaks in parts of the SNMP engine used by this sensor type. |
SNMP Custom and SNMP Custom Advanced |
|
Account Settings |
The Save button to change the password when logged in with a read-only user account shows up again if the account is allowed to change the password. The button was missing in the last version. |
Geo Maps |
If you disable the Geo Maps feature, it will now be disabled in all parts of the PRTG web interface. In previous versions, this was not the case and caused timeouts in the web interface when your PRTG server or client was offline. |
Internet Explorer 11 |
Toplists will correctly appear again when you switch time slots. Internet Explorer 11 had issues with that. |
Reports |
We fixed an issue with CSV reports that caused an empty line at the beginning and at the end of a CSV report for timeframes that were not selected in the settings. |
Tables |
Access Rights tables on several pages in the PRTG web interface work properly again even if you have a lot of user groups. |
Various |
Several other minor fixes and improvements for the PRTG web interface |
API |
|
Security |
In certain cases, the passhash appeared in the URL when switching cluster nodes. We fixed the issue. |
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files |
Windows Server 2003 R2 and Older |
PRTG does not start and run on outdated Windows versions like Windows Server 2003 R2 anymore as of the current PRTG versions 18.3.43.2317 and 18.3.43.2323. Please make sure you install PRTG on an officially supported operating system! |
By Sascha Neumeier • Aug 1, 2018
Maps |
We fixed some issues with maps.
|
Memory Leak |
We fixed a memory leak on the PRTG probe system caused by running SNMP Fujitsu System Health BETA sensors. |
Map Service Provider |
Google will forbid a keyless access to the geocoding API in future, so PRTG will now use the geocode of HERE Maps by default. Geocoding is used to convert the addresses that you enter in the Location (for Geo Maps) settings into geographic coordinates to show the position of your monitoring objects on the geo map. If you still want to use the geocoding API of Google, you have to enable your Maps Static API access key for the Geocoding API in the Google console as well. For details, please see the Knowledge Base article How do I get a Google Maps API key for use in PRTG? |
Placeholders |
We fixed the resolution of the %home placeholder that did no longer add a slash to the URL of the PRTG server when appending one or more characters. The issue resulted in broken URLs in certain cases, for example, in notifications. |
WebGUI |
|
Enterprise Console |
We fixed some layout issues of the Enterprise Console that appeared in the last preview version of PRTG. |
WMI Microsoft SQL Server 2017 |
You can now monitor your Microsoft SQL Server 2017 with PRTG! The new WMI Microsoft SQL Server 2017 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. |
Slack and Teams |
We introduce two new notification types with this version. You can now send notifications to your Slack and Teams channels! Choose the notification type Send Slack Message or Send Microsoft Teams Message in your notification settings, provide the URL of the webhook you set up, and receive your PRTG notifications with all important information directly in your messenger. Note: Please note that proxy usage is not supported in this initial release of the new notification types. |
Send Email |
You can now individually define custom sender email addresses and names per email notification! By default, email notifications use the global sender setting that you define in the Notification Delivery settings. Now you have the option in the settings of a notification to use a custom sender that overrides the global sender settings for this notification. Please note that the outgoing SMTP server must allow the custom email address to deliver the email. |
Execute HTTP Action |
The notification type Execute HTTP Action now also supports the HTTP methods PUT and PATCH in addition to GET and POST. Choose your preferred HTTP method in the notifications settings and enter the payload that PRTG will transmit to the target URL. |
Event Log (Windows API) |
You can now use negative filtering in Event Log (Windows API) sensors! This means that you can exclude specific event sources, IDs, categories, users, computers, and messages from monitoring. Events that you exclude via the sensor settings will not be processed by the event log sensors. |
Libraries |
You can now individually change the Security Context of your libraries in the library settings. In previous versions, the security context was always defined by the PRTG user account that created the library. The security context will now also apply to notification triggers of libraries, so they only will be provoked for monitoring objects for which the security context is defined. |
Monitoring Data |
We reduced cases where monitoring data and sensor messages were missing after PRTG server restarts. |
System Information |
Stability improvements for the System Information feature |
Maps |
We updated older map objects to fit better with the new style of the PRTG web interface. |
sFlow |
We fixed an issue that resulted in sFlow sensors showing incorrect data. In certain cases, the issue appeared because of an ignored "subid" of the agents. |
SNMP CPU Load and Windows CPU Load |
SNMP CPU Load and Windows CPU Load sensors correctly show the Total channel as line in the data graph again when using the Graph Type option Stack channels on top of each other. The channel was erroneously stacked as well in newly created sensors of previous versions. |
SNMP Sensors |
Stability improvements for SNMP sensors: In some cases, SNMP sensors (for example, SNMP RMON, SNMP Cisco System Health) were successfully created but sensor scans failed with SNMP error #223 (no_such_instance). PRTG will handle such cases better now. |
Buttons |
We made functionality and naming of buttons throughout the PRTG web interface more consistent. |
Dark Theme |
Several fixes for the dark theme of the PRTG web interface, for example, better readable texts in filters and toplists |
Internet Explorer 11 |
We fixed the position of several buttons (for example, in reports and the Add Sensor dialog) in the PRTG web interface for Internet Explorer 11. |
Maps |
We fixed an issue with public maps that failed to refresh when including the Data Tables object Tickets. |
System Information |
You can select the text in System Information tables with your mouse again to copy and paste the entries. |
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
API |
We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to Positive Technologies, especially to Dmitry Galecha. Thank you! |
Reports |
We fixed a possible issue with access rights for reports. |
Various |
This version also includes updated language files and some other minor fixes. |
By Sascha Neumeier • Jun 18, 2018
Maps |
We added the donut charts from the PRTG welcome page as map objects, so you can now use donut charts with current sensor states on your dashboards! |
Reports |
The Sensor Status History section in historic data reports now shows more precise values and always displays the statistics down to seconds. In previous versions, PRTG rounded the values to units that were too large in certain cases and so did not add up to the values in the heading of the report. |
SMS Delivery |
We added the Windows registry option to use basic authentication for SMS delivery. This may be helpful when you use custom URLs for SMS delivery and your provider requires basic authentication. For details see the article https://kb.paessler.com/en/topic/79575 in our Knowledge Base. |
Context Menus |
We removed the right-click context menus from the overview pages of libraries, maps, and reports. |
Settings |
We removed the user account settings Max. Groups/Devices per Group and Max. Sensors per Device that defined when to collapse nodes in the device tree, because PRTG automatically handles this. |
API |
We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to Positive Technologies, especially to Dmitry Galecha. Thank you! (CVE-2018-19203, CVE-2018-19410) |
Reports |
We fixed an issue that allowed access to reports under certain circumstances without according permissions. |
Business Process |
Configuration reports for the Business Process sensor work again. |
HL7 |
We improved the order of HL7 sensor settings. |
HTTP Advanced |
The HTTP Advanced sensor now also supports TLS 1.1 and TLS 1.2 connections when using the compatibility mode as monitoring engine. |
Oracle SQL v2 and Oracle Tablespace |
We fixed an issue with device templates that prevented Oracle SQL v2 and Oracle Tablespace sensors from being added via auto-discovery. |
REST Custom |
The REST Custom sensor now works when a proxy server is defined in the Proxy Settings for HTTP Sensors settings. In previous version, the sensor returned an error with the codes PE233 and PE231 when using a proxy. |
SNMP Custom Advanced |
In certain cases, the SNMP Custom Advanced sensor showed incorrect values when very large values were returned by the target device. We fixed the issue. |
SNMP Library |
SNMP Library sensors correctly take custom units from OID libraries again. |
SNMP Sensors |
SNMP sensors will not terminate the scan for available monitoring items during sensor creation anymore when the scan for an entry fails because of an OID that is too long. |
Windows IIS Application |
The Windows IIS Application sensor now supports 32-bit unsigned integer values (UInt32), so it can handle values greater than 2147483647, the maximum value for a 32-bit signed integer. |
Context Menus |
Manually executing sensor scans from context menus works again. Please note that we renamed Check Now to Scan Now to better reflect what this function actually does, which is executing a sensor scan. |
Email Notifications |
Links to your PRTG installation in email notifications work again. |
Management Tab |
We fixed an issue where acknowledging the deletion of many objects at once on the Management tab was not possible because of a cropped window. |
Object Selector |
Changing dependencies to other objects, changing related objects in filters for lists, and changing linked objects in library node settings work again. |
Reports |
|
Tables |
Various performance and layout improvements for tables in the web interface |
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
Event Log (Windows API) |
Filtering by event ID with the Event Log (Windows API) sensor works again. Due to a change in the Windows API the sensor was not able to find events by ID in previous versions. |
Exchange Database DAG (Powershell) |
The Active Copy channel now shows correct data when monitoring Exchange Server 2010. |
HTTP Advanced |
The request method HEAD now properly works with the HTTP Advanced sensor. The channels Bytes received and Download bandwidth only showed 0 values in previous versions. We also improved the bandwidth calculation and the way the sensor monitors really fast connections (for example, LAN or localhost) that sometimes caused the error message "Potential error during bandwidth calculation. (Loading time below 0.1 ms)". |
NetFlow V9 and IPFIX |
We fixed an issue that caused in and out traffic to be assigned in the wrong direction (switched source and target) in certain cases when monitoring a Cisco ASA. The issue affected the sensor types NetFlow V9, NetFlow V9 (Custom), IPFIX, IPFIX (Custom) and was visible when using toplists or filters. |
REST Custom |
|
SNMP Custom and SNMP Custom Advanced |
SNMP Custom and SNMP Custom Advanced sensors show correct values again when the requested OID returns negative values. In certain cases, the sensors only showed the value -1 for returned negative values. |
SNMP Traffic |
We improved the compatibility of the SNMP Traffic sensor with certain target devices that have issues with their current firmware version. In certain cases, the SNMP Traffic sensor could not properly finish requests, which resulted in many log entries on the target device. |
Windows Update Status (Powershell) |
Stability improvements for the Windows Updates Status (Powershell) sensor |
Channel Limits |
Using decimal separators in channel limits works properly again. Saving the settings will not reset entered values to 0 anymore when using decimal separators. |
Sensors |
Security improvements for debug log files that several sensor types can write using the option "write result to disk" |
Maps |
|
Reports |
|
Tables |
Changing object priorities in tables will not result in expanding table rows anymore. |
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
By Sascha Neumeier • May 21, 2018
SNMP Fujitsu System Health |
We added the first native Fujitsu sensor to PRTG! The new SNMP Fujitsu System Health BETA sensor monitors the status of Fujitsu PRIMERGY servers via the iRMC. With this new sensor type you will have an overview about the iRMC status, CPU status, available memory, status of power supplies, the current temperature, the temperature status, and more. |
NetFlow V9 and IPFIX |
NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors now support IPv6 flows. Please note that the IPv6 support for these sensor types is included as experimental feature. We welcome any feedback on the IPv6 functionality, just send it to [email protected]! |
SMB-based Sensors |
The sensor types File, File Content, Folder, and Event Log (Windows API) handle impersonation in a better way and mitigate potential error sources. The sensors now first try to access the target share as LOCAL_SYSTEM Windows user. If they do not succeed, they try impersonation with the Windows credentials defined in the device settings. |
SNMP Custom String and WMI Custom String |
SNMP Custom String and WMI Custom String sensors now show the retrieved string message even when the sensor status is unusual. |
WMI HDD Health |
We improved the naming of the WMI HDD Health sensor channels. The names of the several sensor channels are more meaningful now and will not show just "unknown". |
Desktop Notifications |
PRTG will now ask you when you access the PRTG web interface with a Firefox or Google Chrome browser for the first time if you want to allow Desktop Notifications from PRTG. Because you can directly enable and disable Desktop Notifications from PRTG via your browser, we also removed the Desktop Notification tab from PRTG Setup. |
Quick Action Buttons |
We removed the delete icon (trash can symbol) from the quick action icons of probes, groups, devices, and sensors to avoid deleting objects by accident. Please use the context menu next to the quick action icons to delete objects. The Acknowledge indefinitely quick action icon will now always appear as first icon, so its appearance will not change the order of the buttons anymore to avoid clicking the wrong icon by accident. |
Tables |
We changed the order of columns in sensor tables to improve the readability. The Message column now comes after the Status and Last Value columns so that the available table space is used in a better way. |
NetApp System Health |
We fixed some issues with the NetApp System Health sensor. Important: After the update to PRTG 18.1.39, please create your NetApp System Health sensors anew. Existing sensors of this type show incorrect data since PRTG 18.1.38!
|
Security |
We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to STO LABS, especially to Lucas Carmo, Edward Toledano, and Ricardo Fajin. Thank you! |
Active Directory |
We eased the user rights management for PRTG user accounts that you add via Active Directory groups. You can now define in the user group settings that new users of a certain Active Directory group have read-only rights and the right to acknowledge alarms. In previous versions you had to manually define this right for each user account of a read-only Active Directory group. |
HTTP Transaction |
The HTTP Transaction sensor now also supports TLS 1.1 and TLS 1.2 connections when using the compatibility mode as monitoring engine. |
PowerShell |
We fixed a potential security issue with command line parameters for PowerShell scripts that affected EXE/Script sensors, EXE/Script Advanced sensors, as well as Execute Program notifications (CVE-2018-9276). We also fixed a potential security issue with sample custom notifications (CVE-2018-9278). Note: The fix required changes to the handling of command line parameters. In certain cases, it will be necessary to adapt quoting with backticks (``) in the parameters field because PRTG will process quotes more accurately. |
Outgoing Connections |
Outgoing connections from the PRTG core server to Paessler servers for activation, update check, and downloads now use HTTPS. |
Event Log (Windows API) |
Exclude filters in the settings of the Event Log (Windows API) sensor were erroneously shown in the last PRTG version but they had no functionality. These options will not be shown in the new PRTG version to avoid confusion. We will add the functionality to use exclude filters with this sensor type in a future PRTG version. |
Exchange Public Folder (Powershell) |
The Exchange Public Folder (Powershell) sensor now supports all UTF-8 characters and whitespaces in folder names. |
Exe-based Sensors |
We improved the timeout handling of sensor types that run .exe files to retrieve monitoring data. In certain cases, when the sensor request took too long, the sensors ran into a timeout, which resulted in the error message "Timeout caused by wait for mutex (code: PE035)", and only recovered after a restart of the PRTG probe. |
Units |
We fixed an issue that resulted in a broken sensor channel display when switching from unit "Value Lookup" to unit "Count". This issue affected sensor types that provide channel unit settings in the sensor settings, for example, SNMP Custom Advanced and SQL v2 sensors. |
Internet Explorer 11 |
Several fixes for the usage of the PRTG web interface with Internet Explorer 11
|
Reports |
We improved the readability of historic data reports reports, including a corrected position of percentiles. |
Tables |
Paging on large tables and the selection of table items work properly again, for example, in the Add Sensor dialog, in user group settings for allowed sensor types, and in the dialog for running an auto-discovery with template. We also improved the readability of column headers in data tables. |
User Rights |
PRTG user accounts with read/write user rights are allowed to view dependencies again. |
Various |
Several other small fixes and improvements for the PRTG web interface |
Performance |
We fixed some more issues that caused performance losses and resulted in PRTG core server timeouts in certain cases. |
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
By Sascha Neumeier • Mar 28, 2018
Security |
PRTG 18.1.38 contains an important security update for your PRTG installation. There is a security issue that affects PRTG versions 17.4.35.3326 through 18.1.37.13946. Previous versions are not affected.
The error that causes the issue does not occur on every PRTG instance. If your installation is affected, PRTG will create a ToDo ticket for PRTG administrators that contains more information. PRTG will create this ticket after you have installed the secure version and only if you were affected by the issue. We strongly recommend that you immediately update to the latest PRTG version in any case. Note: In certain cases, the Windows Defender interferes with the PRTG installer. This might cause high CPU load on the PRTG server, which might prevent a successful installation of the update. Please temporarily disable the Windows Defender if you have issues installing the update. |
DICOM and HL7 Sensors |
You can now monitor your medical IT on Digital Imaging and Communications in Medicine (DICOM) and Health Level-7 (HL7) out of the box! The new PRTG version 18.1.38 includes 4 new sensor types that show you important information about your DICOM and HL7 capable systems and devices.
|
WMI Event Log |
You can now use negative filtering in WMI Event Log sensors! This means that you can exclude specific event sources, IDs, categories,users, computers, and messages from monitoring. Events that you exclude via the sensor settings will not be processed by the event log sensors. |
Lookups and Alerting |
You can now explicitly define when sensor channels that use lookups will show a down status and alert you, either based on the lookup definition or based on numerical limits for returned values. You will find the new setting Value Lookups and Limits in the settings of custom channels instead of the Limits settings where you can decide which method is best for your setup. Please keep in mind that only one option will apply! So, if you choose limits as alerting method, an error status as defined in the lookups will not show up. After you have updated PRTG to this version, existing custom channels will be provided with an appropriate default automatically. If you had set alerting by limits and lookups simultaneously before the update, the limit setting will apply after the update and values will not appear as lookup channels, but your notifications still work as expected. Please check that your custom channels still have an alerting method that is suitable in your scenario after the update. |
NetApp System Health |
The NetApp System Health sensor has a new channel Storage configuration path. The channel monitors the current configuration path that describes the connection of the node (multi_path, multi_path_ha, single_path, single_path_ha, mixed_path, mixed_path_ha). |
SSH Sensors |
To reduce CPU load on the PRTG probe system, we improved the timeout handling of all SSH sensors when the target system is not reachable. Important: After the update to PRTG version 18.1.38, the Connection Timeout and Shell Timeout settings of your running SSH sensors will be reset to a default value! This approach will avoid potential errors if you have set individual timeout values. If your configuration requires other timeout values to properly work, please change them again after the update.
|
Event Log (Windows API) and WMI Event Log |
There is a known issue in this version: Event Log (Windows API) and WMI Event Log sensors have a new option to exclude certain events from monitoring (see section Improvements below). By default, the sensors will set the new option to Exclude Filter for each available filter after the update to this PRTG version. This causes the sensors to disregard events that you actually want to monitor and filtered for in previous versions. For example, if you defined to filter for a certain event ID, this ID will now be excluded but all events with another ID will be counted. Please manually correct the sensor filter settings after installing the update. Note: The Event Log (Windows API) sensor shows settings for exclude filters, but the filters are not functional yet. You can only use include filters. We will add the functionality to use exclude filters with the Event Log (Windows API) sensor in one of the next PRTG versions. |
Business Process |
Several fixes for the display of Business Process Specific Settings |
Custom Sensors |
You can specify a scaling factor (multiplication and division) in the channel settings of custom sensors again, including channels of SNMP Library sensors. Scaling factors defined by meta-scan, OID libraries, and PRTG backend results will also apply again. This did not work for non-custom units (for example, bytes/s) in previous versions. |
Exchange (Powershell) Sensors |
As announced in the release notes of PRTG 18.1.37, we removed the Execution Time channels from Exchange (Powershell) sensors. The channel was only delivered in PRTG 17.4.36 and was not functional. |
Folder |
The Folder sensor can now access folders on a network share when the share has specific credentials. If the Windows user account that runs the PRTG probe service has no access rights on the Windows share but there are correct Windows credential defined in PRTG, the sensor will be able to monitor the share. |
SNMP HP ProLiant System Health |
We removed the Integrated Management Log Status channel from the SNMP HP ProLiant System Health sensor because the OID that the sensor used no longer exists. |
SNMP Library |
|
SNMP Linux Meminfo |
The SNMP Linux Meminfo sensor channel Percent Available Memory has no predefined limits anymore to better reflect the behavior of Linux systems. If you need the removed limits, please manually add them again in the channel settings after the update to this PRTG version. By default, the new primary channel of the SNMP Linux Meminfo sensor is Physical Free Percent. |
SSH Disk Free |
The SSH Disk Free channel includes all selected partitions in one sensor again. In previous versions, PRTG erroneously created one sensor for each selected partition with the content of both selected partitions. |
SSL Security Check |
We removed the SSL 2.0 channel. The OpenSSL component that PRTG uses does not support SSL 2.0, so the channel result was incorrect. |
VMware Sensors |
VMware sensors now work on Windows machines with the Federal Information Processing Standard (FIPS) mode enabled. Please note that PRTG still does not support the FIPS mode on Windows systems running the PRTG core server or probe service. |
API |
It is not possible anymore to perform certain actions via API calls without having according user rights. Thanks to Positive Technologies for reporting the issue! (CVE-2018-19411) |
Sensors |
Passwords in debug files will not appear in clear text anymore when you enable the option to write the sensor result to disk. |
Auto-Discovery |
It is possible again to start an auto-discovery on multiple devices in the device list. The option Run Auto-Discovery is now available in the multi-edit context menu. |
Desktop Notifications |
We fixed an issue where desktop notifications did not work when they were temporarily disabled and the last saved alarm count was great than the new count. Also note that Google Chrome requires HTTPS to use desktop notifications since one of its latest updates, so please switch the PRTG web server to SSL if you enable desktop notifications. |
Geo Maps |
In certain cases, Geo Maps were not correctly displayed but shown as JSON code or not at all. We fixed this issue. |
Graphs |
Graphs throughout the PRTG web interface are now better readable. This especially affects colors as well as transparency. For example, the Primary Channel of a sensor is more clearly visible again. Also Maps benefit from these improvements. |
Libraries |
It was mistakenly possible to switch the device tree view on the Management tab of a library. We removed the option. The device tree on this library tab has the default size M. |
Main Menu Structure |
We have removed the entry Tickets | All from the main menu bar. |
Maps |
Previews of graph map objects are displayed again. |
Mobile View |
We fixed an issue with scrolling in the mobile view. |
Reports |
Faster rendering of very long reports |
Search |
Performance improvements for the device tree search. PRTG will show you search results in the device tree much quicker than before. We also fixed some issues with the advanced search. |
Tables |
Several improvements and fixes for the display of tables (both data tables and sensor selection tables in the Add sensor dialog) in the PRTG web interface and in Maps |
Tags |
Several fixes to the usage of new tags |
Various |
Many other minor fixes and improvements to the new PRTG web interface |
API |
It is now possible to use API calls like setobjectproperty.htm on the Total channel of traffic sensors that have channel ID -1 (subid=-1). |
Clone Objects |
Cloning groups and devices that have an auto-discovery setting enabled or that currently have an auto-discovery running will not result in duplicated sensors on the new group or device anymore. |
Remote Probes |
We fixed an issue where approving remote probes resulted in timeouts when the geo location server for Geo Maps was not reached. In certain cases, the PRTG web interface was frozen or the PRTG core server was not reachable when this happened. |
All Parts of PRTG |
Various other fixes and improvements, updated user manual, updated language files. |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
EXE Sensors |
Sensor types that use EXE files for monitoring did not correctly handle invalid JSON and XML responses. We fixed this issue. |
Windows Updates Status (Powershell) |
The auto-discovery added Windows Updates Status (Powershell) sensors to devices that do not run Windows. Because this was not a good idea, we changed the according device template to add sensors of this type only to Windows devices. |
PRTG Web Interface |
We fixed some more issues with the new PRTG web interface, for example:
|
PRTG Core Server |
In certain cases, the PRTG server did not start after the installation of updates or after installing a new PRTG instance. We fixed this issue. |
SNMP Library |
This version includes several fixes for the SNMP Library sensor. The sensor correctly uses the Scale (multiplication and division) from the imported OIDLIB again to show expected values. Custom units are imported and displayed correctly again. |
By Sascha Neumeier • Feb 27, 2018
REST Dell EMC BETA |
We added 5 new sensor types that enable you to monitor your Dell EMC storage systems out of the box! The sensors use the REST API of Dell EMC devices to show you health status and other important measurements of your Dell EMC storage components. PRTG 18.1.37 comes with the following Dell EMC sensors:
|
Exchange Backup (Powershell) |
Stability improvements for the Exchange Backup (Powershell) sensor. It also includes two new channels that show the passed time since the last differential backup and since the last incremental backup. After the update to PRTG 18.1.37, please create your Exchange Backup (Powershell) sensors anew. Existing sensors of this type might show incorrect data! |
Exchange Public Folder (Powershell) |
The Exchange Public Folder (Powershell) sensor can now monitor subfolders. After the update to PRTG 18.1.37, you must create all Exchange Public Folder (Powershell) sensors anew. Existing sensors of this type will stop working! |
Exchange (Powershell) |
Stability improvements for all Exchange (Powershell) sensors. Note: The Execution Time channel of running Exchange (Powershell) sensors will not show any data after the update to PRTG 18.1.37 and will be completely removed in future versions. It was still available in some older running Exchange sensors. |
NetApp LIF |
The NetApp LIF sensor has a new channel Is home that shows if the logical interface is at the home port. |
NetFlow V9 and IPFIX |
Performance improvements for NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors |
SNMP QNAP Logical Disk |
The SNMP QNAP Logical Disk sensor has a new lookup status Synchronizing in channel Volume Status that maps to the sensor status warning. |
Date Format |
We added the date format YYYY-MM-DD HH:MM:SS to make more people feel at home when using PRTG. You can choose your preferred date format in your PRTG user account settings. |
Business Process |
Adding objects to channels in the Business Process Specific Settings works again. |
Cloud HTTP and Cloud Ping |
Cloud HTTP and Cloud Ping sensors now use the Proxy Settings for HTTP Sensors from the parent device (or inherited from other objects higher in the hierarchy). In previous versions the sensors used the proxy configuration for Core & Probes as defined in the PRTG System Administration. |
Common SaaS |
The Common SaaS sensor is now available when filtering for Cloud Services in the Add Sensor dialog. |
FTP Server File Count |
We added passive connection mode support to the FTP Server File Count sensor. You can choose the required FTP Mode in the sensor settings. |
HTTP Push Sensors |
Stability improvements for HTTP Push sensors (HTTP Push Count, HTTP Push Data, HTTP Push Data Advanced) |
Hyper-V Virtual Machine |
The Hyper-V Virtual Machine sensor shows more expressive error messages in case of sensor failures. |
NetApp NIC |
The NetApp NIC sensor can now monitor all physical and logical ports on any node in your NetApp cluster and correctly provides all available monitoring items in the Add Sensor dialog. |
NetApp Sensors |
In certain cases, NetApp sensors for cDOT and ONTAP storage systems failed because of corrupted cache files. We fixed this issue. |
NetFlow V9 and IPFIX |
In certain cases, NetFlow V9 and IPFIX sensors could not collect data. We fixed this issue. |
Probe Health |
The Probe Health sensor will now reset the error message for the Data Storage Free channel when the disk has enough space again. |
REST Custom |
Some more fixes and improvements for the REST Custom BETA sensor, including support for Boolean values |
SNMP Custom sensors |
We changed the naming of the Value Type options of SNMP Custom, SNMP Custom Advanced, and SNMP Custom Table sensors. This will make it clearer what value type you have to choose, absolute or delta values. |
SNMP Traffic |
In certain cases, SNMP Traffic sensors showed access violation errors. We fixed this issue. |
SSL Certificate |
The SSL Certificate sensor now correctly categorizes the key length of ECC certificates in case of compressed coordinates. If you have changed the lookup file to manually avoid issues with the key length of ECC certificates, please choose the original lookup file again after the update. For details, please see this Knowledge Base article: SSL Certificate Sensors and ECC Certificates: Fix for Public Key Length Monitoring |
VMware Sensors |
VMware sensors support TLS 1.2 only connections if required by the target VMware host. |
VMware Virtual MAchine (SOAP) |
If you create a device template that includes a VMware Virtual Machine (SOAP) sensor and run an auto-discovery with the template, discovered VMware Virtual Machine (SOAP) sensors will now have a correct sensor name (was erroneously "Host Performance" in previous versions) and correctly take the Handling of "Powered Off" VM setting. |
Windows Updates Status (Powershell) |
You can add Windows Updates Status (Powershell) sensors via Auto-Discovery again. |
WSUS Statistics |
The WSUS Statistics sensor can handle untrusted certificates when using SSL to connect to the WSUS server. |
Sensor Channels |
Decimal places were not correctly displayed in certain cases, for example when decimal places were set to Automatic in the sensor channel settings with a Custom unit and no custom unit string. We fixed this issue. |
Various Sensors |
In newly created sensors you must select the Value Type "Integer" to use a lookup because lookups only properly work with integer values. This was not validated in previous versions and lead to inconsistencies. This change affects the sensor types ADO SQL v2, Google Analytics, MySQL v2, Microsoft SQL v2, SNMP Custom Advanced, SNMP Custom Table. |
PRTG Web Interface |
We fixed various issues with the new PRTG web interface and further improved usage and appearance.
|
Memory Leak |
We fixed a memory leak caused by historic data graphs. |
Auto-Discovery |
The History tab of a device or sensor now correctly shows the PRTG user account who started an Auto-Discovery that created a sensor. |
PRTG Core Server |
In certain cases, the PRTG server did not start after the installation of updates or after installing a new PRTG instance. We fixed this issue. |
Reports |
The last day of a report time span was not included in the report if you changed the start date without editing the end date. We fixed this issue, the day of the defined end date will now also be included in the report in such cases. |
Stability |
|
Maps |
It is not possible anymore to create objects like maps with a PRTG read-only user account (CVE-2017-15917). |
Debug Files |
All passwords in debug and log files are now masked. This affects, for example, passwords in files that sensors create when you enable the option "Write sensor result to disk" in sensor settings. |
Libraries |
Libraries and the Management tab of libraries can be viewed again in the Enterprise Console. The pages did not correctly load in the previous PRTG version. |
All Parts of PRTG |
Various other fixes and improvements, updated user manual, updated language files |
PRTG Web Interface |
This version includes some more fixes and improvements for the new PRTG web interface, among others:
|
Exchange (Powershell) Sensors |
Exchange (Powershell) sensors work on Exchange Server 2010 again. |
Exchange Backup (Powershell) |
The Exchange Backup (Powershell) sensor will now warn you if there was no backup performed instead of showing an up status. |
All Parts of PRTG |
Some other minor fixes |
PRTG Web Interface |
We already received a lot of feedback for the new PRTG web interface that we released with PRTG version 17.4.35. Your feedback has been quite helpful so far, so we can provide many fixes and improvements for it in PRTG version 17.4.36— the new web interface gets better and better, thanks to you! The fixes include, among others:
|
Common SaaS |
The Common SaaS sensor now uses the Proxy Settings for HTTP Sensors from the parent device (or inherited from other objects higher in the hierarchy). In previous versions the sensor used the proxy configuration for Core & Probes as defined in the PRTG System Administration. |
Exchange Database DAG (Powershell) |
The Exchange Database DAG (Powershell) sensor is now compatible with the Cumulative Update 4 for Exchange Server 2016 (Exchange 2016 CU4). |
Exchange Public Folder (Powershell) |
The Exchange Public Folder (Powershell) sensors now supports Microsoft Exchange Server 2013 and Microsoft Exchange Server 2016. |
Hyper-V Cluster Shared Volume Disk Free |
The Hyper-V Cluster Shared Volume Disk Free sensor supports UTF-8 characters in volume names, including German umlauts. In previous versions, the sensor could not monitor volumes with umlauts in their name. |
NetApp LUN |
The Bytes free % channel now shows correct values. |
NetApp Volume |
The NetApp Volume sensor now properly handles more than 20 snapshots. In previous versions, the sensor showed a wrong number of snapshots and wrong values for the oldest and newest snapshot age channels if there were more than 20 snapshots. |
Share Disk Free |
The Share Disk Free sensor now correctly calculates free disk space on a share. In some cases, the sensor used the free disk space of a whole disk instead of only the share to calculate free space, which resulted in values greater than 100% free disk space, for example. |
SNMP Traffic and SNMP RMON |
When monitoring certain devices (for example, Fortinet FortiSwitch) with SNMP Traffic or SNMP RMON sensors, the automatic sensor name update (if set in the SNMP Compatibility Options) caused a sensor error in the last PRTG version. We fixed this issue. |
SSL Certificate |
Fix for the Certificate Name Validation of the SSL Certificate sensor: In certain cases, the sensor check failed although CN/SAN matched the SNI. |
Windows Updates Status (Powershell) |
Stability improvements for the Windows Updates Status (Powershell) sensor |
PRTG Core Server Service |
In rare cases when running a PRTG update, the PRTG Core Server service got removed and could not be installed again. We fixed this issue. |
Reports |
Double quotes in report names resulted in timeouts while PDF creation in some cases. We fixed this issue. |
System Information |
We fixed an exception that was caused when a vendor was not available for a Software table entry. |
Tickets and Auto-Discovery |
PRTG will now only create one ticket for a completed auto-discovery when at least one new device or sensor has been discovered. |
Amazon SNS Notifications |
The AWS Secret Access Key for Amazon Simple Notification Service notifications is not readable anymore in the PRTG web interface. |
Maps |
We added a check for the file format of background images that you can upload for maps. It is only possible to use the file formats .jpg, .png, and .gif for background images. |
Cluster |
Access keys for remote probes will be automatically synchronized on all cluster nodes for both newly installed remote probes and removed remote probes. |
Installation |
We fixed a small issue affecting the installation of a remote probe via the context menu in the device tree. |
All Parts of PRTG |
Various other fixes and improvements, as well as an updated user manual |
PRTG Web Interface |
Major improvements to the new PRTG web interface! We implemented a lot of your feedback to give you an even better experience with PRTG. |
NetApp LUN |
The NetApp LUN sensor has a new channel Mapped that shows whether the LUN is mapped or not. |
NetApp Volume |
We added 8 new channels to the NetApp Volume sensor for a even more detailed view on your NetApp storage system:
Important: Because of required changes to the volume detection approach of this beta sensor, existing instances of the NetApp Volume sensor will stop working after updating to this PRTG version. Please add your NetApp Volume sensors anew. To keep monitoring data of existing NetApp Volume sensors, you can pause them. It is also not possible anymore to add sensors for volumes that are offline. |
REST Custom |
The REST Custom sensor now uses JSONPath in the REST configuration file to map the retrieved JSON into sensor channels and values. To reflect this change, names of REST configuration files now have the ending .template instead of .json. Please consider this when adding new REST configuration files to PRTG. We also implemented some fixes and improvements for this beta sensor. Note: Existing REST configuration files using the outdated JSON format (.json files) will continue to work after updating to this version, but please be aware that they will not be compatible with PRTG versions in the near future. We recommend that you convert existing REST configuration files to .template files using JSONPath as soon as possible. |
Geo Maps |
This version includes another fix for Geo Maps. |
SNMP Sensors |
Some customers have experienced issues with SNMP sensors in this PRTG version. These issues might result in a damaged PRTG configuration file. We will provide a fixed version as soon as possible. |
NetApp SnapMirror |
We are further enhancing the NetApp monitoring capabilities of PRTG: You are now able to monitor SnapMirror relationships with PRTG and the new NetApp SnapMirror sensor! The sensor accesses the NetApp API via SOAP and supports the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3. Always see the health and relationship status of a SnapMirror, the relationship type (mirror and vault), the mirror state, and important parameters about SnapMirror transfers and failures. This is really great news for all NetApp customers! |
Adding Sensors |
We improved the PRTG internal sensor creation process to speed up things. You will especially benefit from this improvement when adding many sensors at once. This is the case, for example, when sensor types scan for available monitoring items on the target device before the sensors are actually created (meta-scan). PRTG will now create the sensors in background tasks and show the progress to keep you informed—you don't have to wait anymore for the sensors and can continue your business. |
SNMP Library |
We considerably improved the way PRTG creates SNMP Library sensors from an imported MIB (OIDLIB)! When you add the SNMP Library sensor, it will now automatically create SNMP Custom Advanced sensors with up to 10 channels for single values returned by OIDs, SNMP Custom Table sensors with up to 10 channels for returned table rows, and SNMP Custom String sensors for OIDs that return string values instead of creating a lot of single value SNMP Library sensors. This makes adding custom sensors much easier, because you do not have to enter the OIDs manually to start monitoring but just select desired items from an OIDLIB in the PRTG web interface. With the SNMP Library sensor switching to automatically create custom table and advanced sensors, we also eased the process of creating device templates that include custom SNMP sensors. And that's not all: The created sensors will also take the descriptions of used OIDs and add them to the according sensors' Comments tabs. |
SNMP Dell PowerEdge Physical Disk |
We added some new states to the Disk State channel of the SNMP Dell PowerEdge Physical Disk sensor to cover all states returned by the target device. |
System Information |
System Information via SNMP returns more data for the tables System, Processes, and Hardware from a wide variety of Linux machines and a lot of generic network devices. |
Czech Language File |
We removed the Czech language file from PRTG. Existing PRTG installations that use the Czech language file will switch to English after the update to this version. |
Data |
We fixed an issue that occasionally caused missing monitoring data in sensors and empty sensor messages after a PRTG server restart. |
Device Templates |
The device template Buffalo TeraStation NAS now also works in Spanish language versions of PRTG. |
Email Delivery |
We have removed an internal comment part in emails to prevent security software from classifying emails from PRTG as insecure (of course, PRTG will never send you insecure emails!). |
License |
Stability improvements for the PRTG licensing system |
Schedules |
Changing and assigning schedules works more reliably. |
Security |
We fixed two minor potential security issues. |
Folder |
The Change Trigger for notifications of the Folder sensor is working again. |
SNMP Printer |
The SNMP Printer sensor will now correctly interpret negative values as well as 0 values returned by the printer. Such values resulted in unintended sensor warnings and errors in some cases. |
SNMP Traffic |
Some devices have a blank interface description in SNMP v1 (empty ifDescr and ifAlias), so the SNMP Traffic sensor was not able to use the description of such devices for the sensor name. The SNMP Traffic sensor will now take values from SNMP v2 ifXName in this case to avoid an empty name. |
SSL Certificate |
The SSL Certificate sensor comes with predefined limits for the Days of Expiration channel again. PRTG will warn you if your certificate expires in 28 days (keep in mind: it will not warn you about other, even worse "28 days later" scenarios) and show a down status if there are less than 7 days left. |
Windows Updates Status |
Passwords will not be logged in clear text anymore when using the Windows Updates Status (Powershell) sensor. |
WMI Sensors |
Values with data type UInt32 or UInt64 were not converted correctly when monitoring via WMI and resulted in an integer overflow in certain cases. We fixed this issue. |
Device Tree |
Deleting objects while the Auto-Discovery was running on the deleted object resulted in an inconsistent or empty device tree in some cases. We fixed this issue. |
Graphs |
|
Memory Leaks |
We fixed two memory leaks, one caused by Geo Maps, one caused by data tables. |
Various |
Various other fixes and improvements, updated user manual, updated language files |
REST Custom |
The REST Custom BETA sensor now works properly on 32-bit builds and on cloud probes. |
Reports |
In certain cases, CSV report files could not be generated properly. We fixed this issue. |
Geo Maps |
We have fixed the issue with Geo Maps. PRTG now uses HERE Maps as provider so you are able to correctly view Geo Maps again. |
Probe Connection |
Occasionally, probes could not successfully connect to the PRTG core server. This happened when the .NET requirement (.NET 4.5 or later) was not fulfilled. We have fixed this issue. |
REST Custom |
Several fixes and stability improvements for the REST Custom BETA sensor. |
SNMP Cisco System Health |
Custom tags for SNMP Cisco System Health sensors in device templates will now be added to the deployed sensors when running the auto-discovery. In previous versions, the tags have been overridden by default tags. |
SNMP Library |
In certain cases, using the SNMP Library sensor with an imported OID library that contained strings resulted in a huge PRTG configuration file. We have fixed this issue. |
SNMP SonicWALL VPN Traffic |
When running an auto-discovery with a template that contains a SNMP SonicWALL VPN Traffic sensor, PRTG will now always use the identification method for connections defined in the sensor settings. In previous versions, the sensor erroneously used "By index" in certain cases, which resulted in multiple re-added sensors for the same connection. |
Report Graphs |
When adding a sensor to a report multiple times, the graphs in the report did not show any data. We fixed this issue. |
API |
The API call /api/table.xml?content=sensortree now returns the correct lastvalue_raw. Raw data differed from the correct value by factor 10. |
Schedules |
We fixed an issue with schedules in timezones without daylight saving time. Schedules will now also correctly work in such timezones. |
Tickets and Auto-Discovery |
When running an auto-discovery on group level, PRTG will now only create one ticket for the complete auto-discovery. In previous versions, PRTG was a bit chatty and created a ticket for each detected device. |
All Parts of PRTG |
Various minor fixes and improvements, updated user manual |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
WebGUI |
Completely revised and updated look&feel of the PRTG web interface! The new, modern PRTG web interface comes with a cleaner look and many improvements to the usability. You will now find what you need more easily!
|
EXE-based Sensors |
All sensor types that require the .NET framework will need .NET version 4.5, 4.6, or 4.7 on your PRTG server and on all computers running a probe after installing PRTG version 17.3.34. By default, required .NET versions are included in Windows 8 or later and Windows Server 2012 or later. For details, see the Knowledge Base. |
File Lists |
We refined the change from the last PRTG version 17.3.33 and made the handling of file lists in the web interface more comfortable. File lists will now automatically refresh as soon as you open the according page in PRTG to immediately display newly added files like SNMP libraries, device icons, or report templates. Manually reloading file lists will not be necessary anymore in most cases, but if you have to do so for some reason, you can use the (partly) new Load Lookups and File Lists option under Setup | System Administration | Administrative Tools. |
Security |
This version includes general security enhancements for PRTG and the configuration file. |
HTTP XML/REST Value |
We added TLS 1.2 support for the HTTP XML/REST Value sensor. Because this improvement makes the "SSLv3 Connection" setting obsolete, we removed it from the sensor settings. We also fixed a possible stack overflow caused by this sensor. |
SNMP HP ProLiant Physical Disk |
We added two new states to the Disk Status channel of the SNMP HP ProLiant Physical Disk sensor: SSD Wear Out and Not Authenticated |
Security |
We have fixed a possible XSS vulnerability (CVE-2017-12879). |
Amazon CloudWatch SNS |
You can add Amazon CloudWatch SNS sensors again. Previously, when trying to add the sensor, it showed the error message "Could not create the sensor Amazon CloudWatch SNS BETA on device Amazon SNS (8.8.8.8). Operation (ListPlatformApplications) is not supported in this region". |
Docker Container Status |
If you have defined another port than the default port 2376 to connect to Docker, the Docker Container Status sensor will now really use this port. In previous versions, the port was erroneously reset to default. |
NetApp System Health |
The NetApp System Health sensor will now correctly handle partitioned spare disks and not only show 0 GB. |
Various Sensors |
In previous preview versions 17.3.33.2559 and 17.3.33.2599, "last value" in tables and API calls was empty when the sensor was down due to a breached limit. |
Geo Maps |
When you change geo locations for objects in the device tree, Geo Maps will accordingly update and show the defined location again. |
Stability |
Stability improvements for the PRTG core server and probe system |
NetApp System Health |
The NetApp System Health sensor now shows the correct number of spare disks even if the NetApp reports low spare disks. With this fix we also introduced a new sensor channel that shows when spare disks are low. Additionally, the usable spare size channel will now report the correct value and not just 0 if there are disk partitions. |
Enterprise Console and PRTG for iOS |
In the last PRTG preview release, the Save button was missing on various pages in the PRTG Enterprise Console and in the iOS app. We have found it again in the latest preview version 17.3.33.2599. |
NetApp Sensors |
We have added 8 brand new sensor types for your NetApp monitoring! Set up a complete monitoring of your NetApp cDOT or ONTAP storage system with these sensor types:
Note: The sensor types NetApp cDOT Aggregate (SOAP), NetApp cDOT I/O (SOAP), NetApp cDOT Physical Disk (SOAP), and NetApp System Health (SOAP) are now deprecated. If you have running instances of these sensor types, they will be automatically replaced by according new NetApp sensors after updating PRTG. Usually, monitoring with affected sensors will seamlessly continue. If you run into any issues with the migration path for outdated NetApp sensors, please manually add desired NetApp sensors anew. |
REST Custom |
The new REST Custom sensor can monitor almost everything! This sensor is a really powerful tool and gives you the possibilities to go far beyond standard monitoring: you can now query any REST API that returns JSON or XML and map the results into sensor channels. Define your own mapping rules in a dedicated REST configuration file using JSON! It just has to follow the PRTG API specification for the JSON return format.
We deliver various REST configuration files for this sensor by default, so you can immediately see and try out what might be possible with your own REST Custom sensor. You can find the samples in the \Custom Sensors\rest folder in the PRTG program directory, including mappings for the REST APIs of KEMP load balancers, Weather Underground, Docker containers, and PRTG itself, ready-to-use for the sensor. And the REST Custom sensor is also smart: you do not necessarily have to write a REST configuration file in JSON format to get sensor values when querying some REST endpoint. The sensor comes with an automatic detection feature for JSON or XML responses and creates suitable channels on its own! Choose channelDiscovery as REST Configuration setting of the sensor and it will parse the JSON or XML response of the REST query to automatically create channels for all available number and boolean values (including strings if convertible into numbers). You have some cool idea for this sensor or have already implemented a REST configuration file? Great, let us know if you want to share it! |
File Lists |
If you manually add files to the PRTG program directory on the core server while PRTG is running, you now have to manually reload the file lists to immediately show new files in the web interface. For this purpose, use the new Reload File Lists option under Setup | System Administration | Administrative Tools in the PRTG web interface. This change affects these file lists:
Note: These lists will still be automatically updated after 1 hour and after a server restart. If you save new device templates via the web interface, the template list will be refreshed immediately. |
Amazon CloudWatch Sensors |
We have added the region EU (London) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors. |
Amazon SNS Messages |
You can use new locations for the notification method Amazon Simple Notification Service Message: US West (Ohio), Canada (Central), EU (London), Asia Pacific (Seoul), Asia Pacific (Mumbai) |
SMTP Delivery |
SMTP delivery for email notifications now supports TLS V1.1 and TLS V1.2. |
Exchange PowerShell Sensors |
We have fixed a bug in Exchange PowerShell sensors: they will now show a correct error message instead of a NullReferenceException. |
Sensor Factory |
We have fixed a bug that sometimes resulted in incorrect historic data graphs of the Sensor Factory sensor if you set the "use zero as source value" option for missing sensor data. |
SIP Options Ping |
The SIP Options Ping sensor now recognizes all returned status codes and shows the correct status. |
SNMP Custom and SNMP Custom Advanced |
We have fixed a bug that caused a lowercase conversion of strings in OIDs requested by SNMP Custom and SNMP Custom Advanced sensors. This bug resulted in broken OIDs and so prevented the sensors from finding instances (error message: "No such instance"). |
SNMP NetApp Sensors |
We have fixed a bug in the NetApp device template that resulted in an interrupted auto-discovery. |
SNMP Traffic |
|
Windows Updates Status (Powershell) |
The Windows Updates Status (Powershell) supports the Windows 10 Creators update. It now requires at least .NET 4.5 on the probe system and PowerShell 3.0 on both the probe system and target system. |
WMI Sensors |
Stability improvements for WMI multi-query sensors, for example, the Windows Physical Disk I/O sensor |
Server Stability |
In rare cases, the PRTG server performed an unexpected restart because of a deadlock event when scheduling reports. We have fixed this potential deadlock cause. |
Device Templates |
When you create a device template, the object setting When a Sensor Reports an Error in the Scanning Interval section will now be stored in the new template. |
Email Notifications |
We have fixed some broken links in email notifications. |
Notification Trigger |
Changing the internal type of a sensor's down status (down due to limits or scan error) will not prevent PRTG from sending notifications anymore.The notification trigger was not provoked in rare cases because the internal status change (from down by scan error to down by limit to down by scan error) has reset the trigger timer. |
Various |
Various minor fixes and improvements, updated user manual, updated language files |
Common SaaS |
The Common SaaS sensor can check Bing again. Microsoft has deprecated the used URL so you might have seen the sensor message Bing API not available. We have fixed this issue. |
Dell PowerVault MDi Logical Disk |
The Dell PowerVault MDi Logical Disk sensor will now show all available disks on a PowerVault system when adding the sensor. We have fixed a small bug that prevented the sensor from finding all disks during the metascan. |
DHCP |
We have fixed a bug where an overflow could prevent the DHCP sensor from showing the correct results. |
Folder |
We have improved the stability of the Folder sensor when monitoring folders that contain a large number of files and added a proper timeout handling for folder scans. For debugging purposes, the sensor now also provides the option to write the sensor result to disk. |
HTTP Sensors |
HTTPS POST requests with NTLM authentication work again. |
NetFlow |
We have fixed an issue that caused missing data for NetFlow sensors. |
PostgreSQL |
We have fixed an encoding issue to correctly display PostgreSQL sensor error messages. |
Sensor Factory |
If a Sensor Factory sensor included source sensors with delay (like xFlow and Packet Sniffer sensors) and the option use zero as source value was enabled for the setting If a Sensor Has No Data, the Sensor Factory only showed 0 values. We have fixed this behavior. |
sFlow |
Data graphs of the sFlow and sFlow (Custom) sensors showed gaps in certain cases because of wrong assignments to scanning intervals. This was caused by a workaround for buggy target devices that we have implemented in a previous PRTG version. We have fixed this behavior. |
SMTP&IMAP and SMTP&POP3 Round Trip Sensors |
We have fixed a small security issue: passwords in logfiles of SMTP&IMAP Round Trip and SMTP&POP3 Round Trip sensors are now masked when authentication is enabled. |
SNMP Cisco UCS System Health |
We have removed the 'failure predicted' channels from the SNMP Cisco UCS System Health sensor:
Note: Sensors of this type that have already existed before updating to this PRTG version will not show values in these channels anymore. Please add the sensor anew to avoid empty channels. For details, please see this Knowledge Base article: Why are some SNMP Cisco UCS System Health sensor channels not showing any information anymore? |
SNMP HP ProLiant Network Interface |
We have fixed an issue with 0 bytes that resulted in error The network adapter with mac address [mac] could not be found (code: PE157) when using the SNMP HP ProLiant Network Interface sensor. |
SQLv2 Sensors |
|
SSH Script and SSH Script Advanced Sensors |
Security fix for SSH Script and SSH Script Advanced sensors: we have improved the parameter check for SSH script sensors. |
Syslog Receiver |
Summarized email notifications triggered by Syslog Receiver sensors showed a broken header. We have fixed this issue. |
VMware (SOAP) Sensors |
We have fixed a timeout bug that occurred in certain cases when adding a VMware (SOAP) sensor. |
VMware Datastore (SOAP) |
In PRTG language versions other than English, the VMware Datasore (SOAP) sensor created the Free Space channel twice while one of these channels (the one with the name in the selected language) did not show any data. We have fixed this issue. If you use another language version than English, please add running sensors of this type anew after updating to this version to benefit from the fix. |
WMI Vital System Data (V2) |
We have removed the option to add a WMI Vital System Data (V2) sensor for CLR Memory: % Time in GC because the returned value appeared to be meaningless. |
SMS Notifications |
PRTG will not log errors for custom SMS notifications anymore if the HTTP response of the provider is in the 200 range. This fix will also prevent PRTG from re-sending SMS notifications that already have been successfully delivered. |
Failover Nodes |
We have fixed a bug that caused objects on failover nodes to not synchronize and update in a timely manner in certain cases. |
API |
|
Various |
Various minor fixes and improvements, updated user manual, updated language files |
Default Login |
We have removed the Default Login button. If you use the default credentials of PRTG, the login fields are now pre-filled:
|
Create Device Template |
PRTG will now show the names of the sensors that were added to a device template as result of the Create Device Template function. |
Amazon CloudWatch |
We have added the region Canada (Central) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors. You can now monitor all your instances in Canada (Central)! |
HTTP Data Advanced |
We have added advanced options to the HTTP Data Advanced sensor: you can now specify the protocol version (HTTP 1.0 or HTTP 1.1), define the user agent, and use custom HTTP headers. |
HTTP Push |
HTTP Push Count, HTTP Push Data, and HTTP Push Data Advanced sensors support TLS 1.2 encryption (lower TLS/SSL versions are not supported). |
Business Process |
Searching by object ID when defining channels for the Business Process sensor works better now. |
SSH Disk Free |
The SSH Disk Free sensor can show up to 100 channels (99 partitions). Previously, the default limit for channels applied so the sensor only added up to 50 channels. |
Installer |
When installing or updating PRTG, the installer will not start the PRTG core and probe services anymore if a reboot of the computer is required. This fix prevents inconsistent file states and according errors. |
Various |
Various minor fixes and improvements, updated user manual, updated language files |
PDF Reports |
Creating PDF reports works again. |
Buffalo Device Template |
The Buffalo device template works properly again and does not discover too much anymore. |
SNMP Custom Table |
You can add the SNMP Custom Table sensor again. |
SQL Sensors |
Comments with a # in the query do not cause an error anymore. |
Historic Data Reports |
We have fixed a bug where short outages were not correctly recognized as downtime in historic data reports. |
Windows Sensors |
Windows sensors on new PRTG installations will now use WMI only as Preferred Data Source by default (see the Windows Compatibility Options in the device settings) to query monitoring data instead of the hybrid approach (Windows Performance Counters as default, WMI as fallback). The latest major performance and stability improvements for WMI sensors with PRTG version 17.1.28.1341 have such a positive effect on your monitoring experience, so we recommend that you keep the new default setting! Note: This update does not automatically migrate the setting on existing PRTG installations. If you encounter issues with Windows sensors that use Performance Counters by default, please manually change to WMI only as Preferred Data Source. |
Active Directory Replication Errors |
Adding the Active Directory Replications Errors sensor to device templates now works. |
Event Log (Windows API) and WMI Event Log |
The Event Log (Windows API) sensor and the WMI Event Log sensor support up to 2,000 characters in the message. Previously, the message was cut off after 1,024 characters. |
HTTP Push Sensors |
HTTP Push sensors now clear error PE206 if the set port is available again and show the correct status. In previous versions the HTTP Push sensors never came back if the port was blocked once. |
SNMP Custom String |
The SNMP Custom String sensor can now show backslashes (\) in the sensor message. |
SNMP Custom Table |
Creating a device template including several SNMP Custom Table sensors and running the auto-discovery with this template works more reliably. PRTG will now create sensors for all available entries in the SNMP table. We have also fixed a PE247 error that occurred in some cases in the previous PRTG version when auto-discovering SNMP Custom Table sensors. |
SNMP HP ProLiant Network Interface |
The SNMP HP ProLiant Network Interface sensor now also works if there are 0 bytes in the MAC address of the target interface. The error message in this case was: "The network adapter with mac address [mac] could not be found (code: PE157)" |
VMware Datastore (SOAP) |
The VMware Datastore (SOAP) sensor now has predefined channel limits to automatically warn you if your disk is running full. If this change does not apply to your scenario (because of thin provisioning, for example), please adjust the limits in the channel settings. |
Windows Updates Status (Powershell) |
Channel names of the Windows Updates Status (Powershell) sensor are now more appropriate and show the correct severity for updates. We have also added new sensor channels for hidden updates. |
API |
The API call for historic data provides correct raw values again. |
PhantomJS |
We have updated PhantomJS to the current version. PRTG uses PhantomJS to generate PDF reports and screenshots for the HTTP Full Web Page sensor and support bundles. This update will improve and fix some smaller issues regarding these functionalities. |
Schedules |
PRTG will now validate the syntax of period lists for schedules to prevent access violations and resulting failures when starting the PRTG server. |
Security |
We have fixed a small security issue that could result in an access violation showing passwords in clear text in certain cases. |
Uptime Threshold |
In certain cases, the uptime threshold in the Monitoring settings reverted to the default value after a PRTG server restart. PRTG will now keep your individually set desired minimum uptime. |
Cluster |
"Check Now" on failover nodes works again. In previous versions, the action was only executed on the master node. |
All Parts of PRTG |
Various fixes and improvements to all parts of PRTG, including more performance improvements |
Manual Update |
Updated user manual |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
Push Notifications |
Push notifications in PRTG freeware versions work again. PRTG did not send them out anymore after the trial period has expired. |
Citrix XenServer Sensors |
Citrix XenServer Host and Citrix XenServer Virtual Machine sensors now close their sessions on the target device to avoid potential instabilities on the XEN host. |
Custom Script Sensors |
For custom script sensors like the EXE/Script Advanced sensor, you can now provide special characters in custom unit and last message as escape sequences in the returned XML. |
NetApp cDOT Sensors |
The NetApp cDOT sensors support ONTAP 9. |
Python Script Advanced |
The Python Script Advanced sensor correctly replaces parameters again. |
sFTP Secure File Transfer Protocol |
The sFTP Secure File Transfer Protocol now supports the new SSH engine which we introduced with PRTG version 16.2.24 (May 2016). Note: You can still use the old SSH engine as legacy version by selecting the deprecated “Compatibility Mode” in the sensor or device settings, but we will remove this option soon. |
SNMP Custom String |
String search in SNMP Custom String sensor results also works for raw bytes (like MAC addresses). |
SQL Sensors |
The change trigger on the notifications tab of SQL sensors is now available. This means that you can actually use the Trigger 'change' notification setting of SQL sensors in combination with a change trigger to receive notifications if the sensor message changes. |
SSH Sensors |
We have implemented several important fixes and improvements for the default SSH engine that the SSH sensors use to retrieve monitoring data from target devices. SSH sensors will now run more stable and available options like SSH rights elevation will work more reliable. This fix also includes support for special characters (like North Germanic characters) in username and password. If an SSH sensor returns the error read_password_prompt timeout or read_paessh timeout after you have updated to PRTG 17.1.29, please check your SSH Rights Elevation settings in section Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems of the affected device. Ensure you use the setting that your target device requires and enter your password for 'sudo' or 'su' anew. See this Knowledge Base article for details: https://kb.paessler.com/en/topic/73353 |
License Activation |
Stability improvements for the changed license activation system |
Find Duplicates |
The Find Duplicates function for devices will not find false positives anymore when the last octet of the IP address has three digits. |
Maps |
Fixed a small security issue with inactive user accounts |
Tags |
Tags of notifications and schedules work again, for example, if you use these tags to filter for notifications and schedules in tables. Important: You will lose existing tags (which did not work anyway) for notifications and schedules with this update so you will have to define them anew. |
Content-Type |
Emails are now delivered with a correct Content-Type. This will help to prevent anti-spam software from blocking emails from PRTG that include PDF reports, for example. |
All Parts of PRTG |
Many other minor improvements and fixes to all parts of PRTG |
User Manual |
Updated user manual |
SNMP Buffalo TS System Health |
We are glad to present the first dedicated PRTG sensor for Buffalo storage systems with this version! The new SNMP Buffalo TS System Health sensor monitors your Buffalo TeraStation NAS and can show you important system health values like memory and CPU usage, uptime, number of errors and warnings, failover status, firmware update availability, and the RPSU status. To monitor even more data of your Buffalo TeraStation, we also deliver the new device template Buffalo TeraStation NAS. Run an auto-discovery with this template to automatically create SNMP Custom Table sensors with additional useful information, for example, array status. disk smart status, and iSCSI status. Of course, this device template will also create sensors for traffic, memory and load average on your TeraStation. |
Docker Container Status |
The Docker Container Status sensor provides the option to choose the container name as identification method instead of the container ID. In some cases, the ID of the target container changes regularly so that the name might be a better identification method to ensure seamless monitoring. |
GitLab Build Status |
Several improvements and fixes for the GitLab Build Status sensor: for example, you can identify projects and branches more easily. |
SNMP SonicWALL VPN Traffic |
The SNMP SonicWALL VPN Traffic sensors provides the option to use IP ranges as identification method for connections. |
SSH Disk Free |
When adding the SSH Disk Free sensor, you can now select up to 100 disks you want to monitor with one sensor. For the sake of stability and performance, this approach ensures that the sensor will not create too many channels. |
SSL Certificate |
The SSL Certificate sensors supports Elliptic Curve Cryptography (ECC) certificates in addition to RSA certificates. Depending on the used cryptosystem, the sensor will show suitable security ratings for the public key length. |
WMI Sensors |
Stability improvements for WMI sensors |
License Activation |
Stability improvements for the changed license activation system |
License Activation |
In this version, we have changed the technology of how PRTG servers are licensed. Most customers will not see any difference. However, as an experienced PRTG user you will notice some improvements and changes.
|
Remote Probe Install |
We considerably simplified the installation and configuration process for new remote probes! The remote probe installer will now complete almost all steps automatically. Just make sure your PRTG core server accepts incoming probe connections, download and run the installer on your remote system, approve the connection, and enjoy your new remote probe in PRTG! |
DNS |
The DNS sensor query type Host address IPv6 (AAAA) works again. This option caused the error message “Record not found (PE112)” in some cases. We also improved IPv6 parsing in general. |
EXE/Script and EXE/Script Advanced |
The JSON result parser correctly evaluates the ShowChart and ShowTable values and sets these options as returned by your script. |
Oracle Tablespace |
The Oracle Tablespace sensor now uses the identifier you have set when adding the sensor. You can also define if you want to use SERVICE_NAME as sensor name prefix to distinguish sensors for several databases on the same server more easily. |
SNMP Printer |
On some HP printer types, adding SNMP Printer sensors could lead to null byte errors in rare cases. This should not happen again. |
SSL Certificate |
The SSL Certificate sensor can now evaluate Subject Alternative Names (SAN) additionally to the Common Name (CN). Just choose the new option Compare and show 'down' status if common name/alternative names and address/SNI do not match for the Certificate Name Validation sensor setting. |
WMI Sensors |
Stability improvements for WMI sensors. Timeouts in meta-scans of WMI sensors should not result in crashes anymore. |
Core/Server |
We have fixed a load configuration error that occurred in rare cases when starting PRTG. |
Email Delivery |
Enhanced error handling in case of failed email delivery |
PDF Generation |
PRTG uses a correct fallback port now if the default PDF port 8085 is blocked at startup. |
Tree Map |
The Tree Map view refreshes automatically again. |
Maps |
Stability improvements for maps and the Map Designer |
Various |
We fixed several other minor issues in the PRTG web interface. |
Languages |
Updated language files |
User Manual |
Updated PRTG user manual |
All Parts of PRTG |
Many other minor improvements and fixes which didn’t make it on this page. |
Core/Server |
Minor security fix |
SSL Security Check |
We changed the behavior of the SSL Security Check sensor and adjusted its TLS 1.0 security rating! It will show a warning status (weak security) for accepted TLS 1.0 connections as of the previous PRTG version 16.3.26. Please see this article for more information: How do you determine the protocol security ratings of the SSL Security Check sensor? |
Removed Beta Status |
The following sensors are not in beta status anymore and are now fully supported.
|
Core/Server |
Performance and stability improvements for large PRTG installations |
Cisco IP SLA |
The Cisco IP SLA sensor shows correct values again. |
EXE/Script |
Security fix for the EXE/Script sensor |
GitLab Build Status |
Several improvements and fixes for the GitLab Build Status sensor |
NetApp cDOT |
Several improvements and fixes for the NetApp cDOT sensors |
SNMP NetApp Disk Free |
The Inodes Free channel shows correct values now. Under some conditions, this channel displayed wrong values due to an overflow in the calculation. |
Sunburst |
You can zoom in and out the sunburst view again. Additionally, you can change the position of the sunburst via drag and drop. |
Map View |
Fixed potential “line too long” errors which have occurred in some scenarios |
Various |
Several other minor fixes and improvements to all parts of PRTG, as well as an updated user manual |
Channels |
Rounding small channel values is more accurate now. |
Cisco IP SLA |
Stability improvements |
Citrix XenServer |
Citrix XenServer Host and Citrix XenServer Virtual Machine sensors support Xen7. |
HTTP Advanced |
The HTTP Advanced sensor uses correct decimal separator also in compatibility mode. |
HTTP Push |
Stability improvements for HTTP Push Count, HTTP Push Data, and HTTP Push Data Advanced sensors. |
HTTP Transaction |
The HTTP Transaction sensor now sets the correct status derived from the keyword check. |
Hyper-V Cluster Shared Vol. Disk Free |
Stability improvements |
NetFlow Sensors |
NetFlow sensors now support flow traffic from ASA version 9.1 and higher. |
Python Script Advanced |
Security fix for the Python Script Advanced sensor |
SNMP Cisco System Health |
The SNMP Cisco System Health sensor shows correct values which match the values from the target device. |
SNMP Dell EqualLogic Logical Disk |
The SNMP Dell EqualLogic Logical Disk sensor finds now also volumes without assigned groups/members. |
SQL v2 |
SQL v2 sensors support whitespaces and tabulators in declare queries. In the sensor message of SQL v2 sensors, the placeholder {0} is replaced by the defined table value again and will not just return "Ok". |
SSH INodes Free |
The SSH INodes Free sensor shows now an error message instead of 0% in case of an error. |
Windows Physical Disk I/O and WMI Logical Disk I/O |
Both sensor types now show decimal places. The unit of the channel values has changed to ms to receive more detailed values. Please add the sensor anew to see this change. |
Config |
Stability improvements for the configuration file. In certain cases, the PRTG server could not start because of NULL bytes in the config. |
Tickets |
PRTG will now check the ticket database on startup and once a day, try to repair it if it is corrupted, and tell you about such an event. |
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
All Parts of PRTG |
Many other minor improvements and fixes to all parts of PRTG! |
SSL Security Check |
We changed the behavior of the SSL Security Check sensor and adjusted its TLS 1.0 security rating! It will show a warning status (weak security) for accepted TLS 1.0 connections as of this version. |
GitLab Build Status |
The new GitLab Build Status BETA sensor monitors the status of the latest build on one specific branch. You can monitor your builds in either your own GitLab environment or on GitLab.com! |
WMI Microsoft SQL 2016 |
You can now use the new WMI Microsoft SQL Server 2016 sensor to monitor the performance of your MS SQL Server 2016 instance! |
Logout Countdown |
If you have defined an automatic logout from the PRTG web interface for PRTG user accounts because of inactivity, the logout countdown appears now with a nice graphical display one minute before the actual logout. |
Map Designer |
You can now undo and redo up to 50 changes when working on a map. Changes are saved persistently in your configuration, so you can even revert changes later. |
Public Maps |
You can now disable links on public maps with a dedicated maps setting. |
Amazon CloudWatch |
Amazon CloudWatch sensors include the AWS region Asia Pacific (Mumbai). |
Folder |
We improved the sensor usability: The down and warning states for the file age check are now based on channel limits so the sensor will still receive data if this check fails by definition. You can still define the setting for the file age check when adding the sensor, but for existing sensors please use channel limits. |
IMAP |
We changed the way settings look like for a better understanding of their functionalities. Note that we did not change any functionality. |
Meta-Scans |
As an advanced PRTG user, you can now write your own generic meta-scan for any sensor type. For details, please see this article: https://kb.paessler.com/en/topic/70882 |
SSL Certificate |
The SSL Certificate sensor supports SOCKS5 proxy. We also improved the certificate validation and the sensor shows Common Name and certificate thumbprint in the sensor message. |
SSL Security Check |
The SSL Security Check sensor supports SOCKS5 proxy. TLS 1.0 is now considered to be insecure. |
WMI Sensors |
Various performance and stability improvements for WMI sensors. |
WMI Volume |
Template support for the WMI Volume sensor. |
HTTP-based Notifications |
HTTP notifications and notifications based on custom SMS providers support SNI. |
Encryption |
Improved encryption for PRTG connections with a fallback mechanism for some sensor types to support stricter configurations which exclude TLS 1.0 entirely. |
PRTG Administration Tool |
Files are uploaded via FTPS now. |
Removed Mobile GUI |
As announced in previous versions, we have finally removed the Mobile Web GUI from PRTG. After you have updated to this version, you will not be able to access PRTG via this interface. Please see this article for details: https://kb.paessler.com/en/topic/66920 |
SNMP Trap Receiver |
Bugfix for problematic UDP messages. |
Reports |
In some configurations, graphs where missing in (historic data) reports. |
Core |
Stability improvements. |
Geo maps |
We are currently rerouting the map requests from MapQuest to Nokia Maps. |
Server |
We fixed a potential CBC cipher vulnerability (CVE-2016-2107) by disabling the AES-NI extension ("Intel Advanced Encryption Standard Instructions"). Older browsers and other clients which do not use GCM ciphers may lose performance per CBC calculation because of this fix. This fix also includes the library update to OpenSSL version 1.0.1t |
Webgui |
We fixed a potential XSS vulnerability: This XSS exploit has been only possible when accessing the PRTG web interface with Firefox. See this article for details about Firefox and security: How secure is it to access the PRTG web interface with Firefox? |
SSL Certificate |
The SSL Certificate sensor shows a down status now if "Certificate Name Validation" fails (common name check). |
SNMP Trap receiver |
SNMP Trap Receiver sensors display received trap messages with line breaks and final 0 correctly again. As before, zeros within texts will be displayed as hexcode. |
Access rights |
PRTG users with sufficient access rights can view maps correctly again. The map refresh caused an incorrect access rights error for certain PRTG user groups before. |
Stability |
Several minor fixes and improvements for probe stability and WMI |
License Names |
We changed the license name of PRTG Unlimited to PRTG XL1 and replaced the license PRTG 5 Core Global with PRTG XL5. PRTG XL1 allows an unlimited number of sensors on 1 core server installation, PRTG XL5 on 5 core servers worldwide. Please consider the PRTG system requirements for installations with many sensors. |
Performance |
Optimized pipe handling of EXE based sensors |
SSH Engine |
Fixed AV in SSH dll |
Graphs |
Historic data reports display graphs again. In certain cases PRTG used an incorrect address to load graphs. |
Cisco IP SLA |
Fixed an error that caused a down status of the Cisco IP SLA sensor in certain cases. |
HTTP Advanced |
HTTP Advanced sensor now correctly escapes quotation marks when used in the sensor settings. |
Oracle SQL v2 |
Fixed an issue caused by the connection encryption of the Oracle SQL v2 sensor. |
SNMP Custom Table |
SNMP Custom Table sensors now use the correct identification column even if you add them via auto-discovery without having an MIB available. |
SNMP SonicWALL VPN Traffic |
Fixed auto-discovery with the default device template for the SNMP SonicWALL VPN Traffic sensor. |
SNMP Synology System Health |
The SNMP Synology System Health sensor works also on target devices with missing temperature OID. |
SNMP Traffic |
Improved port name update and handling of very large traffic counters. |
SQL v2 Sensors |
SQL v2 sensors can handle float values. Furthermore, the enabled “Count table row” option does not cause an error anymore when 0 rows are returned. |
Various Sensors |
Fixed debug option (“Write Result to Disk”) for several sensor types. |
Various Sensors |
Improved encoding method for various sensor types:
|
All Parts of PRTG |
Many other minor improvements and fixes to all parts of PRTG |
SNMP Sensors |
We removed the “SNMP Debug Log” option to avoid filling the whole disk on the probe system by accident. |
Deprecated Sensors |
As announced in previous PRTG versions, we have removed deprecated sensor types from PRTG. Running sensors of this type will stop monitoring and show a down status as soon as you update to this version. Please see this article for details: The PRTG Sensor Cleanup Note: The deprecated sensor types ADO SQL, Microsoft SQL, MySQL, and Oracle SQL will continue monitoring (now using the new SQL engine in the background) and keep their configuration. Please see this article for details: Migration Path for Deprecated SQL Sensors |
Notification Summarization |
PRTG collects up to 25 email notifications per defined gathering interval and sends the summarization as soon as this number is reached. Because of this, you may receive more than one summarization per gathering interval. The reason for this change is that some email clients have issues with long (HTML) emails. |
HTTP Sensors |
HTTP sensors added by the auto-discovery are now named HTTP, HTTP (8080), or HTTPS depending on the connection to the target device. This helps to distinguish automatically added HTTP sensors at one look. |
Oracle Tablespace |
The Oracle Tablespace sensor includes new channels for “Database Size” (current size of the database) and “Database Size on Disk” (managed tablespace). |
SQL v2 Sensors |
You can now use placeholders in SQL query files of SQL v2 sensors (@prtg for Microsoft SQL, MySQL, PostgreSQL, :prtg for Oracle SQL, ? (question mark) for ADO SQL). Provide the input parameter in the sensor settings and PRTG will replace the placeholder in the SQL query. This is a great option if you use many SQL sensors where the queries differ in only one parameter! Furthermore, a change trigger is available for changing sensor messages of SQL v2 sensors. |
Windows Network Card |
The Windows Network Card sensor can show more data now, including 64-bit counters, virtual network interfaces, teamed adapters, and virtual connections (for example, VPN). |
Software Table |
The software scan now always uses credentials set for the device’s parent probe. |
Hardware Table |
The hardware table shows the RAM of the device. |
Maps Design |
Connection lines between objects on maps can now show colors for all object states. |
SSH Sensors |
Major fixes for the new SSH engine |
Syslog Sensor |
Fixed potential deadlock of Syslog sensor |
SSH Sensors |
Compatibility fixes for the new SSH engine |
Probes |
Stability improvements for PRTG probes |
Security |
Fixed a potential XSS vulnerability and other minor security fixes |
WebGUI |
Several minor fixes for the PRTG web interface |
Notifications |
Stability improvements for email notifications |
SQL v2 |
SQL v2 sensors work again when you use SQL server authentication. These sensors showed an error in the previous PRTG version. |
Cisco IP SLA |
ECHO monitoring with the Cisco IP SLA sensor works again. These sensors showed an error in the previous PRTG version. |
Performance |
Fixed performance impact that occurred in certain cases when running the auto-discovery |
Login |
Auto-complete of username and password on the login page works again. |
Various |
Several other minor fixes for the PRTG web interface |
Core/Server |
Several minor fixes |
System Information |
You can now view system information for all devices that PRTG monitors (when PRTG has the appropriate credentials). The devices can be either a supported Windows version or they have SNMP enabled to get information data. Open the "System Information" tab on a device overview page and see what hardware and software is installed, what processes and services run on this computer and which user accounts are logged in. Together with your day-to-day monitoring you get a really profound knowledge about your IT infrastructure by using only one source—your PRTG Network Monitor! |
SNMP Dell EqualLogic |
This version comes with three new sensor types for EqualLogic monitoring! Native support for EqualLogic monitoring has been demanded by many of our customers so we are glad that we can offer this feature to you now. You can monitor logical disks, physical disks, and the health of storage array members with three dedicated sensor types:
|
ADO SQL v2 |
The new ADO SQL v2 sensor can monitor any data source that is available via OLE DB or ODBC. It is the successor of the deprecated ADO SQL sensor. |
Windows Physical Disk I/O |
The new Windows Physical Disk I/O sensor monitors input/output operations on a disk. Important note: This sensor type supersedes the Windows Physical Disk sensor which is deprecated as of now and will be removed with the next PRTG version. Please replace the deprecated sensor with the new Windows Physical Disk I/O sensor! |
WMI Logical Disk I/O |
The new WMI Logical Disk I/O sensor monitors logical disks on a Windows device. Important note: This sensor type supersedes the WMI Logical Disk sensor which is deprecated as of now and will be removed with the next PRTG version. Please replace the deprecated sensor with the new WMI Logical Disk I/O sensor! |
SSH Sensors |
SSH sensors use a new SSH library to provide best performance and security. Note: You can still use the old SSH engine as legacy version by selecting the deprecated “Compatibility Mode” in the sensor or device settings, but we will remove this option soon. |
Beta Sensors |
The following sensor types are not in beta status anymore and are now fully supported:
|
Amazon CloudWatch |
Amazon CloudWatch sensors support the region Asia Pacific (Seoul). |
SNMP CPU Load |
You can now store limits of the SNMP CPU Load sensor's “Total” channel into device templates. |
SQL v2 |
SQL v2 sensors have now the option to count table rows which a SELECT statement returns. You can also use @-variables in your SQL statements as of this version. |
Status Placeholder |
We removed the %state placeholder because it duplicated the %status placeholder. Please check your notifications and change this placeholder to %status if necessary. |
Data Graphs |
Improved chart rendering for data graphs in the PRTG web interface and in historic data reports. In particular, several PRTG language versions like Korean will benefit from this improvement. |
Cisco IP SLA |
The Cisco IP SLA sensor shows correct values in the channels “TCP RTT” and Max. Latency Source – Destination”. We also improved performance and stability of this sensor. |
Citrix XenServer |
Citrix XenServer sensors use the correct unit for additional channels. |
Dell PowerVault |
Dell PowerVault MDi Logical Disk and Dell PowerVault MDi Physical Disk sensors can read values from a 64-bit registry. |
NetFlow |
NetFlow sensors which you clone to other probes receive data automatically. |
Sensor Factory |
Deleting channels of the Sensor Factory sensor works without causing an error. Sometimes this resulted in an Access Violation in the PRTG core. |
SNMP Cisco ASA VPN Traffic |
SNMP Cisco ASA VPN Traffic sensor supports 64-bit counters. |
SNMP NetApp Enclosure |
SNMP NetApp Enclosure sensor now includes default limits for all channels. |
SNMP RMON |
SNMP RMON sensors portname templates show the correct port. |
SQL v2 |
SQL v2 sensors work with passwords that contain certain special characters. |
SSH SAN Physical Disk |
Fixed occasional spikes in the data of SSH SAN Physical Disk sensors. |
VMware Datastore (SOAP) |
Channel Unit Configuration for VMware Datastore (SOAP) sensors is now available. |
VMware Virtual Machine (SOAP) |
VMware Virtual Machine (SOAP) sensor can now follow changes in the assignment of IDs and metrics on VMware. Affected sensor channels showed 0 values in this case before. |
Port Range |
Fixed template creation for devices with Port Range sensors |
Email Fallback Server |
The fallback SMTP server of PRTG can now send notification emails also if you use SASL authentication. |
Eventlog |
Event log notifications to the PRTG Network Monitor event log now work. |
Icons |
Auto-Discovery adds the correct vendor specific device icons again. |
Stability |
Stability improvements: In certain cases auto-discovery caused access violations. |
WebGUI |
The timer of the automatic page refresh resets when you change tabs and pages in PRTG. |
Reports |
Data files of reports show the data and time in a readable format now. Previously this column included data in raw format only. |
All Parts of PRTG |
Many small fixes and improvements for web interface, Enterprise Console, and all other parts of PRTG |
Setup |
We fixed the PRTG setup that crashed under certain circumstances. |
WMI Free Disk Space (Multi Disk) Sensor |
Limits that you define in the sensor settings work again. |
Updated Language Files |
Updated language files for French, Chinese, Russian, Spanish, and Brazilian |
Server/WebGUI |
Various minor fixes and improvements |
Deprecated Sensors |
The following sensor types are deprecated as of now, you cannot add them any more, and they will be completely removed with the upcoming PRTG version 16.x.25, due out in about 2 months. Sensor types which have been deprecated already before will be removed as well.
Please see this article for details: The PRTG Sensor Cleanup |
SNMP Custom Lookup |
We renamed the sensor type "SNMP Custom Lookup" to SNMP Custom String Lookup sensor. The new name indicates the intended usage of this sensor in a better way. |
Core Health |
The Core Health sensor includes two new channels that will help you to keep your PRTG installation up-to-date (and safe, for example, by always having all security updates installed):
|
Beta Sensors |
The following sensor types are not in beta status anymore and are now fully supported:
|
SSL Security Check |
The SSL Security Check sensor supports SNI: You can define it in the sensor settings. |
HTTP Sensors |
For HTTP sensors you can now define if you want to inherit the SNI from the parent device or if you want to determine the SNI from the sensor URL setting only. For more information about SNI handling in PRTG, please see this article: https://kb.paessler.com/en/topic/67398 |
Maps Designer |
We added a new icon set for maps and HTML settings are now better reachable in the maps designer. |
Exchange Database/SQL v2 |
Channel Unit Configuration for Exchange Database (Powershell) and SQLv2 sensors is now available. |
Exchange Database DAG |
Exchange Database DAG (Powershell) sensors now properly work on Exchange 2010 and Exchange 2013 with the latest updates. |
EXE/Script Advanced |
Metascans for custom EXE/Script Advanced sensors support PowerShell scripts in addition to exe-files. |
HTTP XML/REST Value |
|
jFlow |
jFlow sensors correctly use the fields SenderIP, InboundInterface, OutboundInterface, SourceASI, and DestinationASI again. |
Microsoft SQL v2 |
Microsoft SQL v2 sensor interprets Boolean values correctly. |
Oracle Tablespace |
Oracle Tablespace sensor now uses the timeout setting in the parent device (section “Credentials for Database Management Systems”). |
SNMP Cisco System Health |
SNMP Cisco System Health sensor can recognize 64-bit memory counters. |
SNMP Custom String |
SNMP Custom String sensor supports 0 bytes in MAC addresses. |
SNMP Custom Table |
SNMP Custom Table sensor supports custom OIDs in the name template. |
SNMP Linux Disk Free |
SNMP Linux Disk Free sensor supports very large partitions/volumes. |
SNMP Printer |
SNMP Printer sensor no longer duplicates channels after a PRTG server restart. |
SNMP RMON |
Improved handling of SNMP v1 by the SNMP RMON sensor |
SNMP Traffic |
SNMP Traffic sensors update interface names correctly if the target device returns "No such object" instead of "No such name" |
SNMP Trap Receiver |
SNMP Trap Receiver sensor now supports hex content (MAC addresses). The sensor did not show trap content in this case before. |
VMware Virtual Machine |
VMware Virtual Machine sensor shows latency channels again. These channels were missing on some systems. |
Channels |
Difference channels of sensors show correct historic data when the probe reconnects instead of zero values. Recalculate the PRTG graph data cache under "Administrative Tools" in the PRTG web interface to fix affected historic data. |
Templates |
Device templates include value lookups of multi-channel sensors now. |
Auto-Discovery |
Several improvements and fixes for auto-discovery groups |
Notifications |
Several improvements and fixes for email notifications |
Lookups |
Fixed historic data for range-based lookups |
Maps |
Public maps which use the data table map object "Tickets" are now accessible. |
Security |
Access rights for manually added objects are now shown correctly in the PRTG web interface. Display and actually used rights were inconsistent in some cases. |
WebGUI |
Many small fixes for the PRTG web interface |
API |
We added the new API calls getticketstatus.htm and getticketmessage.htm. You can now also use the parameter subtype for the API call setobjectproperty.htm to set, for example, channel properties. |
Manual |
Updated user manual |
Core/Server |
Many other minor improvements and fixes |
Cluster |
Sensors with dynamic channels show data again when you add them to remote probes with enabled cluster connectivity. |
Enterprise Console |
The Enterprise Console shows its usual performance again. |
Core/Server |
Various minor fixes and improvements |
Updated Language Files |
Updated language files for Brazilian, French, Russian, Chinese, Spanish |
Favorite Sensors |
Fix for traffic and trap sensors that are flagged as "favorite" in the Enterprise Console |
Core/Server |
Several minor fixes |
Notifications |
Channel tables and icons in HTML email notifications are shown correctly again. |
Reports |
Scheduled reports are sent out to PRTG user groups again. |
Packet Sniffer/Flow Sensors |
Filters for Packet Sniffer and Flow sensors work correctly again. |
WMI Sensors |
Fixed scan exception in ntdll for WMI sensors |
Core/Server |
Improved scheduler |
Minor Fixes |
This is a maintenance release with several minor fixes. |
Minor Fixes |
This is a maintenance release with several minor fixes. |
Data Files |
You can now generate CSV and XML data files along with the PDF file of a report for its data tables. This is a great option to import data into other programs! |
PDF Generator |
We added a new PDF generator for reports to PRTG. |
Docker Container Status BETA |
The new Docker Container Status BETA sensor monitors status, uptime, exit code, CPU usage, and memory of a Docker container. |
Amazon CloudWatch Alarm BETA |
The new Amazon CloudWatch Alarm BETA sensor monitors the status of configured alarms for CloudWatch services via the AWS CloudWatch API. |
Web Server |
Performance improvements for the web server |
Certificates |
Important: We renewed the certificates with which we sign PRTG. We strongly recommend that you update to this version to be able to seamlessly update to future versions of PRTG. |
Optimizations |
We fixed the root cause for the security issue that has been hotfixed with PRTG version 16.1.21.1441/1442. This version also contains various optimizations in context of this security flaw. |
Sensor Channels |
You can now define a scaling factor (multiplication and division) for values of sensor channels with custom units. You can find this option in the respective channel settings. Note: Sensors with a scaling option in the sensor settings do not provide this option in channel settings. There are also some other sensors with custom units that do not support this feature. |
EXE/Script Advanced |
The EXE/Script Advanced sensor can now make use of a meta-scan functionality. For details please see this article: https://kb.paessler.com/en/topic/68109 |
HTTP Transaction |
HTTP Transaction sensor shows the URL of the page that provokes a warning or error status in the sensor message. |
SSL Certificate |
Newly added SSL Certificate sensors have limits for the “Days to Expiration” channel by default. This sensor type has also an improved logging (“Write result to disk”). With this option enabled certificates of the cert chain are additionally logged for better debugging possibilities, especially for the “Root Authority Trusted” channel. |
SNMP Cisco System Health |
Improved performance for the SNMP Cisco System Health sensor |
SNMP Sensors |
SNMP sensors now use paging for SNMP requests to improve their stability. |
Windows Updates Status (Powershell) |
You can define a custom port for the Windows Updates Status (Powershell) sensor. |
WMI/Windows Sensors |
All WMI/Windows sensors provide a debug option. |
Options |
We removed the outdated option to automatically refresh whole PRTG pages from the account settings. By default, PRTG only refreshes single page elements. You can still disable auto refresh completely. |
SSH SAN System Health |
The SSH SAN System Health sensor adapts an HP firmware upgrade. After the firmware update, some sensor channels might show different data than before. Please try to add this sensor anew to get correct channel data. The corresponding error message is: The sensor encountered some problems. This might be caused by a firmware upgrade. Please try to recreate the sensor. |
SNMP Custom Advanced |
SNMP Custom Advanced and SNMP Custom Table sensors did not properly take the unit “BytesBandwidth” if you changed the configuration of this unit in a parent device or group. |
Dell PowerVault MDi Logical Disk |
Dell PowerVault MDi Logical Disk sensor now correctly recognizes disk with a minus (-) sign or an underscore (_) in the name. |
SSL Security Check |
SSL Security Check sensor prevents connection timeouts in a better way. |
SNMP Cisco System Health |
SNMP Cisco System Health sensor now shows correct memory utilization above 4 GB. |
SNMP Dell PowerEdge Physical Disk |
We fixed an issue that caused an “index out of bounds” error in some cases when adding the SNMP Dell PowerEdge Physical Disk sensor. |
NetApp cDOT sensors |
Fix for Int32 errors of NetApp cDOT sensors (support of Int64 values added). cDOT I/O and cDOT System Health sensors also perform a meta-scan when you add one of these sensor types, so you can create one sensor for one system node. This approach fixes wrong values for the "uptime" channel of the cDOT System Health sensor. Please add these sensors anew to apply the fixes. |
SCVMM sensors |
SCVMM sensors now show correct status values. |
Packet Sniffer |
Packet Sniffer sensor shows selected network adapter(s) again. |
Windows Network Card |
Windows Network Card sensor correctly shows 64 bit values. |
SNMP Printer |
Improved template handling of the SNMP Printer sensor |
SSL Certificate |
SSL Certificate sensor shows an "Unknown" status instead an error if the key length check fails. |
SNMP Custom Advanced |
OIDs for the SNMP Custom Advanced sensor support can start with points (.) |
SSL Certificate |
Adding the SSL Certificate sensor using a device template works correctly. |
SNMP Cisco System Health |
SNMP Cisco System Health can show negative values. |
Placeholders |
Placeholders in notification emails were not replaced correctly in certain cases. |
Lookups |
Stability improvements for custom lookups |
Manual |
Updated user manual |
Languages |
Updated language files |
All Parts of PRTG |
Many small fixes and improvements for web interface, Enterprise Console, and all other parts of PRTG |