PRTG Network Monitor Changelog

What's new in PRTG Network Monitor 24.2.95.1535 Preview

Apr 23, 2024

Improved:
Security:
Webserver:
We hardened PRTG against possible Reflected Cross-Site Scripting (RXSS) attacks.
Server:
Notifications:
We improved the delivery time for HTTP notifications that took longer in certain cases in the previous PRTG versions when you used a HTTP target URL in the Execute HTTP Action section of the notification template. This issue occurred because the PRTG fallback handling for SSL still tried to establish a TLS secured connection what did not lead to an error but to a longer waiting time for PRTG.
Sensors:
Ping v2:
You are now able to create the Ping v2 sensor via device template if you select the option Create Device Template on a device where you can select the Ping v2 sensor in the Create Device Template dialogue window. The Ping v2 sensor left its BETA status with PRTG version 24.1.92.1554 and is now fully supported. This feature also works on a device for the Multi-Platform Probe.
Multi-Platform Probe:
Probe Adapter:
You will now receive a proper error message in the probe adapter log when your NATS server for connection does not offer a secured TLS connection but PRTG is configured to connect with TLS in the Multi-Platform Probe Connection Settings.
Fixed:
Server:
Contact support:
We fixed an issue where the button Contact Support was missing in the help bar and also in the Support section on the PRTG Setup page when you ran PRTG with a trial license. This issue also affected Paessler PRTG Hosted Monitor.
Cluster
We fixed an issue where the API call for api/health.json reported wrongly a disconnected Cluster probe although the probe was connected at this time. You could also see this behavior on the System Status page in PRTG under Probes where the Cluster Probe was reported as not connected yet.
Maps
We fixed an issue for public maps access that allowed users to see objects in the device tree despite of their assigned security context when you had two or more public maps open in a tab for map rotation view.
PRTG Administration Tool
You will no longer receive an error when you click on the button Stop Service or Start Service (ignore changed settings) for the Core and Probe service in the PRTG Administration Tool when you run it as a 64bit version on your system. This issue occurred in the previous PRTG stable version 24.2.94.1400 but did not happen when you run the PRTG Administration Tool in a 32bit mode. The reported error message in this case was One or more required program components of PRTG (PRTG Server.exe, PRTG Probe.exe) could not be found! Please re-run the installation program.
Search
You will now receive proper results from our Help documentation when you click on the More button on the Search Results page. This did not work in the previous PRTG versions and returned the message Your search request did not return any results (Help Documents) when you, for example, searched for the term Core Health. You could also see that your seach term was not resolved properly and displayed as core%20health.
Single Sign-on
You are now able to send a support bundle with all relevant files via Contact Support button on the Setup page when you are logged in to PRTG with a Single Sign-on user account. In the previous PRTG versions, sending a support bundle as a logged in Single Sign-on user would trigger the overload protection in PRTG and the bundle would not contain any htm files.
XML tables
We fixed an issue where the returned table for a queried XML was broken when you had an object, e.g. sensor, with a tag that contained an ampersand & in it.
Security:
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

New in PRTG Network Monitor 24.2.94.1400 (Apr 10, 2024)

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.
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.
We fixed an open redirect which could potentially be used for phishing and other purposes. The severity is 4.3-Medium and calculated as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N.
We hardened PRTG against possible Cross-Site Scripting (XSS) attacks during Probe creation. The severity is 6.9-Medium and calculated as CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N.
Improved:
Server:
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.
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.
Fixed:
WebGUI:
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.
Note:
Sensors:
Discontinued sensors with PRTG 24.2.94:
With this version we discontinue the below already deprecated sensors:
Amazon CloudWatch sensors (announced as deprecated with PRTG version 22.3.78.1873)
Cloud HTTP sensor and Cloud Ping sensor (announced as deprecated with PRTG version 22.3.78.1873)
DNS sensor (announced as deprecated with PRTG version 21.2.69.1308)
REST Dell EMC sensors (announced as deprecated with PRTG version 21.2.67.1531)
If you run any of these sensor types they will show an error message This sensor type was removed from PRTG. For more information, see https://kb.paessler.com/en/topic/68227. (code:PE258), when you update your PRTG installations to version 24.1.94. 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?
Changed:
Sensors:
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.
Fixed:
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.
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.
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 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.
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.
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.
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.
Fixed:
Server:
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.
Maps:
We fixed an issue where the public map display resulted in an empty window if a read-only user had access only to one object on the map. The issue occurred when the objects were linked with a connector and the read-only user had access only to one of these objects. When the map was opened in a separate incognito window with the option Public Access without login, it would only display an empty page, although the Security Context was set to the read-only user.
Your public map display will now work properly again when you are logged in to PRTG with a user that has No access to the relevant map. Previously, when you opened a map with the link for Public Access and you were logged in to PRTG with a user that has No access under Access Rights for the map, the page would then display Map refresh failed, although the map was configured for public access.
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.
Fixed:
PRTG App for Desktop:
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.
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.

New in PRTG Network Monitor 24.1.94.1397 Preview (Mar 28, 2024)

New in PRTG Network Monitor 24.1.94.1355 Preview (Mar 18, 2024)

New in PRTG Network Monitor 24.1.93.1655 Preview (Feb 26, 2024)

Improved:
Security:
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.
Webserver:
We fixed an open redirect which could potentially be used for phishing and other purposes. The severity is 4.3-Medium and calculated as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N.
We hardened PRTG against possible Cross-Site Scripting (XSS) attacks during Probe creation. The severity is 6.9-Medium and calculated as CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N.
Improved:
Server:
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.
Note:
Sensors:
Discontinued sensors with PRTG 24.1.94:
With this version we discontinue the below already deprecated sensors:
Amazon CloudWatch sensors (announced as deprecated with PRTG version 22.3.78.1873)
Cloud HTTP sensor and Cloud Ping sensor (announced as deprecated with PRTG version 22.3.78.1873)
DNS sensor (announced as deprecated with PRTG version 21.2.69.1308)
REST Dell EMC sensors (announced as deprecated with PRTG version 21.2.67.1531)
If you run any of these sensor types they will show an error message This sensor type was removed from PRTG. For more information, see https://kb.paessler.com/en/topic/68227. (code:PE258), when you update your PRTG installations to version 24.1.94. You can pause existing sensors afterwards but you will not be able to deploy them anymore.
Changed:
Sensors:
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.
Fixed:
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.
Fixed:
Server:
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
We fixed an issue where the public map display resulted in an empty window if a read-only user had access only to one object on the map. The issue occurred when the objects were linked with a connector and the read-only user had access only to one of these objects. When the map was opened in a separate incognito window with the option Public Access without login, it would only display an empty page, although the Security Context was set to the read-only user.
Your public map display will now work properly again when you are logged in to PRTG with a user that has No access to the relevant map. Previously, when you opened a map with the link for Public Access and you were logged in to PRTG with a user that has No access under Access Rights for the map, the page would then display Map refresh failed, although the map was configured for public access.
Fixed:
PRTG App for Desktop:
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.
Fixed:
Paessler PRTG Hosted Monitor:
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.
Fixed:
WebGUI:
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.

New in PRTG Network Monitor 24.1.92.1554 (Feb 14, 2024)

New in PRTG Network Monitor 24.1.92.1545 Preview (Feb 7, 2024)

New in PRTG Network Monitor 24.1.92.1496 Preview (Jan 23, 2024)

New:
Sensors:
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.
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.
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.
Improved:
Security:
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 a vulnerability in the editlicense.htm endpoint which could enable an attacker, with user interaction, to change license details.
Fixed:
Server:
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.
Fixed:
Sensors:
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).
Fixed:
WebUI:
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.

New in PRTG Network Monitor 24.1.91.1583 Preview (Jan 10, 2024)

New in PRTG Network Monitor 23.4.91.1566 Preview (Dec 7, 2023)

Improved:
Security:
Webserver:
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.
Improved:
Server:
Notifications:
We added the option for SNMP Trap notifications to notify third party systems of alarms in PRTG when you have added an SNMP Trap Receiver sensor. For the notifications template Send SNMP Trap you can enter the placeholder %sensorid in the Message field which will be sent as an extra OID entry in the trap message. To enable this option, you need to select Do also send sensor id in the setting for Send sensor id. If you request this option, the sensor ID will be sent as OID 1.3.6.1.4.1.32446.1.1.5.
Update to OpenSSL 1.1.1w
To ensure secure communication furthermore we updated to the OpenSSL version 1.1.1w. For more information please visit https://www.openssl.org/news/cl111.txt.
Fixed:
Server:
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.
Fixed:
Sensors:
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.
Fixed:
Web GUI:
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.
Note:
Installer:
Security:
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Lab:
Sensors:
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.
We fixed an issue where only one device template was returned in the settings even if there were multiple device templates for auto-discovery assigned to a device when you executed a GET request with /api/v2/experimental/devices/{id}/settings. This issue also affected the former APIv1 via /api/getobjectproperty.htm.
We fixed an issue that occurred when you sent a PATCH request to /devices/{id} endpoint in order to set the IPv4 host of a device. If you sent a GET request to /devices/{id} in order to check if basic.host is set to 127.0.0.1, you would notice that the host option was not set correctly. The issue happened when you created a device in the classic web interface in PRTG before with the IPv6 Hostname set without the IPv4 or a IPv4 Hostname given.
We made several changes for the experimental endpoint. We added the sortIndex field and sections and settings are not sorted anymore by the appserver. Default values like false for boolean or empty strings are omitted in the response.
Fields for read only users are now masked in the endpoints /devices/{id}/settings and /devices/{id}, for example the Credentials for Windows systems. In the previous PRTG version, those setting fields were not masked when you logged in with a read only user to the appserver and executed a GET request on a device with all settings included.
We fixed an issue where the parent tag of a device was not returned when you executed a GET request for the api/v2/devices endpoint. For example, if you added a tag to a specific group to which the device was added and requested the device details via endpoint afterwards, the parent tag for that device was not returned in the response.
We fixed an issue for the Create Device endpoint /api/v2/schemas/device?purpose=create&parent=1 that resulted in 404 NOT FOUND error although the API call was on a valid schema.
Devices:
You can now create a device under a group or local probe via API v2. You can create a device by sending the according POST request on the endpoint experimental/groups/{id}/device in the Swagger UI. The device will be created on group level. For a device on probe level you need to use the endpoint experimental/probes/{id}/device.
Read-only users are now able to see information of the Credentials for Windows Systems settings of a device via the /devices/{id} endpoint. The available information is if the Inherit From toggle is activated or not and where the data is inherited from.

New in PRTG Network Monitor 23.4.90.1299 (Nov 15, 2023)

Improved:
Security:
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.
Improved:
Sensors:
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.
Microsoft Azure sensors:
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.
We generally hardened the approach how Microsoft Azure sensors retrieve data to avoid gaps in the sensor data.
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.
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:
AWS v2 sensors
Cisco Meraki (BETA) sensors
Cloud HTTP v2 sensors
Cloud Ping v2 sensors
Dell EMC sensors
FortiGate sensors
HPE 3PAR Common Provisioning Group
HPE 3PAR Virtual Volume
HTTP v2 (BETA) sensors
Microsoft 365
Microsoft Azure
NetApp sensors
Redfish sensors
REST Custom v2 (BETA) sensors
Soffico Orchestra sensors
Veeam sensors
Zoom Service Status sensor
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.
Changed:
Sensors:
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.
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.
Fixed:
Server:
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.
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.
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.
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 Store result option was enabled under Debug Options in the sensor settings.
Fixed:
Sensors:
AWS sensors:
We implemented various improvements for the AWS v2 sensors:
You can add the AWS Alarm v2, AWS RDS v2, and AWS ELB v2 sensors again as expected even if 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.
We fixed an issue for AWS sensors that could not be created when you ran an auto-discovery via device template. Adding the sensors with auto-discovery now works again as expected.
AWS EBS v2: We improved the wording of an error message text when the ID of the AWS EBS volume that this sensor monitors is not found. The error message displayed in the Down status of the sensor is No volume with the ID x was found.
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 365 Mailbox sensor:
You can now again save changes in the sensor Settings of your M365 Mailbox sensor. This did not work before in the previous PRTG version 23.3.86.1520. Previously If you had changed the sensor settings and tried to save them, you would have received an Unauthorized ajax error message, the site page would have reloaded, and the settings would have reverted to the previous state. You could have saved the settings initially when you added this sensor type as new sensor during the creation process.
We fixed an issue where you could not add the Microsoft 365 Mailbox sensor to your PRTG when it inherited credentials given under Credentials for Microsoft 365 from Root group. PRTG would report the following in this case PRTG Network Monitor has encountered a problem. Your last request could not be processed properly. You could also observe the following entry in the CoreWebServer.log: Error: The request cannot be processed because the object ID is missing.
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.
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.
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.

New in PRTG Network Monitor 23.4.90.1279 Preview (Oct 24, 2023)

Improved:
Sensors:
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.
Fixed:
Server:
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.
Fixed:
Sensors:
Microsoft 365 Mailbox sensor:
You can now again save changes in the sensor Settings of your M365 Mailbox sensor. This did not work before in the previous PRTG version 23.3.86.1520. Previously If you had changed the sensor settings and tried to save them, you would have received an Unauthorized ajax error message, the site page would have reloaded, and the settings would have reverted to the previous state. You could have saved the settings initially when you added this sensor type as new sensor during the creation process.
We fixed an issue where you could not add the Microsoft 365 Mailbox sensor to your PRTG when it inherited credentials given under Credentials for Microsoft 365 from Root group. PRTG would report the following in this case PRTG Network Monitor has encountered a problem. Your last request could not be processed properly. You could also observe the following entry in the CoreWebServer.log: Error: The request cannot be processed because the object ID is missing.
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.
Changed:
Sensors:
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.
Lab:
Sensors:
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.
Lab:
New UI:
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.
Improved:
Various:
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.

New in PRTG Network Monitor 23.4.89.1539 Preview (Oct 12, 2023)

New in PRTG Network Monitor 23.3.88.1421 (Oct 2, 2023)

New in PRTG Network Monitor 23.3.88.1393 (Sep 20, 2023)

Improved:
Server:
Security:
Your API Keys are no longer logged in a readable format in the CoreWebServer.log when you have created an API key before and executed an API call request with it. The issue only occurred for the Log in Debug Level.
Improved:
Sensors:
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.
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.
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.
Fixed:
Server:
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.
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.
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
We fixed an issue that prevented notification templates from being edited within the notification trigger tab.
We fixed an issue for the notifications template Send Syslog Message where the message contained a wrong character (?) at the beginning, regardless of the format (ANSI, UTF-8) you selected before.
We fixed an issue in the delivery of sms notifications that occurred in cases when you used NowSMS service as an sms endpoint for PRTG. The delivery of sms notifications was delayed in these cases in the previous PRTG version.
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.
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.
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.
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.
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.
Fixed:
Sensors:
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.
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 sensors:
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.
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 sensors:
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.
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.
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 Logssensors 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 resetted 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.
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
Fixed:
PRTG Desktop:
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.
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.

New in PRTG Network Monitor 23.3.88.1385 Preview (Sep 13, 2023)

New in PRTG Network Monitor 23.3.88.1359 Preview (Sep 6, 2023)

New in PRTG Network Monitor 23.3.88.1319 Preview (Aug 30, 2023)

Sensors:
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.
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.
Fixed:
Server:
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:
We fixed an issue for the notifications template Send Syslog Message where the message contained a wrong character (?) at the beginning, regardless of the format (ANSI, UTF-8) you selected before.
We fixed an issue in the delivery of sms notifications that occurred in cases when you used NowSMS service as an sms endpoint for PRTG. The delivery of sms notifications was delayed in these cases in the previous PRTG version.
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.
Fixed:
Sensors:
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 Logssensors 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 resetted 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.
Fixed:
PRTG app for desktop:
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.

New in PRTG Network Monitor 23.3.86.1520 (Aug 30, 2023)

Improvements and Fixes:
ITOps Board version 3.11 comes with improvements to accessibility on the boards page and context menu, as well as excluded child boards by default on display and improvements to integration settings.
It also covers fixed issues. For integrations that have a large number of components, an internal server error may have occurred in previous ITOps Board versions when you have performed a search. Also boards will no longer remain in maintenance mode when the scheduled maintenance period has ended.
Security Update: We updated the ITOps Board to version 3.11.4 to fix an issue in the remote agent installation file where the connection credentials were stored in a readable format and are now masked again.
Improved:
Security:
Vulnerabilities:
We fixed a vulnerability where a PRTG user with write permissions could trick a few sensors into creating possibly executable files on the host system, which could then be executed under certain circumstances. The vulnerability can be tracked under CVE-2023-31448, CVE-2023-31449 and CVE-2023-31450.
We fixed a vulnerability where it was possible to bypass the CSRF protection. The vulnerability can be tracked under CVE-2023-31452.
We fixed a vulnerability where it was possible for a PRTG user with write permissions to trick certain sensors to use sensor specific files from unintended locations on the host system which could lead to arbitrary actions within the capabilities of the sensors. The vulnerability can be tracked under CVE-2023-32781 and CVE-2023-32782.
We fixed a vulnerability where a target url could be tricked to redirect the user to foreign domains.
For further information please also see our Knowledge Base article: https://kb.paessler.com/en/topic/91845
Improved:
Sensors:
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
Improved:
Web server:
Web server Security:
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. Specifically, by using the bodyclass as a get parameter in conjunction with specifically encoded javascript, an attacker could trick a victim into running the injected code and disclose information to the attacker. Thanks to Nicolas Verdier for reporting the issue. The vulnerability can be tracked under CVE-2023-28148.
Fixed:
Server:
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.
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.
Fixed:
Sensors:
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 }.
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.
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.
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 response 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:
We fixed an issue for the OPC UA Certificate Sensor, OPC UA Custom Sensor and OPC UA Server Status Sensor that went into an error status after one or more scan intervals with the message BadSessionInvalid. The issue happened during session establishment where the session timeout response from the server was not taken into account by the sensor.
You can now set the connection configuration for OPC UA to SecurityMode = None in the Endpoints tab with additional user name authentication via Username & Password for a user account. This combination did not work previously and the connection to the OPC UA sensors could not be established before.
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 than 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
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.
Fixed:
PRTG Mobile Apps:
User Login:
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.
Note: This fixes also an issue for PRTG Desktop where non admin users were also not able to log in anymore with PRTG version 23.2.84.1566.

New in PRTG Network Monitor 23.2.86.1515 Preview (Jul 12, 2023)

New in PRTG Network Monitor 23.2.86.1462 Preview (Jul 4, 2023)

New in PRTG Network Monitor 23.2.85.1327 Preview (Jun 15, 2023)

New in PRTG Network Monitor 23.2.85.1310 Preview (Jun 6, 2023)

Fixed:
Server:
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.
Sensors:
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 Mobile Apps:
PRTG for Android 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.
New UI:
Device settings:
Your device Settings are now divided in collapsible sections providing you a clear overview of the available settings.
You can now filter for items in the device Settings via an integrated search field. The matching results will be displayed expanded per section so that you can immediately change them.
You can now collapse and expand the settings sections with a toggle button. Basic Device Settings are expanded by default. When you have expanded all settings sections, the button will display close all and open all when the settings sections are collapsed.
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.
Improved:
Various:
All parts of PRTG:
Various other minor fixes and improvements.

New in PRTG Network Monitor 23.2.84.1566 (May 24, 2023)

New:
Sensors:
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.
Your NetApp Volume v2 sensor now reports volumes correctly in a NetApp MetroCluster configuration setting. Previously, the sensor displayed an error with the message The queried field "space.available" is empty. when it was used in cluster configurations.
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.
Improved:
Security:
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.
Sensors:
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.
Fixed:
Server:
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.
Sensors:
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.
Changed:
PRTG Desktop:
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.

New in PRTG Network Monitor 23.2.84.1562 Preview (May 17, 2023)

New in PRTG Network Monitor 23.2.84.1532 Preview (May 11, 2023)

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.
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.
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.
We hardened PRTG against possible data extraction from instances on the PRTG status page.
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.
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.
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.
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.
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.
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.
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.
Your NetApp Volume v2 sensor now reports volumes correctly in a NetApp MetroCluster configuration setting. Previously, the sensor displayed an error with the message The queried field "space.available" is empty. when it was used in cluster configurations.
You can now select unit types and lookups for each channel in the Channel Settings of your REST Custom v2 sensor. Input fields for Channel # Lookup ID and Channel # Custom Unit are now available. For custom units you can set a unit name now. Currently, all settings are visible when you enable the Channel # Custom Unit with Absolute (integer), Absolute (float) and Delta (counter) as value types. If you select lookup as channel type the sensor will be created using the given lookup file. Please note that you have to provide the name of the lookup during sensor creation for now when you want to select a lookup file and that the lookup can only be edited in the channel settings after sensor creation.
We improved the error handling of the REST Custom v2 sensor that will now display an according error message in case of an error and will run into an error status. For example, the error message will include the HTTP status code of the REST response in case the parsing fails due to invalid JSON.
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.
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.
We improved the Script v2 sensor that now supports the new sensor result JSON schema that allows you to use custom scripts. 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. Additionally we updated 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.
We improved the Priority setting in the device Settings where you now can select a star rating.
We added the section Additional Device Information that displays the Service URL.
We fixed an issue with the Keyword filter action on sensor and channel lists. Previously the filter input would not return results with the search term from the primary channel column. With the new fix the filter returns the results from a group that includes the search term in the primary channel column. This action was fixed in a group, device, probe and sensor level.
We fixed an issue for the Automatic Refresh option in the PRTG Web Interface settings that occurred when you had the radio button Do not automatically refresh pages selected in the classic UI. The refresh timer was displayed in the new UI and returned an unknown error when you activated it. It is now hidden in the new UI when you have deactivated the Automatic Refresh option
We fixed an issue for the link different endpoints on the PRTG APIv2 card that did not open in a new browser tab before.
You can now clone a group with sensors that have channel limits without losing the given settings. Previously, the channel limits of a sensor were not adopted if you cloned the group of the sensor what could result in a wrong sensor status.
Various other minor fixes and improvements.
We updated the Dutch, Japanese, French, Portuguese, Russian and Chinese language files.

New in PRTG Network Monitor 23.2.83.1760 (Apr 12, 2023)

New in PRTG Network Monitor 23.1.83.1742 Preview (Mar 30, 2023)

Fixed:
Sensors:
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.
Server:
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.
Improved:
Security:
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)
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.
Server:
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 new OpenSSL:
To ensure secure communication furthermore we updated to the OpenSSL version 1.1.1. 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.
Sensors:
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 Logssensors 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 Logssensors 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
SSL Security Check sensor now has a new channel for TLS 1.3 TLS 1.3 (Perfect) that the sensor will check if it is supported by the target device and either display Accepted or Denied. In case of Denied, the sensor will report an error in the channel Security Rating.
HTTP Push Data sensor, HTTP Push Data Advanced sensor, HTTP Push Count sensor, HTTP IoT Push Data Advanced sensor now have a third option for TLS Settings for HTTPS high security (TLS 1.2 to 1.3 and strong ciphers). Default setting for added sensors will be HTTP Unsecure. If you use sensors running on HTTPs and update to this PRTG version, the sensors will use HTTPS low security (TLS 1.0 to 1.3 and weak ciphers) to stay compatible.
Please note that all HTTP Push sensors always support TLS 1.3 even in low security setting. If you use HTTPS high security setting, TLS 1.0 and TLS 1.1 will be disabled and the sensors use the high security ciphers instead.
Sensor security digital signature:
We improved several sensor types by signing them digitally with Secure Hash Algorithms sha256. 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.
Security:
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.
LAB:
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.
Sensors:
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:
The REST Custom v2 sensors now support the count function in arrays to get the number of elements that are included in an array.
We implemented a new value type String (status) which displays three text input fields when you select it for channel strings mapped to the Up, Warning and Down status. The text field input is optional. The channel is assigned to a static lookup file mapping the values for up, warning and down to the according status. The values are mapped to an integer before accordingly.
Your REST Custom v2 sensors now display the primary channel correctly on the sensor overview page when they are deployed via device template. In the previous PRTG versions, you had to set the primary channel manually afterwards of the device template auto-discovery.
You can now perform basic calculations on the result of REST queries with the REST Custom v2 sensors without using an extra custom script.
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).
Multi-Platform Probe:
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
New UI:
Controls:
You can now open the channel graphs page via the context menu button Show Channel Graph. The channel details and channel graph dialogues show error information in case of an error when data cannot be found or loaded.
You will now get a dialogue pop-up when you click on the Discard button for changing settings. The dialogue offers the options to Cancel or Confirm discarding your changes. You will get a similar dialogue message when you try to navigate to a different page or when you close the page. The dialogues only appear when you changed settings that you did not save.
Device Settings
We improved the Basic Device Settings by displaying the Monitoring Status and the IP Version options as radio group. This change applies only if there are less than five selections per option.
You will now see the action bar buttons Discard and Save Settings when you are on the Basic Device Settings page. The action buttons were only visible after you made changes before. After the change, a text appears how many changes you have made, like 1 Change.
Web Interface:
Channel details of a sensor are now displayed when you log in to the new UI again after a logout or timeout.
Data cache is now cleared when you log out from PRTG in the new UI.
We fixed an issue for lookups that in some cases displayed an error when you used custom lookup definitions with an unknown type.
We fixed an issue where the scrolled down position was saved on the sensor overview page. If you now scroll down on a sensor overview page and select another sensor overview page it will be displayed on the top again.
You now can use the new UI only with a valid license. In case you use an inactive license you will be redirected to https:///activation.htm when you log in to the new UI.
PRTG API v2:
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:
We fixed an issue for the information text file about open source libraries used in PRTG. You can find the prtgappserver_license_report.txt file in the PRTG installation path. The file contains information about library name, version, notice and license text.
We fixed an issue where in some cases the application server ran on 32-bit when the core server was operating in 64-bit mode. The application server now uses the same version that the core server runs.
We improved the startup check of the PRTG application server that in some cases did not come up when it did not receive certain sensor IDs from the PRTG core server.

New in PRTG Network Monitor 23.1.82.2175 (Mar 1, 2023)

Fixed:
Sensors:
HPE 3PAR sensors:
The sensor types HPE 3PAR Virtual Volume, HPE 3PAR Drive Enclosure, and HPE 3PAR Common Provisioning Group work again. The sensors showed a down status with the error message 415 Unsupported Media Type after updating to the last PRTG version 23.1.82.2074 due to an issue with HTTP POST requests via REST API. This also affected the experimental REST Custom v2 (BETA) sensor.
HTTP push sensors:
HTTP push sensors work with HTTPS again. The sensors remained in unknown status after updating to the last PRTG version 23.1.82.2074 with HTTPS enabled in the sensor TLS settings and did not receive any answers for your sensor requests in this case. Affected sensor types were HTTP Push Data, HTTP Push Data Advanced, HTTP Push Count, and HTTP IoT Push Data Advanced.
Notifications:
Notification delivery:
PRTG successfully sends your email notifications again when you use Microsoft Office 365 as SMTP relay server. In PRTG version 23.1.82.2074, email notifications did not work with Microsoft 365 and showed the error message Error sending "Email": Connection to SMTP relay server "outlook.office365.com" failed in the logs due to an issue with TLS connections.
Licenses:
License name:
You can activate licenses again when the license name contains an ampersand (&) character. The activation of the license failed with the message License name and key do not match activation file. in the last PRTG version 23.1.82.2074 due to an issue with encoding.
Known Issues:
Notifications:
The subject of email notifications is not correctly displayed the current PRTG version if it contains special characters like diacritics or umlauts. If you primarily use special characters or Asian and Cyrillic characters in your email notifications, we recommend that you do not update your PRTG installation to version 23.1.82. We will deliver a fix for this issue with an upcoming PRTG version.
Windows MSMQ Queue Length:
In certain configurations, the Windows MSMQ Queue Length sensor reports an error with the message Queuename not found on specified machine. The error may come up during authentication on the target device. We are investigating the cause of this issue.

New in PRTG Network Monitor 23.1.82.2074 (Feb 8, 2023)

Improved:
Sensors:
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.
Improved:
Security:
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:
Active Directory Replication Errors sensor
FTP Server File Count sensor
HTTP XML/REST Value sensor
IP on DNS Blacklist sensor
Ping Jitter sensor
Traceroute Hop Count sensor
Windows Print Queue sensor
Windows MSMQ Queue Length sensor
WSUS Statistics sensor
Previously, passwords were sent in clear text. Now they are encrypted, so they are no longer visible in the Windows Event Log or Task Manager.
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.
Fixed:
Sensors:
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.
Fixed:
Server:
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.
Fixed:
WebGUI:
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.
Installer:
Security:
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

New in PRTG Network Monitor 23.1.82.2026 Preview (Jan 25, 2023)

Improved:
Sensors:
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.
Improved:
Security:
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:
Active Directory Replication Errors sensor
FTP Server File Count sensor
HTTP XML/REST Value sensor
IP on DNS Blacklist sensor
Ping Jitter sensor
Traceroute Hop Count sensor
Windows Print Queue sensor
Windows MSMQ Queue Length sensor
WSUS Statistics sensor
Previously, passwords were sent in clear text. Now they are encrypted, so they are no longer visible in the Windows Event Log or Task Manager.
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.
Fixed:
Sensors:
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.
Fixed:
Server:
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
Fixed:
WebGUI:
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.
Note:
Installer:
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:
sha256_exe B5A8A06EF616F023E6EFCE31031036ACDB08EC128BAEF5143DD16F36E18DFEE2
sha256_zip F04C82387B012049633C48CDAAA369A7368D58C3B6CA3B36B654CF79F5F41683
Lab:
Sensors:
HTTP v2:
We fixed an issue in the multi-edit menu that caused an error in the required fields validation for the post body. As a result, the Post Body field is no longer marked as a required field when you select POST as Request Method.
We fixed an issue with the timeout setting in the HTTP v2 sensor. Previously, the sensor did not report an error even if the requested HTTP page did not respond within a certain limit of time.
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.
Lab:
New UI:
Controls:
You can now change the basic settings of a device in the Basic Device Settings section. The basic settings of a device include Status, IPv4 Address/DNS Name, IP Version, Device Name and Priority.
You can now resume acknowledged alarms for sensors using the Clear Acknowledged Alarm button via the context menu and bulk edit change.
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:
You can now share the graphs page with a URL link.
You can now see the specific scanning times of a sensor if you have defined them as described in https://https://kb.paessler.com/en/topic/3723. In this case, the scanning interval is named Irregular and shows the scanning times in a tooltip.
We implemented live graphs for channels that show a down or warning status on the sensor and device overview cards.
We fixed an issue on the sensor graphs page that caused a reset after an automatic refresh if you interacted with the graphs, such as zooming in.
You can open graphs in a dedicated, larger view.
We have updated the content of the PRTG Welcome page to reflect the new features available.
Lab:
PRTG API v2:
Devices:
You can now delete a device with a DELETE request in the experimental section /experimental/devices/{id}. If the request was successful, you will get a 204 response code in return.
Note: You can only delete devices, not probes or groups, for example.
You can now edit the settings of a device by sending a PATCH request to /experimental/devices/ {id}. Please note that this feature is still in experimental status and does not contain all functionalities yet.
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.
Improved:
Various:
All parts of PRTG:
Various other minor fixes and improvements.

New in PRTG Network Monitor 22.4.81.1532 (Nov 29, 2022)

Fixed:
Sensors:
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.
Server:
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.
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.
Sensors:
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.
New UI:
Sensors:
The sensor information on the sensor overview page now displays placeholders while the object information is loading.
We fixed an issue for the Filter by keywords search option on the sensor list.
Channels:
The primary channel of a sensor now has a pin icon indicator in the card for sensor channels.
We fixed an issue for primary channels that caused an unknown error. The issue occurred only when the primary channel of the sensor had not yet received any data.
Web Interface:
We implemented a new subpage for sensors that shows all limit channels in interactive line graphs. You can select a timespan for the graphs from predefined options: live, short, medium, long.
We added time ranges to the timeseries interval picker that is available in the Graphs tab of a sensor.
We fixed an issue where deleting objects, likes sensors, devices and groups, led to an unknown error.
You will now receive a proper message for objects like sensors, devices and groups when they are moved to a paused status.
New API:
API:
We fixed an issue for sensor channels with lookup values that were not correctly formatted. The values are now displayed as percentages. The issue occurred in the /api/v2/experimental/timeseries/{id}/{type} endpoint.
We fixed an issue for new created devices in the experimental settings endpoints /experimental/devices/ID/settings and /experimental/sensors/ID/settings that led to a 404 not found error when you performed a get request.
You can now get information about settings and structure of a device with the GET endpoint /api/v2/experimental/devices/{id}/settings that we first introduced with PRTG 22.4.80.1553 for the experimental section.
PRTG application server:
We improved stability and performance of the PRTG application server.
Improved:
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual.
Languages
We updated the German and Spanish language files.

New in PRTG Network Monitor 22.4.81.1504 Preview (Nov 22, 2022)

Fixed:
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.
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.
Lab:
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.
Sensors:
The sensor information on the sensor overview page now displays placeholders while the object information is loading.
We fixed an issue for the Filter by keywords search option on the sensor list.
Channels:
The primary channel of a sensor now has a pin icon indicator in the card for sensor channels.
We fixed an issue for primary channels that caused an unknown error. The issue occurred only when the primary channel of the sensor had not yet received any data.
Web Interface:
We implemented a new subpage for sensors that shows all limit channels in interactive line graphs. You can select a timespan for the graphs from predefined options: live, short, medium, long.
We added time ranges to the timeseries interval picker that is available in the Graphs tab of a sensor.
We fixed an issue where deleting objects, likes sensors, devices and groups, led to an unknown error.
You will now receive a proper message for objects like sensors, devices and groups when they are moved to a paused status.
API:
We fixed an issue for sensor channels with lookup values that were not correctly formatted. The values are now displayed as percentages. The issue occurred in the /api/v2/experimental/timeseries/{id}/{type} endpoint.
We fixed an issue for new created devices in the experimental settings endpoints /experimental/devices/ID/settings and /experimental/sensors/ID/settings that led to a 404 not found error when you performed a get request.
You can now get information about settings and structure of a device with the GET endpoint /api/v2/experimental/devices/{id}/settings that we first introduced with PRTG 22.4.80.1553 for the experimental section.
PRTG application server:
We improved stability and performance of the PRTG application server.
Improved:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual.
Languages:
We updated the German and Spanish language files.

New in PRTG Network Monitor 22.4.80.1553 (Nov 7, 2022)

Improved:
Security
Improved:
Sensors:
Microsoft 365 Service Status Advanced:
We improved the filtering process of issues from the Graph API for the Microsoft 365 Service Status Advanced sensor.
Fixed:
Sensors:
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.
Changed:
Sensors:
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
Lab:
Sensors:
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:
For the NetApp LIF v2 (BETA) sensor we fixed an issue in the Throughput Read, Throughput Total and Throughput Write channel settings that are now configured as counter channels, as well as the NetApp NIC v2 (BETA) sensor channels Link Down Count, Receive Errors and Transmit Errors where you can now also set limits.
With this version comes the experimental NetApp SnapMirror v2 sensor (BETA) that we introduce additionally to the already released experimental NetApp v2 sensors (BETA) in PRTG 22.3.79.2108. The sensor supports the new ONTAP REST API as of ONTAP 9.6
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.
Lab:
New UI:
Sensors:
You can now switch between the channels of a sensor via dropdown menu in the channel detail dialog.
We added an overview tab with channel cards to the sensor view.
Lab:
New API:
API:
The experimental section now includes a GET endpoint for the settings of a device /api/v2/experimental/devices/{id}/settings. This endpoint is still under development and does not include all features yet.
We fixed an issue where cloned groups with added devices and sensors did not show the correct path for the sensor channels.
We fixed an issue in the /experimental/timeseries/{id}/live endpoint that in some cases wrongly displayed gaps in graphs for precalculated data.
We fixed an issue for the channel ID filter where you could not search for comma separated IDs with the endpoint /experimental/timeseries/{id}/{type}.
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.

New in PRTG Network Monitor 22.4.80.1542 (Oct 27, 2022)

New in PRTG Network Monitor 22.3.80.1498 (Oct 5, 2022)

New in PRTG Network Monitor 22.3.79.2107 Preview (Sep 13, 2022)

New in PRTG Network Monitor 22.3.79.2073 Preview (Sep 1, 2022)

New:
Sensors:
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.
The filter option in the Microsoft 365 Mailbox Settings is now divided into Contains All and Contains Any to enable a filter for different words in mails. Please note that already created sensors that had the filter option Contains will have the option Contains All after updating to this version.
You can now choose different folders in your mailbox to monitor when you add the Microsoft 365 Mailbox sensor.
You can now choose different folders in your mailbox to monitor when you add the Microsoft 365 Mailbox sensor.
We removed an empty settings field for Microsoft OAuth 2.0 Specific that appeared when you added a Microsoft 365 Mailbox sensor. You can see the following information for the Microsoft OAuth 2.0 specific field when the sensor has been added in the sensor settings: The OAuth 2.0 authorization renew feature is currently under development. If you change OAuth 2.0 settings in Microsoft Azure that require a reauthorization, you must add the sensor anew.
On creation of the Microsoft 365 Mailbox sensor you will see a dialogue for the Shared Mailbox User where you can add a mailbox account from a different user.
Server:
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.
Improved:
Sensors:
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:
Exchange Backup (PowerShell) sensor
Exchange Database (PowerShell) sensor
Exchange Database DAG (PowerShell) sensor
Exchange Mail Queue (PowerShell) sensor
Exchange Mailbox (PowerShell) sensor
Exchange Public Folder (PowerShell) sensor
Citrix XenServer Host sensor
Citrix XenServer Virtual Machine sensor
Hyper-V Cluster Shared Volume Disk Free sensor
RADIUS v2 sensor
SIP Options Ping sensor
HTTP Advanced sensor
HTTP Transaction sensor
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.
SNMP sensors:
We updated the net-snmp library that SNMP sensors use to version 5.9 and to enable a more secure communication via SNMP v3, we extended the Authentication Methods and Encryption Types in the Credentials for SNMP Devices settings. Additionally supported are now AES192 and AES256 as encryption type and SHA-224, SHA-256, SHA-384 and SHA-512 as authentication method.
Security:
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.
Changed:
Sensors:
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.
Fixed:
Sensors:
AWS Cost sensor:
The AWS Cost sensor now correctly calculates the forecast values again in the given forecast channels.
Core Health (Autonomous):
We improved the stability of the Core Health (Autonomous) sensor. Under certain circumstances, the sensor wrote error messages to the core.log file with each sensor scan.
The Core Health (Autonomous) sensor as well as the Application Server Health (Autonomous) sensor show the correct status again when you deactivate the new UI and new API instead of remaining in status Unknown.
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:
We fixed an issue with SNI inheritance affecting HTTP sensors. In previous versions, HTTP sensors showed a down status if the parent device had an IP address as host and the affected sensor was set to Inherit SNI from parent device. The error message in this case was Error connecting with SSL or similar.
We improved the compatibility of HTTP sensors with certain web servers. HTTP sensors now only set the content-type application/x-www-form-urlencoded on POST requests because using it with GET requests resulted in a down status in some cases.
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.
Server:
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.
WebGUI:
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.
Lab:
Sensors:
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, NetApp System Health 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.
New UI:
Controls:
The back button now works as expected again on all pages in the new PRTG web interface.
When the Show all sensors view on a Device Overview is selected, the view is now kept when opening a sensor and using the back button to navigate back to the Device Overview.
You can now scroll horizontally and vertically on object information cards as expected again.
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:
Breadcrumbs are now dynamic and will be truncated if they exceed a certain length.
Items in the Device List are now sorted as expected again.
The URL of a device tree now reflects the filter status of the device tree to allow users to share specific device tree views.
Web interface:
We have improved the visibility of the buttons in the filter bar on small screens.
We have improved the Reset filter button icon to clarify its function.
The new PRTG web interface now displays the correct error page if the PRTG application server is not available.
The Overview, Device List, and Sensor List tabs are now in horizontal orientation.
You can now see all details about an object on its Object Information page.
We updated and improved the layout of object headers.
You can now right-click any sensor and select Show Channel Details to see the current measurement, limits, minimum and maximum measurements, and lifetime average or the lookup definition and status of the primary channel of the selected sensor. You can also click any channel on the sensor's Overview tab to open the channel details.
New API:
Documentation:
We improved the documentation.
PRTG application server:
The results returned by the /settings/public endpoint now contain graph setting data.
We fixed a bug that caused an internal error if the ExecutionTimeoutInSecond was set to -1.
We moved the /sensors/{id}/settings endpoint from the sensors section to the experimental section. The new URL path is now /experimental /sensors/{id}/settings.
We improved the security of the PRTG application server.
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual.

New in PRTG Network Monitor 22.2.77.2204 (Jun 22, 2022)

New in PRTG Network Monitor 22.2.77.2201 (Jun 20, 2022)

New in PRTG Network Monitor 22.2.76.1705 (Apr 28, 2022)

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

New in PRTG Network Monitor 22.2.76.1624 Preview (Apr 5, 2022)

Single sign-on:
Okta:
You can now use Okta as provider for single sign-on (SSO) to login to PRTG with multi-factor authentication. Okta is the second SSO provider that you can integrate to PRTG. Azure Active Directory (Azure AD) is available since PRTG 21.2.68. You can choose the SSO provider that you work with in the system administration of PRTG and configure the settings for your SSO access.
New:
Sensors:
AWS Alarm v2:
The new AWS Alarm v2 sensor monitors your favorite metric and composite AWS alarms and will be the successor of the existing Amazon CloudWatch Alarm sensor.
AWS EBS v2:
The new AWS EBS v2 sensor monitors the status and performance of an AWS EBS volume and will be the successor of the existing Amazon CloudWatch EBS sensor.
AWS EC2 v2:
The new AWS EC2 v2 sensor monitors the performance of an Amazon EC2 instance and will be the successor of the existing Amazon CloudWatch EC2 sensor.
Note: If you use the same IAM policy that you use for the Amazon CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?
AWS ELB v2:
The new AWS ELB v2 sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor.
HPE 3PAR Drive Enclosure:
The new HPE 3PAR Drive Enclosure sensor monitors a drive enclosure of your HPE 3PAR storage system and shows status and temperature metrics.
HPE 3PAR Virtual Volume:
The new HPE 3PAR Virtual Volume sensor monitors a virtual volume of your HPE 3PAR storage system and shows the status as well as used and free space on the volume.
Redfish Power Supply:
The new Redfish Power Supply sensor monitors the status of the power supply of your servers, the power efficiency, and various other parameters.
Redfish System Health:
The new Redfish System Health sensor monitors the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac.
SNMP Rittal CMC III Hardware Status:
The new SNMP Rittal CMC III Hardware Status sensor monitors the hardware status of a Rittal CMC III processing unit and shows the status of every attached external sensor.
Improved:
Sensors:
Modbus sensors:
Modbus RTU Custom and Modbus TCP Custom sensors now support connection sharing for multiple unit IDs on the same device. Previously, connection sharing only worked for a single unit ID on a device, so that you could only create a few Modbus sensors until the maximum number of allowed sessions was reached.
MySQL v2:
The MySQL v2 sensor now supports MariaDB version 10.6 as we updated the MySQL data library that PRTG uses to version 8.0.28.
PostgreSQL:
The PostgreSQL sensor now supports TLS 1.2 connections as we updated the Npgsql library that the PostgreSQL sensor uses to monitor your database to version 6.0.3.
SSH sensors:
We updated the SSH library that SSH sensors use to monitor the target devices. The update improves the security of SSH sensors.
Sensor security:
We updated the logging library log4net that several sensor types use to version 2.0.14 to improve the security of PRTG. Affected sensor types are DICOM sensors, Exchange Mailbox (PowerShell), HL7, NetApp (cDOT/ONTAP) sensors, Windows Update Status (PowerShell), SQL v2 sensors.
Fixed:
Sensors:
Veeam Backup Job Status Advanced:
The Veeam Backup Job Status Advanced sensor now supports the status Postprocessing and shows more expressive error messages in many cases instead of just Reason: Unknown. or The queried field "Reason" is empty.
Fixed:
Server:
XML:
The View as XML button returns data again when you generate the XML from a sensor's Logs tab, for example.
Lab:
Sensors:
Cisco Meraki Network Health
The experimental Cisco Meraki Network Health (BETA) sensor now supports the uplink status not connected.
NetApp Volume v2:
You can try out the experimental NetApp Volume v2 (BETA) sensor that supports the new ONTAP REST API as of ONTAP 9.6 and will be the successor of the existing NetApp Volume sensor.
Improved:
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual
Note:
Sensors:
Python Script Advanced:
PRTG version 22.2.77 that we will publish in June 2022 will include a new Python distribution. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.9 when you update to PRTG 22.2.77.
You only need to consider the change if you are using the Python Script Advanced sensor. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/90484.

New in PRTG Network Monitor 22.1.75.1594 (Mar 30, 2022)

New in PRTG Network Monitor 22.1.75.1589 (Mar 24, 2022)

New in PRTG Network Monitor 22.1.75.1569 (Mar 15, 2022)

Improved:
Security:
Server:
PRTG now sanitizes channel names to close a potential XSS vulnerability. (CVE-2021-42695)
Improved:
Sensors:
Packet Sniffer:
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 1.60. The new version includes several fixes and improvements compared to the previously delivered version 1.10.
Improved:
Server:
Single sign-on:
You have now the option to use GraphQL to retrieve group claims from Microsoft Graph when you integrate Azure Active Directory for single-sign on (SSO) in PRTG. With GraphQL, you can also properly create SSO user accounts that are member of more than 200 groups. The default approach for group claim retrieval is using an Access token as before.
The login with a new SSO user account now succeeds even if there already is a user account with the same login name that only differs in upper case and lower case letters.
Fixed:
Sensors:
HTTP Push Data Advanced:
We improved the stability of the HTTP Push Data Advanced sensor. In previous versions, the sensor occasionally showed a down status with the error message could not bind socket after some time. The issue appeared in cases when there were more than one sensor of this type running.
Microsoft Azure sensors:
Microsoft Azure sensors now can handle all name strings as specified in the Resource name rules by Microsoft. In previous versions, the Microsoft Azure SQL sensor, for example, could not handle whitespaces in elastic pool names and showed HTTP error 400 after creation.
SQL v2 sensors:
SQL v2 sensors show data table values in the sensor message again if you enable the Use Data Table Value in Sensor Message setting. In previous versions, the defined value of the data table was missing in the message of the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, PostgreSQL, and Oracle SQL v2.
Syslog Receiver:
We improved the reliability of the Syslog Receiver sensor in case of probe restarts to reduce issues with blocked ports.
Fixed:
Server:
Historic data:
You can generate historic data files in XML and CSV format via the web interface again. In the previous version, running historic data reports for sensors did not work via the web interface and returned an Unauthorized error if the file format was XML or CSV.
Stability:
This version comes with a number of stability improvements for the PRTG core server.
Lab:
Sensors:
Cisco Meraki sensors:
We improved the connection stability of the Cisco Meraki License (BETA) and Cisco Meraki Network Health (BETA) sensors. The sensors now also handle HTTP response code 429 that returns in case of breached request limits in a more comprehensible way.
The meta-scan for available monitoring objects when adding the Cisco Meraki Network Health (BETA) sensor now succeeds even if the API access is disabled for some organizations so that you can still add the sensor in such cases.
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.
The experimental Redfish Power Supply (BETA) sensor can also monitor devices that return null for non-existent values. In previous versions, the sensor showed a down status in such cases.
You can easier find Redfish sensors in the Add sensor dialog when you look for sensors that monitor devices of a specific vendor because the sensor descriptions now show supporters of the Redfish standard like Broadcom, Dell, Emerson, HPE, Intel, Lenovo, Microsoft, Supermicro, and VMware.
REST Custom v2:
You can now define up to 5 individual placeholders for the experimental REST Custom v2 (BETA) sensor in the Credentials for REST API settings of devices. You can use the placeholders, as well as newly introduced placeholders for credentials, in the Request URL, POST Body, and Custom Header fields of the REST Custom v2 sensor. PRTG does not display the corresponding values in the sensor log nor in the sensor settings.
Lab:
New UI:
Device list:
You can now select the Device List view to see all devices on root group, probes, or groups.
Web interface:
The Welcome page and the page footer now contain information about the installed PRTG version and the selected release channel.
Down (Acknowledged) status icons on the monitoring overview are no longer cropped.
Controls:
The Open new UI button in the classic PRTG web interface in German language no longer causes the global sensor status symbols to overlap the search box.
Tables:
We updated the style of linked sensor names in tables.
Lab:
New API:
POST Requests:
We increased the maximum size of the request body of POST requests to 15 kB.
Sensors:
The Core Health (Autonomous) sensor now keeps working as expected if you deactivate the new UI and API.
The Sensor Factory sensor now sends added and deleted channels to the sensor data and overview endpoints of the new API as expected.
Certificates:
The PRTG application server does not use a hard-coded fallback certificate anymore. If the PRTG application server cannot load the provided certificate, it stops the startup process.
Performance:
We have increased the performance of the PRTG application server.
Documentation:
We improved the documentation.
Lab:
PRTG Desktop:
Probe transfer:
We improved the stability of the probe transfer when transferring large probe configuration files.
Improved:
Various:
Languages:
We updated and improved all language files.
All parts of PRTG:
Various other minor fixes and improvements, updated user manual

New in PRTG Network Monitor 22.1.74.1869 (Feb 1, 2022)

IMPROVED:
SECURITY:
Server:
We hardened PRTG against Cross Site Request Forgery (CSRF) attacks. This prevents changes to PRTG via web forms not originating from PRTG that attackers may use to trick PRTG users into performing requests with the user account's context. (CVE-2021-34547)
SENSORS:
AWS Cost:
You can now create device templates that include the AWS Cost sensor. You can use the device templates to add AWS Cost sensors via auto-discovery.
DNS v2:
The DNS v2 sensor now also considers the authority section of the DNS response when counting and matching DNS records.
Monitoring PTR records now works the same way as with the DNS v1 sensor. You can only provide the IP address as Domain Name and do not need to manually add .in-addr.arpa anymore.
Veeam Backup Job Status Advanced:
You can now also monitor file share backup jobs with the Veeam Backup Job Status sensor and with the Veeam Backup Job Status Advanced sensor. The sensors did not support this job type before. We also fixed the monitoring of replica and immediate backup copy jobs for which the sensors showed incorrect data in previous versions.
We renamed the default primary channel Status of the Veeam Backup Job Status Advanced sensor to Last Result, which makes it clearer that this channel shows the status of the last backup job run. The separate Status channel that now appears shows the overall status of the backup job.
CHANGED:
SENSORS:
Oracle Tablespace:
We changed the name of the Database Size channel of the Oracle Tablespace sensor to Tablespace Size. Tablespace Size is the correct naming because this is what the channel monitors. The same is for the Tablespace Size on Disk channel that we accordingly changed as well.
SSL Security Check:
We changed the TLS 1.1 (Strong) channel of the SSL Security Check sensor to TLS 1.1 (Weak). This means that the sensor will now show a warning status if the target device accepts TLS 1.1 connections. We also changed the TLS 1.2 (Perfect) channel to TLS 1.2 (Strong), which comes without a changed behavior for the sensor status.
CHANNEL UNITS:
Channel Unit Configuration:
We changed the default channel units for probes, group, devices and sensors. New PRTG installations and newly created probes, group, devices, and sensors with turned off inheritance now have the following units defined by default as you can check in the Channel Unit Configuration settings.
Bytes (Bandwidth): MB and Mbit/sec
Bytes (Memory): GB
Bytes (Disk): GB
Bytes (File): MB
The default units on existing PRTG installations are not changed and still have KB and kbit/second for bandwidth, MB for memory, MB for disk, and bytes for file.
FIXED:
SENSORS:
SNMP Cisco CBQoS:
Running an auto-discovery with a device template that includes SNMP Cisco CBQoS sensors now successfully adds sensors of this type. In previous versions, this did not work due to incorrect entries for this sensor type in created device templates and the sensors were not added.
SERVER:
API:
Filtering in table API calls returns only exact matches again. In previous versions, the filter also returned objects if it matched their prefixes.
Cluster:
PRTG properly synchronizes the settings of notification templates from the master node to failover nodes again. In previous versions, defined settings of newly created notification templates were not taken over on failover nodes, which could result in notifications not being sent from a failover.
Down (Acknowledged)
The sensor message of sensors in Down (Acknowledged) status shows the original error message again. The error message was missing for acknowledged sensors in previous versions.
Installation:
The command line parameter /LANG for the language used in PRTG works again when installing PRTG via command line as specified in the Knowledge Base article What command line codes and exit codes can I use with Paessler setups? You can now even use /LANG for silent installations. In previous version, PRTG was always installed with the default English language file when using the command line for setup.
Libraries
We fixed the: channel selection of notification triggers in cloned libraries. In previous versions, you could not select a sensor channel in the settings of speed, threshold, and volume triggers if the library was a clone.
Limits:
You can save changes to sensor channels again even if another channel of the same sensor has the setting Enable alerting based on limits with no defined limits activated. In previous versions, the input validation failed in such cases and you received an Error (Bad Request) dialog window with the message The validation of the data you entered failed. You have set Alerting to limit-based, but have entered no limit value.
LAB:
SENSORS:
Cisco Meraki License:
You can try out the experimental Cisco Meraki License (BETA) sensor as of this version and monitor the status of your Meraki licenses. It shows days to expiration, license model, and license count.
Cisco Meraki Network Health:
You can try out the experimental Cisco Meraki Network Health (BETA) sensor as of this version and monitor the health of Cisco Meraki network devices.
FortiGate VPN Overview:
You can try out the experimental FortiGate VPN Overview (BETA) sensor as of this version and monitor VPN connections of your Fortinet FortiGate firewall. The sensor shows the number of connected SSL clients, as well as the number of both up and down IPsec tunnels.
REST Custom v2:
The REST Custom v2 (BETA) sensor now supports Boolean values. If you select content type JSON and value type Integer, the sensor can map a Boolean value (false or true) to 0 or 1. Use Boolean lookups to get a neat display of the channel on the sensor overview tab.
You can now also use email addresses in the Request URL of the REST Custom v2 (BETA) sensor. In previous versions, the sensor did not work with such URLs.
NEW UI:
Context menus:
You can now open the corresponding context menu if you right-click linked objects or headers.
Devices:
You can now sort sensor lists based on the time since the last scan.
Notifications:
Line breaks in notifications no longer break up single words.
NEW API:
Sensors;
Sensors now immediately display measurements after the start of the PRTG application server regardless of the sensor’s scanning interval.
Documentation:
We improved the documentation.
PRTG application server:
The PRTG application server can now always establish a connection to a PRTG core server via the default IP address 127.0.0.1:23580.
Incoming channel information do not longer cause out-of-memory errors that led to crashes of the PRTG application server.
We fixed an issue that caused high memory consumption by the 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.
MULTI-PLATFORM PROBE:
Supported platforms:
The multi-platform probe now supports ARM based systems with either ARMv7 or aarch64 architecture. This enables you to deploy your probe on systems like Raspberry Pi, AWS EC2 with Graviton CPU, and NAS systems, for example. See the Knowledge Base for more details: What is the Multi-Platform Probe and how can I use it?
PRTG DESKTOP:
Probe transfer:
You can now allow PRTG Desktop to access the configuration files of your probes to transfer a probe to another server. You find the setting Probe Transfer in the Experimental Features section of the PRTG web interface.
TREE VERSION:
Tree version update:
The configuration file of this version is not downwards compatible with previous PRTG versions.
Various other minor fixes and improvements, updated user manual, updated German and Dutch language files

New in PRTG Network Monitor 22.1.74 Beta (Jan 18, 2022)

Security:
Server:
We hardened PRTG against Cross Site Request Forgery (CSRF) attacks. This prevents changes to PRTG via web forms not originating from PRTG that attackers may use to trick PRTG users into performing requests with the user account's context. (CVE-2021-34547)
Note: API calls now always explicitly require credentials even if the user account is currently logged in in PRTG. Otherwise, PRTG will return Unauthorized. If you have issues with saving changes to settings, clear your browser cache with CTRL+F5 after updating and opening the PRTG web interface because we also updated the JavaScript version with this security improvement.
Sensors:
AWS Cost:
You can now create device templates that include the AWS Cost sensor. You can use the device templates to add AWS Cost sensors via auto-discovery.
DNS v2
The DNS v2 sensor now also considers the authority section of the DNS response when counting and matching DNS records.
Monitoring PTR records now works the same way as with the DNS v1 sensor. You can only provide the IP address as Domain Name and do not need to manually add .in-addr.arpa anymore.
Veeam Backup Job Status Advanced:
You can now also monitor file share backup jobs with the Veeam Backup Job Status sensor and with the Veeam Backup Job Status Advanced sensor. The sensors did not support this job type before. We also fixed the monitoring of replica and immediate backup copy jobs for which the sensors showed incorrect data in previous versions.
We renamed the default primary channel Status of the Veeam Backup Job Status Advanced sensor to Last ResultStatus channel that now appears shows the overall status of the backup job.
Sensors:
Oracle Tablespace:
We changed the name of the Database Size channel of the Oracle Tablespace sensor to Tablespace Size. Tablespace Size is the correct naming because this is what the channel monitors. The same is for the Tablespace Size on Disk channel that we accordingly changed as well.
SSL Security Check:
We changed the TLS 1.1 (Strong) channel of the SSL Security Check sensor to TLS 1.1 (Weak). This means that the sensor will now show a warning status if the target device accepts TLS 1.1 connections. We also changed the TLS 1.2 (Perfect) channel to TLS 1.2 (Strong), which comes without a changed behavior for the sensor status.
Channel units:
Channel Unit Configuration:
We changed the default channel units for probes, group, devices and sensors. New PRTG installations and newly created probes, group, devices, and sensors with turned off inheritance now have the following units defined by default as you can check in the Channel Unit Configuration settings.
The default units on existing PRTG installations are not changed and still have KB and kbit/second for bandwidth, MB for memory, MB for disk, and bytes for file.
Sensors:
SNMP Cisco CBQoS:
Running an auto-discovery with a device template that includes SNMP Cisco CBQoS sensors now successfully adds sensors of this type. In previous versions, this did not work due to incorrect entries for this sensor type in created device templates and the sensors were not added.
Server:
API:
Filtering in table API calls returns only exact matches again. In previous versions, the filter also returned objects if it matched their prefixes.
Cluster
PRTG properly synchronizes the settings of notification templates from the master node to failover nodes again. In previous versions, defined settings of newly created notification templates were not taken over on failover nodes, which could result in notifications not being sent from a failover.
Down (Acknowledged)
The sensor message of sensors in Down (Acknowledged) status shows the original error message again. The error message was missing for acknowledged sensors in previous versions.
Installation:
The command line parameter /LANG for the language used in PRTG works again when installing PRTG via command line as specified in the Knowledge Base article What command line codes and exit codes can I use with Paessler setups? You can now even use /LANG for silent installations. In previous version, PRTG was always installed with the default English language file when using the command line for setup.
Libraries:
We fixed the channel selection of notification triggers in cloned libraries. In previous versions, you could not select a sensor channel in the settings of speed, threshold, and volume triggers if the library was a clone.
Limits
You can save changes to sensor channels again even if another channel of the same sensor has the setting Enable alerting based on limits with no defined limits activated. In previous versions, the input validation failed in such cases and you received an Error (Bad Request) dialog window with the message The validation of the data you entered failed. You have set Alerting to limit-based, but have entered no limit value.
Sensors:
Cisco Meraki License:
You can try out the experimental Cisco Meraki License (BETA) sensor as of this version and monitor the status of your Meraki licenses. It shows days to expiration, license model, and license count.
Cisco Meraki Network Health:
You can try out the experimental Cisco Meraki Network Health (BETA) sensor as of this version and monitor the health of Cisco Meraki network devices.
FortiGate VPN Overview:
You can try out the experimental FortiGate VPN Overview (BETA) sensor as of this version and monitor VPN connections of your Fortinet FortiGate firewall. The sensor shows the number of connected SSL clients, as well as the number of both up and down IPsec tunnels.
REST Custom v2:
The REST Custom v2 (BETA) sensor now supports Boolean values. If you select content type JSON and value type Integer, the sensor can map a Boolean value (false or true) to 0 or 1. Use Boolean lookups to get a neat display of the channel on the sensor overview tab.
You can now also use email addresses in the Request URL of the REST Custom v2 (BETA) sensor. In previous versions, the sensor did not work with such URLs.
New UI:
Context menus:
You can now open the corresponding context menu if you right-click linked objects or headers.
Devices:
You can now sort sensor lists based on the time since the last scan.
Notifications:
Line breaks in notifications no longer break up single words.
New API:
Sensors:
Sensors now immediately display measurements after the start of the PRTG application server regardless of the sensor’s scanning interval.
Documentation:
We improved the documentation.
PRTG application server:
The PRTG application server can now always establish a connection to a PRTG core server via the default IP address 127.0.0.1:23580.
Incoming channel information do not longer cause out-of-memory errors that led to crashes of the PRTG application server.
We fixed an issue that caused high memory consumption by the 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.
PRTG Desktop:
Probe transfer:
You can now allow PRTG Desktop to access the configuration files of your probes to transfer a probe to another server. You find the setting Probe Transfer in the Experimental Features section of the PRTG web interface.
Tree version:
Tree version update:
The configuration file of this version is not downwards compatible with previous PRTG versions.
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual

New in PRTG Network Monitor 21.4.73.1656 (Dec 1, 2021)

NEW:
Notifications:
OPC UA:
You can now use OPC UA notifications to forward PRTG alerts to your northbound systems like SCADA, DCS, or any other system that has an OPC UA server. By creating an OPC UA notification template, you can build meaningful error messages that PRTG sends to your OPC UA server. This supports you in seeing and reacting on issues in your network infrastructure as fast as possible.
IMPROVED:
Sensors:
Business Process:
Requesting data of the Business Process sensor via the API now returns values in value_raw fields in a better consumable way.
DNS v2:
You can now define multiple filter values for the DNS v2 sensor to filter for more than one IP address, for example.
Modbus sensors:
The sensor types Modbus RTU Custom and Modbus TCP Custom now provide a timeout setting. If the reply from the target device takes longer than the defined Receive Timeout (msec), the request will be aborted and the sensor stops trying to connect.
CHANGED:
Sensors:
Lookups:
You can now easier identify sensors with a missing or broken lookup file. Sensors that have an issue with their lookups will change their status to warning with the message At least one channel uses a lookup that is not available or could not be loaded. (PE272) as of this version to indicate that the sensor cannot properly monitor. In previous versions, you only received a ToDo ticket in such cases but affected sensors kept their status.
Microsoft 365 Service Status sensors:
The sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced support the new Microsoft 365 Service Health and Communications Graph API as of this version. This change is necessary to seamlessly continue monitoring your Microsoft 365 services because Microsoft soon will shut down the current API version that the sensors used until now.
Important: Both sensors now require the API permission ServiceHealth.Read.All to be able to retrieve data from Microsoft Graph and continue monitoring.
Scanning interval:
We changed the default scanning interval for several newer sensor types that we introduced over the last couple of PRTG versions.
FIXED:
Sensors:
Microsoft Azure Virtual Machine:
The Microsoft Azure Virtual Machine sensor now shows a down status with an appropriate error message if the target device is not reachable anymore, for example, due to changed credentials. In previous versions, the sensor incorrectly showed a misleading up status with 0 values in such cases. We also improved the general stability of the sensor.
WebGUI:
Channel Unit Configuration:
The dropdown menu for the unit of Bytes (Bandwidth) in the Channel Unit Configuration settings is properly shown again. In Google Chrome and Edge, it was difficult to select the desired unit due to display issues in previous versions.
LAB:
Sensors:
AWS v2 sensors:
We implemented various improvements for the experimental AWS v2 sensors.
The metric channel of the AWS Alarms v2 (BETA) sensor now shows a proper unit.
The AWS EC2 v2 (BETA) sensor now only creates the channels Disk Read, Disk Read Ops, Disk Write, and Disk Write Ops if they receive values.
We added a lower error limit to the CPU Credit Balance channel of the AWS EC v2 (BETA) and AWS RDS v2 (BETA) sensors. Channel values below 1 will now trigger a down status because they indicate low performance.
We generally hardened the approach how AWS v2 sensors retrieve data to avoid gaps in the sensor data.
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.
New UI:
Initial alpha release:
We are working on a complete redesign of the PRTG web interface. The redesign is based on extensive user research and the feedback that we have received over the years. The user interface will be fully responsive and will follow the Web Content Accessibility Guidelines (WCAG).
New API:
Initial alpha release:
Our new RESTful API will enable you to easily automate your monitoring and to integrate it with other tools. Our goal is to build a comprehensively documented RESTful API that is consistent across all endpoints.
Multi-platform probe:
Initial alpha release:
The new multi-platform probe will enable you to deploy PRTG probes on various platforms like Windows, Linux, and Docker.
IMPROVED:
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual, updated German and French language files

New in PRTG Network Monitor 21.4.73.1581 (Nov 21, 2021)

New in PRTG Network Monitor 21.4.73.1545 (Nov 15, 2021)

New:
Notifications:
OPC UA You can now use OPC UA notifications to forward PRTG alerts to your northbound systems like SCADA, DCS, or any other system that has an OPC UA server. By creating an OPC UA notification template, you can build meaningful error messages that PRTG sends to your OPC UA server. This supports you in seeing and reacting on issues in your network infrastructure as fast as possible.
Improved:
Sensors:
Business Process Requesting data of the Business Process sensor via the API now returns values in value_raw fields in a better consumable way.
DNS v2 You can now define multiple filter values for the DNS v2 sensor to filter for more than one IP address, for example.
Modbus sensors The sensor types Modbus RTU Custom and Modbus TCP Custom now provide a timeout setting. If the reply from the target device takes longer than the defined Receive Timeout (msec), the request will be aborted and the sensor stops trying to connect.
Changed:
Sensors:
Lookups: You can now easier identify sensors with a missing or broken lookup file. Sensors that have an issue with their lookups will change their status to warning with the message At least one channel uses a lookup that is not available or could not be loaded. (PE272) as of this version to indicate that the sensor cannot properly monitor. In previous versions, you only received a ToDo ticket in such cases but affected sensors kept their status.
Microsoft 365 Service Status sensors The sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced support the new Microsoft 365 Service Health and Communications Graph API as of this version. This change is necessary to seamlessly continue monitoring your Microsoft 365 services because Microsoft soon will shut down the current API version that the sensors used until now.
Important: Both sensors now require the API permission ServiceHealth.Read.All to be able to retrieve data from Microsoft Graph and continue monitoring. For details, please see the Knowledge Base article How do I obtain credentials and set permissions for the Microsoft 365 sensors?
Please also note that the Microsoft 365 Service Status Advanced sensor cannot monitor subservices anymore and will show the message Channel is deprecated for affected channels. We will remove the channels in an upcoming PRTG version.
Scanning interval
We changed the default scanning interval for several newer sensor types that we introduced over the last couple of PRTG versions.

New in PRTG Network Monitor 21.4.72.1649 (Oct 26, 2021)

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

New in PRTG Network Monitor 21.3.71.1416 (Sep 21, 2021)

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

New in PRTG Network Monitor 21.3.70.1629 (Aug 17, 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.
Improved:
Sensors:
Microsoft 365 sensors
You can now create device templates that include the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced. This enables you to add these sensors via auto-discovery.
Modbus TCP Custom
We implemented session sharing for the Modbus TCP Custom sensor and the experimental Modbus RTU Custom sensor. Session sharing reduces the load on the monitored system compared to previous PRTG versions where each sensor created its own connection to the Modbus gateway.
OPC UA Custom
The OPC UA Custom sensor now supports up to 10 channels so that you can monitor up to 10 values returned by specific OPC UA node IDs with one sensor of this type.
WMI Event Log
The WMI Event Log sensor now supports filtering by multiple event IDs.
Zoom Service Status
You can now create device templates that include the Zoom Service Status sensor. This enables you to add sensors of this type via auto-discovery.
Fixed:
Sensors:
MySQL (v1)
Still existing instances of the deprecated sensor type MySQL (v1) work again and continue monitoring upon updating to PRTG 21.3.70 or later. In PRTG versions 21.2.68 and 21.3.69, they showed a down status with the error message parameter -sslmode is missing. Please note that we strongly recommend that you replace all sensors of the deprecated type MySQL (v1) with the MySQL v2 sensor.
SNMP Custom Table
Adding SNMP Custom Table sensors with an identification column other than table_index or ifindex properly works again. In previous versions, the sensors showed a down status after creation with error code PE247 in such cases.
Fixed:
Server:
Active Directory:
We fixed an issue with the login of Active Directory user accounts. If the display name or full name of a user in the Active Directory contained certain special characters like, for example, ampersand (&), a newly introduced security mechanism blocked the login in the last PRTG version 21.3.69. This also affected PRTG user accounts with two or more consecutive whitespaces in login or display name.
Cluster
Failover nodes in a PRTG cluster now keep the password of the PRTG System Administrator user account when you have changed it. In previous versions, the administrator password on failover nodes always reverted to default upon updating the PRTG server.
Important: The PRTG default login with password prtgadmin will not work on failover nodes anymore upon updating to PRTG 21.3.70 or later. Please use the PRTG Administration Tool on the failover node to generate a new password.
Device templates
We fixed an issue with certain sensor types like the SNMP HPE ProLiant Memory Controller sensor that, if included, prevented a successful creation of device templates. The created template did not appear in the list of device templates in such cases.
Single sign-on
We fixed an issue with external callback URLs for the endpoint handling that included uppercase letters. In such cases, you could not login into PRTG via single sign-on and received the error message The URL you are using to connect to PRTG is not enabled for single sign-on.
Time zones
Status messages of down (acknowledged) and paused sensors now show the time zone of the user account instead of the server time. In the logs, the messages are displayed in server time.
Fixed:
WebGUI:
Home page URL:
Home page URLs with URL parameters that you define for PRTG user groups work again. In previous versions, parameters were removed from the URL so that the you did not land on the defined home page when you logged in into the PRTG web interface.
Internet Explorer
Adding new notification triggers and displaying existing triggers in Internet Explorer 11 works again.
Lab:
Sensors:
AWS EC2 v2 and AWS ELB v2:
We added comprehensible region names to the channels of the experimental AWS EC2 v2 and AWS ELB v2 sensors.
Local Folder
We introduce the experimental Local Folder (BETA) sensor with this version. The sensor monitors the number of files and folders in a local folder on the probe device, as well as its size and the age of oldest and newest files.
Redfish System Health
You can try out the experimental Redfish System Health (BETA) sensor as of this version. With this sensor, you can monitor the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac.
Improved:
Various:
Languages:
We updated and improved all language files.
All parts of PRTG
Various other minor fixes and improvements, updated user manual

New in PRTG Network Monitor 21.3.69.1333 (Jul 6, 2021)

new Sensors:
Veeam Backup Job Status Advanced:
The new Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs on the Veeam Backup Enterprise Manager. The sensor monitors the status of the backup job, the duration, the time since the last run, and if the backup job is scheduled.
We released this sensor type as experimental sensor in PRTG 21.1.65 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we resolved two more issue for this release.
Adding a new Veeam Backup Job Status Advanced sensor works more reliably now. In certain scenarios, you could not add the sensor and received the error message An error occurred. The queried field is empty.
We added the new lookup value None so that the sensor can now handle the combination job status idle and job result none. Previously, the sensor showed a down status with the error message An error occurred: Bad optional access in such cases.
Dell EMC Unity Enclosure Health:
The Dell EMC Unity Enclosure Health v2 sensor now can also monitor Power Consumption in a dedicated channel.
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.
Security:
Active Directory:
PRTG now validates all fields that are imported from Active Directory when creating a new user account to close a potential XSS vulnerability. (CVE-2021-29643)
Fixed Sensors:
Microsoft Azure sensors:
We improved the stability of the Microsoft Azure sensors. In previous versions, the sensors had connection issues in some cases, which resulted in wrong down and warning states.
DNS v2:
The Records Resolved channel of the DNS v2 sensor correctly uses a lookup with the states yes and no again.
Microsoft 365 Service Status sensors:
We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against unknown service states that Microsoft 365 may return. In such cases, the sensors previously showed a down status with the message error.generic[invalid map key].
SNMP Printer:
We improved the stability of the SNMP Printer sensor. In rare cases, the sensor showed a down status with the message No such instance (SNMP error # 223) after some time when monitoring certain types of printers.
Fixed Server:
API:
API calls for tables with content=probenodes return all probes again.
Auto-Discovery:
Devices now keep their settings even after running an auto-discovery on this device. Previously, the first auto-discovery on a device occasionally overwrote your manually configured settings like names, icons, or tags.
Graphs:
The graph on the 2 days tabs of sensors shows the correct downtime again. In previous versions, the 2 days tab showed a wrong downtime in various cases, for example, always 0% even if there was a downtime reported and correctly shown in the data table. The percentage values on the y-axis of 2 day graphs are also back again.
Single sign-on:
Logging in with single sign-on now also works if you use an Azure AD group name (sAMAccountName) with upper-case letters as SSO Group Access Claim. We also fixed the misbehavior that PRTG logged out SSO user accounts after some time.
Fixed WebGUI:
Maps:
We fixed a display issue on maps that affected channel gauges on View Map tabs. Sometimes, the gauge values of previously opened sensor pages erroneously appeared in gauge map objects instead of the real values until the page was refreshed.
Lab Sensors:
AWS EC2 v2:
You can try out the experimental AWS EC2 v2 (BETA) sensor as of this version. The sensor monitors the performance of an Amazon EC2 and will be the successor of the existing Amazon CloudWatch EC2 sensor.
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:
e fixed the Custom Headers of the REST Custom v2 sensor. In the last PRTG version, sending custom HTTP headers did not work correctly.

New in PRTG Network Monitor 21.2.68.1492 (May 26, 2021)

New:
Login:
You can now login to PRTG via single single-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.
Paessler PRTG Hosted Monitor:
We added the cloud region US East for the hosting option of Paessler PRTG Hosted Monitor. Region transfers of instances between Europe and United States (and vice versa) are now possible. Please contact our support for according inquiries.
Improved:
Sensors:
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.
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.
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.
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.
Server:
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.
Notifications:
We improved the usability of the SMS service provider setup, which will help you to more easily configure SMS notification delivery. All necessary fields now require you to fill them in before saving the settings to ensure you provide all necessary information. By default, the SMS configuration mode is now disabled if you have not had configured SMS delivery before.
Fixed:
Sensors:
EXE/Script and EXE/Script Advanced sensors now escape round brackets in the Parameters field to prevent potential code injection.
We fixed an issue with the MQTT Statistics sensor that showed wrong data after some time of monitoring in certain cases.
We corrected the traffic calculation of NetFlow v9 and IPFIX sensors. The sensors reported too much traffic with certain combinations of flow fields.
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.
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.
Server:
We fixed an issue with API calls that returned no data in certain cases, for example, when querying System Information via /api/table.json.
You can define the same values for upper and lower sensor channel limits again.
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.
We implemented stability improvements for probe connections after a PRTG server restart, which will be especially helpful if you have many remote probes.
Lab:
Sensors:
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!
The experimental Microsoft Azure SQL Database (BETA) now shows correct channel names.
Improved:
Various
We updated the German language file.
Various other minor fixes and improvements, updated user manual.
Note:
Sensors:
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.

New in PRTG Network Monitor 20.4.64.1402 (Nov 24, 2020)

NEW:
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.
IMPROVEMENTS:
Sensors:
Modbus TCP Custom
Thanks to your feedback, we implemented several improvements for the Modbus TCP Custom BETA sensor that we introduced in the last PRTG version.
We improved the usage of the sensor settings.
We increased the range for register addresses.
Register numbers can now start from 0.
You can define a lower scanning interval than 60 seconds.
The sensor log provides more information.
We updated help texts and documentation.
Important: After updating from PRTG 20.4.63 to 20.4.64 or later, you will have to add the sensor anew. Running Modbus TCP Custom sensors will show a down status after you have installed the update due to changes in our underlying Modbus monitoring configuration.
MQTT sensors
You can now create device templates that include the sensor types MQTT Round Trip, MQTT Statistics, and MQTT Subscribe Custom. You can use the device templates to add MQTT sensors via auto-discovery.
MySQL v2
The MySQL v2 sensor now supports authentication with caching_sha2_password on MySQL 8.0 and later. In previous versions, the sensor showed the error message Authentication method 'caching_sha2_password' not supported by any of the available plugin when you tried to monitor MySQL server version 8.0.
OPC UA Server Status
We further improved the OPC UA Server Status BETA sensor that we introduced in the last PRTG version. Thank you for your feedback!
The sensor can now monitor session related metrics if diagnostics data is activated on the server, so that PRTG can notify you if there are too many ongoing sessions or the amount of timeout sessions increases.
We added support for authentication with username and password, as well as you can use encryption and provide a certificate to authenticate the sensor against the OPC UA server.
We improved the general performance of OPC UA sensors in this version by minimizing their network communication.
We drastically reduced the amount of log entries that OPC UA sensors write into the probe.log file.
SSL CERTIFICATE:
The SSL Certificate sensor has a new timeout setting for TCP read requests, which is useful if you monitor a slow server with the sensor.
FIXED:
Sensors:
Cisco IP SLA
Tag and Owner are now in the correct column when adding the Cisco IP SLA sensor. Furthermore, the sensor will not erroneously add a vendors_cisco tag to a device anymore when you run an auto-discovery and the discovered device is not a Cisco device.
Google Analytics
You can add Google Analytics sensors again. The sensor type needed a new OAuth verification by Google to be able to access data.
HTTP Push Data sensors:
HTTP Push Data and HTTP Push Data Advanced sensor 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.
The HTTP Push Data Advanced sensor now applies the unit to a channel value if provided in the push message and as defined in the Channel Unit Configuration settings.
HTTP Transaction:
Smart URL Replacement in the HTTP Transaction sensor now even works if you use the Alternate/Compatibility Mode as Monitoring Engine. In previous versions, the URL replacement only worked with the recommended default monitoring engine. Please note that support for ports in smart URL replacement when using the compatibility mode will only come with a later version.
SNMP Custom Table
We fixed an issue with SNMP Custom Table sensors that are created via auto-discovery. In certain cases, the sensors were created with invalid IDs and uncommon sensor names and immediately showed a down status after creation.
SQL v2 sensors
We fixed an issue with SQL v2 sensors that caused a down status with the message Error: An item with the same key has already been added because PRTG did not properly reset the parameters after a sensor timeout.
WMI sensors
The auto-discovery with template can add certain WMI sensors again. In previous versions, you could not add the sensor types WMI Exchange Server, WMI Sharepoint Process, and WMI Vital System Data v2 sensors, for example, by using an auto-discovery with template.
FIXED:
Server:
Active Directory:
If you change the Login Name of an Active Directory user account in PRTG, it is not possible anymore to login with the changed login name because this user account does not exist in the Active Directory. The login with the original login name still works and will create a new Active Directory user account in PRTG. In previous version, the behavior in such cases was unreliable.
API
We fixed an issue with historic data queries via the PRTG API. In certain scenarios, the queries could take too much time since we improved the memory consumption of historic data queries in PRTG 20.1.57.
Config
We fixed a potential deadlock that could happen when PRTG saved the configuration, resulting in a server crash in rare cases.
Languages
The Local Probe now keeps its name after a server restart in Japanese, Russian, and Chinese language versions. In previous versions, the name of the probe was overridden by question marks (??) after a restart.
Login
We fixed an issue with the login of PRTG user accounts that occurred in rare cases when changing the password of a user who was logged in into PRTG Desktop at the same time. A re-login was not possible for some time in such cases.
Maps
We fixed a potential deadlock that could happen in rare cases when using the Map Designer. PRTG became unresponsive in such cases and required a server restart to work again.
Multi-Edit:
You can edit the settings of multiple devices, groups, and probes at once again. In previous versions, multi-edit on these objects resulted in an error with the message The validation of the data you entered has failed when you saved your changes.
Multi-editing limits of sensors now properly works for sensors with channels that display data in percent of the maximum value. In previous versions, the applied limit values were incorrect if two or more multi-edited channels had different maximum values.
Notification Templates:
We removed some redundant entries from the History tab of notification templates that still appeared on 64-bit installations of PRTG.
Reports
Links to sensors and devices in PDF reports work again. In previous versions, the links included a wrong port and could not be opened.
Uninstall
We fixed an issue that prevented a clean uninstall of PRTG on Windows 10 Pro 64-bit instances.
WebGUI:
Libraries:
You can collapse and expand library nodes again.
System Information:
Data:
The System table on System Information tabs shows data for specific SNMP devices again. In previous versions, PRTG could not retrieve system information data from SNMP devices if an interface had multiple IP addresses. You received the message Error: duplicates not allowed in this case.
PRTG for Android:
Sorting:
Sorting by status in the alarms section of PRTG for Android corresponds to the sorting in the web interface again if you connect your app to PRTG version 20.4.64 and later.
Note:
Sensors:
Beta Sensors:
The following sensor types are not in beta status anymore and are now fully supported.
AWS Cost
Cloud HTTP v2
Cloud Ping v2
DNS v2
Microsoft 365 Service Status
Microsoft 365 Service Status Advanced
MQTT Round Trip
MQTT Statistics
SNMP Nutanix Cluster Health
SNMP Nutanix Hypervisor
SNMP Fujitsu System Health v2
WMI Microsoft SQL Server 2019
Zoom Service Status
Experimental Sensors:
We added two new experimental sensors that you can manually enable.
Microsoft Azure SQL Database: The experimental Microsoft Azure SQL Database sensor monitors your Microsoft Azure SQL Database instances so that you are notified if there is an issue with your SQL instance. The sensor in the current experimental status has the known issue that the sensor will stop working as expected it if the database type changes or has changed from vCore to DTU or vice-versa. If you try out the sensor and encounter this issue, we would kindly ask you to contact us and provide the sensor logs if possible. This will help us to further develop the sensor.
Modbus RTU Custom: The experimental Modbus RTU Custom sensor monitors up to 5 values that your Modbus RTU device returns.
Improved:
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual, updated German language file

New in PRTG Network Monitor 20.3.63.1427 (Oct 29, 2020)

New in PRTG Network Monitor 20.3.63.1412 (Oct 20, 2020)

New:
Sensors
Dell EMC Unity VMware Datastore v2
The new Dell EMC Unity VMware Datastore v2 BETA sensor monitors a VMware datastore on your Dell EMC Unity storage system. With this sensor type, you can keep track of the free size of a VMware datastore on your Dell EMC storage, as well as you will always see the number of hosts, virtual machines, and virtual drives at a glance.
Microsoft Azure Virtual Machine
The new Microsoft Azure Virtual Machine BETA sensor monitors the status of a virtual machine in a Microsoft Azure subscription. Additionally to the overall status of a virtual machine, you can also monitor CPU usage as well as used and remaining CPU credits with this sensor. This will help you to act before your credits run out and the virtual machine stops.
Modbus TCP Custom
The new Modbus TCP Custom BETA sensor monitors values that your Modbus TCP server returns. With this new sensor type, you can keep an eye on your environment equipment like cooling units, power supply, backup generators, and temperature. This helps you to ensure your infrastructure always runs at its best.
OPC UA Server Status
The new OPC UA Server Status BETA sensor monitors status, uptime, and diagnostic information of your OPC UA server. With this new sensor type you can ensure your devices are available using OPC UA and your production processes run flawlessly.
In this version, you can also try out an experimental OPC UA Custom sensor that you can manually enable. The sensor monitors multiple nodes of OPC UA servers and returns the contained values.
Soffico Orchestra Channel Health
The new Soffico Orchestra Channel Health BETA sensor monitors the availability of the Soffico Orchestra API and shows the status and overall number of successful and failed channel calls.
Improved:
Cloud HTTP v2
The Cloud HTTP v2 BETA sensor now supports Smart URL Replacement like other HTTP sensors. With this functionality, you can easier define custom URLs that you want to monitor with this sensor type.
Exchange (PowerShell) sensors
You can now monitor Exchange Server 2019 with all Exchange (PowerShell) sensors. The sensor types support all Exchange server versions as of 2010.
Exchange Backup (PowerShell)
Exchange Database DAG (PowerShell)
Exchange Database (PowerShell)
Exchange Mailbox (PowerShell)
Exchange Mail Queue (PowerShell)
Exchange Public Folder (PowerShell)
SNMP Cisco ASA VPN Connections:
We improved the error handling of the SNMP Cisco ASA VPN Connections sensor. In cases where the requested OID of a channel is missing on the target device, the OID is now shown in the sensor message with according information and the sensor keeps its status. In previous versions, the sensor showed a down status with the error message "No such object" (SNMP error # 222) in such cases even if other channels were able to retrieve data.
SNMP Cisco ASA VPN Traffic
We added the option to monitor VPN connections that work with IKEv2 tunnels to the SNMP Cisco ASA VPN Traffic sensor. You can choose the new IKEv1 and IKEv2 option in the IKE Version Handling section of the sensor settings in this case.
Note: This option is in beta status and might not work properly in every case, so we would love to hear your feedback about it. Please send it to [email protected].
Changed:
Microsoft 365 Service Status
Degraded services in the Microsoft 365 Service Status BETA sensor now result in a warning status instead of down by default. This change also corresponds to the status definition of degraded services in the Microsoft 365 Service Status Advanced BETA sensor, where degraded services were always defined as warning status.
Improved:
Notifications
Notification Templates
We improved the content of the History tab for notification templates. The history of a notification template now only shows one entry per creation or modification and only the settings that were actually changed. The entries have a clearer wording aligned to other places in the web interface and referenced objects are written with both their name and ID. This will help you with tracking the creation and changes of a specific notification template.
Notification Triggers
You can now define if you want to inherit notification triggers from parent objects for new sensor types. Several sensor types that we added over the last few PRTG versions were missing the inherit option on their Notification Triggers tab and showed the message (Property not found) instead.
Server
Libraries
We slightly improved the performance of libraries by changing the approach of how libraries are calculated to event-based instead of doing regular polling. You will especially benefit from this improvement if you have libraries with a high amount of sensors.
Fixed:
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.
WebGUI:
System Information
The column headers of tables on System Information pages are correctly displayed again.
Improved:
Various
Language Files
We updated the German and Japanese language files.
All parts of PRTG
Various other minor fixes and improvements, updated user manual
Changed:
Tree version
Tree version update:
The configuration file of this version is not downwards compatible with previous PRTG versions.

New in PRTG Network Monitor 20.3.62.1397 (Sep 15, 2020)

New in PRTG Network Monitor 20.3.61.1649 (Aug 11, 2020)

New in PRTG Network Monitor 20.3.60.1623 (Jul 7, 2020)

Improved:
Sensors:
Amazon CloudWatch sensors:
We added the region Europe (Stockholm) (eu-north-1) to all Amazon CloudWatch sensors so that you are able to monitor AWS instances located there.
VMware Host Hardware (WBEM)
We added a lookup file for the Healthstate channel of the VMware Host Hardware (WBEM) sensor to visualize the health status in a more comprehensible way.
Note: To apply the new lookup file prtg.standardlookups.esxelementhealthsensor.healthstate, you have to add running sensors of this type anew.
WMI Disk Health and WMI Storage Pool
We added the WMI Disk Health sensor to the standard auto-discovery, and the WMI Storage Pool sensor to the detailed auto-discovery. We also removed the beta status from both sensor types. They are now fully supported. Thank you for your feedback!
Server:
Active Directory:
We added a validation for domain controllers that you can individually define for the PRTG Active Directory integration since the last version 20.2.59. PRTG checks if the IP addresses and DNS names that you enter for primary and backup domain controllers exist and if the according host is a domain controller. If not, you will not be able to save your changes to the settings to avoid issues afterwards.
Dependencies
We improved the performance of the dependency calculation. This is especially noticeable when changing dependencies in larger PRTG installations with several thousands of sensors. PRTG now only uses potentially affected monitoring objects in the device tree to calculate dependencies, which significantly reduces the number of performed operations compared to the previous approach. Previously, all objects were considered for calculation, which could result in frequent Ajax timeouts on some large installations due to the huge number of operations.
Licenses
We improved the license information for PRTG Enterprise Monitor that appears on various places in PRTG to always provide you correct information about your license.
Notifications:
Amazon SNS:
You can now send Amazon Simple Notification Service (SNS) messages to encrypted topics. In previous versions, SNS notifications only worked for non-encrypted topics.
We added new regions to the Location setting of Amazon SNS notifications. You can now choose any region for SNS notifications that AWS currently provides.
SMS Delivery:
You can now use HTTP basic authentication for custom service providers to deliver SMS notifications. If your provider requires authentication, you can define this with the according HTTP Authentication option in your SMS Delivery settings.
Note: Using basic authentication for custom service providers was already possible with a registry key option in previous versions (see the Knowledge Base article Basic authentication for SMS Delivery). If you have applied this registry key, PRTG will still use basic authentication for SMS delivery after updating to the current version.
We added updated endpoints for BulkSMS delivery. You can now choose www.bulksms.co.uk (https/443) or, if you are located in South Africa, bulksms.2way.co.za/ (https/443) to send SMS notifications with BulkSMS. The new endpoints use encryption (HTTPS) and run on a standard port (443). We marked all other entries for BulkSMS in the list of service providers as deprecated and will remove them in an upcoming PRTG version to simplify configuration.
We marked all other entries for BulkSMS in the list of service providers as deprecated and will remove them in an upcoming PRTG version to simplify configuration. We recommend that you update your SMS Delivery settings already now and check that the new endpoints work in your configuration to avoid any issues when we finally remove the deprecated endpoints.
Note: We also removed Clickatell from the list of service providers. This provider is deprecated since PRTG version 17.1.30.
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.
Security:
Web Server:
We fixed a security issue that allowed unauthenticated users to show status information about the PRTG installation. Thanks to Christian Varas for reporting the issue. (CVE-2020-11547)
We fixed a potential XSS vulnerability that could be exploited as part of a chained attack via a malicious URL. Thanks to Dmitry Galecha from Positive Technologies for reporting the issue.
The HTTP session cookie is initialized as secure again. The secure cookie attribute is always set when accessing PRTG via a secure connection.
We fixed a potential XSS vulnerability on alarmsgauges.htm and device.htm.
Sensors:
Minor security fix for the VMware Virtual Machine (SOAP) sensor
Fixed:
Sensors:
EXE/Script Advanced:
The meta-scan of EXE/Script Advanced sensor now supports the placeholders %device and %deviceid as described in the Knowledge Base article Using the Meta-Scan Functionality for EXE/Script Advanced Sensors.
IMAP
If you change the sensor behavior setting of a running IMAP sensor from the count or process emails option back to the default option Check connectivity only, do not process emails, the connectivity check will now also work without valid credentials. In previous versions, the sensor still used the authentication settings to connect to the mailbox in this case.
NetApp I/O
We improved the handling of very big values (64-bit unsigned integer) returned to the NetApp I/O sensor. In previous versions, the sensor showed 0 values in this case due to an issue with the internal value processing.
SNMP Nutanix Hypervisor
e improved the stability of SNMP Nutanix Hypervisor BETA sensors. In previous versions, this sensor type could cause NULL bytes in the PRTG configuration file, resulting in changes to PRTG that were not saved anymore after the NULL bytes appeared.
We aligned the naming of two SNMP Nutanix Hypervisor BETA sensor channels to the official wording of Nutanix. Newly added sensors of this type now create the channels Packets Drop In and Packets Drop Out instead of using the word packages.
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
Performance impact bars in the Add Sensor dialog show the correct help text again when you point your mouse on them.
Performance impact bars for the sensor types DNS v2, MQTT Round Trip, and MQTT Statistics are now also available on sensor pages.
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.
Server:
Auto-Update:
We improved the stability of automatic PRTG updates. In certain cases, the PRTG auto-update did not successfully complete in previous versions and you had to manually install the new PRTG version.
Passwords
We fixed an issue with newly generated PRTG Administrator user passwords using the PRTG Administration Tool, for example, on failover nodes in a cluster. Please log in as PRTG Administrator user at least once after generating a new password and perform a proper server restart to ensure the password keeps working after another PRTG server restart.
Reports
Historic data reports for Sensor Factory sensors contain values again even if you select No Interval (Display Raw Data) as Average Interval.
Languages:
French:
This version comes with the most current French language file again. In the previous PRTG version 20.2.59, we delivered an old French version by accident. Veuillez nous excuser pour la gêne occasionnée.
Various
We updated the German, Japanese, and Dutch language files.
Improved:
Various:
All parts of PRTG
Various other minor fixes and improvements, updated user manual

New in PRTG Network Monitor 20.2.59.1689 (May 26, 2020)

New:
Sensors:
DNS v2
The new DNS v2 BETA sensor monitors a DNS server, resolves domain name records, and compares the records to a defined filter. It shows the response time of the DNS server and if records were resolved, the number of records, as well as the number of records matching the filter. With the help of this monitoring data, you can check if resolving a domain works, if the number of certain records changes, and if a certain record exists for a domain.
In comparison to the already existing DNS sensor, the new DNS v2 sensor provides more features and works more reliable in certain configurations. For your convenience, the original DNS sensor will still work after the update to PRTG 20.2.59, as well as you can still add sensors of this type, but please note that we may deprecate the DNS sensor at some time in the future. Of course, we will inform you in time before the deprecation.
MQTT Statistics
The new MQTT Statistics BETA sensor monitors MQTT topics and shows related statistics of the broker, for example, the number of incoming messages from a subscribed topic and the received payload. With this new sensor type you can check if your IoT devices and the broker still send messages. We are looking forward to hearing your feedback about this new beta sensor! Please send your feedback to [email protected].
Changed:
Sensors:
MQTT Round Trip
This version comes with a completely rewritten MQTT Round Trip BETA sensor. The new version of this sensor type replaces the original MQTT Round Trip BETA sensor.
Any previously deployed MQTT Round Trip BETA sensors will immediately stop working upon updating to PRTG 20.2.59 or later because of the significant changes in the sensor implementation. You have to add the sensors anew after the update to continue your MQTT round trip monitoring. To keep historic data, you can pause existing instances of deprecated sensors.
Improved:
WebGUI:
Maps
We added new map objects for MQTT brokers. This enables you to create maps that visualize the status of your MQTT brokers on your dashboards so that you can identify the status right away. You find the new map objects in the map designer sections Default A and Default B.
Improved:
Sensors:
Amazon CloudWatch sensors
This version includes a minor security improvement for Amazon CloudWatch sensors.
AWS Cost
We added the setting sections "Scanning Interval", "Schedules, Dependencies, and Maintenance Window", "Access Rights", as well as "Channel Unit Configuration" to the AWS Cost BETA sensor.
You can now add the AWS Cost BETA sensor to devices on remote probes and cluster probes as well, which also includes cluster support for this sensor. In previous versions, you could only add the sensor to your local probe.
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].

New in PRTG Network Monitor 20.2.58.1629 (Apr 21, 2020)

Server:
Active Directory
The PRTG active directory integration now supports LDAP over SSL (LDAPS). You can define to use SSL encryption as LDAP Transport Security in the Active Directory Integration section of your Core & Probes settings. Default is LDAP transport security without encryption.
Languages:
Japanese:
We completely revised the Japanese language version of PRTG. Thanks to significantly improved texts, the new Japanese version helps you to even better find your way in the PRTG web interface, makes your monitoring tasks easier, and you can enjoy your administrator life even more. If you speak Japanese, we highly recommend this update and trying out the new language file.
All languages
We also updated all other language files additionally to the completely revised Japanese version.
Sensors:
Business Process (Processus métier):
You can edit the channel definition settings of the Business Process (Processus métier) sensor again even when using the French language version of PRTG. In previous versions, a malformed link in the French language file made it impossible to add or change the channel definitions.
HTTP sensors
HTTP sensors properly support URLs that include a hash sign (#) again. In certain cases, when monitoring URLs that include the character sequence /#/, for example, HTTP sensors encoded the hash sign and showed error 404 (not found).
HTTP Full Web Page
The HTTP Full Web Page sensor supports URLs that include an equals sign (=) again. In previous versions, the sensor encoded the equals sign so that the sensor could not monitor the target URL and showed an error. We also increased the sensor message visibility to 255 characters and malformed results now show error PE132.
Python Script Advanced
You can install new packages in PRTG Python using pip or easy_install, for example, like normal again. In previous versions, you received an error message in such cases because the PRTG Python post-install script was not working when the base path included whitespaces, which is typically the case in PRTG Network Monitor installation paths. We also updated the Python distribution delivered with PRTG to version 3.7.7.
SNMP Fujitsu System Health v2
We added the missing lookup file for the Redundancy Mode channel of SNMP Fujitsu System Health v2 BETA sensors that monitor the power supply redundancy status (default sensor name: iRMC Power Supply Redundancy: Status). The sensor channel shows a warning status if there is no redundancy, and an up status if there is a PSU redundancy, dual AC redundancy, or triple AC redundancy.
SNMP Trap Receiver and Syslog Receiver
SNMP Trap Receiver and Syslog Receiver sensors now purge their messages after 180 days if you select this option in the Purge Messages After settings. In previous versions, both sensor types already purged the messages after 120 days even if you had selected 180 days.
SSH Meminfo
The SSH Meminfo sensor now queries MemAvailable instead of MemFree from the target device to monitor the channels Available Memory and Percent Available Memory. This approach reflects the actual RAM usage of Linux systems in a better way and is aligned with the values that the SNMP Linux Meminfo sensor monitors.
Custom advanced sensors
We fixed an issue with custom advanced sensors that sometimes showed wrong values in tables (differing by 1 from the correct values) while showing correct values in the data graph. The issue was caused by the Decimal Places channel setting (the custom option worked correctly) and affected sensor types that use XML input like EXE/Script Advanced, Python Script Advanced, SSH Script Advanced, HTTP Push Data Advanced, HTTP IoT Push Data Advanced, HTTP Data Advanced, and REST Custom.
Server:
Maps:
You can now use JPEG files as Background Image for maps. In previous versions, maps only supported JPG, PNG, and GIF images for the background.
Opening monitoring objects like groups and devices from the sunburst in public maps works again. In previous versions, you received the error message Map refresh failed in such cases.
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.
Enterprise Console:
Housekeeping
We deliver the PRTG Enterprise Console Remover with this PRTG version. With this tool, you can simply uninstall the deprecated Enterprise Console from your server. You find it in your PRTG Network Monitor program folder, as well as there is a shortcut in the Windows Start Menu.
Sensors:
MQTT Round Trip:
The upcoming PRTG version 20.2.59 will include a new, significantly changed MQTT Round Trip sensor. We already inform you now about the change because any previously deployed MQTT Round Trip BETA sensors will immediately stop working upon updating to PRTG 20.2.59 or later and you will have to add them anew.
All parts of PRTG:
Various other minor fixes and improvements, updated user manual
Tree Version:
Tree Version Update:
The configuration file of this version is not downwards compatible with previous PRTG versions.

New in PRTG Network Monitor 20.2.58.1532 Beta (Apr 8, 2020)

Improved - Server:
Active Directory: The PRTG active directory integration now supports LDAP over SSL (LDAPS). You can define to use SSL encryption as LDAP Transport Security in the Active Directory Integration section of your Core & Probes settings. Default is LDAP transport security without encryption.
Improved - Languages:
Japanese: We completely revised the Japanese language version of PRTG. Thanks to significantly improved texts, the new Japanese version helps you to even better find your way in the PRTG web interface, makes your monitoring tasks easier, and you can enjoy your administrator life even more. If you speak Japanese, we highly recommend this update and trying out the new language file.
Fixed - Sensors: HTTP sensors: HTTP sensors properly support URLs that include a hash sign (#) again. In certain cases, when monitoring URLs that include the character sequence /#/, for example, HTTP sensors encoded the hash sign and showed error 404 (not found).
HTTP Full Web Page: The HTTP Full Web Page sensor supports URLs that include an equals sign (=) again. In previous versions, the sensor encoded the equals sign so that the sensor could not monitor the target URL and showed an error. We also increased the sensor message visibility to 255 characters and malformed results now show error PE132.
Python Script Advanced: You can install new packages in PRTG Python using pip or easy_install, for example, like normal again. In previous versions, you received an error message in such cases because the PRTG Python post-install script was not working when the base path included whitespaces, which is typically the case in PRTG Network Monitor installation paths. We also updated the Python distribution delivered with PRTG to version 3.7.7.: SNMP Fujitsu System Health v2
We added the missing lookup file for the Redundancy Mode channel of SNMP Fujitsu System Health v2 BETA sensors that monitor the power supply redundancy status (default sensor name: iRMC Power Supply Redundancy: Status). The sensor channel shows a warning status if there is no redundancy, and an up status if there is a PSU redundancy, dual AC redundancy, or triple AC redundancy.
SNMP Trap Receiver and Syslog Receiver: SNMP Trap Receiver and Syslog Receiver sensors now purge their messages after 180 days if you select this option in the Purge Messages After settings. In previous versions, both sensor types already purged the messages after 120 days even if you had selected 180 days.
SSH Meminfo: The SSH Meminfo sensor now queries MemAvailable instead of MemFree from the target device to monitor the channels Available Memory and Percent Available Memory. This approach reflects the actual RAM usage of Linux systems in a better way and is aligned with the values that the SNMP Linux Meminfo sensor monitors.
Custom advanced sensors: We fixed an issue with custom advanced sensors that sometimes showed wrong values in tables (differing by 1 from the correct values) while showing correct values in the data graph. The issue was caused by the Decimal Places channel setting (the custom option worked correctly) and affected sensor types that use XML input like EXE/Script Advanced, Python Script Advanced, SSH Script Advanced, HTTP Push Data Advanced, HTTP IoT Push Data Advanced, HTTP Data Advanced, and REST Custom.
Fixed - Server:
Maps: You can now use JPEG files as Background Image for maps. In previous versions, maps only supported JPG, PNG, and GIF images for the background.
Opening monitoring objects like groups and devices from the sunburst in public maps works again. In previous versions, you received the error message Map refresh failed in such cases.
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.
Improved - Various:
All parts of PRTG: Various other minor fixes and improvements, updated user manual
Changed - Tree Version
Tree Version Update: The configuration file of this version is not downwards compatible with previous PRTG versions.

New in PRTG Network Monitor 20.1.57.1786 (Apr 1, 2020)

New in PRTG Network Monitor 20.1.57.1745 (Mar 24, 2020)

SECURITY:
Server:
This version includes an important security update for your PRTG core server. We recommend that you update as soon as possible. Please find more details in the email we sent to the email address provided in your license information. (CVE-2020-10374)
IMPROVED:
Sensors:
LDAP:
The LDAP sensor now supports LDAP over SSL (LDAPS). If you want to monitor your secured Active Directory server, choose the option Use LDAP over SSL for the sensor setting Connection Security in section LDAP Specific. LDAP without encryption is default. You can also define a custom port for the connection to the LDAP server or use the default port.
VMware Host Hardware Status (SOAP)
The VMware Host Hardware Status (SOAP) sensor now categorizes unknown states reported by the VMware host server as entity with its own sensor channel and does not show them as warnings anymore. You also have the sensor settings option to not show unknown states in the sensor message. The setting Known Warnings is only purposed for warning states now.
IMPROVED:
Server:
Notifications:
We added a few more placeholders for notifications. You can use a new placeholder that only resolves to the current sensor status and additional placeholders for elapsed times since status updates.
%laststatus simply resolves to the current sensor status to ease, for example, automation tasks in comparison to the more complex %status placeholder
%elapsed_lastcheck resolves to the elapsed time since the last scan of a sensor as shown in its general information section and is a simpler version of %lastcheck because it omits the timestamp
%elapsed_lastdown resolves to the elapsed time since the last down status of a sensor and is a simpler version of %lastdown because it omits the timestamp
%elapsed_lastup resolves to the elapsed time since the last up status of a sensor and is a simpler version of %lastup because it omits the timestamp
IMPROVED:
WebGUI:
Reports:
The column in the list of reports that shows the number of sensors included in the last run of a report now also updates if you run an HTML report. In previous version, only PDF reports were considered. We also renamed the column to # Sensors in last run to make it clearer what the numbers actually show.
Security
We updated the bootstrap.js plugin that we ship with PRTG because the previously used version 3.2.0 had an XSS vulnerability. (CVE-2019-8331)
FIXED:
Sensors:
NetApp Volume:
We fixed an issue with the snapshot time calculation of the NetApp Volume BETA sensor. In certain cases, values of sensor channels like, for example, Latest snapshot and Oldest snapshot did not match the times displayed in the NetApp interface because the sensor mixed up the handling of UTC and local time.
Sensor channels:
The sensor channel option Hide from tables immediately takes effect again. In previous versions, channels with this option enabled only disappeared from tables after a PRTG server restart.
We fixed a display issue of channel gauges that occurred when switching the alerting mode from limit-based to lookup-based and back.
WMI sensors:
WMI sensors now show an according error message (PE069) if they do not find any items to monitor on the target device during the meta-scan on sensor creation.
FIXED:
Server:
API:
When you use an API call that returns PRTG objects sorted by a numerical property like objid, the returned objects are now numerically sorted. In previous versions, the objects were alphabetically sorted.
For example, as of the current PRTG version, IDs (objid) are sorted like [2419, 2470, 10359, 10360], where in previous versions the sorting was [10359, 10360,2419, 2470] in such a case.
Cluster
PRTG now shows a correct error message if you provided a wrong cluster access key and try to log in into the failover node so that you can easier help yourself.
Licensing
We fixed an issue with the PRTG PLUS license where, in certain cases, PRTG instances erroneously showed the message your license will expire in [x] days so that you had to manually reactivate the license each time this case occurred.
Maps
You can add custom background images to maps again. In the previous PRTG version 20.1.56, PRTG showed an internal server error when you selected a file as Custom Image to use as Background Image and tried to save the map settings.
Memory Usage
The PRTG server may consume less memory over time in certain monitoring scenarios. We also improved the memory usage of maps that include many historic graph images.
Reports
The default Security Context of a report is again the PRTG user account that creates the report.
Timezones
The default timezone for newly created user accounts and reports is the system timezone of the PRTG server again.
IMPROVED:
Various:
All parts of PRTG
Various other minor fixes and improvements, updated user manual including a style update
Sensors:
Npcap:
We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 0.9987.
Beta sensors
The following sensor types are not in beta status anymore and are now fully supported.
Dell PowerVault MDi Physical Disk
DICOM Bandwidth
DICOM C-ECHO
DICOM Query/Retrieve
HL7
HTTP IoT Push Data Advanced
HTTP Push Data
SNMP Buffalo TS System Health
SNMP Custom String Lookup
Windows Physical Disk I/O
WMI Battery
WMI Logical Disk I/O

New in PRTG Network Monitor 20.1.56.1547 (Feb 25, 2020)

New:
Sensors:
AWS Cost:
The new AWS Cost BETA sensor monitors the costs of your Amazon Web Services (AWS) account. It shows the total costs as well as a forecast of the total costs of your AWS account. You can optionally monitor additional types for costs and forecasts, like the cost types amortized and unblended costs, as well as the forecast types blended and net amortized costs, for example.
The AWS Cost sensor will help you to keep an eye on your company AWS account's spending, as well on your single purpose AWS account's spending. If you set up channel limits, it can individually notify you if the costs become too high.
Improved:
WebGUI:
Checkboxes:
We improved the appearance of checkboxes. You now find a standard checkbox icon everywhere in the PRTG web interface. In previous versions, PRTG used an individual icon in some sections, for example, in sensor lists, which made it unnecessarily difficult to immediately recognize its meaning.
Sensors:
The performance impact bar that we added to sensor tabs in the last PRTG version 20.1.55 is now also available in several sensor lists. You can also directly open sensor lists sorted by performance impact from the main menu bar via Sensors | By Performance Impact and from the PRTG Status page, section Sensors by Performance Impact.
The lists provide you a quick overview of the performance impact of all running sensors without having to individually look at each sensor, as well as the possibility to perform multi-edit on sensors with a certain impact, for example, to adjust scanning intervals and tweak the performance of PRTG.
Serve:
Active Directory:
We improved the performance of Active Directory user connections to the PRTG server. In rare cases, nearly simultaneous logins and usage with Active Directory based user accounts from PRTG Desktop and PRTG mobile apps were quite slow when the last connections were longer ago.
Cluster:
Sensors in status Down (Acknowledged) now also show the according sensor log message on cluster failover nodes.
Notifications:
You can now use placeholders for tags in notifications. With %objecttags you get the tags of the sensor that triggers the notification, %parenttags resolves to all inherited tags, and %tags is for the sensor's tags plus all inherited tags. Using tags in your notifications enables you, for example, to automatically route notifications to the appropriate response teams based on included tags. See also the Knowledge Base article What placeholders can I use with PRTG?
Password Recovery:
PRTG no longer sends redundant emails during the forgot password process. With the improvements in this context in previous versions, you already get the information from the removed emails in the PRTG web interface.
Security:
If you change the password of your PRTG user account, the content of the fields Old Password, New Password, and Retype Password is now always masked when the change is written to a log file. If you entered a wrong old password in previous versions so that PRTG could not save the password change, the according error message was logged with the entered old, new, and retyped passwords in clear text on the PRTG server.
Session Handling:
We implemented further improvements for the handling of user sessions.
Fixed:
Sensors:
Cisco IP SLA:
The Cisco IP SLA sensor now even finds interfaces if the meta-scan (querying available interfaces on sensor creation) exceeds 9,000 SNMP requests so that you are able to create all possible instances of the sensor on a large target system. You can also individually define the interface range for the meta-scan of the Cisco IP SLA sensor in the SNMP Compatibility Options of the parent device with the options Start Interface Index and End Interface Index as of this version.
NetApp SnapMirror:
We fixed an issue with the NetApp SnapMirror BETA sensor that you could not create in certain scenarios. PRTG expected a return field that did not exist in such cases, resulting in error messages like An item with the same key has already been added. or Error: Object reference not set to an instance of an object when trying to add the sensor.
SIP Options Ping:
We fixed an issue with the SIP Options Ping sensor where in certain cases the authentication failed because of an incorrect realm sent by PRTG.
SNMP Traffic:
The default primary channel of SNMP Traffic sensors is always the Total channel again. In previous version, SNMP Traffic sensors that you newly added to PRTG with at least one of the Additional Channels came with Traffic In as primary channel.
VMware Datastore (SOAP):
The auto-discovery can create VMware Datastore (SOAP) sensors again. This did not work with custom device templates in previous versions.
Server:
Maps:
We fixed an issue with public maps that, in rare cases, caused very high CPU load on the server when viewing a public map with changed security context.
Object Names:
Names of monitoring objects like, for example, sensors, devices, groups, are now properly displayed on the object's details page even if they contain the character sequence left square bracket and a ([a). In previous versions, the name was cut off at this position.
Sensor Values:
We fixed a rounding issue were numbers close to 0 like 0.01 or -0.01 were mistakenly rounded to 0 in sensor messages instead of correctly showing the decimal places.
WebGUI:
Cluster:
Switching the cluster node in map rotation works again.
Graphs:
The values you enter into Vertical Axis Maximum and Vertical Axis Minimum in section Vertical Axis Scaling of channel settings now even take effect in graphs if you set the Display in percent of maximum option in the channel setting's Data section.
Libraries:
Clicking summarized sensor status elements in library nodes opens a list that only contains sensors from this library node in the particular status again. In previous versions, the filter did not properly work and just showed all sensors of the PRTG instance in this status.
Pagination in the Filter by Type section of library node settings works properly again. Directly clicking page numbers did not work in previous versions, only clicking a small area above a number helped.
Lookups:
We fixed some minor display issues of bitmask lookups on sensor pages.
Changed:
Sensors:
Logging:
PRTG now stores sensor logs in the Logssensors 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:ProgramDataPaesslerPRTG Network MonitorLogsSensors. In previous versions, sensor logs were written to the folder Logs (sensors).
Improved:
Various:
All Parts of PRTG:
Various other minor fixes and improvements, updated user manual, updated German language file
Note:
Sensors:
MQTT Round Trip:
We plan major changes to the MQTT Round Trip BETA sensor in an upcoming PRTG version. Once released, the changes will mean that any previously deployed sensors of this type will stop working and you will have to create them anew. We will inform you again as soon as the changes are included in a new PRTG version.

New in PRTG Network Monitor 20.1.55.1775 (Jan 22, 2020)

New:
Sensors:
SNMP Nutanix Cluster Health
The new SNMP Nutanix Cluster Health BETA sensor provides an overview of your Nutanix cluster and shows the status of the cluster, as well as several performance metrics. Additionally to the quick status overview where you can see whether the cluster is started or stopped, for example, the new SNMP Nutanix Cluster Health sensors enables you to check I/O operations per second, used I/O bandwidth, and I/O latency with PRTG.
SNMP Nutanix Hypervisor
The new SNMP Nutanix Hypervisor BETA sensor monitors the health of your Nutanix cluster hypervisors. The sensor shows an overview of hypervisor performance metrics like CPU usage, traffic, and I/O data, as well as the number of active virtual machines on a node.
Improved:
Server:
Access Rights:
We improved the performance of the access rights check. This will speed up the loading times of objects in PRTG for non-administrative user accounts after the login. In certain cases, loading all objects after the login took quite long for user accounts except for the PRTG system administrator.
Login
We modernized the password reset approach that consists of receiving a link by email from where you can set your new password.
Probe Connections
We improved the stability of probe connections to the PRTG server. After performance improvements for probe connections in PRTG version 19.2.50, some customers reported issues with the connection stability in certain scenarios.
For example, probe reconnects could result in an error state in which the communication between PRTG core server and the probe did not succeed although the connection was established. This resulted in sensors in unknown status on this probe.
To prevent such issues, PRTG now uses the unique GID of the probe to identify the probe node and management object and not the ID. Because of this, all GIDs must have a valid format. It is not possible anymore to define any string as probe GID. If you previously used an invalid GID, PRTG will automatically generate a new, valid GID for the probe.
For more details, see the article The probe GID of my remote probe changed. What is the reason? in the Knowledge Base.
Improved:
WebGUI:
Geo Maps:
If PRTG cannot retrieve data for geo maps when using the Google Maps API because of, for example, a wrong API key or unavailability of the service, PRTG now will show according information in the geo map section and logs to exactly tell you what went wrong.
Reports
We improved the appearance of reports that include data graphs. The height of main and monthly graphs is now consistent in all report templates that include graphs. In previous versions, graphs in "graphs only" report templates were very large, so we reduced their size to be able to display channel averages on the same page and so help you to get as much information as possible at a glance.
Sensors
You are now able to directly identify the impact on the PRTG system performance of a running sensor in its general information section. Each sensor shows the performance impact bar that you already know from the Add Sensor page on its overview tab, live data tab, and data by days tabs. This information will help you to easier decide about what sensor types to use and which scanning intervals to configure to get the best PRTG system performance possible.
Improved:
Security:
Login:
We improved the handling of user sessions.
WebGUI:
We fixed a potential XSS vulnerability of the PRTG web interface.
Web Server:
This PRTG version comes with a more strict web server security by default to keep PRTG as secure as possible. TLS 1.2 will be the new default web server connection security.
Note: The change may affect you if your PRTG users or third-party systems use outdated versions of browsers or PRTG mobile apps, the Enterprise Console, or old automation tools that interact with the PRTG API. You will receive a ToDo ticket in PRTG with further information.
Changed:
Sensors:
Python Script Advanced:
This PRTG version includes a new Python distribution because of the end-of-life announcement for Python 3.4. Please make sure that your custom Python scripts are compatible with Python 3.7 when you update PRTG.
Note: You only need to consider the change if you are using the Python Script Advanced sensor. PRTG also creates a ToDo ticket with further information for you in this case.
REST Custom (Sigfox)
We adjusted the default Sigfox templates for the REST Custom sensor to adapt the Sigfox v2 API. With this change we also combined the device state template (sigfox.device.template) and the token state template (sigfox.device.token.template) into one new template with different channels. Also, required lookup files are available again.
Note: To apply these changes, please create a new REST Custom sensor with the template sigfox.device.template. REST Custom sensors that use the old templates will not work anymore.
WMI Disk Health and WMI Storage Pool
We implemented some cosmetic improvements for the beta sensors WMI Disk Health and WMI Storage Pool that we newly introduced in the last PRTG version 19.4.54.
Note: With these improvements, we also changed the names of some WMI Disk Health and WMI Storage Pool sensor channels. This change may lead to duplicated channels on running instances of these sensor types after updating PRTG. Channels with an old name will not receive data anymore and cannot be deleted. Please add sensors with duplicated sensor channels anew.
Changed:
Geo Maps:
Providers:
We removed the deprecated geographical map service provider CloudMade from PRTG. You cannot choose this provider anymore in section Geo Maps of the user interface settings in the PRTG system administration. If you had selected CloudMade before your PRTG update, the provider setting will be automatically changed to default.
Fixed;
Sensors:
EXE/Script sensors:
We fixed an issue with encrypting passwords that contain certain special characters like the dollar sign ($). The issue affected EXE/Script and EXE/Script Advanced sensors. The dollar sign, for example, broke the encryption method, which resulted in a password being partly visible as clear text in the sensor log when you enabled the option Write EXE result to disk and used according placeholders in the parameters field.
MQTT Round Trip
The Client Key Password of the MQTT Round Trip BETA sensor is now masked in the sensor log that is written when you enable the option Write sensor result to disk.
In case you change the credentials for MQTT settings from TLS to not using TLS and the sensor was down with the message Subscriber could not connect before, the status of the MQTT Round Trip BETA sensor will now change to OK if appropriate. In previous version, the MQTT Round Trip BETA sensor just stayed down in such a case.
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
The Response Code channel is the new default primary channel of the SIP Options Ping sensor to make the channel gauge better visible. Because of too many lookup states of this channel, the visibility of the gauge as non-primary channel was not optimal.
The password for the SIP account that you use for the connection to the SIP server now supports the equals sign (=). In previous versions, this character broke the password so that you received the sensor error message Parameter -pw is mandatory.
SMTP&IMAP Roundtrip:
The SMTP&IMAP Roundtrip sensor now automatically comes back after being down due to connection issues as soon as the connection is established again. In previous version, the sensor stopped working after connection interruptions like a firewall restart.
SNMP Cisco System Health
SNMP Cisco System Health sensors that you create via auto-discovery using the device template Cisco Device (Generic) now get only tags assigned that are suitable for the created sensor scope (for example, voltage, current, temperature). In previous versions, the automatically created sensors just got all Cisco system health tags assigned.
SNMP Fujitsu System Health v2
The SNMP Fujitsu System Health v2 BETA sensor now updates the OID index if it changed (for example, after a restart of the target device) and the identifier still exists in the OID table. In previous versions, the sensor was not able to automatically repair the index if the OID table changed in a way that the OID index was not available anymore. This resulted in a down status with the sensor error message no such name, for example.
SNMP HPE BladeSystem sensors
We fixed a memory leak caused by running SNMP HPE BladeSystem Blade and SNMP HPE BladeSystem Enclosure System Health sensors.
SSL Security Check
The SSL Security Check sensor now actually uses the SOCKS proxy that you define in the Connection Specific settings of the sensor. In previous versions, the sensor just connected to the target host without using a proxy even if you defined one.
Fixed:
Server:
Active Directory:
PRTG now automatically synchronizes user group memberships with the current status of a user account in the Active Directory. In previous versions, user accounts with changed Active Directory group memberships just remained in all user groups they have ever been members of.
Auto-Discovery:
We improved the check for already existing devices so that the PRTG auto-discovery more reliably avoids creating duplicate devices for the same host. The fix applies in particular to cases where the host names of found devices only differ in uppercase and lowercase letters.
Deleting:
You can directly delete devices from the device tree again even if they are paused by dependency. In previous versions, a device paused by dependency that you were trying to delete remained in the tree but only the sensors on the device were deleted.
PRTG Status:
The PRTG Status page now lists sensors with a fixed scanning interval in the correct section of Sensors by Interval. This fix applies to Common SaaS and Windows Updates Status sensors, for example.
Reports:
We fixed an issue with PDF reports that you could not generate anymore when using a symbolic link (symlink) or junction directory for the reports. The broken symlink functionality was also the reason that in some cases PDF reports did not work anymore after you have updated from a very old PRTG version to a current one.
Search:
The search in PRTG works again even if you search for objects that include UTF-8 characters (for example, German umlauts or Russian or Japanese characters). In the last PRTG version 19.4.54, you did not get any search results in such a case.
Sensor History:
The History tab of a sensor only shows entries for actual changes on sensor settings again. In previous versions, tags always showed up as changed in the history even if you only changed other sensor settings.
Fixed:
WebGUI:
Automatic Logout:
PRTG user accounts that were automatically logged out from the PRTG web interface after being inactive for a certain time see the reason for being logged out on the login page again. You can define the automatic logout under Setup | User Interface with the setting Automatic Logout in section Website.
Firefox ESR
PRTG now correctly recognizes and handles Firefox Extended Support Release (ESR) versions as supported. If you access the PRTG web interface with Firefox ESR 68 or later, PRTG will not mistakenly show the warning message Sorry, your browser is not supported! anymore.
Maps
Maps now correctly display Korean characters like the timestamps in graphs that you show on a map.
Schedules
The Save button gets activated again if you uncheck a specific time via hour or weekday buttons in the time table of a schedule in your account settings.
Improved:
Various:
All Parts of PRTG:
Various other minor fixes and improvements, updated user manual, updated Dutch language file

New in PRTG Network Monitor 19.4.54.1506 (Nov 25, 2019)

New:
Sensors:
WMI Disk Health:
The new WMI Disk Health BETA sensor monitors the health of virtual or physical disks on your Windows servers. It shows the operational and health status of a disk. It does not matter which disk type, the sensor works with all kinds like SSD, SATA, or SAS, for example. The WMI Disk Health sensor shows detailed information about the operational status like degraded or predictive failure in the sensor message.
With this new sensor type, you will always have a quick and easy overview of the status of your disks.
WMI Storage Pool:
The new WMI Storage Pool BETA sensor monitors a storage pool on your Windows servers. A storage pool consists of multiple disks and provides RAID functionality without real RAID hardware. This new sensor type shows the operational and health status of the storage pool, as well as free space, and provides detailed information about the operational status like stressed or relocating.
With the new WMI Storage Pool sensor, you will always have an overview of the status of your storage pool.
Important:
Security:
Server:
This version includes an important security update for your PRTG core server. We recommend that you update as soon as possible. Please find more details in the email we sent to the email address provided in your license information. Special thanks go to Aleksandr Melkikh from Positive Technologies for pointing us to the right direction. (CVE-2019-19119)
Improved:
Security:
Access Rights:
Users with restricted access rights to sensors now only see a sensor's relationship in the Similar Sensors Overview if their user account has access to both related sensors.
Sensors:
We fixed a potential Remote Code Execution (RCE) vulnerability of the HTTP Transaction sensor. (CVE-2019-11073)
Server:
We fixed a potential Remote Code Execution (RCE) vulnerability of the PRTG core server. Many thanks to Sittikorn Sangrattanapitak - Cybersecurity Researcher, Nuttakorn Tungpoonsup & Ammarit Thongthua - Secure D Center Research Team, Secure D Center Co.,Ltd. for reporting the issue.
Version Number:
PRTG does not show the current version number in HTTP headers anymore to improve security by not providing attackers potentially relevant information. For the same reason, the page footer of the web interface now only shows the version number on pages that require a logged in user account.
Fixed:
Sensors:
MySQL v2:
MySQL v2 sensors support user-defined variables in your SQL scripts again. This did not work in previous PRTG versions due to a change in the MySQL library, which added a new connection setting to allow user variables. The sensors showed the error message Fatal error encountered during command execution when running a SQL statement with user-defined variables.
Port:
You can now also save the advanced Port sensor setting Goal into custom device templates. The goal of a Port sensor can be an open or closed port to define an up status.
SNMP Library:
SNMP Library sensors again create each channel only once. If you selected more than 10 OIDs when adding the sensor in previous versions, the last channel of the sensor created for the first 10 OIDs was also created as first channel of the sensor added for the next 10 OIDs.
Server:
Cluster:
Minor stability improvements for PRTG cluster installations
Data Purging:
PRTG now correctly applies the data purging value for Historic Sensor Data even if you define a value that is greater than 1095 days (3 years). In previous versions, PRTG did not purge historic data anymore if you used a value above 1095 days. You can now define a maximum value of 9999 days.
Overload Protection:
PRTG will only create one ToDo ticket and one log entry again when overload protection gets activated due to 100 failed logons since the last start of PRTG. In previous versions, PRTG was too noisy with an active overload protection, which could result in way too many tickets indicating that Web server is slowing down login attempts (Protective measure) in some cases.
Reports:
PRTG now automatically removes temporary files and folders that are generated when running a report to not unnecessarily fill up the disk.
The reporter.exe that PRTG uses to generate PDF reports is now signed. This will help to prevent anti-virus software from flagging the exe, as well as you can be assured that the file is really from Paessler.
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.
Webgui:
Libraries:
Libraries do not contain buttons to add devices, sensors, or to run an auto-discovery anymore. The buttons had no functionality anyway because libraries are designed for visualization, not interaction.
Maps:
The object selector in the map designer to link a map object with an object from the device tree shows the whole tree again. In previous versions, objects at the bottom of the device tree were cut off so you could not select them.
Multi-Edit:
You can see and change Sensor Display settings again when you open the settings of one or more sensors via multi-edit.
Updating:
The auto-update confirmation dialog window now immediately reacts when you click the Yes, install update now button.
Changed:
Api:
Json:
The value of the notifiesx_raw field returned by the API call api/table.json?content=sensorxref is never null now and always the same value no matter which language. In previous versions, notifiesx_raw could be empty as well. If you use external tools or scripts that use the PRTG API, please keep this change in mind and adjust them if necessary.
Webgui:
Optional Downloads:
The PRTG web interface now also shows download links for PRTG Desktop on the Welcome page and under Setup | Optional Downloads on PRTG instances hosted by Paessler.
Clients:
Enterprise Console:
We no longer deliver the Enterprise Console with the PRTG installer. This change will not affect running Enterprise Console instances, but please note that they may stop working anytime in upcoming PRTG versions. We recommend that you switch to PRTG Desktop soon.
Improved:
Various:
All parts of PRTG:
Various other minor fixes and improvements, updated user manual, updated language files

New in PRTG Network Monitor 19.4.52.3515 (Oct 10, 2019)

New in PRTG Network Monitor 19.3.52.3502 (Oct 1, 2019)

New:
Sensors:
WMI Battery:
The new WMI Battery BETA sensor monitors status and available capacity of batteries that are connected to Windows devices. Additional channels of this new sensor type show voltage, time estimations until the battery is full or empty depending on the status charging or discharging, and an overall battery health value.
The sensor makes it possible for you to see the level of batteries in your IT infrastructure at a glance. PRTG alerts you as soon as a battery threshold is breached. You can even generate reports to get to know how much time laptops spend charging, for example.
Please note that the sensor is in beta status and only works if the required WMI battery classes are available on the monitored device. We welcome any feedback about the sensor and what you are trying to monitor. Please send your feedback to [email protected], thank you!
Improved:
Various:
All Parts of PRTG:
Various other fixes and improvements to all parts of PRTG, updated user manual, updated German and Japanese language files
WebGUI:
Device Icons:
We added new device icons for several vendors. PRTG will automatically add suitable icons to devices detected via auto-discovery if possible. Of course, you can also manually select any device icon in the device settings, section Additional Device Information. The new set includes icons for the following vendors.
Juniper
Baracuda
Fortinet
PaloAlto
Kentix
Watchguard
Oracle
Westermo
Sophos
MikroTik
Qnap
Cybernetics
Brocade
Axis Cameras
Nimble Storage
Checkpoint (Firewalls)
Ruckus
Kemp
Aruba
Sonoff
Adtran
Sensors:
SNMP Dell PowerEdge Physical Disk:
Newly added SNMP Dell PowerEdge Physical Disk sensors now include the enclosure ID in the sensor name if available. For example, a sensor name can be Physical Disk 1:0:0:16, where the first of four numbers is the enclosure ID (here: 1). If there is no enclosure ID available, there will be three numbers in the sensor name, for example, Physical Disk 0:0:16. This improvement will help you to easier find the disk you are looking for in PRTG.
Fixed:
Security:
PRTG Core Server:
We fixed potential reflected XSS vulnerabilities with medium severity on the PRTG core server. 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 a sensor type. Please note that the fixed vulnerability required a logged in PRTG user account with elevated rights to be exploited. (CVE-2019-11074)
Sensors:
Event Log (Windows API):
You can filter for more than two event IDs with the Event Log (Windows API) sensor again. In the previous version, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of more than 2 IDs.
Exchange (PowerShell) sensors:
Exchange (PowerShell) sensors now correctly close the runspace. In previous versions, Exchange (PowerShell) sensors sometimes showed a down status with the error message Fail to create a runspace because you have exceeded the maximum number of connections allowed. The fix applies to all Exchange (PowerShell) sensor types, Exchange Backup (PowerShell), Exchange Database (PowerShell), Exchange Database DAG (PowerShell), Exchange Mail Queue (PowerShell), Exchange Mailbox (PowerShell), Exchange Public Folder (PowerShell).
EXE/Script sensors:
EXE/Script and EXE/Script Advanced sensors again support the special characters round brackets "()", dot ".", and comma "," in the Parameters field. This allows you to pass arrays from the sensor to the script.
Sensor Factory:
We fixed an issue where, in rare cases, modifying the spike filter in combination with Sensor Factory sensors caused issues with the PRTG core server, resulting in gray sensors, for example.
SNMP Cisco System Health:
We improved the stability of SNMP Cisco System Health sensors. The sensor can handle packet loss and delays better now due to request retries that properly work again. This will prevent the sensor from occasionally showing down states with error message Queries for the following channel IDs returned no data: %s (code: PE269) in many cases.
SNMP Cisco System Health sensors get correct names and units again after sensor creation. In previous versions, all channels except for the first one were only named by the index of the OID in certain cases.
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
Adding SNMP Traffic sensors now also works when you use the ifName OID [1.3.6.1.2.1.31.1.1.1.1] in the Port Name Template of the SNMP Compatibility Options. In previous versions, you were not able to add SNMP Traffic sensors in this case and got an access violation.
If you monitor interfaces with a lot of traffic, for example, 10 GB interfaces, and choose the Data option Display in percent of maximum in the settings of an SNMP Traffic sensor channel, PRTG will now automatically add an appropriate value to the Maximum (kbit/s) field. In previous versions, you had to manually configure a maximum value on which the percentage calculation is based in this case because the setting did not appropriately handle Int64 values.
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.
Notifications:
Notification Delivery:
We removed the Test SMTP Settings button in the Notification Delivery settings on PRTG instances that are hosted by Paessler. As PRTG hosted by Paessler customer, you use the email infrastructure of Paessler so that testing the SMTP delivery settings is not necessary for you.
Notification Templates:
PRTG user accounts with read/write rights and write or full access rights to a notification template can now change the user group as the recipient of an email, push, or SMS notification.
Logged in read/write users can see and select all user groups they are member of, as well the currently selected user group in the Send to User Group field of a notification template. In the Send to User field, read/write users can see and select all user accounts from all user groups they are a member of, as well as the currently selected user account.
SMS Notifications:
Sending SMS notifications via custom SMS providers works again with both number conventions, plus (+) or 00 followed by country code and number. In previous versions, the plus sign was not correctly encoded so SMS messages could not be delivered.
We made SMS delivery via custom URL more robust. Due to a missing semicolon (;) behind content-type in the HTTP header, SMS delivery failed in certain cases with a bad request error.
Reports:
PDF Layout:
We fixed an issue with PDF reports that erratically caused big gray boxes in generated reports.
PDF Stability:
We implemented stability improvements for PDF reports with many sensors, especially regarding timeouts with the error message Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome.
Libraries:
Node Types:
Libraries again only show a subtree if you select Show a subtree of the device tree in the library as Node Type for a library node. In previous versions, library nodes additionally showed an unordered list of sensors included in the subtree.
Usability:
The buttons to collapse and expand library nodes are now also available in the smallest view (S).
Server:
Data:
We fixed an issue where values of primary sensor channels with negative channel ID were not displayed in some data tables, for example, the Traffic Total channel of SNMP Traffic sensors (channel ID -1). The value of this channel was missing in headers of historic data reports and as Last Value in Cluster Node tables, for example, when set as primary channel in the last PRTG version.
Logging:
We fixed an issue with log files that became very large in rare cases and filled up the disk on the PRTG server. Log files now cannot grow bigger than 64 MB. PRTG will create a second file if this size is reached with a maximum of two copies of the same log file.
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.
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.
WebGUI:
Dependencies:
It is not possible anymore to configure a sensor to be its own dependency. Having a sensor as its own dependency resulted in a situation where a sensor endlessly paused itself when it switched to a down status without the possibility to resume the sensor.
Gauges:
The gauge of a sensor's primary channel now always shows the unit for the minimum value. In previous version, the unit for the minimum value was missing if the minimum was 0 and the channel had a custom unit.
Multi-Edit:
You can now acknowledge one or more down states on the Alarms tab of probes using the multi-edit menu, as well as open the settings of one or more probes.
Tables:
We fixed some layout issues of meta-scan tables in sensor settings so that especially large tables are displayed in a better way.
Internet Explorer 11:
We fixed some more layout issues that occurred when accessing the PRTG web interface with Internet Explorer 11. For example, the Save button was cut off on some pages, the Hide and Show buttons for master dependencies in the dependencies graph were missing, and tickets sometimes occupied more space than given to them.
Changed:
Server:
Probes:
Connecting remote probes now automatically downgrade to the correct version if the PRTG core server runs an older version than the probe.
Tags:
It is not possible anymore to add the same tag to one object in PRTG more than once.
User Accounts:
It is not possible anymore to create user accounts with a login name that includes the special characters " / [ ] : ; | = , + * ? > <
Note: User accounts that already existed before the update to PRTG 19.3.51 and have a login name that includes one of the outlined special characters will still be able to login after the installation of version 19.3.51. However, affected user accounts will not be able to change and save their account settings without changing the login name.
Note:
Sensors:
SNMP Fujitsu System Health:
The upcoming PRTG version 19.4.53 will include a new, significantly improved SNMP Fujitsu System Health sensor. We already inform you now about the change because any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later and need to be added anew.
Outdated Windows Versions:
Outdated Windows Versions:
It is not possible anymore to install PRTG on the outdated operating system Windows XP. This is a side-effect of changing the PRTG license check to a 64-bit binary. Please make sure you install PRTG on an officially supported operating system.
Known Issues:
Summarized Notifications:
In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information.
Status: We are currently working on a fix.

New in PRTG Network Monitor 19.2.51.2830 (Sep 10, 2019)

Improved:
Sensors:
Active Directory Replication Errors:
The Active Directory Replication Errors sensor now supports different Active Directory naming contexts. When you add the sensor, you can now choose between Configuration (default), Schema, DomainDnsZones, Domain, and ForestDnsZones as Naming Context to check your Windows Domain Controller for replication errors. In previous versions, the sensor always used Configuration as naming context.
Improved:
Notifications:
Notification Delivery:
PRTG will now provide clearer communication in logs and tickets when an SMS notification fails due to a missing definition for an SMS provider in the Notification Delivery settings.
Notification Triggers:
You can now directly create a new Notification Template while editing or defining a Notification Trigger without leaving the notification trigger tab. Click the plus symbol (+) in the dropdown list of a trigger to create a new notification template for the notification trigger.
Improved:
Server:
Active Directory:
We improved the login process for Active Directory (AD) users by explicitly requesting read-only access.
Device Templates:
If you create a new device template, you now only need to define a name for the template. You do not have to provide a file name anymore, PRTG will automatically create the corresponding template file with the extension .odt.
PRTG Core Server:
Performance and memory footprint improvements for the PRTG core server, as well as several other improvements and fixes
Reporter:
We added enhanced logging to the new reporter engine to be able to better help you in case of issues when generating reports.
Improved:
Security:
Maps:
We fixed a potential XSS vulnerability in the context of maps. Thanks to Dmitry Galecha from Positive Technologies for reporting the issue.
Notifications
Passwords of Execute Program notifications, webhooks for Slack and Microsoft Teams notifications, as well as the AWS Secret Access Key of Amazon SNS notifications are now masked on the History tab of according notification templates in the PRTG web interface. Notification templates are only accessible for PRTG administrator users and read/write users with access rights for a particular notification template.
We found the issue in internal tests, it was not public before. If your PRTG installation is affected, you will receive a Todo ticket in PRTG. Please follow the instructions there.
Sensors:
Passwords of the following sensor types are now also masked in log files when you enable the debug option: FTP Server File Count, HTTP XML/REST Value, SIP Options Ping, Citrix XenServer Host, Citrix XenServer Virtual Machine, IPMI System Health
Improved:
Language Files:
Language Files:
Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG.
Fixed:
Sensors:
Event Log (Windows API):
You can filter for two event IDs with the Event Log (Windows API) sensor again. In previous versions, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of IDs.
Note: With this version, it is not possible to filter for more than two event IDs. We plan to fully support filtering for multiple IDs again for the next PRTG version 19.3.52.
EXE-based Sensors:
Sensors that require .NET version 4.7.2 now actually show the required version number 4.7.2 in the error message if the .NET framework version 4.7.2 is not available on the probe system. The full error message is This sensor requires the .NET Framework version 4.7.2 (code: PE104)
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
The SNMP Traffic shows an according sensor message again when the Traffic Total channel breaches a defined limit. The fix also works for sum channels with ID -1 of other traffic sensors.
If you multi-edit two or more SNMP Traffic sensors, the connection-dependent buttons to select or deselect interfaces will not be available anymore. The buttons do not make sense for running SNMP Traffic sensors and had no functionality.
VMware Datastore (SOAP):
The VMware Datastore (SOAP) sensor now also properly works if the name of the monitored datastore starts or ends with host. In previous version, the sensor showed a down status with the error message The object '[name]' has already been deleted or has not been completely created in such cases.
Fixed:
Probes:
Memory Leak:
We fixed a small memory leak on the PRTG probe system. The memory leak was caused by SNMP sensors that use SNMP bulk walks with more than 20 channels.
Probe Connections:
We improved the stability of remote probe connections to the PRTG server. In some scenarios, customers encountered frequent disconnects of remote probes with the previous PRTG version 19.2.50.
Note: In certain cases, there may still occur issues with probe connections. We are working on further stability improvements for upcoming releases.
Probe GID
PRTG now always blocks connection attempts of deleted or rejected remote probes if there is an according entry in the Deny GID field of the Probe Connection Settings. The entry was not correctly saved in previous versions when using the French language file, Other language versions were not affected
Fixed:
Server:
Cluster:
Sending support bundles from failover nodes works again.
Dependencies:
We fixed an issue with dependencies where in certain cases devices and sensors did not resume automatically from paused by dependency. This happened, for example, after changing the dependency type from "Master object for parent" to "Use parent".
Device Tools:
Opening the Service URL of a device via Device Tools now even works if the service URL contains an ampersand (&).
Geo Maps:
Locations that you newly define for devices and groups in PRTG show up at the corresponding location in geo maps again.
PRTG Core Server:
We fixed an issue with the PRTG core server that was not able to start and remained stuck in Loading Graph Cache if the configuration file contained an invalid speed trigger value. This happened in a few cases by error after cloning sensors with defined with speed triggers.
Raw Data Buffer:
We fixed an issue that resulted in a full raw data buffer (see the according channel of the Core Health sensor) in certain scenarios with the previous PRTG version 19.2.50. This could happen, for example, when having many remote probes connected. The issue could also cause a loss of monitoring data with many sensors in unknown status.
User Accounts:
It is possible again to change the settings of a user account at any time. Previous PRTG versions erroneously showed the error message A user with this login name already exists. Login names have to be unique. in certain cases when changing user settings. This especially happened for user accounts that you integrated via Active Directory.
Fixed:
WebGUI:
Access Rights:
Primary groups of read/write user accounts in PRTG again automatically get write access to libraries, maps. reports, notification templates, and schedules that they create. This way, the new object remains visible after a page fresh for the user who created it.
Breadcrumbs:
We implemented some minor improvements for the consistency of breadcrumbs and their translations.
Contact Support:
PRTG user accounts with read/write rights can now also open the contact support form via Setup | Contact Support in the main menu bar.
Dark Theme:
Historic data graphs keep their dark theme appearance again when you use the scroll and zoom buttons.
Homepage URL:
Changing the PRTG Homepage URL in your account settings or via Make This My Homepage in the main menu bar on a PRTG hosted by Paessler instance now actually takes effect.
Hover Popups:
PRTG will open the correct tab again when you click a graph in a hover popup.
We fixed the layout of graphs in hover popups for Internet Explorer 11.
Reports:
PRTG can now generate reports and screenshots for the support bundle even if port 9222 is blocked on the PRTG core server. This did not work in the previous PRTG version 19.2.50 after the initial change to Chromium as reporter engine.
We fixed the validation of manually defined date ranges in report settings that showed some issues when using Google Chrome and the date format DD.MM.YYYY (24h or AM/PM) in PRTG 19.2.50. The date validation in general works more consistently now.
Search:
Text that you are searching for in PRTG is correctly displayed again even if your search contains special characters or whitespaces. Search results were not affected by the issue.
Tags:
Tags can now contain certain special characters like ampersand (&) and percentage (%) without causing issues with the PRTG web interface when you filter for such a tag.
Welcome Page
The ticket count on the PRTG welcome page again shows the correct number of open tickets that are assigned to you.
Fixed:
Various:
All Parts of PRTG:
Various other fixes and improvements to all parts of PRTG, updated user manual
Changed:
Sensors:
Loopback Adapter:
PRTG will not install a loopback adapter as part of the Npcap library for Packet Sniffer sensors anymore. When enabled, the adapter could lead to unwanted side-effects on other services, for example, DHCP servers.
Changed:
Tree Version:
Tree Version Update:
The configuration file of this version is not downwards compatible with previous PRTG versions.
Note:
Known Issues:
Enterprise Console:
The Enterprise Console will show two error messages when you close it: MM Operation after uninstall. and Runtime error 204
The messages do not have negative impact. You can ignore them and just close the message windows.
Status: Will not be fixed. Please note that we will stop officially supporting the Enterprise Console with PRTG 19.4.53. Please use PRTG Desktop as successor of the Enterprise Console.
Optional Sensor Channels:
Some sensor types create optional channels that were not intended to be created. For example, SNMP Traffic sensors create all channels from settings section Additional Channels even if they were not selected in the Add Sensor dialog. The Ping sensor creates channels for minimum and maximum ping time, as well as the packet loss channel, even if you select the option Send one single Ping when adding the sensor.
The issue does not have functional impact as long as you do not set one of the erroneously created channels as primary channel. In this case, the sensor may switch to the unknown status. Please note that channels cannot be deleted anymore once they are created, so we recommend that you wait for the next PRTG version if you plan to add sensors of these types without optional channels.
Status: We are working on a fix for the upcoming PRTG version 19.x.52.
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: We are working on a fix for the upcoming PRTG version 19.x.52.
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: We are working on a fix for the upcoming PRTG version 19.x.52.

New in PRTG Network Monitor 19.2.51.2725 (Jul 31, 2019)

Improved:
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 Domain (default), Configuration, Schema, DomainDnsZones, and ForestDnsZones as Naming Context to check your Windows Domain Controller for replication errors. In previous versions, the sensor always used Domain as naming context.
DeliveryPRTG will now clearer communicate in logs and tickets when sending an SMS notification failed due to missing definition of 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.
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.
Fixed:
We fixed a potential XSS vulnerability in the context of maps. Thanks to Dmitry Galecha from Positive Technologies for reporting the issue.
Notifications
Passwords of Execute Program notifications, webhooks for Slack and Microsoft Teams notifications, as well as the AWS Secret Access Key of Amazon SNS notifications are now masked on the History tab of according notification templates in the PRTG web interface. Notification templates are only accessible for PRTG administrator users and read/write users with access rights for a particular notification template.
We found the issue in internal tests, it was not public before. If your PRTG installation is affected, you will receive a Todo ticket in PRTG. Please follow the instructions there.
Sensors
Passwords of the following sensor types are now also masked in log files when you enable the debug option: FTP Server File Count, HTTP XML/REST Value, SIP Options Ping, Citrix XenServer Host, Citrix XenServer Virtual Machine, IPMI System Health
Improved:
Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG.
Fixed:
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
The SNMP Traffic shows an according sensor message again when the Traffic Total channel breaches a defined limit. The fix also works for sum channels with ID -1 of other traffic sensors.
If you multi-edit two or more SNMP Traffic sensors, the connection-dependent buttons to select or deselect interfaces will not be available anymore. The buttons do not make sense for running SNMP Traffic sensors and had no functionality.
VMware Datastore (SOAP)
The VMware Datastore (SOAP) sensor now also properly works if the name of the monitored datastore starts or ends with host. In previous version, the sensor showed a down status with the error message The object '[name]' has already been deleted or has not been completely created in such cases.
Fixed:
We fixed a small memory leak on the PRTG probe system. The memory leak was caused by SNMP sensors that use SNMP bulk walks with more than 20 channels.
Probe Connections
We improved the stability of remote probe connections to the PRTG server. In some scenarios, customers encountered frequent disconnects of remote probes with the previous PRTG version 19.2.50.
Note: In certain cases, there may still occur issues with probe connections. We are working on further stability improvements for upcoming releases.
Probe GID
PRTG now always blocks connection attempts of deleted or rejected remote probes if there is an according entry in the Deny GID field of the Probe Connection Settings. The entry was not correctly saved in previous versions when using the French language file, Other language versions were not affected
Fixed:
Sending support bundles from failover nodes works again.
Dependencies
We fixed an issue with dependencies where in certain cases devices and sensors did not resume automatically from paused by dependency. This happened, for example, after changing the dependency type from "Master object for parent" to "Use parent".
Device Tools
Opening the Service URL of a device via Device Tools now even works if the service URL contains an ampersand (&).
Geo Maps
Locations that you newly define for devices and groups in PRTG show up at the corresponding location in geo maps again.
PRTG Core Server
We fixed an issue with the PRTG core server that was not able to start and remained stuck in Loading Graph Cache if the configuration file contained an invalid speed trigger value. This happened in a few cases by error after cloning sensors with defined with speed triggers.
Raw Data Buffer
We fixed an issue that resulted in a full raw data buffer (see the according channel of the Core Health sensor) in certain scenarios with the previous PRTG version 19.2.50. This could happen, for example, when having many remote probes connected. The issue could also cause a loss of monitoring data with many sensors in unknown status.
User Accounts
It is possible again to change the settings of a user account at any time. Previous PRTG versions erroneously showed the error message A user with this login name already exists. Login names have to be unique. in certain cases when changing user settings. This especially happened for user accounts that you integrated via Active Directory.
Fixed:
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
PRTG will open the correct tab again when you click a graph in a hover popup.
We fixed the layout of graphs in hover popups for Internet Explorer 11.
Reports:
PRTG can now generate reports and screenshots for the support bundle even if port 9222 is blocked on the PRTG core server. This did not work in the previous PRTG version 19.2.50 after the initial change to Chromium as reporter engine.
We fixed the validation of manually defined date ranges in report settings that showed some issues when using Google Chrome and the date format DD.MM.YYYY (24h or AM/PM) in PRTG 19.2.50. The date validation in general works more consistently now.
Search:
Text that you are searching for in PRTG is correctly displayed again even if your search contains special characters or whitespaces. Search results were not affected by the issue.
Tags
Tags can now contain certain special characters like ampersand (&) and percentage (%) without causing issues with the PRTG web interface when you filter for such a tag.
Welcome Page
The ticket count on the PRTG welcome page again shows the correct number of open tickets that are assigned to you.
Fixed:
Various other fixes and improvements to all parts of PRTG, updated user manual
Changed:
PRTG will not install a loopback adapter as part of the Npcap library for Packet Sniffer sensors anymore. When enabled, the adapter could lead to unwanted side-effects on other services, for example, DHCP servers.
Changed:
The configuration file of this version is not downwards compatible with previous PRTG versions.
Known Issues:
Under certain circumstances, there may be issues with the device tree synchronization between cluster nodes so that sometimes changes to settings may be lost after an outage and restart of the primary master. Manually restarting the failover node to trigger a new sync may improve the situation if you encounter issues.
Status: We are currently investigating the issue.
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: We are working on a fix for PRTG 19.3.52.

New in PRTG Network Monitor 19.2.49.2018 (Apr 16, 2019)

New in PRTG Network Monitor 19.1.49.1966 (Mar 28, 2019)

New
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.
Changed:
Sensors:
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.
Changed:
API:
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.
Improved:
Server:
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
Improved:
Sensors:
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).
Fixed:
Security:
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!
Fixed:
Sensors:
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.
Fixed:
Server:
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.
Fixed:
WebGUI:
Cluster:
We improved the layout of the Cluster Status page so that each host name is now fully shown.
The refresh of sensors pages on the cluster probe device now happens without unnecessarily appearing spinning wheels at the bottom of the page.
Switching the cluster node when using map rotation now works. In previous versions, PRTG was not able to find a map ID after switching the node and showed an according error message in this case.
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:
When moving objects in the device tree (for example, groups or devices), the More button that appears when more than 20 sub-objects (for example, sensors) are affected by the action will now redirect to a search page that lists all affected objects. In previous versions, this page just was empty and did not show any search results.
Using special characters like a dot (.) as custom channel unit now works and will not result in a broken device tree view anymore.
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:
System information pages now only request data according to the PRTG standard refresh timer (every 30 seconds) and do not cause the browser to send update calls every second for every table anymore.
The refresh button or the refresh indicator is now always visible on system information tables, depending on the current status of the table.
We removed spurious bullet points that sometimes appeared in system information tables when no data has been retrieved yet.
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.
Fixed:
Various:
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

New in PRTG Network Monitor 19.1.49.1916 (Mar 19, 2019)

New:
Apps:
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.
Changed:
Sensors:
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.
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.
API:
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.
Improved:
Server:
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
Sensors:
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).
Fixed:
Security:
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!
Sensors:
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.
Server:
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.
WebGUI:
Cluster:
We improved the layout of the Cluster Status page so that each host name is now fully shown.
The refresh of sensors pages on the cluster probe device now happens without unnecessarily appearing spinning wheels at the bottom of the page.
Switching the cluster node when using map rotation now works. In previous versions, PRTG was not able to find a map ID after switching the node and showed an according error message in this case.
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:
When moving objects in the device tree (for example, groups or devices), the More button that appears when more than 20 sub-objects (for example, sensors) are affected by the action will now redirect to a search page that lists all affected objects. In previous versions, this page just was empty and did not show any search results.
Using special characters like a dot (.) as custom channel unit now works and will not result in a broken device tree view anymore.
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:
System information pages now only request data according to the PRTG standard refresh timer (every 30 seconds) and do not cause the browser to send update calls every second for every table anymore.
The refresh button or the refresh indicator is now always visible on system information tables, depending on the current status of the table.
We removed spurious bullet points that sometimes appeared in system information tables when no data has been retrieved yet.
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.
Various:
Languages Files:
Major update of the Dutch language file, especially more consistency in terminology, and updated German language file
All Parts of PRTG

New in PRTG Network Monitor 19.1.48.2929 (Mar 4, 2019)

New in PRTG Network Monitor 19.1.48.2891 (Feb 19, 2019)

New in PRTG Network Monitor 19.1.48.2876 (Feb 14, 2019)

New in PRTG Network Monitor 19.1.48.2868 Beta (Feb 11, 2019)

Improved:
Sensors:
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.
Server:
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!).
WebGUI:
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.
Fixed:
Sensors:
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 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.
Security:
Login:
We fixed a security issue that allowed to modify text on the login page of the PRTG web interface. This content spoofing issue could have been exploited for phishing, for example.
We fixed a reflected XSS vulnerability on the login page of the PRTG web interface. Special thanks to Damian Schwyrz for reporting the issue!
Reports:
We removed PRTG credentials (login name and passhash) from the URL of HTML reports that appeared in certain cases.
Server:
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.
Notifications:
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.
WebGUI:
Dark Theme:
We improved the look of the dark theme on various places in the web interface.
Graphs in historic data reports will now always appear in light theme style, even if you use the dark theme of the PRTG web interface and run a historic data report. Reports always have a white background, but graphs appeared dark in previous versions when using the dark theme.
Graphs:
Unclickable graph legends do not appear as clickable anymore
Removed needless page footer when zooming a graph in a new window
Graphs on device tabs (2 days, 30 days, 365 days) show full sensor names again.
Maps:
If you delete an object like a sensor from the device tree, maps that include this object will still properly work afterwards. In the previous version, maps that included a deleted object were suddenly empty, which you could only resolve with a restart of the PRTG server.
Better responsiveness of status icons to the length of current messages
Map objects now indicate when they are already on the lowest layer and so cannot be sent to back anymore in this case.
Improved readability of Minigraph only objects
High priority maps with 5***** stars now show their name on the browser tab instead of "undefined" when you open them via Home from the PRTG main menu bar.
We fixed an issue with auto-scaling of public maps that occurred when using the cluster map object.
Note: Please note that due to these improvements to maps, a longer existing issue with the Data Tables map object Alarms (gauges) became visible. We fixed the issue in this version, but you might encounter public maps that are constantly reloading after you updated PRTG from version 18.4.47 or previous. The issue occurs if your map contains a custom map object that uses the code of the Alarms (gauges) object and you are not logged in to PRTG. For more details, please see the article Why does my public map constantly refresh?
Multi-Edit
We fixed an issue that appeared in rare cases when multi-editing sensors. If one or more sensors selected for multi-edit were created via auto-discovery but include settings that were required but not filled, multi-editing resulted in a validation error. This special scenario affected the IMAP sensor, for example.
The multi-edit menu is now always visible on larger lists even when you scroll down.
Fixed layout when showing all objects (for example, sensors) in multi-edit dialog windows
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:
Better usage of available space for several tables, which also results in tables without jumping content
The mouse pointer now indicates that you can click channels in a sensor table to open the settings.
Font sizes in tables are now the same in each column.
Some minor fixes for filtering with tags
Tickets:
Several style fixes for the PRTG ticket system
The multi-edit menu now works with lists of tickets, for example, to reopen 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.
Buttons: Improved positioning and style of several buttons
Breadcrumbs: Several layout fixes
Channel settings: The color picker now always reflects the current hex value.
Cluster: Several layout fixes for cluster visualizations, for example, on cluster status and cluster setting pages
Configuration reports: Several style fixes
Dependencies graph: Minor display fixes
Device tree: Fixed loading icons that only disappeared after a page refresh
Dialog windows: Several style fixes and usage improvements for dialog windows that you open via context menus, for example.
Hover popups: Graphs are ordered by covered time span again
Icons: Several fixes for icons throughout the web interface, for example, the object selector has the correct reading glass symbol now in dependency and library settings
IE11 and Edge: Several fixes for the web interface when used with Internet Explorer 11 and Edge
Language selection: We removed the needless request to select a file.
Lists: The behavior of "Select all" checkboxes in lists is more consistent now.
Management tab: Several layout fixes
Notification templates: Better usage of available space in the list of notification templates, so that longer template names are not cut off too early anymore
Priority and favorites: Several fixes for the option to set priority and favorites on several places
Remote probe installer dialog: Layout and style fixes for the dialog window that guides you through installing a remote probe
Reports: Several layout fixes for historic data reports
Setup page: No more empty boxes that appeared for user accounts with certain rights
Simulate error: Sensors now immediately show the "Simulated error" status after clicking the simulate error button and do not require a (manual) page refresh anymore.
Sunburst: Sections without elements that appear white in sunburst view have borders again.
Toplists: Several style and layout fixes for toplist pages
Various:
All Parts of PRTG:
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files
Note:
Probe and Sensors:
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.

New in PRTG Network Monitor 18.4.47.1962 (Dec 11, 2018)

Improved:
WebGUI:
Notifications:
You can now see all defined notification methods in your PRTG user account settings at a glance. The Notification Templates overview table has a new column that shows the Actions a notification template will perform when it is triggered.
You can now use a search field to filter for existing notification templates when you add or edit a Notification Trigger.
Maps:
We improved the readability of map objects with status-related background colors.
Server:
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.
Sensors:
HTTP Push Data Advanced:
The HTTP Push Data Advanced now supports UTF-8 characters in the section of received messages and can display, for example, Chinese, Japanese, or Russian characters in the sensor message.
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:
substring: This is the default mode that works like bindings[oid,value].
exact: This mode enforces an exact match of a value.
equal, greater, greaterorequal, less, lessorequal: This mode compares received numbers with the defined value.
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.
Fixed:
Server:
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.
Sensors:
Channels:
You can edit channel names in a sensor's channel settings again (where supported). In previous versions, the Name field in the channel settings often was read-only by mistake.
If you select the Data option Display in percent of maximum in the settings of a sensor channel, PRTG will now interpret any set Limits as percentage based on the maximum value to avoid false alarms.
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.
Notifications:
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.
WebGUI:
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
API:
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.
VariousL:
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

New in PRTG Network Monitor 18.4.46.1736 (Nov 16, 2018)

New in PRTG Network Monitor 18.4.46.1706 (Nov 7, 2018)

Improved
Server
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.
Improved
Sensors
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.
Changed
API
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.
Fixed
Sensors
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.
Fixed
WebGUI
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
Fixed
Various
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

New in PRTG Network Monitor 18.4.45.1898 (Oct 19, 2018)

New in PRTG Network Monitor 18.4.45.1889 (Oct 18, 2018)

Improved WebGUI:
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!
Improved Sensors:
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.
Improved Server:
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.
Fixed Sensors:
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.
Fixed WebGUI:
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:
The Messages tab of SNMP Trap and Syslog Receiver sensors now always shows the complete messages without the need to hover over each message.
Access rights tables that have more than 1 page because of many PRTG user groups work properly again. In previous versions, saving access rights on page 2 and onward resulted in a reset to None for each group.
Fixed Various:
All Parts of PRTG:
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files
Changed Tree Version:
Tree Version Update:
The configuration file of this version is not downwards compatible with previous PRTG versions.

New in PRTG Network Monitor 18.3.44.2054 (Sep 24, 2018)

Improved:
Security:
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.
Improved:
Sensors:
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
The NetApp System Health sensor now supports the storage configuration paths quad_path and quad_path_ha.
All NetApp sensors that use SOAP to retrieve monitoring data now support NetApp ONTAP version 9.4.
Improved:
WebGUI:
Notifications:
The "clear condition" for the State Trigger now denotes more clearly in which cases the rule will apply.
Reports:
You can run a report another time when you change 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
Improved:
Server:
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=&subtype=channel&subid=0&name=limitwarningmsg&show=nohtmlencode returns the warning message that is defined for a channel limit.
Auto-Discovery:
We improved the device rescan functionality of the auto-discovery. If you have selected the option Skip auto-discovery for known devices/IPs, PRTG will recognize more devices that were already discovered as known and skip the rescan. The improvement is especially useful if host names can be resolved to more than one IP address.
You can now start the auto-discovery with template on multiple devices at the same time via device lists and the multi-edit menu.
We also fixed some internal errors that occurred during auto-discovery in certain cases.
Logging:
This version includes some more improvements for the new logging framework. For example, we fixed an issue that prevented PRTG from writing web server logs in certain cases.
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
Web Server Starter:
We fixed a timing issue that resulted in failing automatic starts of the web server in certain cases.
Fixed:
Sensors:
Exchange (Powershell) Sensors:
Stability improvements for Exchange (Powershell) sensors
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.
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:
The Sensor Factory sensor now correctly calculates values even if the source sensor has been down for some time. In previous versions, the sensor sometimes used very high source values to calculate values according to the formula instead of correctly using 0 values.
The Sensor Factory sensor now shows data in graphs and reports even if source sensors are paused for a longer time. In previous versions, graph data was missing in such cases.
sFlow:
We fixed an issue with sFlow sensors that did not properly process very high traffic values of inbound and outbound interfaces.
SNMP Sensors:
The SNMP timeout of SNMP sensors works again.
The OID that you can use as variable in the name of custom and generic SNMP sensors will be replaced with its value again.
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
Fixed:
WebGUI:
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.
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.

New in PRTG Network Monitor 18.3.43.2323 (Aug 20, 2018)

New in PRTG Network Monitor 18.3.43.2317 (Aug 14, 2018)

New:
Sensors:
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.
Improved:
Sensors:
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:
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 Templates is the new wording for the section in your PRTG user account settings where you define notification methods and their content (before: "Notifications").
"Triggers" are now called Notification Triggers, for example, the triggers tab on a sensor's or device's page.
On the Notification Triggers tab of a monitoring object, triggers now have a Rule that provokes a trigger (the according table heading was "Notifications" before).
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.
Server:
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.
Search:
We improved the search speed in the manual that is delivered with your PRTG installation.
WebGUI:
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.
Fixed:
Sensors:
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:
SNMP custom sensors correctly return negative values again.
SNMP custom sensors correctly display speed values again when using delta as value type.
WebGUI:
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
Server:
API:
You can set limits via the according API call again.
The API call getsensordetails.json will now return valid JSON even if there are quotes in object names (like sensors, devices, groups, probes).
Security:
In certain cases, the passhash appeared in the URL when switching cluster nodes. We fixed the issue.
Various:
All Parts of PRTG:
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files

New in PRTG Network Monitor 18.3.42.1748 (Jul 18, 2018)

New in PRTG Network Monitor 18.3.42.1727 (Jul 11, 2018)

New:
Sensors:
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.
New:
Notifications:
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.
Changed:
Geo Maps:
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.
Improved:
Notifications:
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.
Improved:
Sensors:
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.
Improved:
Server and Probes:
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
Improved:
WebGUI:
Maps:
We updated older map objects to fit better with the new style of the PRTG web interface.
Fixed:
Sensors:
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.
Fixed:
WebGUI:
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
Hover Popups:
We added the Scan Now button to hover popups again. It was not available in previous versions by mistake.
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.
Fixed:
Various:
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.
Various:
Several other minor improvements and fixes, updated user manual, updated language files
System Information:
You can select the text in System Information tables with your mouse again to copy and paste the entries.
Changed:
Tree Version:
Tree Version Update:
The configuration file of this version is not downwards compatible with previous PRTG versions.

New in PRTG Network Monitor 18.2.41.1652 (Jun 6, 2018)

New:
WebGUI:
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:
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
Changed:
WebGUI:
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.
Fixed:
Security:
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. In certain cases, it was possible to generate and view reports without using correct credentials
Fixed:
Sensors:
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
Fixed:
WebGUI:
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:
We improved the graph alignment in PDF reports.
We fixed some corner cases that caused wrong time spans in historic data reports when using quick range buttons.
Tables:
Various performance and layout improvements for tables in the web interface

New in PRTG Network Monitor 18.2.40.1683 (May 7, 2018)

New:
Sensors - 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.
Improved:
Sensors - NetFlow V9 and IPFIX:
NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors now support IPv6 flows.
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".
WebGUI - 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.

New in PRTG Network Monitor 18.2.39.1661 (Apr 11, 2018)

FIXED:
Sensors:
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.
WebGUI:
Internet Explorer 11
Several fixes for the usage of the PRTG web interface with Internet Explorer 11
Offline activation of your license with Internet Explorer 11 works again.
Using checkboxes on certain tables now works with Internet Explorer 11.
Creating maps and reports with Internet Explorer 11 is possible again.
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
Server:
Performance: We fixed some more issues that caused performance losses and resulted in PRTG core server timeouts in certain cases.
Several other minor improvements and fixes, updated user manual, updated language files

New in PRTG Network Monitor 18.1.39.1661 (Apr 11, 2018)

Security:
Improved:
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. Please use single or double quotes to escape special characters and whitespaces in the parameters fields.
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 STO LABS, especially to Lucas Carmo, Edward Toledano, and Ricardo Fajin. Thank you!
Outgoing Connections:
Outgoing connections from the PRTG core server to Paessler servers for activation, update check, and downloads now use HTTPS.
User Rights:
Improved:
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.
Sensors:
Improved:
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.
Changed:
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!
The monitoring data of this sensor was assigned to the wrong channels in the previous PRTG version 18.1.38. We fixed this issue, but you have to add your NetApp System Health sensors anew to benefit from the fix, existing sensors of this type will not be updated.
The Storage configuration path channel will now return N/A as channel value and show an Up status if there is no configuration path available, because its availability depends on the NetApp version. This approach will prevent the sensor from showing false errors.

New in PRTG Network Monitor 18.1.38.11934 (Mar 7, 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) level 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.
The DICOM Bandwidth sensor monitors the bandwidth usage of a C-STORE request. It sends one or more DICOM images that you have stored on a local disk or share and checks if the DICOM device can handle the C-STORE request. You can use the sensor to test your Picture Archiving and Communication (PACS) system, for example.
The DICOM C-ECHO sensor monitors the availability of DICOM devices by sending C-ECHO requests. You can use the sensor to verify that the DICOM handshake is executed and that your target system is capable of answering DICOM messages.
The DICOM Query/Retrieve sensor monitors the C-FIND capability of DICOM devices. It sends a C-FIND request or Modality Worklist (MWL) query to the target device and counts all found items. You can specify search levels to only count specific items.
The HL7 sensor monitors the availability of HL7 interfaces. It sends an HL7 message to the target device and checks for a valid response.
EVENT LOG (WINDOWS API) AND WMI EVENT LOG:
You can now use negative filtering in Event Log (Windows API) sensors and 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.
The sensor types SSH Disk Free, SSH INodes Free, SSH Load Average, SSH Meminfo, SSH Remote Ping, and SFTP Secure File Transfer Protocol will revert to the default Connection Timeout 60 seconds and to the default Shell Timeout 10 seconds. Note: The timeout settings will only revert to default when you had set the timeout to more than 60 seconds in previous versions!
The sensor types SSH SAN Enclosure, SSH SAN Logical Disk, SSH SAN Physical Disk, SSH SAN System Health will always revert to the default Connection Timeout 300 seconds and to the default Shell Timeout 300 seconds. It is not possible to change the timeout settings for these sensors, the underlying PRTG system will always use the default values!

New in PRTG Network Monitor 18.1.37.12158 (Feb 6, 2018)

New in PRTG Network Monitor 18.1.36.3733 (Jan 23, 2018)

New in PRTG Network Monitor 17.4.36.3670 (Dec 19, 2017)

New in PRTG Network Monitor 17.4.36.3595 (Dec 12, 2017)

Improved:
Sensors:
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:
Compression savings bytes
Compression savings bytes %
Deduplication savings bytes
Deduplication savings bytes %
Total savings bytes
Total savings bytes %
Files free
Files free %
Changed:
Sensors:
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.
Fixed:
WebGUI:
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:
Device Tree: improved usage of available space in the M-view of the device tree (more sensors visible at a glance, sensor names are not abbreviated too early, better differentiation between devices, and more)
Input fields: disabled auto-complete for input fields (for example, username, password) in settings
Reports: fixed layout of header, footer, comments
Reports: General layout fixes and improvements, for example, tables now use the full paper width.
Maps: Connection lines in the Map Designer are visible again with Snap to Grid enabled.
Maps: fixed display in full-screen mode
Maps: improved visibility of text in map objects
Maps: fixed map object "Alarms Gauges"
Maps: PRTG for Android can open maps again.
Graphs: better visibility of the primary channel
General: layout fixes for certain screen resolutions
Libraries: several fixes for the Libraries page
Cluster: Failover nodes are read-only again.
Smart Setup: fixed several issues with the Smart Setup
Table Lists: We improved the behavior of mouse overs on table lists like device and sensor lists. Tables will not jump around anymore and the table width dynamically adjusts to your browser size.
Dialog windows: Dialog windows (for example, setting dialogs) automatically adjust to browser size and stay centered.
Fixed
Sensors
Common SaaS
Sensors:
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
Server:
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
Security:
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
Remote Probes:
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
Various:
All Parts of PRTG:
Various other fixes and improvements, as well as an updated user manual

New in PRTG Network Monitor 17.4.35.3441 (Nov 27, 2017)

New in PRTG Network Monitor 17.3.33.3251 (Nov 6, 2017)

NEW
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:
NetApp Aggregate
NetApp I/O
NetApp LIF
NetApp LUN
NetApp NIC
NetApp Physical Disk
NetApp System Health
NetApp Volume
The sensors monitor your NetApp accessing the API via SOAP and support the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3.
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 Sensorsrest 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!
CHANGED
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:
Report templates
Device templates
Device icons
SNMP library (oidlib) files
Language files
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.
IMPROVED
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.

New in PRTG Network Monitor 17.3.33.2830 (Sep 11, 2017)

New:
Sensors:
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:
NetApp Aggregate
NetApp I/O
NetApp LIF
NetApp LUN
NetApp NIC
NetApp Physical Disk
NetApp System Health
NetApp Volume
The sensors monitor your NetApp accessing the API via SOAP and support the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3.
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 Sensorsrest 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!
Changed:
Core/WebGUI:
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:
Report templates
Device templates
Device icons
SNMP library (oidlib) files
Language files
Improved:
Sensors:
Amazon CloudWatch Sensors:
We have added the region EU (London) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors.
Notifications:
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.

New in PRTG Network Monitor 17.3.33.2753 (Aug 30, 2017)

New in PRTG Network Monitor 17.3.33.2686 (Aug 23, 2017)

FIXED SENSORS:
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.
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
The auto-discovery now works when using a generic metascan with the SNMP Traffic sensor.
Data graphs of SNMP Traffic sensors have an improved scaling when showing in and out traffic as positive and negative area chart.
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
FIXED SECURITY:
SECURITY
We have fixed a possible XSS vulnerability (CVE-2017-12879).
FIXED WEBGUI:
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.
GEO MAPS
When you change geo locations for objects in the device tree, Geo Maps will accordingly update and show the defined location again.
FIXED SERVER AND PROBES:
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.
Stability improvements for the PRTG core server and probe system
FIXED AUTO-DISCOVERY:
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.
FIXED NOTIFICATIONS:
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.
FIXED VARIOUS:
VARIOUS
Various minor fixes and improvements, updated user manual, updated language files

New in PRTG Network Monitor 17.3.32.2478 (Jul 26, 2017)

New in PRTG Network Monitor 17.3.32.2339 (Jul 11, 2017)

New in PRTG Network Monitor 17.3.32.2309 (Jul 5, 2017)

New in PRTG Network Monitor 17.2.32.2279 (Jun 28, 2017)

New in PRTG Network Monitor 17.2.32.2206 Beta (Jun 15, 2017)

CHANGED:
LOGIN:
DEFAULT LOGIN. We have removed the Default Login button. If you use the default credentials of PRTG, the login fields are now pre-filled- Login Name: prtgadmin and Password: prtgadmin. Use the Login button to proceed. If you have changed the default credentials (which we strongly recommend!), the login works as before: just enter your PRTG user account credentials and log in.
IMPROVED:
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).
FIXED:
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 0values. 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: Fan Failure Predicted, Fan Module Failure Predicted, Power Supply Failure Predicted. These channels do not return the expected values from the target device.
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:
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. The setting "Use Data Table Value in Sensor Message" of SQLv2 sensors will now be saved when you create a device template with these sensors.
Several fixes for processing block comments in SQL scripts.
We have improved the handling of DECLARE statements for SQLv2 sensors. For example, you can now use DECLARE without semicolons (;). This allows you to copy&paste SQL queries directly from your SQL Server Management Studio, for example, into your .sql file that you use with your SQL sensor.
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. The API call /api/discovernow.htm will correctly return an error if a non-existing device template is passed with the call instead of just returning OK.
The columns "datetime" and "timeonly" will now return the same, correct time.
The API call /api/getsensordetails.json will now return a value (true or false) for the "favorite" property.
VARIOUS. Various minor fixes and improvements, updated user manual, updated language files

New in PRTG Network Monitor 17.2.31.2153 (Jun 8, 2017)

New in PRTG Network Monitor 17.2.31.2018 (May 16, 2017)

New in PRTG Network Monitor 17.2.31.1977 (May 10, 2017)

New in PRTG Network Monitor 17.2.31.1917 (May 3, 2017)

New in PRTG Network Monitor 17.2.30.1883 (Apr 25, 2017)

New in PRTG Network Monitor 17.2.30.1825 (Apr 19, 2017)

New in PRTG Network Monitor 17.2.30.1767 (Apr 11, 2017)

New in PRTG Network Monitor 17.1.30.1719 (Apr 6, 2017)

New in PRTG Network Monitor 17.1.30.1681 (Mar 28, 2017)

New in PRTG Network Monitor 17.1.29.1427 (Feb 28, 2017)

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.
Push Notifications:
Push notifications in PRTG freeware versions work again. PRTG did not send them out anymore after the trial period has expired.

New in PRTG Network Monitor 17.1.28.1341 (Feb 16, 2017)

New in PRTG Network Monitor 17.1.28.1032 (Jan 10, 2017)

New in PRTG Network Monitor 16.4.28.7352 (Dec 9, 2016)

New in PRTG Network Monitor 16.4.28.7339 (Dec 8, 2016)

New in PRTG Network Monitor 16.4.28.7279 (Dec 2, 2016)

New in PRTG Network Monitor 16.4.27.7140/7141 (Nov 22, 2016)

New in PRTG Network Monitor 16.4.27.6984 (Nov 9, 2016)

New in PRTG Network Monitor 16.4.27.6845 (Oct 26, 2016)

New in PRTG Network Monitor 16.4.27.6719 (Oct 11, 2016)

New in PRTG Network Monitor 16.3.26.6384 (Sep 28, 2016)

New in PRTG Network Monitor 16.3.25.5488 (Aug 2, 2016)

New in PRTG Network Monitor 16.3.24.4979 (Jul 13, 2016)

New in PRTG Network Monitor 16.2.24.4655 (Jun 29, 2016)

New in PRTG Network Monitor 16.2.24.4469 (Jun 23, 2016)

New in PRTG Network Monitor 16.2.24.4045 (Jun 1, 2016)

New in PRTG Network Monitor 16.2.24.3791 (May 12, 2016)

New in PRTG Network Monitor 16.2.24.3685 (May 10, 2016)

FIXED SENSORS:
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
FIXED NOTIFICATIONS:
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
FIXED AUTO-DISCOVERY.
Icons. Auto-Discovery adds the correct vendor specific device icons again.
Stability. Stability improvements: In certain cases auto-discovery caused access violations.
FIXED - VARIOUS:
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, as well as an updated user manual

New in PRTG Network Monitor 16.2.23.3171 (Apr 11, 2016)

New in PRTG Network Monitor 16.1.22.2391 (Mar 3, 2016)

New in PRTG Network Monitor 16.1.22.2251 (Feb 24, 2016)

New in PRTG Network Monitor 16.1.22.2011 (Feb 22, 2016)

FIXED:
SENSORS:
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. Adding the SSL Certificate sensor using a device template works correctly.
SNMP Custom Advanced:
OIDs for the SNMP Custom Advanced sensor support can start with points (.)
SNMP Cisco System Health:
SNMP Cisco System Health can show negative values.
NOTIFICATIONS:
Placeholders:
Placeholders in notification emails were not replaced correctly in certain cases.

New in PRTG Network Monitor 16.1.21.1257 (Jan 18, 2016)

New in PRTG Network Monitor 15.4.21.5215 (Dec 3, 2015)

New in PRTG Network Monitor 15.4.21.5161 (Dec 1, 2015)

New in PRTG Network Monitor 15.4.20.4775 (Nov 12, 2015)

New in PRTG Network Monitor 15.4.20.4705 (Nov 9, 2015)

New in PRTG Network Monitor 15.4.20.4491 (Oct 29, 2015)

New in PRTG Network Monitor 15.4.20.4377 (Oct 20, 2015)

New in PRTG Network Monitor 15.4.19.4197 (Oct 6, 2015)

New in PRTG Network Monitor 15.3.19.4027 (Sep 21, 2015)

New in PRTG Network Monitor 15.3.19.3971 (Sep 14, 2015)

New in PRTG Network Monitor 15.3.18.3615 (Aug 20, 2015)

New in PRTG Network Monitor 15.3.18.3591 (Aug 20, 2015)

New in PRTG Network Monitor 15.3.18.3509 (Aug 13, 2015)

New in PRTG Network Monitor 15.3.18.3333 (Aug 3, 2015)

New in PRTG Network Monitor 15.3.18.3271 (Aug 3, 2015)

New in PRTG Network Monitor 15.3.17.2995 (Aug 3, 2015)

New in PRTG Network Monitor 15.3.17.2803 (Aug 3, 2015)

New in PRTG Network Monitor 15.2.17.2631 (Jun 11, 2015)

New in PRTG Network Monitor 15.2.16.2219 (Apr 29, 2015)

New in PRTG Network Monitor 15.1.14.1977 (Mar 31, 2015)

New in PRTG Network Monitor 15.1.14.1777 (Mar 16, 2015)

New in PRTG Network Monitor 15.1.14.1709 (Mar 10, 2015)

New in PRTG Network Monitor 15.1.14.1609 (Feb 25, 2015)

New [Sensors]:
SNMP Cisco UCS Blade sensor: monitors the health status of a blade server in a Cisco UCS device.
SNMP Custom Lookup (BETA) sensor monitors a string value returned by a specific OID and maps it to a sensor status.
Cloud HTTP (BETA) sensor monitors the loading time of web servers from various locations worldwide via HTTP using the new PRTG cloud
Cloud Ping (BETA) sensor monitors the ping time to a target device from various locations worldwide using the new PRTG cloud
Improved/Changed/Bugfixes [Sensors]:
FTP Server File Count sensor with a dedicated port setting
SNMP Cisco ASA VPN Traffic sensor has now the option to keep the "Up" status if there is no active connection. You can specify this behavior in the sensor settings.
QNAP Physical Disk: Damaged disks now result in a "Warning" status of the sensor (instead of an error); this allows to continue monitoring of other values.
Fixed keyword check of the HTTP Transaction sensor, response strings did not trigger status changes ("response must include"/"response must not include")
SCVMM sensors: Improvements to version check for add-snapin / import modules
Various fixes to the "Custom HTTP Headers" function of the HTTP XML/REST Value sensor.
Debug options ("write result to disk") for HTTP Push Data sensors and Windows Terminal sensors
Windows Last Update sensor showed a false error message that said that Windows Registry Service is not running in some cases
SNMP Custom String sensor threw an error for an empty string when triggering a change notification.
Fixed Smart URL Replacement for HTTP Advanced Sensor in compatibility mode
More descriptive channel names for Cisco System Health sensors
MySQL v2 sensor could not process a specific data type ("System.UInt64")
SSH SAN sensors with better differentiation between "wrong data format" and "timeout" errors
SNMP Dell PowerEdge System Health sensor could not process channel masks
Windows Performance Counter sensors sporadically showed an error when a PerfCounter connection had to be re-created
WMI SQL sensors shows incorrect values for the category "locks"
File Content sensor with better error handling and transmitting only new lines now optimized also for very large files
SSH SAN System Health sensor now supports devices that provide no other information than name, value, and status.
Windows Registry sensor correctly queries its parent device again. It mistakenly queried the parent probe before.
SNMP Windows Service sensor had problems to show service names correctly in some Windows language versions (for example, Russian, Japanese)
Sensor channels that show if something (for example, a service or device) is on/off or successful/failing have now a more beautiful and comprehensive graphical display.
WMI Microsoft SQL sensors does not round values of channels with "per second" units to integers anymore. This caused incorrect sensor results for some metrics (for example, for "deadlocks per second") previously.
New/Improved/Changed [WebGUI/Server]:
Speed optimizations for auto-discovery
New API call shows the legend of data graphs (ID, name, unit, color): /api/chartlegend.json?id=[sensor_id]
New API call /api/getsensordetails.json?id=[sensorid] is the JSON equivalent to the existing XML call.
Stability improvements to location resolution in Geo Maps
"Quick ranges" on historic data pages set incorrect dates
Stability improvements for Toplists
Restructured "Setup" menu
Library triggers are now completely independent from the "inherit trigger" switch on the "Notifications" tab of objects in the device tree.
PRTG Administration Tool does not allow any more to enter used ports when defining ports for web server and probe connections. Improved server restart rules.
Notifications: Logs now show when a notifications was triggered but could not be delivered because there is no corresponding active notification contact for the target user.
Libraries: We preset the filter for „Linked Object" in the Node Display Settings with „Root" for your convenience.
The PRTG Status page now shows how busy PRTG was for you in the new "Activity History".
Geo Maps zoom fixed.
You can make the passhash of your PRTG user account visible with a "Show Passhash" button. We previously removed the passhash display for security reasons.
Amazon SNS notifications did not work when containing the special characters * or § in subject or message.
Buttons in the "Compare Sensors" dialog did not work.
Library node filter "by status" did not work.
Updated user manual: Now with a neat overview of available channels and screenshots in all sensor chapters!
Updated language files
Deeper integration of the online help into the PRTG web interface
"Configuration Guru" enhanced with helpful video tutorials
Bugfixes [Core/Server]
When using the historic data function for "all nodes" in a cluster, percentiles were incorrect.
Bugfix [MiniProbes]: Stability improvements for connections via PRTG's mini probe interface
Bugfixes [EC]:
Fixed an error when deleting active server connections
Now showing better default values for start date in date time picker for "Acknowledge Until" and "Pause Until"
Some minor fixes and improvements to the Enterprise Console.
We also implemented various other minor fixes and improvements to all parts of PRTG that did not make it onto this page.

New in PRTG Network Monitor 15.1.13.1455 (Feb 11, 2015)

New in PRTG Network Monitor 15.1.13.1311 (Jan 28, 2015)

New in PRTG Network Monitor 15.1.13.1089 (Jan 15, 2015)

New: Free-to-Use Push Notifications:
With this update, we introduce a great new notification option: You can now send push notifications to your Android or iOS devices—for free, included in every PRTG version, even in the PRTG Freeware! This is a very comfortable way to get alerts from PRTG. All you need is PRTG for Android or PRTG for iOS and you can set up your free push notifications within seconds. Please see the Knowledge Base article How can I send push notifications with PRTG? for details.
New [WebGUI/Server]:
PRTG introduces responsive design so that the webGUI automatically adjusts to the size of your screen. This allows you to see even more information at a glance!
To get a much better and more detailed picture about your devices, PRTG now analyzes the devices you add and recommends appropriate sensor types on the device overview page. Only one click to add a sensor suggestion directly to the device and you never miss important information about your equipment again!
Together with push notifications, we introduce notification contacts. PRTG users can now define and edit their own dedicated ways to get notifications to email address(es), phone number(s), and push device(s). For the notifications types "Send Email", "Send SMS/Pager Message", and "Send Push Notification" you can now choose a user or user group from a list to send a notification to the current notification contacts of the according recipient(s).
You can now generate configuration reports for various objects in PRTG like users, user groups, maps, reports, and system configuration. This function is available under Reports | Configuration Reports in the main menu bar.
You can now specify the channels you want to show in historic data graphs that you generate via the "Historic Data" tab of a sensor.
You are now able to zoom into data graphs and to scroll on the time axis with according control buttons to analyze your monitoring data even smarter.
Maps ('dashboards') have an auto-scaling option to adapt automatically to your screen size.
You can now enter your PRTG license key directly into the webGUI so you do not need to use the Administrator tool for this purpose anymore.
You can now define a custom port for your Mini Probe connections.
PRTG removes masked passwords that you entered into settings pages from the support bundle and does not send them.
New [Sensors]:
The Dell PowerVault MDi Physical Disk sensor show statistics for a physical drive on a Dell PowerVault storage system. Note: We renamed the existing Dell PowerVault MDi sensor to Dell PowerVault MDi Logical Disk sensor because of this.
The WMI Microsoft SQL Server 2014 sensor monitors the performance of a database
The MongoDB System Health sensor monitors the status of a MongoDB server via HTTP and the admin web console
New [EC]:
Facelift: The new appearance of the Enterprise Console comes with a fresh and clear user interface and new graphics, similar to the webGUI
Improved [WebGUI]:
Map editor with better performance and new map objects "QR codes" and "traffic lights"
PRTG notifies you if Similar Sensors analysis is off
You can filter device lists by tag
You can use the logical operators + (must have) and - (must not have) in library and table tag filters, e.g., -windows would show all sensors/devices that do not have "windows" as tag, +A;B-C would mean "objects with the tags A and B but not with the tag C"
Added a quick print button for QR codes on device lists
Tables have more columns to show more information
The "Compare Sensors" feature has more options to analyze compared data
Improved [Sensors]:
SNMP Traffic sensors with new option to ignore 'deactivated' (ifAdminStatus=down) status
WMI Security Center sensor now uses lookups
Channel names of probe and system health sensors are now more meaningful
SNMP Linux Disk Free sensor enhanced with a channel for free INodes
SNMP QNAP sensors use more appropriate OIDs now, including fallback. Note: If you already use QNAP sensors and experience strange values now, please add the sensors anew.
Google Analytics sensor has new metrics (exceptions, fatalExceptions, exceptionsPerScreenview, fatalExceptionsPerScreenview) and allows special characters in the password field.
Hyper-V Virtual Storage Device sensor supports Hyper-V on Windows Server 2012 R2
HTTP XML/REST Value sensor supports Smart URL Replacement and has an optional setting to define custom HTTP headers
Various sensors have now an optional debug log setting
FTP Server File Count sensor supports SSL connections and can count the files in a specific folder or in all subfolders. It also supports port definitions: When monitoring via a URL, you can add the port number with ":[port]", and when checking a folder on the parent device, the sensor provides an extra port setting
EXE/Script Advanced, SSH Scrip Advanced, and HTTP Push Data Advanced sensors support now JSON results
Windows Network Card sensor supports teamed adapters on Windows Server 2012
Amazon CloudWatch sensor with additional channels for averages and with more expressive error messages
SNTP sensor supports IPv6 devices and we improved its stability
HTTP Advanced sensor with new authentication method "Digest Access Authentication" and the option to check for keywords in the response
SNMP Custom String sensor has a new setting that allows you to define the format of the result value: String, hexadecimal bytes (e.g., MAC addresses), or decimal bytes (e.g., IP addresses)
Windows MSMQ Queue Length sensor can show the number of messages in outgoing queues
AVM FRITZ!Box WAN Interface sensor asks for credentials when you add it manually. Note: If an existing sensor shows an error after a Fritz!OS update, please add the sensor anew to see the new credentials option.
Complete rework of the RADIUS sensor: better performance and compatibility with RADIUS servers
SNMP Linux Meminfo sensor has 6 new channels to monitor used physical memory, used swap memory, and used memory on the whole system (percentage and absolute values)
SNMP RMON sensors use the "Port Name Template" of the SNMP Compatibility Options of the parent device
Improved [Security]:
We implemented further improvements to the overall security of PRTG for a better protection against potential attacks.
Account pages and QR codes do not include the password hash anymore. Note: If you need a user account's passhash for API programming, please use the according API function to query a passhash using username and password.

New in PRTG Network Monitor 14.4.13.3799 (Dec 22, 2014)

New in PRTG Network Monitor 14.4.13.3771 (Dec 17, 2014)

New in PRTG Network Monitor 14.4.13.3741 (Dec 11, 2014)

New in PRTG Network Monitor 14.4.13.3721 (Dec 11, 2014)

New: Free-to-Use Push Notifications:
With this update, we introduce a great new notification option: You can now send push notifications to your Android or iOS devices—for free, included in every PRTG version, even in the PRTG Freeware! This is a very comfortable way to get alerts from PRTG. All you need is PRTG for Android or PRTG for iOS and you can set up your free push notifications within seconds. Please see the Knowledge Base article How can I send push notifications with PRTG? for details.
New [WebGUI/Server]:
PRTG introduces responsive design so that the webGUI automatically adjusts to the size of your screen. This allows you to see even more information at a glance!
To get a much better and more detailed picture about your devices, PRTG now analyzes the devices you add and recommends appropriate sensor types on the device overview page. Only one click to add a sensor suggestion directly to the device and you never miss important information about your equipment again!
Together with push notifications, we introduce notification contacts. PRTG users can now define and edit their own dedicated ways to get notifications to email address(es), phone number(s), and push device(s). For the notifications types "Send Email", "Send SMS/Pager Message", and "Send Push Notification" you can now choose a user or user group from a list to send a notification to the current notification contacts of the according recipient(s).
You can now generate configuration reports for various objects in PRTG like users, user groups, maps, reports, and system configuration. This function is available under Reports | Configuration Reports in the main menu bar.
You can now specify the channels you want to show in historic data graphs that you generate via the "Historic Data" tab of a sensor.
You are now able to zoom into data graphs and to scroll on the time axis with according control buttons to analyze your monitoring data even smarter.
Maps ('dashboards') have an auto-scaling option to adapt automatically to your screen size.
You can now enter your PRTG license key directly into the webGUI so you do not need to use the Administrator tool for this purpose anymore.
You can now define a custom port for your Mini Probe connections.
PRTG removes masked passwords that you entered into settings pages from the support bundle and does not send them.
New [Sensors]:
The Dell PowerVault MDi Physical Disk sensor show statistics for a physical drive on a Dell PowerVault storage system. Note: We renamed the existing Dell PowerVault MDi sensor to Dell PowerVault MDi Logical Disk sensor because of this.
The WMI Microsoft SQL Server 2014 sensor monitors the performance of a database
The MongoDB System Health sensor monitors the status of a MongoDB server via HTTP and the admin web console
New [EC]:
Facelift: The new appearance of the Enterprise Console comes with a fresh and clear user interface and new graphics, similar to the webGUI
Improved [WebGUI]:
Map editor with better performance and new map objects "QR codes" and "traffic lights"
PRTG notifies you if Similar Sensors analysis is off
You can filter device lists by tag
You can use the logical operators + (must have) and - (must not have) in library and table tag filters, e.g., -windows would show all sensors/devices that do not have "windows" as tag, +A;B-C would mean "objects with the tags A and B but not with the tag C"
Added a quick print button for QR codes on device lists
Tables have more columns to show more information
The "Compare Sensors" feature has more options to analyze compared data
Improved [Sensors]:
SNMP Traffic sensors with new option to ignore 'deactivated' (ifAdminStatus=down) status
WMI Security Center sensor now uses lookups
Channel names of probe and system health sensors are now more meaningful
SNMP Linux Disk Free sensor enhanced with a channel for free INodes
SNMP QNAP sensors use more appropriate OIDs now, including fallback. Note: If you already use QNAP sensors and experience strange values now, please add the sensors anew.
Google Analytics sensor has new metrics (exceptions, fatalExceptions, exceptionsPerScreenview, fatalExceptionsPerScreenview) and allows special characters in the password field.
Hyper-V Virtual Storage Device sensor supports Hyper-V on Windows Server 2012 R2
HTTP XML/REST Value sensor supports Smart URL Replacement and has an optional setting to define custom HTTP headers
Various sensors have now an optional debug log setting
FTP Server File Count sensor supports SSL connections and can count the files in a specific folder or in all subfolders. It also supports port definitions: When monitoring via a URL, you can add the port number with ":[port]", and when checking a folder on the parent device, the sensor provides an extra port setting
EXE/Script Advanced, SSH Scrip Advanced, and HTTP Push Data Advanced sensors support now JSON results
Windows Network Card sensor supports teamed adapters on Windows Server 2012
Amazon CloudWatch sensor with additional channels for averages and with more expressive error messages
SNTP sensor supports IPv6 devices and we improved its stability
HTTP Advanced sensor with new authentication method "Digest Access Authentication" and the option to check for keywords in the response
SNMP Custom String sensor has a new setting that allows you to define the format of the result value: String, hexadecimal bytes (e.g., MAC addresses), or decimal bytes (e.g., IP addresses)
Windows MSMQ Queue Length sensor can show the number of messages in outgoing queues
AVM FRITZ!Box WAN Interface sensor asks for credentials when you add it manually. Note: If an existing sensor shows an error after a Fritz!OS update, please add the sensor anew to see the new credentials option.
Complete rework of the RADIUS sensor: better performance and compatibility with RADIUS servers
SNMP Linux Meminfo sensor has 6 new channels to monitor used physical memory, used swap memory, and used memory on the whole system (percentage and absolute values)
SNMP RMON sensors use the "Port Name Template" of the SNMP Compatibility Options of the parent device
Improved [Security]:
We implemented further improvements to the overall security of PRTG for a better protection against potential attacks.
Account pages and QR codes do not include the password hash anymore. Note: If you need a user account's passhash for API programming, please use the according API function to query a passhash using username and password.
Bugfixes [Sensors]:
SNMP Printer sensor can handle negative supply values (error codes)
IMAP sensor now only checks the age of an email if it could process the date correctly
Windows Last Update sensor checks if the remote registry service is running and triggers the start of the service automatically if it is not running
SSH Script Advanced sensor didn't show values for the "Execution Time" channel
WMI and SNMP Custom String sensors couldn't completely display messages with a '#' sign
Some sensors did not work with IPv6 devices although they should do so
The '"Value Mode" of sensor channels sometimes calculated incorrect values
SNMP HP ProLiant System Health sensor did not work after an update of "HP Insight Management Agents for Windows Server x64 Editions". Furthermore, this sensor type uses the correct OID for the overall status channel now.
HTTP Transaction sensor: keyword check did not work
Stability improvements for SID connections of the Oracle v2 sensor
File Content sensor with better error handling and reading only appended lines now works also with very large files
Bugfixes [WebGUI/Server]:
Change trigger were not correctly displayed for some sensors
Several fixes to data tables and reports
Auto-Discovery with templates executed a full auto-discovery and not only the selected templates
Ticket search found tickets but didn't list them
Device template of the Active Directory Replication Errors sensor used wrong AD neighbors
Reports ignored the "hours-of-day" settings for up- and downtime lists
Hover popups appear now faster on group, device, and sensor pages
When a map object file was deleted from the PRTG data folder, it is now possible to remove this object from a map. Before this fix, this was only possible with a workaround.
Stability improvements for map rotation when using custom scripts
Fixed display of min/max values in gauges
Libraries were not displayed correctly in some cases (nodes were cut off)
Bugfixes [EC]:
Fixed problems when deleting an active server connection
Stability and performance improvements, as well as many other fixes
Bugfix [Notifications]: PowerShell Notifications caused errors and the corresponding scripts were executed too often
Bugfix [Mini Probes]: Several fixes to the Mini Probe interface
Changed [Administration]: We renamed the "PRTG Administrator" program to "PRTG Administration Tool"
Hundreds of minor fixes and improvements to all parts of PRTG, as well as updates and a facelift for the user manual in your installation.

New in PRTG Network Monitor 14.4.12.3469 (Nov 13, 2014)

New in PRTG Network Monitor 14.4.12.3409 (Nov 6, 2014)

New in PRTG Network Monitor 14.4.12.3331 (Oct 28, 2014)

New in PRTG Network Monitor 14.4.12.3283 (Oct 22, 2014)

Improved [Security]:
Fix for POODLE: We have already implemented a fix for this SSLv3 security vulnerability and disabled the outdated SSL 3.0 encryption for PRTG.
We have massively upgraded the encryption security of PRTG’s webserver to make the usage of PRTG even more secure.
We have upgraded the OpenSSL libraries to version 1.0.1h (these are used for SSL connections of the web server, the core/probe and probe/probe connections as well as for most sensor types that offer SSL).
We have locked down the accepted ciphers for SSL connections to the most secure ones that will allow for “Perfect Forward Secrecy” and TLS 1.2, ensuring that a session key derived from a set of long-term keys cannot be compromised if one of the long-term keys is compromised in the future. Even if somebody wire taps your communication with your PRTG server and gets access to your private keys later, he will not be able to decrypt the old data.
Note: Older browsers and older versions of the Enterprise Console may not be able to connect to the PRTG webserver any more. There is an option in the PRTG webserver settings that allows to (temporarily) switch to a compatibility mode with weakened security, so these clients can connect again. Please update your browsers and the Enterprise Console to the latest version.
The admin can set a time after which the WebUI automatically performs a logout to prevent unauthorized access (under System Administration | User Interface).
When sending a "support bundle" with a configuration file to Paessler support, passwords are not included anymore. We are now removing all encrypted passwords from the config.dat file before it is sent to Paessler support in support bundles when the user chooses this function.
Extended [Freeware]: We are making the Freeware of PRTG 3 times more valuable! The freeware edition can now monitor up to 30 sensors for free (instead of only 10 sensors)!
New [Sensors]:
SSL Connectivity BETA Sensor checks a target for the allowed SSL protocols and shows a security rating
There are 4 new sensor types for SQL server monitoring: The sensors Microsoft SQL v2, MySQL v2, Oracle v2, and PostgreSQL monitor SQL databases directly using .NET 4.0 and are much more flexible than the previous SQL sensors.
The new SSH SAN Enclosure sensor monitors the health of an enclosure on an SAN that supports CLI over SSH.
You can now specify after how many failed sensor scans a sensor status will be set to a ‘down’ status if a device reports an error. Define this in the "Scanning Interval" setting.
Newly created Ping sensors now send multiple ping requests with 5 pings by default. All requests have to fail to set the sensor in a "down" status. Existing Ping sensors keep their current setting. This will minimize false alarms due to packet loss.
The new open source tool QoS Reflector enables you to use a QoS (Quality of Service) Round Trip sensor without installing a remote probe at the 'end' of the connection. The QoS Reflector is a Python script so that you can use any Linux machine as QoS roundtrip endpoint.
New [WebGUI]:
Google Universal Analytics integration: You can track the usage of the WebUI of PRTG in your Google Universal Analytics account. Simply create a Google Analytics Tracking ID in the analytics portal and enter it into PRTG’s system administration settings and PRTG will dynamically integrate it into the website. See our Knowledge Base for details: http://kb.paessler.com/en/topic/61406
New [WebGUI]: There is a new visual representation for sensors using lookups with bitfields
Changed [System Administration]:
The PRTG Server Administrator and PRTG Probe Administrator tools are now together in one universal admin tool: The new “PRTG Administrator” tool includes all available probe and core settings (besides the administration settings which you can change via the webGUI).
You can now change administrative probe settings (outgoing IP, restart options) on the "Settings" tab of local and remote probes in the webGUI. This was in the PRTG Probe Administrator tool before.
Changed [Reports]: Scheduled reports will not be executed on failover nodes by default anymore.
Improved [Sensors]:
HTTP SSL Certificate Expiry Sensor now checks for revokes certificates
NetApp sensors can now treat N/A measurements als valid (no error will be triggered if the according option is activated)
Amazon CloudWatch Elastic Load Balancer (ELB) sensor has two new channels for the HTTP status codes 3XX and 5XX (analog to the already existing 2XX and 4XX channels)
The File Content sensor allows now to specify the “Read Behavior”: You can choose to process only lines which are appended to the file to improve performance instead of reading the whole file with each sensor scan.
HTTP Push Data sensors have now the option to define an age threshold. If no data is received for this time or longer, the sensor shows an error
The DNS sensor now supports IPv6 requests to monitor DNS servers which are only reachable via an IPv6 address.
The SNMP Traffic sensor has a new option to ignore the ‘disconnected’ status if the port is set correspondingly in the hardware (‘admin down’).
Improved [Templates]: You can now exclude specific sensors from a device when you create a device template.
Improved [Libraries]: Libraries include now "Add Library Node" and “Add Group” buttons similar to the “Add Device” and “Add Group” buttons in the device tree for easier creation of a library.
Improved [Notifications]: New placeholders for syslog receiver and trap receiver notifications show the last 20 entries without any filter before the notification was triggered: %syslogmessages, %trapmessages
Bugfixes [Security]:
Improved security for the PRTG web interface
Read only users could view a list of Administrator users on the same installation
Bugfixes [Core]:
On some systems, the PRTG installer could not perform a necessary restart in autoupdate mode
On some systems, the Windows shortcut icon that starts the web interface did not work
In rare cases, the PRTG server Windows service could not start any more after the installation. We have fixed this.
Extended stability improvements for outgoing emails and HTTP notifications
Bugfixes [Sensors]:
In some configurations, reports generated by the "Historic Data" tab did not include sensor graphs
Syslog Receiver sensor showed structured data multiple times
In some configurations, limits of sensor channels were not correctly interpreted
SNMP Linux Meminfo sensor showed wrong values in some cases
Fixed a bug that caused failing SNMP sensors when using SNMPv3 with encryption
Improvements to the recently added SQL (v2) sensors
Graphs of sensor channels using the "maximum" value mode could show fringed graphs in some cases
Better stability for HTTP and HTTP Advanced sensors
Extended fields for Syslog sensor
Fixes for HTTP Push Count, HTTP Push Data, and HTTP Push Data Advanced sensors
Fixes for PostgreSQL Sensor
Hyper-V sensors can now handle server names which include parentheses “()”
HTTP Push Data sensors didn’t filter correctly for the specified HTTP request method; if there are POST requests, only the postdata part will be processed (has to be "application/x-www-form-urlencoded") and not the GET parameters.
WMI Security Center Sensor now triggers a change notification when the status code of the antivirus software changes.
Cisco CBQoS sensor works more robustly
Amazon CloudWatch sensor (ELB) now retrieves the correct value for maximum with (Un)HealthyHost (was the sum value before)
Syslog Receiver displayed UTF-8 encoded messages incorrectly.
Bugfixes [WebGUI]:
Fixed hidden feature /speedtest.htm
The QR code shown in the upper right corner can now be used again with our mobile apps
Fixed “selection tree” and “breadcrumbs” behavior for read-only users (the “Find Duplicates” and “Compare Sensors” functions did not work properly; clicks on specific breadcrumbs caused an error)
“Down Acknowledged” sensor list could not be opened via the status icon in maps
“Desktop Notifications” work again with Google Chrome browser and now Firefox is also supported.
Several minor improvements
Bugfixes [Cluster]:
In a PRTG cluster, not all settings for the cluster connections were correctly deployed
Sensor names on cluster probes were shown incorrectly when collapsed
Bugfix [Notifications]: Improved handling of error messages in HTTP notifications
Bugfix [Reports]: In some configurations, reports generated by PRTG did not include sensor graphs
New [EC]: The Enterprise Console now includes a history for Libraries, Maps, and Reports
Hundreds of other improvements and fixes to the Enterprise Console, the web interface, and all other parts of PRTG, as well as an updated user manual.

New in PRTG Network Monitor 14.3.11.2953 (Sep 15, 2014)

New in PRTG Network Monitor 14.3.11.2897 (Sep 10, 2014)

New in PRTG Network Monitor 14.3.11.2749 (Aug 25, 2014)

New in PRTG Network Monitor 14.3.11.2661 (Aug 14, 2014)

New in PRTG Network Monitor 14.3.11.2625 (Aug 11, 2014)

New [Sensors]:
IPMI System Health BETA sensor: monitors temperature, fans, voltage via Intelligent Platform Management Interface (IPMI)
SNMP Printer BETA sensor: can monitor the status (based on rfc1759) of various printers (e.g., among others: HP OfficeJet printers, HP LaserJet printers, RICOH SP 5200, SP 3410, SP C242DN, MP C3003, MP C2503)
New [WebGUI/Server]:
The new Dependencies Graph visualizes the dependencies between monitoring objects
The new Object History for libraries, maps, reports, notifications, schedules, user accounts, user groups, and settings shows all recent edits, creations, deletions, etc. of such objects
Overview tabs of devices and groups now show the date/time of last auto-discovery
Improved channel settings dialog to ease editing multiple sensor channels
New API call shows all sensor types which are currently used: /api/sensortypesinuse.json
Improved [Security]:
OpenSSL libraries have been upgraded from 0.9.8.* to Version 1.0.1h
We include a new PRTG default certificate (with RSA 2048bits) and this automatically overwrites the old default certificate (if you use a custom certificate it will not be touched)
When using administrative pages in the webGUI, PRTG now requires that the last credential based login was less than 15 minutes ago. If more time since the last login has passed the user must re-authenticate before he can continue. This secures the webGUI against potential fishing attacks.
Browser form auto-complete for login name and password on the login page can now be disabled via a registry key option as security enhancement
Registry key option to deny loading of PRTG web pages in frame elements (use with Caution: denies also loading of maps!). This helps protect against potential clickjacking attacks
Some minor security improvements
Improved [WebGUI]:
Contact support form now shows helpful resources to help you find quick solutions to your issues
Search box size automatically increases by mouse hover and focus
A big red alarm box will now appear if a PRTG health sensor is down (and not acknowledged) to focus your attention on serious problems in your installation
Easier approval of new probe connections via a corresponding message box in the webGUI
Sensor graphs on group and device overview tabs are now bigger and more graphs are shown than before to provide you a better overview on your monitoring data
HTTP notifications now work with and without SSL (also with servers which do not use SSLv3)
Improved [Sensors]:
SCVMM sensors now with corresponding error message if VM/host does not exist on the target system
Windows Scheduled Task sensor can ignore specific status codes
SNMP NetApp Enclosure sensor with better error handling
Syslog and SNMP Trap Receiver sensors show a corresponding error message if the probe is not connected
Adding filters on the Messages tab for Syslog/Trap Receiver sensors by clicking on the content of a column
SNMP NetApp Logical Unit sensor with more comprehensible columns when adding the sensor
Performance Counter sensors with a more comprehensible error message if the request contains duplicate channel names
WMI Process sensor now supports hybrid mode (32bit and 64bit Windows versions) and divides CPU load through the number of cores; furthermore, it does not count the "PRTG Server Administrator" in PerfCounter mode anymore if only "PRTG Server" is monitored
SNMP NetApp Logical Unit sensor now with optional alignment monitoring (an additional channel will be added by demand when creating the sensor)
HTTP Push Data sensor now shows an expressive error message if the port could not be opened
Bugfixes [Sensors]:
SNMP Dell System Health sensor returns a correct OK status, corrected lookup states assignments
Improved Error handling in Amazon CloudWatch sensor
Hyper-V sensors: Virtual machines without a virtual IDE controller do not cause access violations anymore
Hyper-V Virtual Machine sensor shows the correct error message if the VM is off and the sensor uses only Performance Counters
HTTP Full Web Page sensor sometimes did not write screenshots when this feature was enabled
Limit fields in sensor / channel settings did not accept float values
Windows Scheduled Task sensor did not create a primary channel
Very long OIDs could cause access violation within SNMP sensors
Bugfixes [WebGUI]:
Approve button for new probes did not work properly
Page refresh did not update everything
Keyboard enter did not work to confirm a dialog
SNMP Memory sensors were not shown in the top 10 memory sensors map object
Remote probe installation via Device Tools did not work for some customers
More relaxed validation of email address in webGUI and admin tools
"Sensors with status" filter sometimes did not display the correct sensors
Search function is now more robust in big installations
Top 10 lists didn't handle the filter status correctly
Read-only users cannot see context menu quick buttons anymore
DNS name is fully considered now when generating email and QR code links
Many other minor fixes
Bugfixes [EC]:
Lists could not be turned over to the end
Improved moving groups in the device tree
Many other improvements and fixes in all parts of the software, as well as an updated user manual

New in PRTG Network Monitor 14.3.10.2421 (Jul 8, 2014)

New in PRTG Network Monitor 14.2.10.2255 (Jun 11, 2014)

New in PRTG Network Monitor 14.2.10.2113 (May 22, 2014)

New in PRTG Network Monitor 14.2.10.2103 (May 20, 2014)

New [Sensors]:
HTTP Push Data (Advanced) BETA sensor: Displays data from received messages which are pushed via an Hypertext Transfer Protocol (HTTP) request to the PRTG server.
Jacarta Interseptor Pro Environment sensor: Queries data from a Jacarta interSeptor Pro environmental monitoring system via Simple Network Management Protocol (SNMP).
Cisco UCS Physical Disk sensor: Monitors a physical disk of a Cisco Unified Computing and Server (UCS) device via Simple Network Management Protocol (SNMP).
New [WebGUI]:
Notifications and schedules now have a history tab
Social Media and Feedback links can be disabled via a registry key option
Add sensor dialog alphabetically organized with most used sensor types on top and registry option for the shown sensor count
New filter options for the sensors list
Changed [Notifications]: The POST data part of HTTP notifications now supports line breaks. If you have configured such notifications, please check them for functionality.
New [API]: New API call for lists of toplists: api/table.xml?content=toplists&columns=objid,sensor,name
New [Maps]: Added a new map object to replace the use of iFrame
Improved [Sensors]:
SNMP Dell PowerEdge System Health sensor enhanced with multi-chassis support and better performance
HTTP Full Web Page sensor now with http basic and NTLM authentication
Stability improvements for Windows sensors using the Performance Counter method
SNMP Dell System Health sensor supports iDRAC
Better error handling of NetApp sensors and stability improvements
Flow sensors: The default filter rules are now editable
SNMP Cisco ASA VPN Traffic sensor enhanced with total traffic (sum) channel
SSH SAN sensors with better error handling and stability
Stability improvements for HTTP Push sensors
New WSUS Statistics sensors could not be created
Added a debug option to Traceroute Hop Count sensor
Added an SSLv3 option to HTTP SSL Certificate Expiry and HTTP XML/REST Value sensors
Easier setup for Active Directory Replication Errors sensor
Improved/Bugfix [Core]:
Stability improvements for the ticket database
SSL connections: In some cases, parts of a PRTG page could not be loaded due to single assets failing to load
Improved [Notifications]: New placeholders for syslog and trap notifications show the last 20 entries before a notification was triggered: %syslogwarnings, %syslogerrors, %trapwarnings, %traperrors
Improved [Tickets]: Tickets regarding probe connection port errors with enhanced description
Improved [Remote Probes]: Stability improvements for the case that a remote probe is connected to the core server via an unstable connection
Improved [Translations]: Updated Czech language version
Bugfixes [WebGUI]:
Sunburst did not take full space when there were less than 2000 sensors
Large ad hoc "Historic Data" reports could trigger PRTG's overload protection in some cases
QR code scanning of user account did not work
Dozens of tweaks, improvements, and fixes for the Ajax Web Interface
Bugfixes [Sensors]:
HTTP XML/REST Value sensor sometimes returned an error instead of returning the requested value although the JSON code was valid
SSH SAN Logical Disk sensor showed the error "Wrong Data Format" in some cases
Exchange PowerShell sensors produced an error entry in the eventlog of Exchange servers at each scan for public folder databases
Better connection handling for Enterprise Virtual Array (EVA) sensor
HTTP sensors now work with IPv6 and "smart URL replacement"
Better error handling of SNMP sensors
The total channel of some disk free sensors was missing
Fix for HTTP XML/REST sensor for JSON data containing links and other html code
Increased timeout for SSH sensors
SNMP Cisco System Health sensor now returns an error status for the "not functioning" value
New [EC]: Notification triggers can now be set for libraries
Bugfixes [EC]:
Cloning sensors did not work in some cases
Resume monitoring after simulating an error was sometimes not possible
Drag&drop changed sensor order in specific cases
Editing notifications from device context menu did not work in some cases
Fixed a memory problem in the Enterprise Console which could crash it when left open without interaction for a while
Fixed bug with SSH SAN Physical Disc sensors' graphs
Start date of maintenance window wasn't applied
Graph display with CBQoS sensors works again
Fixed reports which have shown an empty window
Last viewpoint wasn't recovered when starting EC from tray
"Start with Windows" was inactive after updates
Bugfix [Reports]: Scheduled reports were re-sent on PRTG restart
Updated user manual
Hundreds of other improvements and bugfixes

New in PRTG Network Monitor 14.2.10.2077 (May 14, 2014)

New in PRTG Network Monitor 14.2.9.1798 (Apr 23, 2014)

New in PRTG Network Monitor 14.2.9.1689 (Apr 1, 2014)

New in PRTG Network Monitor 14.1.9.1644 (Mar 27, 2014)

New [Sensors] - 3 new sensor types:
HTTP Push Data BETA sensor provides a URL (webhook) that can be used to push messages to the PRTG server using HTTP
SSH SAN Logical Disk sensor monitors a logical disk on SANs that support CLI over SSH
SSH SAN System Health sensor monitors system health on SANs that support CLI over SSH
New [WebGUI]:
The "Add sensor" dialog now automatically shows the most used sensor types first (this is calculated for each user)
Several webserver and IP settings can now be changed in the "System & Website" settings (was in the PRTG Server Administrator tool before only)
The sensors page can now be filtered for objects and tags with an inline filter directly above the table
Added a filter option on similar sensors overview page
Extended filter for search in tickets
Toplists now show range lookups
Added a hidden feature that allows showing geo tracking information provided by an Android probe on a geo map (instead of longitude and latitude in tables only). For details, please see our knowledge base article
Important changes:
[Tickets]: New ToDo tickets are now assigned to the "PRTG System Administrator" user and notifications for these tickets are sent to this user only. This corresponds to the behavior of the former "ToDos". Right after the introduction of the ticket system, new ToDo tickets were assigned (and notified) to the entire "PRTG Administrators" user group. We reverted this due to user feedback
[Sensors]: The following sensors now require .NET 4.0 installed on the probe machine (was .NET 2.0 before)
HTTP XML/REST Value
HTTP SSL Certificate Expiry
Windows Scheduled Task
[Reports]: When generating top 10 or top 100 reports, all pages of one report are now written into one PDF file (could be several files before)
[Auto-Discovery]: Optimized the detection of devices with multiple IP addresses (in order to avoid multiple monitoring of these devices)
[Core]: General internal system backup tasks of PRTG are now performed at 3 a.m. local time (was 3 a.m. UTC before)
[Core]: Passwords may now have more than 3 identical characters
Improved/bugfixes [Sensors]:
Optimized storage for Syslog and SNMP Trap Receiver sensors
Syslog and SNMP Trap Receiver sensors now have an advanced filter dialog to enter custom filters; non-admin users can now view messages for Syslog and SNMP Trap Receiver sensors
Better error handling for HTTP Push Data sensor
HTTP Full Web Page sensor with Chromium engine now supports page redirects
The subject of the emails sent by our Email Round Trip sensors may now contain arrow brackets
SNMP IBM System X System Health Sensor with fixed fan limits
VMware sensors showed an error during backup operations
HTTP Push Data sensor now uses a dot (.) as decimal seperator
Windows Update Sensor now with better error handling for clients with empty update lists
VMware sensors didn't show datastore latencies in some cases
IMAP sensor now has better support for multipart emails
Fixed a bug in NetFlow sensors that could cause regular probe restarts
Flow sensors did not show correct MAC offsets for VLANs
SNMP sensors with extended error code handling
Added "total" channel to the following sensors: SNMP Linux Disk Free, SSH Disk Free, and SSH ESX Disk Free
Hyper-V Virtual Machine sensor now supports Windows Server 2012 R2
SNMP Hardware Status sensor with extended error handling
SNMP IBM System X System Health temperature channel now with extended error handling
HTTP SSL Certificate Expiry sensor now works with SNI and SSLv3
Added new option to HTTP XML/REST Value sensor to define a decimal separator
File Content sensor can now also handle text files containing Unix-Linefeeds
Exchange sensors are now handled better by PRTG's auto-discovery
Stability improvements for HTTP Push sensors
New WSUS Statistics sensors could not be created
Added a debug option to Traceroute Hop Count sensor
Added an SSLv3 option to HTTP SSL Certificate Expiry and HTTP XML/REST Value sensors
Easier setup for Active Directory Replication Errors sensor
Improved/bugfixes [WebGUI]:
Some "device tools" (from the context menu) did not work
Better navigation on Toplist pages
Several improvements to the new tickets feature
Geomaps can be zoomed again using the mouse wheel
The sensor status filter for the device tree now survives a browser refresh
Large ad hoc "Historic Data" reports could trigger PRTG's overload protection in some cases
Improved/bugfixes [EC]:
Fixed a memory problem in the Enterprise Console which could crash it when left open without interaction for a while
Dozens of other tweaks, improvements, and fixes for the Enterprise Console
Improved/bugfixes [Core]:
Stability improvements for installations with Hebrew language strings
Stability improvements for heavy use of toplists
Optimized remote probe updates on very slow connections
Stability improvements for the ticket database
SSL connections: In some cases, parts of a PRTG page could not be loaded due to single assets failing to load
Improved [Remote Probes]: Stability improvements for the case that a remote probe is connected to the core server via an unsteadily connection
Improved [API]:
Historic data XML can now return the channel ID
Device tree now contains lookup values
Bugfix [Cluster]:
Stability improvements, including stability for sensors with different sensor channels among the cluster
Improved [Translations]:
Updated Czech and German and French language version
Hundreds of other improvements and fixes in all parts of the software as well as an updated user manual

New in PRTG Network Monitor 14.1.8.1370 (Feb 19, 2014)

New in PRTG Network Monitor 14.1.8.1307 (Feb 11, 2014)

New in PRTG Network Monitor 14.1.8.1262 (Feb 6, 2014)

New in PRTG Network Monitor 14.1.8.1240 (Feb 5, 2014)

New [WebGUI]:
Completely revised and updated look&feel of the PRTG Ajax Web GUI
Added a filter option on similar sensors overview page
Extended filter for search in tickets
Toplists now show range lookups
New [Tickets]: PRTG now includes its own ticket system. With the ticket system you can manage and maintain various issues which may appear while monitoring your network with PRTG. Note: The new ticket system replaces the existing 'ToDos' functionality. When PRTG needs to tell the admin something important, it will now create a new 'ToDo Ticket'; a notification about this will now be sent to all PRTG System Administrators user groups.
New [ToDos]: The "ToDo" feature has been replaced by the tickets feature. Existing todos are converted into tickets as soon as you update to this version. See above.
New [Sensors]: Completely rewritten Syslog Receiver and SNMP Trap Receiver sensors designed for high performance. For details, please see our blog article.
New [Sensors]: 8 new sensor types:
SNMP Windows Service sensor monitors a service via SNMP
SNMP Cisco UCS Chassis sensor monitors the health status of the chassis of a Cisco "Unified Computing and Server" device
SNMP Cisco UCS System Health sensor monitors the system health of a Cisco "Unified Computing and Server" device
SNMP LenovoEMC Physical Disk sensor monitors a physical disk in LenovoEMC NAS
SNMP LenovoEMC System Health sensor monitors the System Health of a LenovoEMC NAS
SNMP NetApp Logical Unit sensor monitors the I/O on a logical unit of a NetApp storage system
WMI Volume Fragmentation sensor monitors the fragmentation of a logical volume
HTTP Push Count sensor provides a URL (webhook) that can be used to push messages to the server using http. The sensor will count the pushed messages and display the count of received messages with every scan.
Improved [Sensors]:
SNMP IBM System X System Health sensor enhanced with an additional instance for "Overall Health" on Integrated Management Modules (IMMs)
File Content sensor can now also handle text files containing Unix-Linefeeds
Improved [WebGUI]: Safari 7+ and Opera 12+ can now log into the Ajax WebGUI (please note that both browsers are still not officially supported)
Improved [Language]: Updated German, French, and Czech language version
Feature [EC]: Added "One-time maintenance window" and "Add Device Tool..." to context menu
Changed [Auto-Discovery]: Optimized the detection of devices with multiple IP addresses (in order to avoid multiple monitoring of these devices)
Bugfix [Sensors]: Improvements to QNAP NAS Smart status lookup
Bugfix [Sensors]: Some packet sniffer filter fields did not work
Bugfix [Sensors]: Better user interface when creating Amazon SNS sensors
Bugfix [Sensors]: SSH Script Advanced did not show any values in historic data when using "Include Percentiles"
Bugfix [Sensors]: VMware sensors didn't show datastore latencies in some cases
Bugfix [Sensors]: Flow sensors did not show correct MAC offsets for VLANs
Bugfix [EC]: Stability improvements for configurations with multiple PRTG core servers as well as many other improvements and bugfixes
Bugfix [Sensors]: VMware (SOAP) sensors did not work with certain characters in credentials
Bugfix [Sensors]: Windows Update Sensor now with better error handling for clients with empty update lists
Bugfix [WebGUI]: Multiple improvements and bugfixes throughout the entire Ajax web interface, including channel editing, IE 11 compatibility, top 10 lists, and the Maps feature.
Bugfix [WebGUI]: The sensor status filter for the device tree now survives a browser refresh
Bugfix [Notifications]: Notifications that are set for Library groups were not applied to sensors
Bugfix [Reports]: Fixed a bug that appeared in reports when sensor names included quotes
Bugfix [Core]: Stability improvements for setups using Oracle SQL sensors
Various other bugfixes and improvements to the WebGUI, the sensors, the Enterprise Console, and the user manual.

New in PRTG Network Monitor 13.4.7.3747 (Jan 13, 2014)

New in PRTG Network Monitor 13.4.7.3705 (Dec 17, 2013)

New in PRTG Network Monitor 13.4.7.3673 (Dec 17, 2013)

New in PRTG Network Monitor 13.4.7.3531 (Nov 19, 2013)

IMPORTANT! Changed [Core]: When using a secure connection, the PRTG webserver now accepts SSLv3 and TLSv1 with AES or DES only. Note: In former versions, the only accepted encryption was RC4; this is not supported any more. Please make sure you use the latest browser version on your clients.
New [WebGUI]: Sensors showing lookup values now have a graphical representation in the known "gauges" style
New [WebGUI]: New function to find duplicate devices (i.e. devices with the same IP address) in your PRTG configuration: Right-click a device and select "Find Duplicates..."
New [Core]: Similar sensor analysis can now the toggled on/off on a group basis (in the settings of a group in the device tree)
New [EC]: You can now send a "support bundle" to our technical support team direcly for the Enterprise Console
Improved [Maps]: Faster loading of maps, plus stability improvements when viewing public maps for extended time periods (for Internet Explorer 9, Firefox, Chrome)
Improved [Notifications]: You can now use %host as Agent IP in SNMP Trap notifications sent by PRTG
Improved [WebGUI]: When sending a "support bundle" to our technical support team you can now include a screenshot of the current page
Bugfix [WebGUI]: Sensor gauges were not displayed anymore
Bugfix [WebGUI]: Fixed an XSS vulnerability
Minor bugfixes
Minor fixes to the web interface
Many improvements to the core, Maps, Enterprise Console, WebGUI, as well as an updated user manual.
New [Sensors]: 2 new sensor types for the NetFlow 9 successor protocol:
IPFIX sensor monitors standard parameters of IPFIX streams
IPFIX (Custom) sensor allows user defined monitoring of IPFIX streams
Improved [Sensors]:
Massive performance improvements for all VMware (SOAP) sensors
For HTTP sensors you can now define a custom "content type" when using the "POST" request method
HTTP Advanced and HTTP Transaction sensors now have a "Compatibilty Mode" for websites that do not work with the standard method
HTTP Full Web Page Sensor with updated Chromium (webkit) and PhantomJS engines
Easier creation of instances of the "Enterprise Virtual Array (EVA)" sensor
Better QNAP System Health sensor
Better compatibility of SSH Script (Advanced) sensor with Solaris systems
Better compatibility: SNMP Uptime sensor now uses updated OID
EXE/Script sensors now support IPv6
Bugfixes [Sensors]:
Fixed Windows Last Update sensor for queries to localhost
Fixed Sensor Factory sensor
Fixed channel limits for IBM System Health sensor
Fixed Oracle SQL sensor (host string in Oracle Client mode did not work)
Fixed some minor bugs for VMware sensors
Fixed a bug that occured when creating a new SNMP Linux Physical Disk sensor
Windows Updates Status (Powershell) sensor showed incorrect time since last update

New in PRTG Network Monitor 13.4.6.3374 (Oct 30, 2013)

New in PRTG Network Monitor 13.4.6.3305 (Oct 23, 2013)

New in PRTG Network Monitor 13.4.6.3240 (Oct 9, 2013)

New in PRTG Network Monitor 13.4.6.3234 (Oct 8, 2013)

New in PRTG Network Monitor 13.3.6.3109 (Sep 18, 2013)

New in PRTG Network Monitor 13.3.6.3097 (Sep 17, 2013)

New in PRTG Network Monitor 13.3.5.2870 (Aug 26, 2013)

New in PRTG Network Monitor 13.3.5.2684 (Aug 1, 2013)

New [Notifications]: Add an extended notification logging feature that helps analyzing notification delivery problems
New [WebGUI]: Multi-Edit for Channels
New [WebGUI]: Added new dependency list feature to the "Devices" menu of the WebGUI
Improved [EC]: Many improvements, new features, better stability, and other fixes for the Enterprise Console
Improved [Core]: Better stability and performance, also for cluster installations
Improved [Security]: Updated SSL libraries for sensors using https, the PRTG web server, probe-core-connections, SNMP v3, etc., plus other security improvements for the web server
Bugfix [Sensors]: Windows CPU Load Sensor could show wrong values when querying data via direct Performance Counters
Bugfix [Sensors]: Several fixes for the Hyper-V Cluster Shared Volume Disk Free Sensor
Bugfix [Sensors]: More stability for SSH sensors with private key
Bugfix [Sensors]: Apache ModStatus sensors used a wrong path for auto-completion
Bugfix [Sensors]: SQL sensors now can monitor „Record Count" independently from
„Post Processing"
Bugfix [Sensors]: SSH sensors now with better compatibility as well as improved performance and network-load
Bugfix [Sensors]: Hyper-V Virtual Machine Sensor did not observe the "Ignore powered off state" setting
Bugfix [Reports]: Fixed wrong downtime averages in reports
Bugfix [Setup]: Vulnerability fix
Bugfix [WebGUI]: Several improvements and fixes, incl. sunburst view, graph legends, slightly redesigned sensor "Overview" tab
Bugfix [Core]: PRTG sensor count limits were not inherited to sub groups
Bugfix [Core]: Graphs with limits were not displayed correctly in some scenarios
Many other improvements and fixes to the core system as well as an updated user manual
New [Core]: New "Value Mode" available for sensor channels that return absolute values. They can not only show averages, but alsominimum or maximum values in the graphs for the respective time spans.
New [WebGUI]: The „Pause" context menu of all objects now has an option to directly add a one-time maintenance window to pause monitoring during a planned downtime
Improved [Remote Probes]: For more flexibility when using NAT at a remote location, remote probes can now be denied via their global identifier (GID). When deinstalling a remote probe, it will now be automatically added to the "Deny GIDs" list (instead of the "Deny IPs" list).
Improved [Probe]: Better stability for probe connections
Improved [Probe]: Better handling for WMI connections and values reported via WMI
Improved [Sensors]:
Dell PowerVault MDi Sensor now also works with models 3000f, 3620f, and 3620i. It may work with additional models, too.
SNMP QNAP System Health Sensor with better data detection and improved stability
SNMP Custom String Sensor now has a setting for a sensor status "Warning" when certain keywords are matched
SCVMM sensors now also work if no IIS is installed on the target system, they now support Windows 2012, and other improvements
Amazon CloudWatch Sensor with new region filter and a fix for ELB
SNMP Cisco System Health Sensor now shows additional data
Flow and packet sniffer sensors now support „DSCP" in sensor settings
Oracle SQL sensor now supports OCI (Oracle Client)
Better performance and compatibility for several SNMP sensors, incl. Linux SNMP (Debian 7)
New [Sensors] - 5 new sensor types for detailed Exchange monitoring, all based on Powershell:
[New] Exchange Database (Powershell)
[New] Exchange Backup (Powershell)
[New] Exchange Mailbox (Powershell)
[New] Exchange Public Folder (Powershell)
[New] Exchange Mail Queue (Powershell)
New [Sensors] - 6 new sensor types for monitoring devices via SNMP:
[New] SNMP Poseidon Environment Sensor
[New] SNMP GSA System Health Sensor - monitors the system health of a Google Search Appliance
[New] SNMP SonicWALL System Health Sensor - monitors health values of a Dell Sonic Firewall
[New] SNMP Cisco CBQoS Sensor - monitors quality-of-service via compatible devices and supports the following three classes: Class Map, Match Statement, Queueing
[New] SNMP Hardware Status Sensor - monitors compatible hardware via standard OIDs
[New] SNMP Linux Physical Disk Sensor - monitors IO on disks of a Linux/Unix system

New in PRTG Network Monitor 13.3.4.2604 (Jul 23, 2013)

New in PRTG Network Monitor 13.3.4.2526 (Jul 15, 2013)

New in PRTG Network Monitor 13.2.3.2478 (Jul 9, 2013)

Core Improvements:
Improved [Core]: Improvement of overall speed of the PRTG web interface and the Enterprise Console by significantly improved handling of user sessions. You will especially experience increased speed if many users access your core server at the same time.
Improved [Core]: General improvements to the SNMP monitoring engine
Improved [Core]: Enhanced security with better protection against external connection attempts.
Improved [Core]: After a core server restart PRTG now waits longer for an IP address to be assigned to the server. This will solve issues with PRTG's web server switching to localhost after restarts.
New [Core]: New registry key option to centrally disable automatic numbering in PRTG (for example, automatic numbers attached to sensor names when using the auto-discovery).
New Sensors and Sensor Improvements:
New [Sensors]: The „Application Performance Sensor" (currently to be considered beta) is an experimental sensor that can measure the performance of network applications by looking at the timing of network packets going into and coming out of a server using packet sniffing. PRTG analyzes network packets and measures the time between requests and responses. This allows you to monitor the performance of a server/service without actually having direct access to neither the client nor the server (works with TCP-based protocols that initiate a new TCP session with each request). Please give us feedback for this sensor type!
New [Sensors]: Three new sensor types for monitoring QNAP storage systems
[New] SNMP QNAP Physical Disk Sensor
[New] SNMP QNAP Logical Disk Sensor
[New] SNMP QNAP System Health Sensor
New [Sensors]: Three new sensor types for monitoring Synology storage systems
[New] SNMP Synology Physical Disk Sensor
[New] SNMP Synology Logical Disk Sensor
[New] SNMP Synology System Health Sensor
New [Sensors]: Three new sensor types for monitoring IBM System X systems
[New] SNMP IBM System X Physical Disk Sensor
[New] SNMP IBM System X Logical Disk Sensor
[New] SNMP IBM System X Physical Memory Sensor
Improved [Sensors]: Enhanced compatibility for HTTP XML/REST Value Sensor
Improved [Sensors]: Windows Print Queue Sensor now supports print queues with no physical printer attached
Improved [Sensors]: WMI Exchange sensor now shows Active User Count, User Count, Connection Count, Current Unique Users, and Average Response Time (Please note: For existing sensors, the former sensor channel "Active User Count" will show zero values now)
Improved [Sensors]: All http sensors now support Server Name Identification (SNI)
Improved [Sensors]: The HTTP Content sensor now supports NTLM authentication
Improved [Sensors]: The Port Sensor now also supports response _text_ as a result
Improved [Sensors]: Both HTTP Apache ModStatus Sensors now support monitoring of protected ModConf pages.
Improved [Sensors]: Hyper-V Cluster Shared Volume Disk Free Sensor can now query data from localhost
Improved [Sensors]: Updated WSUS Statistics Sensor
Further Improvements:
Improved [WebGUI]: Optimized speed for device trees with many _collapsed_ groups that show red sensors
Feature [WebGUI]: Added a hidden feature to bulk-print QR codes (try /devices-qr.htm?id=0). For details, please see our knowledge base article.
Improved [Language]: New Japanese language file
Improved [Language]: New Chinese language version
Improved [Maps]: In "Maps Designer" you can now search for objects in the device tree by entering keywords
Improved [Maps]: Several fixes and improvements to PRTG Maps behavior and public Maps view, including quicker updates of public maps
Improved [Autodiscovery]: PRTG now gives precedence to creating SNMP sensors for monitoring CPU, memory, disks. Only if SNMP is not available on the target device, PRTG will create Windows/WMI sensors. Note: If you have a _scheduled_ auto-discovery which runs regularly, PRTG will create some double sensors (SNMP and WMI). Only existing configurations are affected by this issue.
Improved [EC]: New menu icons as well as many improvements for the Enterprise Console.
Improved [API]: Graphs can now also be queried in SVG format via the API
Bugfixes Sensors:
Bugfix [Sensors]: PRTG did not accept lookup files containing ranges or bitfields. Details about lookups: http://www.paessler.com/manuals/prtg/define_lookups.htm
Bugfix [Sensors]: SNMP Cisco System Health sensor showed an "unknown" status in some scenarios
Bugfix [Sensors]: Fixed Cisco IP SLA calculation
Bugfix [Sensors]: IMAP sensor did not return correct date for last incoming data in some scenarios
Bugfix [Sensors]: Removed hardcoded default server for IP on DNS Blacklist sensor (dnsbl.njabl.org)
Bugfix [Sensors]: Windows Logged In Users Sensor reported an error when measuring more than 85 logged in users
Bugfix [Sensors]: Dell PowerVault MDi sensor showed speed values with a wrong factor
Bugfix [Sensors]: Oidlib files containing lookups produced an error on sensor creation
Bugfix [Sensors]: Corrected % calculation for Windows Pagefile Sensor
Bugfix [Sensors]: In some cases the SMTP&IMAP Round Trip Sensor and the SMTP&POP3 Round Trip Sensor did not work correctly when using special email subjects
Bugfix [Sensors]: The HTTP Transaction Sensor did not accept cookies in some scenarios
Bugfix [Sensors]: Better stability for the WMI UTC Time Sensor
Bugfix [Sensors]: Better compatibility and stability for SNMP HP ProLiant Disk sensors
Bugfix [Sensors]: Removed a potential memory leak in ADO SQL Sensor
Bugfixes WebGUI and Enterprise Console:
Bugfix [WebGUI]: In some cases, graphs with similar sensors were shown to users that did not have the right to see them.
Bugfix [WebGUI]: Sensor gauges and graphs now show limits correctly, including limits for disk sensors.
Bugfix [WebGUI]: Several other fixes for behavior of sensor gauges
Bugfix [WebGUI]: Read-only users with respective rights could not acknowledge alarms using the Mobile Web Interface.
Bugfix [WebGUI]: Holding down Ctrl key + mouse click in browser now also works on MacOS systems
Bugfix [WebGUI]: Fixed sunburst view
Bugfix [WebGUI]: Improved compatibility with Internet Explorer 10 (SNMP Traffic sensors could not be created manually)
Bugfix [WebGUI]: Improved Libraries
Bugfix [WebGUI]: XSS security fix
Bugfixes [EC]: Several fixes to the Enterprise Console
Bugfixes Notifications:
Bugfix [Notifications]: We corrected the behavior of the SMTP SSL/TLS encryption for outgoing email notifications when using an SMTP relay server. Note: If you experience problems with outgoing email notifications after this update, please check and revise your SMTP delivery settings under "Setup | System Administration | Notification Delivery". Pay special attention to the "Use encrypted connection" setting.
Bugfix [Notifications]: PRTG did not send email notifications via Gmail
Bugfix [Notifications]: PRTG could not send SMS text messages using provider "smsdriver". Note: Please use "Maximum Length of Text" = 0 when setting up this provider in the "Notification Delivery" settings
Bugfix [Notifications]: Email subjects containing "=?" were not transmitted correctly
Others:
Optimization of the monitoring engine, better stability and speed, styling and fixes to the Ajax web interface and the Maps functions, updated user manual, and many other improvements and minor fixes

New in PRTG Network Monitor 13.2.3.2284 (Jun 18, 2013)

New in PRTG Network Monitor 13.2.3.2235 (Jun 11, 2013)

New in PRTG Network Monitor 13.2.3.2219 (Jun 5, 2013)

New in PRTG Network Monitor 13.2.3.2165 (May 28, 2013)

New in PRTG Network Monitor 13.2.3.2134 (May 21, 2013)

New in PRTG Network Monitor 13.2.3.2014 (May 6, 2013)

New in PRTG Network Monitor 13.2.3.1977 (May 1, 2013)

New in PRTG Network Monitor 13.2.3.1926 (Apr 24, 2013)

New in PRTG Network Monitor 13.2.3.1896 (Apr 22, 2013)

New [WebGUI]: Completely revised and updated look&feel of the PRTG Ajax Web GUI:
Faster loading times and almost instant reaction on clicks
All settings loaded in layer popups so you never lose the context of your work
New view modes for Libraries: Sunburst, Tree Map (as known from the device tree)
Revised devices overview page: Extra display of high-priority sensors, in different sizes, for sensors with 4 and 5 star priority
Revised sensors overview page: Graphical display of sensor channels with gages. For xFlow and packet sniffer sensors, the "Toplist" graphs are now shown in the "Overview" tab. Edit channel settings directly on a sensor's "Overview" tab.
Redesign of built-in dashboards, sitemap, and top 10 lists
New sensor comparison page: compare several sensors at a time
New default colors for graphs
Changed appearance of buttons, tables, etc.
New interactive breadcrumbs for an easier navigation
QR codes for easy access to the direct URL of your monitoring objects on your mobile
Many other tweaks here and there
The Enterprise Console profits from the changes, too - whenever it embeds parts of the WebGUI
New [MobileGUI]: Revised Mobile Web GUI: Easier to read and new look&feel
New [Core]: Similar sensors analysis: PRTG automatically detects similar sensor data and shows matches in your sensor's "Overview" tab. This function is totally independent from sensor types and uses pure mathematics for heuristic calculation. (You can configure this feature in the "System & Website" system settings.)
New [Graphs]: Display of sensor limits: If you set a limit in a sensor channel (for example, an upper or lower warning limit, or an upper or lower error limit), these limits will be shown in the new sensor gages as yellow and red areas. Additionally, yellow and red areas can be shown in graphs. In order to show the colored areas in graphs, you must configure your graph to show one sensor channel only. Otherwise the limit areas will be hidden in graphs.
New [Sensors]: We reworked the internal system for SNMP monitoring:
New: PRTG now supports SNMP v3 with AES encryption
We extended the port identification options in the SNMP Compatibility options which allows for better adaptation to different behavior of your switches/routers in the case they reboot.
More stability for SNMP monitoring
New [Core]: Performance improvements for systems with 12 CPUs or more: PRTG now makes better use of CPU power which decreases your PRTG system's load
New [WebGUI]: The Ajax Web Interface now shows latest news from our company blog on the login screen and on the setup main page
New [EC]: The Enterprise Console now shows latest news from our company blog in a status bar at the bottom of the main window
New [Core]: Graphs can now be downloaded as SVG files
New [Core]: We changed the way dependencies between PRTG objects are shown
New [Core]: Faster search in the web interface
Improved [EC]: Many updates, changes, and fixes for the Enterprise Console
Improved [Autodiscovery]: Improved device templates for automatic network discovery.
New [Notifications]: When using a custom URL for SMS text message notifications, you can now define the encoding for SMS (in the "Notification Delivery" system settings), plus there will now be a result shown in PRTG's Logs list
Improved [Sensors]: The WMI Logical Disk sensor now shows more information
Improved [Sensors]: The Email Round Trip sensors now allow for a custom subject text addition and connect correctly when using SSL (TLS)
Improved [Sensors]: The WMI Service sensor can now show CPU load
Improved [Sensors]: The Port sensor now supports SSL-encrypted connections
Improved [Sensors]: Better error handling for the following sensor types: SNMP Cisco ADSL, SNMP Cisco ASA VPN Traffic, SNMP Cisco System Health, SNMP Dell Physical Disk Sensor, SNMP Memory, SNMP Disk Free, SNMP HP ProLiant Logical Disk, SNMP HP ProLiant Network Adapter, SNMP HP Proliant Memory Controller, as well as for all NetApp sensors and SNMP Library sensors
Improved [Reports]: When sending reports as PDF file(s) via email, you can now enable compression so the report files will reach you in ZIP format
Improved [Notifications]: We updated the design of the pre-configured templates for email notifications. Note: Please click on the "Reset to default" link in your email notifications settings to profit from the new templates.
Bugfix [Sensors]: Event Log (Windows API) Sensor could not filter by multiple IDs
Improved [Sensors]: Hyper-V Virtual Machine Sensor can now monitor machines running on Windows Server 2012, plus improved data calculation
Bugfix [Sensors]: Better performance for HTTP sensors when monitoring websites that redirect from http to https
Bugfix [Sensors]: Better error handling for HTTP Full Web Page sensor with Chromium engine
Bugfix [Sensors]: Fixed display issues in WMI Microsoft SQL server sensors settings
Bugfix [Sensors]: Fixed CPU index labels for SNMP CPU Load sensor (effective only when creating new sensors of this kind)
Updated user manual und API documentation, updated translations as well as hundreds of other improvements and fixes to all parts of PRTG
Changed/Removed:
Changed [Sensors]: There is no "Channels" tab any more in the WebGUI and in the Enterprise Console. Instead, you can edit sensor channels directly on a sensor's "Overview" tab, using the small gear icons next to the channel display. To make a sensor channel the primary channel, click on the little pin symbol.
Changed [Sensors]: There is no "Toplist" tab any more in the WebGUI and in the Enterprise Console for xFlow (NetFlow, jFlow, sFlow) and packet sniffer sensors. Instead, access Toplists directly by clicking on the Toplist graphs on a sensor's "Overview" tab.
Changed [Sensors]: For WMI Exchange Server sensors, we restricted the available measurements to a reasonable selection
Changed [Graphs]: The background color of graphs cannot be set any more in the "System & Website" system settings (background color will always be transparent).
Changed [Dashboards]: The former default "Dashboard 4" ("Home | Dashboard 4") was not compatible with the new interface, so we removed it.
Changed [API]: The API for customizations of PRTG's HTML, JavaScript, and CSS has changed. For details, please see http://www.paessler.com/knowledgebase/en/topic/44703
Changed [GeoMaps]: When entering a new "Location" for a probe, group, or device, PRTG now tries to resolve a street address to geo coordinates not only via Yahoo, but also via MapQuestAPI and Nokia.

New in PRTG Network Monitor 13.1.2.1462 (Mar 11, 2013)

New in PRTG Network Monitor 13.1.2.1447 (Mar 4, 2013)

New in PRTG Network Monitor 13.1.2.1382 (Feb 25, 2013)

New [Sensors]: Rewritten system for sensor channel lookups - replace the status codes of your devices with your own status messages
Changed [Notifications]: For enhanced language support, email messages will now be entirely UTF-8 encoded. Note: The header of email messages (including the subject field) will only be UTF-8 encoded if it contains non-ASCII characters. The content (body) of emails will now always be UTF-8 encoded.
Changed [WebGUI]: Fixed Chrome Desktop Notifications (Chrome's API has changed)
Improved [Sensors]: Added support for non-compliant OIDs for sensor types: SNMP Custom, SNMP Custom String, and SNMP Trap Receiver. New feature: In order to enter an OID into the "OID Value" field that does not begin with 1.0., 1.1., 1.2., or 1.3., add the string norfccheck: at the beginning of your OID.
Improved [Sensors]: Active Directory Replication Error sensor: Added option to monitor logged in domain controller only
Improved [Sensors]: HTTP XML/Rest Value sensor: New option for custom content type
Improved [Sensors]: Pingdom sensor
Improved [Sensors]: HP ProLiant Physical Disk sensor
Improved [Sensors]: Improvements to the SIP Options Ping sensor.
Improved [Sensors]: Hyper-V Cluster Shared Volume Disk Free Sensor now accepts umlauts in volume names
Bugfix [Sensors]: SSH Script sensors could show a false error on HP Unix systems
Bugfix [Sensors]: Several fixes in SCVMM Sensors
Bugfix [Sensors]: SSH connections were not closed correctly in some cases
Bugfix [Sensors]: Windows Scheduled Task sensor: Task names with an (.exe) extention caused a "Value did not fall within the expected range" error
Bugfix [Sensors]: Windows Security Center sensor now supports Sophos and Norton antivirus products
Bugfix [WebGUI]: customerscript.js was overwritten during update installations
Bugfix [Autodiscovery]: The auto-discovery did never create a WMI S.M.A.R.T. sensor
Bugfix [Notifications]: Improved Clickatell SMS support
Bugfix [Maps]: On large maps, scrollbars were missing in Maps designer mode
Several other minor fixes and many improvements, plus updated translations

New in PRTG Network Monitor 13.1.1.1265 (Feb 12, 2013)

New in PRTG Network Monitor 13.1.1.1158 (Jan 28, 2013)

New in PRTG Network Monitor 13.1.1.1088 (Jan 16, 2013)

New in PRTG Network Monitor 13.1.1.1086 (Jan 16, 2013)

New in PRTG Network Monitor 12.4.7.3506 (Dec 11, 2012)

New in PRTG Network Monitor 12.4.7.3474 (Dec 5, 2012)

New in PRTG Network Monitor 12.4.6.3298 (Nov 15, 2012)

New in PRTG Network Monitor 12.4.6.3229 (Nov 7, 2012)

New in PRTG Network Monitor 12.4.5.3164 (Oct 24, 2012)

New [Core]: The 64bit PRTG Core Server will be installed on 64bit Windows systems with at least 6 GB RAM; for systems not meeting this requirement the 32bit core server will be installed.
New [Sensors]: Port Range Sensor scans a range or list of ports
New [Sensors]: WMI Custom String Sensor performs a custom WQL query and expects a string value as result
Improved [Libraries]: PRTG now comes with several pre-configured libraries: They show all bandwidth sensors, all CPU sensors, all memory sensors, all VMware sensors, etc.
Improved [Remote Probes]: Optimized sequences in Remote Probe installer and improvements for Remote Probe auto-update
Improved [EC]: Optimized user session management as well as various improvements and bugfixes for the Enterprise Console
Improved [Notifications]: New placeholder %commentsprobe can now be used in notifications
Improved [Translations]: Many changes to the translations: DE, FR, NL, BR, JP
Improved [Sensors]: XenServer sensors optimized for performance
Improved [Sensors]: Cisco IP SLA Sensor now shows additional values (channels) (existing sensors won't be changed)
Improved [Sensors]: SSH Remote Ping sensor now allows you to enter custom parameters
Improved [Sensors]: All NetApp sensors now also work with SNMP v1
Improved [Sensors]: FTP Sensor can now write results to disk (for debugging)
Improved [Sensors]: In the XML returned by EXE/Script (Advanced) sensors you can now define warning and error limits as well as custom warning and error messages
Improved [Installation]: Improved the startup code for Remote Probe installer and uninstaller
Changed [Sensors]: In the XML returned by EXE/Script (Advanced) sensors the sensor message length () is now limited to 2000 characters
Bugfix [Sensors]: XenServer sensors stopped receiving data in specific situations
Bugfix [Sensors]: SSH Disk Free Sensor could show incorrect percentage values and returned wrong values for AIX systems
Bugfix [Sensors]: WMI Custom Sensor did not show correct message in specific situations
Bugfix [Core]: A PRTG core server installation could provoke warning messages in Windows Server 2012 Server Manager
Bugfix [Webinterface]: Main menu did not show all available items for large configurations (limitations still apply within the "Devices | Group View" sub menu; please navigate through the device tree instead to see all available groups)
Bugfix [Core]: SMS messages were always cut off at 150 chars
Bugfix [Sensors]: Auto-discovery could not detect APC UPS devices
Bugfix [Sensors]: Fixed memory leak in http sensors
Bugfix [Core]: Fixed "Cannot locate protected program data" error message
Bugfix [Webinterface]: Trigger settings were broken for xflow sensors with inherited triggers
Bugfix [Webinterface]: Fixed an 'Operation not allowed on sorted List' error which occured in special cases
Many other bugfixes and improvements to the core, web interface, and cluster
New [Sensors]: Added new "hybrid" sensors (experimental). These new sensors replace the respective WMI sensors. For better performance, they try to use Windows "Performance Counters" to query data from the target system and use WMI only as fallback.You can preselect the usage of WMI or performance counters in the device settings:
New: Hyper-V Virtual Storage Device BETA
New: Windows Pagefile BETA
New: Windows System Uptime BETA
Offer an alternative to WMI monitoring (can ease the load on the WMI system for installations with many WMI sensors)
Sensors use RPC for communications (less overhead than WMI) and require the "Remote Registry Service" to be enabled on the target systems, this is usually the case for Windows server products, but not for workstations.
New [Sensors]: Added sensor for HP Proliant servers:
New: SNMP HP Proliant Network Interface
New [Sensors]: Added Sensors for NetApp SANs:
New: SNMP NetApp License BETA: Shows remaining days of a NetApp license
New: SNMP NetApp Enclosure: Shows hardware values
New [Sensors]: Added sensors for hardware monitoring via SNMP (work for SNMP-enabled Windows and Linux systems as well as for the management software of hardware racks, e.g. Dell, HP, etc.):
SNMP Memory
SNMP Disk Free
SNMP CPU Load

New in PRTG Network Monitor 12.4.4.3098 (Oct 16, 2012)

New in PRTG Network Monitor 12.3.4.3048 (Oct 1, 2012)

New in PRTG Network Monitor 12.3.4.2993 (Sep 18, 2012)

New: [Core]: Language Brazilian Portuguese
New [Sensors]: Added Sensors for NetApp SANs:
New: SNMP NetApp Disk Free Sensor
New: SNMP NetApp System Health Sensor
New: SNMP NetApp I/O Sensor
New: SNMP NetApp Network Interface
New [Sensors]: Added Sensor Family „Performance Counters" BETA (experimental):
New: Performance Counter CPU Sensor
New: Performance Counter Memory
Offers an alternative to WMI monitoring (can ease the load for installations with many WMI sensors)
Sensors use RPC for communications (less overhead that WMI) and require the "Remote Registry Service" to be enabled on the target systems, this is usually the case for Windows server products, but not for workstations.
Improved [Core]: PRTG web server can now run on https (SSL) on a user specific port (other than 443)
Improved [Sensors]: In the XML returned by EXE/Script (Advanced) sensors you can now specify the encoding
Improved [Sensors]: WMI Service sensor can now write results to disk (for debugging)
Improved [Autodiscovery]: Optimized discovery of SNMP RMON sensors
Changed [Core]: Internet Explorer 10 (Windows 8/2012) can now be used to access the PRTG Ajax web interface
Changed [Sensors]: SSH Port settings has been moved to the device settings (and can be overridden in the sensor settings, if necessary)
Changed [Sensors]: The Windows Scheduled Task sensor now can monitor systems running on Windows 2003
Bugfix [Core]: Double spaces (e.g. in object names) were removed from the configuration
Bugfix [Core]: Geo maps were not shown in Mobile Web GUI in some cases
Bugfix [Sensors]: WMI Windows Security Center Sensor did not work with Microsoft Defender anti-malware
Bugfix [Sensors]: IP on DNS Blacklist sensor rejected DNS zones like zen.spamhaus.org and did not show a warning in case it found an IP on a blacklist
Bugfix [Reports]: Dropdown list could show empty lines in some cases
Bugfix [Cluster]: Schedules did not work on all failover clusters
More than 100 other bugfixes and improvements as well as an updated manual

New in PRTG Network Monitor 12.3.3.2854 (Aug 29, 2012)

New in PRTG Network Monitor 12.3.3.2834 (Aug 28, 2012)

New in PRTG Network Monitor 12.3.2.2629 (Aug 13, 2012)

New [Cluster]: Users can now select which cluster nodes are used to monitor a specific group/device (e.g. when not all cluster nodes can connect to a subnet or VPN)
New [Sensors]: MS Exchange Transport Queue Sensor
New [Sensors]: Added a third option to the HTTP Full Page sensors. With this new third option you can enable screenshotting of each sensor run. You can either save only the latest screenshot, or each screenshot of this sensor. The image files will be stored on the probe system (user can set the number of days until the files are purged, creates a lot of data on the disk). This option needs plenty of CPU cycles and should not be used too heavily.
New [WebGUI]: Added an experimental feature that allows a user inside the WebGUI to install a remote probe on a Windows device in the sensor tree (Context menu of devices, device tools, install remote probe). The remote probe is automatically installed and configured. Afterwards it will show up at the bottom of the sensor tree and the user must approve the probe. Then sensors can be set up as usual. This is a great way to circumvent WMI or other connectivity problems by running sensors directly on the device.
Improved [Core]: When Active Directory integration is used all requests to the AD servers are now cached for one hour. Before this caching was implemented large and/or slow AD environments could potentially slow down PRTG’s user interfaces. If a password is changed in the AD you must either wait for 1h or clear the cache manually (on the status page).
Improved [Graphs]: Graphs now display the applied averaging interval at the bottom right
Improved [Sensors]: Added timestamp into emails of email round trip sensors
Improved [Sensors]: SNMP Custom String now supports RegExp
Improved [Sensors]: When devices need extensive time to answer WMI requests the sensor will be labeled “sluggish” because these sensors can actually affect the performance of the complete WMI system for all devices. We recommend to either install a probe directly on these devices or at least move these sensors to a dedicated probe
Bugfixes: Various bugfixes for the EC, core, sensors and probe

New in PRTG Network Monitor 12.3.1.2419 (Jul 30, 2012)

New in PRTG Network Monitor 12.3.1.2365 (Jul 19, 2012)

New in PRTG Network Monitor 12.2.2.2210 (Jun 28, 2012)

New in PRTG Network Monitor 12.2.2.2156 (Jun 20, 2012)

New in PRTG Network Monitor 12.2.1.1972 (May 29, 2012)

New in PRTG Network Monitor 12.2.1.1880 (May 25, 2012)

New in PRTG Network Monitor 12.2.1.1767 (May 10, 2012)

New Build, delivery, and test system as well as "Continuous Rollout":
We have redesigned our development, build, and delivery process completely
This allows us to deliver new features and bug fixes faster and with short release cycles while maintaining maximum stability and reliability
User can choose between different channels: "Stable", "Preview", and "Canary"
Simplified installation and the new „ Configuration Guru":
WebGUI Design „Facelift"
Toplist Visualizations display the observed traffic pattern in a beautiful and easy to understand graph
Improved and interactive geo maps:
PRTG now supports several map data providers:
Map Quest (free) - This is our recommended option
Nokia Maps (free service)
Cloud Made (free service, API key required)
Google (using the static maps API (like in PRTG 9), free service, API key required)
You can now position the markers on the maps manually with the mouse or by entering an address or by entering geo coordinates
You can now zoom and move the maps
There are no limitations for the number of markers on a map any more (except for potentials performance limitations with hundreds of markers or more)
Sensors:
Application Sensors:
New: VMware Host Server Health Sensor monitors the health of a VMware host server via SOAP. It will show an overview of your host servers' states, just as known from the vCenter console ("green" / "warning" / "error").
New: WMI Sharepoint Process Sensor monitors a sharepoint process via WMI
New: WMI IIS Application Sensor (monitors TotalBytesReceived, TotalBytesSent, TotalGetRequests, TotalPostRequests, TotalAnonymousUsers, TotalFilesReceived/Sent, and other metrics of IIS, using WMI)
Hardware Sensors:
New: SNMP Cisco ASA VPN Connections Sensor (monitors the active VPN connections on a Cisco ASA firewall via SNMP)
New: SNMP Cisco ASA VPN Traffic Sensor (monitors the traffic of permanent VPN IPsec connections via SNMP) and alerts if a connection is not established
New: Fritz!Box WAN Interface Sensor (monitors the popular AVM internet access router for SOHOs and small businesses in Europe)
New: Google Analytics Sensor (gets traffic data for a website from Google Analytics, makes it easy to use this data in PRTG's maps, e.g. for office dashboards)
New: WMI Remote Ping Sensor (measures PING times from a remote computer)
New: SIP Options Ping Sensor (monitors whether a SIP server (e.g. VoIP telephony system) will accept a call and will be able to forward it to the next hop); the sensor will show an error if the device does not accept calls or if the device is not able to route calls)
New: Xen Host Sensor. Monitors CPU, memory, and network usage, as well as other vital system parameters on XEN hosts.
Rewrite: Amazon Cloudwatch Sensor (monitors instances of EC2, EBS, RDS DB, ELB, SNS, SQS, ElastiCache in the Amazon AWS Cloud)
Rewrite: Xen Virtual Machine Sensor. Monitors CPU, memory, and network usage, as well as other vital system parameters of Xen virtual machines.
Rewrite: SMTP Sensor now automatically supports TLS
Improved Active Directory Integration (among others PRTG will now get the email address of new users from the active directory, when the AD integration is used)
Improved: IMAP Sensor can now be used to monitor backup processes and other scheduled processes by looking for specific emails (e.g. by topic) in a mailbox and checking that the most recent email is not older than x days
Improved: SSH sensors now support Solaris 9 and 10
Discontinued: old VMware Host sensors must be manually replaced with new versions
Discontinued: old XEN server sensors must be manually replaced with new versions
Enterprise Console:
Improved: Now covers about 90% of WebGUI functionality
Other changes:
Improved web server security
PRTG now handles all strings internally as UTF-8 (including web server and emails), this means that you can now mix different languages, charsets and single-byte as well as double-byte strings inside one installation

New in PRTG Network Monitor 9.2.1.2270/2271 (Mar 19, 2012)

New in PRTG Network Monitor 9.2.0.2195/2196 (Feb 22, 2012)

New in PRTG Network Monitor 9.2.0.2141/2142 (Feb 9, 2012)

New in PRTG Network Monitor 9.2.0.2120/2121 (Jan 25, 2012)

More than 400 changes since V9.1.6 released December 15th
New: [Sensors] Chromium Based Full Page Sensor can now use the Chromium "WebKit" engine for monitoring (as alternative to the IE installed on the probe system)
New: [Sensors] WMI UTC Time Sensor measures time difference between the system clock of a monitored device and the time of the PRTG system
Changed: [Sensors] Improved handling of private keys for SSH sensors
Changed: [Sensors] New DLLs for SQL database sensors
Changed: [Sensors] Improved FTP Sensor (can now count only new files, too)
Changed: [Sensors] QoS Round Trip sensor has a RTT (Round Trip Time) channel, Calculation for MOS Score corrected
Changed: [Sensors] HTTP XML/REST Value Sensor now supports multiple name spaces in XML data
Changed: [Core] Auto-Discovery can now work with (mixed) lists of DNS names and/or lists of IPs
Changed: [Notifications] SMS messages can now be trimmed to 160 characters
Changed: [Cluster] Improvements for the clustering code
Bugfix: [Sensors] Scale Factor for various WMI Sensors corrected
Bugfixes: Various bugfixes and changes
New: [Sensors] VMware 5 support:
ESX 5 and Virtual Center 5, and support for vApps
New VMware sensors support ESX 4-5. Old sensors will keep working (not rewritten to new ones), but you cannot create the old ones anymore
Note: Monitoring is currently limited to one thread at a time because of limitations of the VMware platform. Monitoring with VMware sensors is limited to about 30 sensors at 1 minute interval or 150 sensors at 5 minute interval (recommended)
In case you reach these limits you can spread VMware sensors on different remote probes.
Note: For VMware monitoring, the .NET 4.0 framework must be installed on the system running the PRTG probe (either the core server or the system running a remote probe)
Changed: [WebGUI]: Two hands full of additional awesomeness for the AJAX WebGUI (various new features/improvements):
Rewrite of the sensor selection for reports
Libraries can now be created with nested layers/groups
Management tab optimized: now including multi-edit of object properties
Faster Ajax Web GUI (speed optimized HTML/CSS)
Official support for the new device tree views "sunburst" and "treeMap"
Added a device tree navigation to the breadcrumbs
Multi-edit for "Sensor Display" option (must select multiple sensors of one sensor kind)
Display new version releases notes before auto-update is started
You can now show/hide channels lines in graphs of sensors
Rewritten page for "Setup | Downloads"
Changed: [MobileGUI] Full rewrite of the Mobile Web GUI:
Optimized for iOS 3.2+, Android 2.1+/Honeycomb, Blackberry 6+, Windows Phone 7+, WebOS 1.4+, Meego, Kindle 3+, Firefox Mobile, Opera Mobile 11+
Based on jQuery Mobile 1.0.
Changed: [EC] Extended functionality within the Enterprise Console:
Gets a "back"/"forward" button for viewpoints
Setup functions are now available directly within the Enterprise Console window

New in PRTG Network Monitor 9.1.5.1899/1900 (Nov 29, 2011)

New in PRTG Network Monitor 9.1.4.1883/1884 (Nov 26, 2011)

New in PRTG Network Monitor 9.1.4.1877/1878 (Nov 23, 2011)

New in PRTG Network Monitor 9.1.4.1839/1840 (Nov 16, 2011)

New in PRTG Network Monitor 9.1.3.1792/1793 (Oct 27, 2011)

New in PRTG Network Monitor 9.1.3.1759/1760 (Oct 22, 2011)

New in PRTG Network Monitor 9.1.3.1756/1757 (Oct 20, 2011)

New in PRTG Network Monitor 9.1.2.1687/1688 (Oct 7, 2011)

New in PRTG Network Monitor 9.1.1.1644/1645 (Oct 3, 2011)

New in PRTG Network Monitor 9.1.1.1630/1631 (Sep 30, 2011)

New in PRTG Network Monitor 9.1.1.1620/1621 (Sep 29, 2011)

New in PRTG Network Monitor 9.1.0.1581/1582 (Sep 27, 2011)

New in PRTG Network Monitor 9.1.0.1547/1548 (Sep 22, 2011)

New in PRTG Network Monitor 9.1.0.1537/1538 (Sep 22, 2011)

New in PRTG Network Monitor 9.1.0.1534/1535 (Sep 22, 2011)

New in PRTG Network Monitor 9.1.0.1527/1528 (Sep 22, 2011)

"Libraries" and Improved Tree Display:
Users can build their own "trees"
Highly interactive tree display, e.g. monitoring objects in trees and libraries can be moved or cloned by drag&drop (use the "Manage" tab)
Speed improvements for large installations
Our new "Enterprise Console":
Our former "Windows GUI" makes a big leap forward: The "Enterprise Console" now supports viewing data of multiple PRTG core installations at a glace: Your entire monitoring data in one single program, even in huge setup scenarios
Connects to one or several PRTG servers
Displays aggregate information for all servers
Enables the user to monitor virtually unlimited number of sensors by scaling "horizontally" (i.e. distributing sensors on many PRTG servers)
Many new features inside, now supports almost all functionality of the Web GUI
Monitoring of IPv6 Networks:
IPv6 is becoming an important part of IT management. PRTG 9 supports monitoring IPv6 based networks:
70% of available sensor types support IPv6
Among these sensor types are, for example, ICMP, SNMP, WMI, HTTP, and most TCP based sensors, and the Packet Sniffer sensor
New "Add Sensor" Dialog and Added "Hardware" Sensor Types:
This is the new user interface used for sensor type selection when you add new sensors manually. And we have added dedicated hardware sensors for selected vendors, e.g. Cisco, Dell, HP, APC, etc. as well as several new sensor types (see below).
New Monitoring Features:
New Two-Way QoS Sensor for "two way" monitoring (sends packets back and forth between two probes and measures QoS)
QoS sensors now support DSCP/TOS setting to set QoS parameters inside the UDP test packets ("Traffic Control")
Qos sensors now calculate MOS values
New SSH ESX Disk Sensor for ESX/ESXi
New WMI Physical Disk Sensor
New WMI Hyper-V Virtual Network Adapter Sensor
New SNMP String Sensor to monitor OIDs that return a string
New Registry Sensor
New Health Sensors for Probe, Core, Cluster and System (monitoring internal status and status of the system that PRTG runs on)
Rewrite of WMI Vital System Data Sensor
DNS sensor now also supports other record types than "A"
HTTP Advanced, Port, DNS and DHCP sensors can parse sensors results using regular expressions
SSH sensors now support private keys
Added a "Dependency Delay" feature
"Percentage Channels": A channel of a sensor can now display the current measurement in percent of a given maximum value, e.g. the "link speed" of a port
xFlow sensors now support sampling
xFlow sensors can now distinguish packets from various devices sending flow data to the same IP/port ("sender-IP based flow analysis")
New Packet Sniffer engine "WinPcap". This is the same engine on which the well-known "WireShark" system is based on
Amazon SNS Notifications: PRTG can now send "Simple Notification Service" messages via Amazon
More functionality for the Sensor Factory sensor type (including boolean functions)
User Interface UpdateThe whole web interface got a "facelift"
Rewrite of "Notifications trigger" editing
Rewrite of "Sensor Selection" when creating new sensors
Added Multi-Edit-function for sensor channel settings
Rewrite of the "Welcome Assistant" (improved user guidance on initial setup)
Rights report displays the user access rights for a monitoring objects and how these rights have been inherited from parent objects. Very useful for users that manage access rights in-depth
New "Acknowledge Until" feature for Alarms acknowledgement for a certain period of time
New "Pause Until" feature can pause a sensor for a certain period of time
Update of AJAX functionality with speed improvements
Support for "Desktop Notifications" with Google Chrome browser
User Management using Active Directory:
Login accounts for PRTG users can be managed using Active Directory.
This makes it much easier to manage large numbers of users that have access to the PRTG interface
Improved Cluster Functions:
Users can now access maps on all Cluster Nodes
Map background images are automatically synchronized between nodes
User can easily switch between cluster nodes (in Web interface and Maps)
"Master Heartbeat": The current Master Node runs a script every 5 minutes that can e.g. change the IP address for access to the cluster in a DynDNS setup, to make sure the users will always be connected to the current Master Node.
Improved Auto-Discovery:
Added auto-discovery support for IPv6 (paste IP list)
PRTG detects the vendor of devices by analyzing their MAC addresses
Automatic Software Update for Your PRTG Servers:
When a new version of PRTG is available, PRTG will automatically download the latest version and will notify you about the update
Now you can click a link and PRTG will update itself automatically
Automatic update is available for all trial and freeware users and for all commercial licenses with an active maintenance contract

New in PRTG Network Monitor 8.4.2.2380/2381 (Jul 15, 2011)

New in PRTG Network Monitor 8.4.2.2356/2357 (Jun 28, 2011)

New in PRTG Network Monitor 8.4.2.2320/2321 (May 31, 2011)

New in PRTG Network Monitor 8.4.1.2282/2283 (May 3, 2011)

New in PRTG Network Monitor 8.4.0.2246/2247 (Apr 20, 2011)

New in PRTG Network Monitor 8.3.3.2199/2200 (Mar 29, 2011)

New in PRTG Network Monitor 8.3.2.2157/2158 (Mar 22, 2011)

New in PRTG Network Monitor 8.3.1.2088/2089 (Mar 8, 2011)

New in PRTG Network Monitor 8.3.1.2079/2080 (Mar 2, 2011)

New in PRTG Network Monitor 8.3.0.2021/2022 (Feb 16, 2011)

[Translations] Added Dutch, French*, Chinese*, and Japanese* translation (*2% of strings still in English language)
[Sensors] Added 16 new sensor types (.NET 2 required on probe system if not mentioned otherwise)
HTTP XML/REST Value (consumes REST based XML APIs to retrieve a sensor value)
HTTP SSL Certificate Expiry (monitors the number of days left until the SSL certificate of a HTTPS website expires)
Traceroute Hop Count (monitors the number of hops required to reach a remote system and alerts when route changes)
Logfile Content Check (scans a text file and alerts if a certain string is contained within the file)
Windows Logged in users (monitors the number of active user sessions on a Windows system)
WMI Windows Version (monitors the currently installed Windows version)
Windows Last Update (monitors the number of days since the last Windows update)
Active Directory Replication Errors (monitors Active Directory domain controllers for replication errors)
POP3 Email Count (counts number of mails in a POP3 mailbox)
FTP Server File Count (Counts number of files on a FTP server)
INI File Content Check (check the content of an INI file)
Ping Jitter (sends a number of PINGs to a remote system and calculates the Jitter value)
Ping with Delayed Up (intended to be used as a dependency sensor for devices where other services need extra time to become available after a (re-)boot)
Windows Print Queue (monitors the number of jobs and the state of a print queue on a Windows server, alerts e.g. if paper has run out)
Windows MSMQ Queue Length (monitors the queue length of a MS Message Queue Server)
IP on DNS Blacklist (checks various blacklist servers in order to verify if an IP address is blacklisted due to spam emails)
[Sensors] HTTP Transaction sensor now displays request time for each step of the transaction in an individual channel
[Webserver] Various performance optimizations, especially for the web interface for large installations (>500 sensors) and multiple simultaneous users
[WebGUI] Large live graphs now refresh with half the sensor interval: for sensors with short intervals you will see monitoring results coming in "live" without the need to click "refresh" manually.
[Reports] Added a new PDF generator (based on WebKit engine) for PDF reports (faster and not dependent on local IE installation)
[WinGUI]: Added Google Maps to WinGUI, various bugfixes
[Help] Added numerous context sensitive links from the WebGUI into the online manual
Changed: Native support for all instant messengers has been removed (please use external tools, see KB article)
Changes: Improved WMI stability (fixed PE054 flooding)
Bugfix: NetFlow 5 sensors now correctly evaluate TOS Byte
Bugfix: In some situations the spike filter did not work properly
Various smaller bugfixes and enhancements

New in PRTG Network Monitor 8.2.0.1930/1931 (Jan 25, 2011)

New in PRTG Network Monitor 8.2.0.1898/1889 (Jan 18, 2011)

[Core Server] New database format:
We implemented a new, faster database system for log, ToDo, and Toplist data. This new system is much faster and will provide a much swifter user experience, especially on systems with 500 and more sensors. In our tests we found that it can be up to 300 times faster, depending on your system and configuration
After upgrading to V8.2.x or later your previous databases will be converted during PRTG’s startup - which can take between a few seconds and a few minutes. Only the potentially huge multi-gigabyte Toplist databases will be converted in the background after the startup, as soon as the monitoring process has been restarted. During the conversion you may see drops of Toplists (gaps in your Toplist data) whenever the system performance is not capable of supporting simultaneous conversion and monitoring. Note: The old database files will be deleted 70 days after the database upgrade.
[Sensors] Important change for Ping and Port sensors:
Their time values no longer cover the DNS resolution in their measurements, now values are analogous to the Windows built-in Ping command. Depending on the type of DNS entry used for the parent devices this can change the values dramatically to smaller values. For devices that are set up using IP addresses the values do not change at all.
[Auto-Discovery] Massive upgrade of the Auto-Discovery system:
Auto-Discovery now covers 95% of the available sensor types, depending on your network you may see 20-50% more sensors during an auto-discovery scan.
Added various options to enter IP ranges for auto-discovery, including Class A address ranges and IP lists. Note: Only subnets with up to 65536 IP addresses can be discovered.
Added 5 new device templates to the Auto-Discovery system, including “Linux SNMP”, “Server RDP”, and “XEN Server”.
Users can now select the time of day when daily, weekly, and monthly auto-discoveries are performed (default is 4 a.m.).
WebGUI shows a note about potentially degraded performance while auto-discoveries are running.
[Device Templates] Massive upgrade of the device template system:
Now all sensors that make sense to be stored in device templates will be used (covering about 95% of available sensor types).
[Sensors] 3 new sensor types:
New DHCP sensor checks whether a DHCP request is answered by a DHCP server in the network
New SSH VMware ESX(i) Disk Sensor monitors disk space on attached storage of VMware ESX and ESXi servers via SSH
New jFlow V5 Sensor supports Juniper jFlow (version 5) monitoring. Note: Sensor does not support sampling yet, please disable sampling on the device.
New: [Sensors] Added an alternate connection method for VMware sensors (.NET required on the probe system), during testing we saw some situations where the alternate connection worked more reliably than the default one.
New: [Sensors] EXE/Script sensors now support environment variables (all environment variables have a "prtg_" prefix)
Changed: [Sensors] The TCP port can now be selected manually for MySQL sensors
New: [Core Server] We implemented various performance enhancements that will mainly be visible on installations with 500 or more sensors. Many web pages created by the web server are now up to 100 times faster than before (on systems with thousands of sensors).
New: [WebGUI] Submit buttons on setting pages are now always scrolled into view automatically
New: [WinGUI] Various improvements of the WinGUI, including the option to select the default browser engine to open web pages.
New: [Reports] Reports with tables now include a list of down- and uptimes of a sensor
New: [WMI] Yet again, another bunch of WMI improvements, mainly for systems with many WMI sensors (500 or more)
Changed: [Cluster] "Simulate Error" now propagates across a cluster
Bugfix: [WebGUI] Fixed a potential Cross Site Scripting (XSS) vulnerability
Bugfix: In total more than 300 bugfixes and improvements are included in this build.

New in PRTG Network Monitor 8.1.2.1809/1810 (Nov 17, 2010)

New in PRTG Network Monitor 8.1.2.1775/1776 (Nov 17, 2010)

New in PRTG Network Monitor 8.1.2.1750/1751 (Nov 4, 2010)

New in PRTG Network Monitor 8.1.1.1695/1696 (Oct 19, 2010)

New in PRTG Network Monitor 8.1.0.1621/1622 (Sep 28, 2010)

New in PRTG Network Monitor 8.1.0.1607/1608 (Sep 28, 2010)

All-In Licensing for PRTG:
With version 8, Paessler takes a revolutionary step and completely simplifies its licensing model. Using our new add-on-frede software product PRTG 8 you monitor your network without worrying about paying extra money for additional features. Everything is included in one license because we are confident this makes your work easier. Simply choose an installation size for your setup and benefit from the new functionalities PRTG brings to your network.
"PRTG Cluster" Failover Solution:
Up to 5 PRTG instances ("Nodes") work together
A cluster consists of one primary instance of PRTG ("Master Node") and 1 to 4 secondary servers ("Failover Nodes")
Objective 1: Achieve 100% uptime for the monitoring solution. Not even a software update causes downtime for a PRTG cluster.
Objective 2: Automatic failover: If the primary node fails or looses connection to the cluster, another node immediately becomes the master server and manages notifications => Notifications are always sent, even if the primary master has no connectivity or has crashed.
Objective 3: Multiple points-of-presence monitoring: All nodes monitor all sensors all the time. This means that response times are measured from different locations in the network (LAN/WAN/VPN) and can be compared with each other. Additionally, aggregated up/downtimes can be computed.
And here comes the best part of this new feature - our customer-friendly-licensing: All PRTG licenses allow you to create a "Single Failover" installation (two installations of PRTG working together) with just one license key (additional license keys are required for 3 or more nodes).
This means that you don't pay extra to use PRTG's new high-availability feature (compare with other vendors!). We assume that most commercial PRTG installations will be "Single-Failover" installations (1 primary node plus 1 failover node).
New: Improved and redesigned web interface: We've rearranged the web interface, added new on-mouse-over features, and redesigned the overall look and feel to make the web interface even more convenient for your daily work.
New: Added a "Mini-HTML" interface for mobile and low bandwidth access designed for iPhone, Android, Blackberry, Windows Mobile, Opera Mini, and even Internet Explorer 5/6 (does not require Ajax/Javascript)
New: Support for Google Maps in the web interface (maps that show red/green/etc. flags for down/up/etc. devices). Simply enter a postal address, city name, or geotag in the "location" field of groups and/or devices to populate the maps with live monitoring data!
New: Improved "Maps" feature: PRTG now includes 280 beautifully designed network icons and you can connect map objects with lines that follow their objects when they are moved. With the new editor, PRTG now supports you in creating maps of your whole network structure, even without additional background graphics.
New chart types: PRTG's charts are now easier to read with the optional new "filled" and "stacked" styles. For traffic sensors the in and out channel can be shown as positive and negative values.
New: Native and Agentless Linux Monitoring
In-depth monitoring of Linux systems without extensive modifications on the clients
Uses SSH, WBEM, or SNMP for monitoring
Support for all major Linux distributions and Mac OS X
New: Added New Sensor Types
NTP sensor
ADO sensor (i.e. support for all ADO compatible databases)
LDAP sensor
XEN Server sensor
WMI Hyper-V Virtual Storage Device sensor
WMI Terminal Server sensor
WMI Share sensor
WMI Printer sensor
WMI Uptime sensor
Windows Event Log sensor (Windows API based)
Linux SSH sensors (load average, meminfo, disk free)
Linux SNMP sensors (load average, meminfo, disk free)
VMware Host Hardware sensor (using WBEM)
WBEM Custom Sensor
New: HTTP sensors and HTTP notifications now offer proxy support
New: Reporting is now fully decoupled from the web server and user interface, so report generation no longer affects user experience. This allows us to ease the minimum interval limits for reports: reports with 1 minute interval can now be created for up to 40 days instead of one day, 1 hour reports are possible for up to one year now.
Improved: Email notifications: Notification HTML emails now look great on most email clients.
Improved: Notification summarizing (to avoid email floodings)
Improved: WMI connection management
Improved: API - Many new features have been added to make it easier to create your own custom sensors and scripts.
New: Added a graphical visualization of sensor dependencies
Improved: Monitoring scheduler now avoids load peaks on monitored devices caused by simultaneous monitoring requests
Improved: Performance improvements throughout the whole software
Changed: Dropped support for Flash graphs in the web interface
Changed: Dropped support for Internet Explorer 7 by the Ajax interface (IE6 and IE7 can use the HTML-Only interface)

New in PRTG Network Monitor 7.3.5.5801/5802 (Jul 23, 2010)

New in PRTG Network Monitor 7.3.5.5787/5788 (Jul 14, 2010)

New in PRTG Network Monitor 7.3.5.5780/5781 (Jul 14, 2010)

New in PRTG Network Monitor 7.3.5.5746/5747 (Jun 1, 2010)

New in PRTG Network Monitor 7.3.4.5709/5710 (May 12, 2010)

New in PRTG Network Monitor 7.3.3.5633/5634 (Mar 31, 2010)

New in PRTG Network Monitor 7.3.3.5610/5611 (Mar 29, 2010)

Overview: This update contains performance optimizations for large installations (>1000 sensors) as well as bugfixes
New: Optimizations for large installations (thousands of sensors and more)
On installations with thousands of sensors PRTG's Web GUI felt sluggish under certain conditions
Thanks to various internal optimizations and an optional "speed mode" (see below) web pages can now be generated 5-50 times faster (compared to V7.3.2 or earlier)
Our test installations with 10.000 and 20.000 sensors now deliver all web pages (except for sensor lists) in less than 1 second (down from 5-30 seconds)
New "Speed mode" switch: When enabled (see System Settings|Webserver Settings) the following aspects of the software will change:
Slower updates for the data displayed in the web interface: It can now take up to 60 seconds for a new sensor state (up/down) to be displayed in the web interface (alerts/notifications will still be sent instantly) (Web GUI und Windows GUI)
Web GUI does not alert for new todos in the browser window (todo emails will still be sent instantly)
Web GUI does not dispay the mini graphs for sensors and at the top of the window
Web GUI does not show sensor-tree related menu items (devices by group, sensors by tag, sensors by type, sensors by group)
New: "Security Context" for reports (security improvement for reports): You can now select a user account for each report that will be used when creating HTML and PDF reports. Reports will only contain objects (devices, sensors, etc.) which the selected user is allowed to view. By default it is the user who has initially created this report (administrators are able to change this setting).
Changed: Improved memory handling when saving configuration (some users saw an out-of-memory error while the configuration was written to the disk)
Bugfix: Removed a potential deadlock in the dependency processing
Bugfix: For some users the PDF generator and config-check tool did not work due to spaces in pathnames
Bugfix: Fixed a sporadic handle leak in Custom EXE sensors

New in PRTG Network Monitor 7.3.2.5476/5477 (Mar 9, 2010)

New in PRTG Network Monitor 7.3.1.5459/5460 (Mar 3, 2010)

New in PRTG Network Monitor 7.3.0.5365/5366 (Feb 16, 2010)

New in PRTG Network Monitor 7.2.6.5299/5300 (Feb 1, 2010)

New in PRTG Network Monitor 7.2.5.5513 / 5514 (Jan 13, 2010)

New in PRTG Network Monitor 7.2.4.5046 / 5047 (Dec 10, 2009)

New in PRTG Network Monitor 7.2.3.4990 / 4991 (Nov 27, 2009)

New in PRTG Network Monitor 7.2.3.4966 / 4967 (Nov 24, 2009)

New in PRTG Network Monitor 7.2.2.4944 / 4945 (Nov 17, 2009)

New in PRTG Network Monitor 7.2.1.4722 (Oct 9, 2009)

New in PRTG Network Monitor 7.2.1.4717 (Oct 7, 2009)

New in PRTG Network Monitor 7.2.1.4688 (Sep 28, 2009)

New in PRTG Network Monitor 7.2.1.4661 (Sep 25, 2009)

New in PRTG Network Monitor 7.1.4.4609 (Sep 21, 2009)

New: Windows GUI
Especially for larger installations (500 sensors and more) the Windows based user interface is faster and more comfortable when managing sensors. The WinGUI includes all features of the former Tray Tool plus interactive editing of objects. It can be installed and used on multiple computers at once. You can continue to use the classic web-based interface, too.
Connects to a PRTG Core Server through HTTP/HTTPS (using our own PRTG API)
Displays the device tree, sensor list, alarms list, maps, reports etc.
Allows to add/edit/delete sensors, groups, and devices
Allows to arrange groups, devices and sensors using drag&drop
Allows to compare live data, graphs and historic data tables of two or more sensors
Alerts you with popup dialogs and/or sound alarm when events occur on the PRTG server
Additional Sensor Types
Support for sFlow and Netflow 9
QoS (Quality of Service) sensor measures vital network connectivity parameters like jitter, packet loss, and packet delay variation between two probes – the perfect tool to find network issues that can affect VoIP sound quality or video streaming hickups. Some vendors would call this a “VoIP Sensor”.
IP SLA Sensor (monitors results of IP-SLA on Cisco routers, some would call this a “VoIP Sensor”, too)
Amazon CloudWatch Sensor uses data from Amazon’s CloudWatch service to monitor EC2 instances
Sensors for servers running Microsoft HyperV
RADIUS Server Sensor
Syslog and SNMP Trap receiver sensor
Sensors for Microsoft Exchange 2007 and more detailed monitoring of Exchange 2003
Improved Web-based User Interface
Multi Object Editing feature (e.g. edit the interval of 2 or more sensors at once)
Improved multi edit menu in tables of sensors, maps, reports, etc.
Improved “S” view for groups for large installations
User can select an icon for each device
You can now select two or more items from a search result to work on them
Toplists now show Pie Charts
Maps have a refresh icon at the bottom left, refresh interval can be set to 10/30/60 seconds
“Map Rotation” feature: The map display rotates through selected maps (select two or more maps from the list of maps and choose “Map Rotation” from the multi edit menu)
And many more
Improved Reporting
To improve reporting we have added new templates (Top 100 Lowest/highest sensor values, Top 100 best/worst uptime) as well as the following new default reports:
Top 100 Busy/Idle Processor Sensors
Top 100 Uptime/Downtime Report
Top 100 Fastest/Slowest PING Sensors
Top 100 Most/Least Used Bandwidth Sensors
Top 100 Most/Least Used Memory Sensors
Now also the Sensor selection for a report can be filtered by tag (e.g. to only include PING sensors in a report) and you can create “Working Hour” Reports (a schedule can be assigned to a report, data is only used for specified hours of day/week). And we have added new reports templates that only show data tables without graphs.
New: "Historic Data" feature allows to dig into the historic data for a specific time frame. You can display or export the raw data (each single monitoring request) as well as averaged data (exports to HTML, XML, CSV)
New: "Acknowledge Alarm" feature: Sensors with error state can be marked as “acknowleged”. User can enter a message which is shown with the username as long as the error state goes on (e.g. this allows to show a “I will handle this” message in sensor lists). As soon as an alarm has been acknowledged, no further escalation notifications will be send for this sensor.
Updated: Improved “Unusual Detection”: Detection has been simplified and now looks at hour of day and day of week
PRTG has been certified for the official “Works with Windows 2008 Server” logo by Microsoft

New in PRTG Network Monitor 7.1.4.3443 (Aug 11, 2009)

New in PRTG Network Monitor 7.1.4.3437 (Jul 29, 2009)

New in PRTG Network Monitor 7.1.4.3432 (Jul 22, 2009)

New in PRTG Network Monitor 7.1.4.3417 (Jul 9, 2009)

New in PRTG Network Monitor 7.1.3.3376 (Jul 2, 2009)

New in PRTG Network Monitor 7.1.3.3333 (Jun 5, 2009)

New in PRTG Network Monitor 7.1.3.3317 (May 26, 2009)

New in PRTG Network Monitor 7.1.2.3273 (May 13, 2009)

New in PRTG Network Monitor 7.1.2.3262 (May 8, 2009)

New in PRTG Network Monitor 7.1.1.3072 (Apr 8, 2009)

Improved Web Interface:
New: Massive speed improvements on all browser platforms
New: Groups, devices, and sensors can now be moved using drag&drop
New: Quick edit tools and live graphs pop up when mouse pointer hovers over an object
New: Improved object selection (e.g. for maps, dependencies)
New: Alerts are now optionally shown at the bottom right of the browser window
New: Added various new map object templates, including larger icons and channel list for sensors
Recommended browser for PRTG 7 is now Google Chrome (see blog entry "The Best Browser for PRTG 7")
Automatic Probe Updating for Remote Probes:
Whenever a new version of PRTG is installed on the core server all remote probes will automatically download and install the updated version of the probe as soon as they reconnect to the updated core (see blog entry "Automatic Probe Updating")
When updating from V 7.0.x to V7.1 you must update all remote probes manually for the last time
New Sensor Types:
"Sensor Factory" is the successor to the "Aggregation Sensor" in PRTG 6 (see blog entry "The Sensor Factory")
HTTP Full Page Sensor (uses an instance of Internet Explorer to measure download time for a webpage including all page elements)
SMTP&POP3/IMAP Email Round Trip Sensor (sends an email by SMTP and measures the time until it reaches a POP3/IMAP inbox, see blog entry "Email Round Trip Monitoring")
HDD Health Sensor (uses SMART feature for IDE disk drives to measure drive temperature, drive failures, etc.)
Custom EXE sensor for load testing of available CPU and disk resources (computes 1 Mio primes or reads/writes 1000 files)
HTTP Advanced sensor now also measures "time-to-first-byte", "bytes received" and "download bandwidth" (see blog entry "Monitoring the Available Bandwidth")
Toplists Feature:
For Packet Sniffer and NetFlow sensors PRTG can now display the Top Talkers (IPs that use the most bandwidth), Top Connections (connections that use the most bandwidth) and Top Protocols (most used protocols in the network) as well as customized toplists (see blog entry "Toplists")
Improved Reporting:
Percentile-Calculation
You can now select groups and devices for a report (all their sensors will be dynamically included in the report)
PDF reports are automatically broken into several files when necessary to avoid overload
PDF Reports now include all table columns (by zooming)
Improved Notifications:
Email notifications use HTML format (optional)
Added Syslog Notifications
Added SNMP Trap Notifications (see blog entry "SNMP Trap Notifications")
"Simulate Error" (sensor context menu) switches a sensor to error state in order to test notifications
Channel Settings:
User can change various settings for each channel of a sensor
Editing of channel name, graph color and line width
Editing of axis minimum/maximum per channel
Spike Filter hides impossible values or counter rollovers for delta sensors
Alarm limits and warning limits can now be entered per channel
Enable/disable individual channels for charts and for tables
For tables the number of decimal places can be set for each channel
The primary channel can be selected for sensors with multiple channels
Stability and Reliability Improvements:
New: Major improvements for probe/core connections
New: Major improvements for WMI monitoring (WMI engine was completely rewritten for more stability, especially for installations with hundreds and more WMI sensors)
New: Probe and Core service are marked „restart on failure” in service manager to improve uptime
New: Probe automatically performs a service-restart when instabilities occur
Other New Features:
New: Official support for virtualized platforms (PRTG was tested on VMware, XEN Server, Amazon EC2 and Virtuozzo; see blog entry "Official Support for Virtualized Platforms")
New: Added Multi Language Support, added Language "German"
New: Device Templates can be created from existing devices and stored on disk for reuse with the auto discovery features (see blog entry "Copying Devices by Cloning or Using Device Templates")
New: Updated API documentation with more functions documented
New: API supports logging in using username/passhash along with the previous username/password option
New: Tray tool now uses a password hash instead of the password when opening web pages in a browser
New: Divide/Multiply setting for WMI Custom sensors
New: Multiple Custom EXE Sensors can be serialized using a Mutex
New: Event Log sensor can filter events
New: A default report is created for new installations
New: Notifications can now be paused
Notable Changes:
Changed: Updated drivers for SQL monitoring (MySQL, MS-SQL, Oracle)
Changed: Updated SQLite drivers (used for internal databases)
Changed: Public maps are now refreshed by Javascript (instead of META REFRESH tag) to avoid constant reloading of css files and images
Changed: The URL in HTTP sensors can now optionally be entered without a servername (e.g. /home), the device name will automatically be added for sensors checks
Discontinued: Support for SNMP Helper (please switch to its parent product SNMP Informant)
Plus bugfixes and countless smaller improvements, too many to mention them all

New in PRTG Network Monitor 7.1.1.3016 (Apr 3, 2009)

Improved Web Interface:
New: Massive speed improvements on all browser platforms
New: Groups, devices, and sensors can now be moved using drag&drop
New: Quick edit tools and live graphs pop up when mouse pointer hovers over an object
New: Improved object selection (e.g. for maps, dependencies)
New: Alerts are now shown at the bottom right of the browser window
New: Added various new map object templates, including larger icons and channel list for sensors
Recommended browser for PRTG 7 is now Google Chrome (see blog entry "The Best Browser for PRTG 7")
Automatic Probe Updating for Remote Probes:
Whenever a new version of PRTG is installed on the core server all remote probes will automatically download and install the updated version of the probe as soon as they reconnect to the updated core (see blog entry "Automatic Probe Updating")
When updating from V 7.0.x to V7.1 you must update all remote probes manually for the last time
New Sensor Types:
"Sensor Factory" is the successor to the "Aggregation Sensor" in PRTG 6 (see blog entry "The Sensor Factory")
HTTP Full Page Sensor (uses an instance of Internet Explorer to measure download time for a webpage including all page elements)
SMTP & POP3 / IMAP Email Round Trip Sensor (sends an email by SMTP and measures the time until it reaches a POP3/IMAP inbox, see blog entry "Email Round Trip Monitoring")
HDD Health Sensor (uses SMART feature for IDE disk drives to measure drive temperature, drive failures, etc.)
Custom EXE sensor for load testing of available CPU and disk resources (computes 1 Mio primes or reads/writes 1000 files)
HTTP Advanced sensor now also measures "time-to-first-byte", "bytes received" and "download bandwidth" (see blog entry "Monitoring the Available Bandwidth")
Toplists Feature:
For Packet Sniffer and NetFlow sensors PRTG can now display the Top Talkers (IPs that use the most bandwidth), Top Connections (connections that use the most bandwidth) and Top Protocols (most used protocols in the network) as well as customized toplists (see blog entry "Toplists")
Improved Reporting:
Percentile-Calculation
You can now select groups and devices for a report (all their sensors will be dynamically included in the report)
PDF reports are automatically broken into several files when necessary to avoid overload
PDF Reports now include all table columns (by zooming)
Improved Notifications:
Email notifications use HTML format (optional)
Added Syslog Notifications
Added SNMP Trap Notifications (see blog entry "SNMP Trap Notifications")
"Simulate Error" (sensor context menu) switches a sensor to error state in order to test notifications
Channel Settings:
User can change various settings for each channel of a sensor
Editing of channel name, graph color and line width
Editing of axis minimum/maximum per channel
Spike Filter hides impossible values or counter rollovers for delta sensors
Alarm limits and warning limits can now be entered per channel
Enable/disable individual channels for charts and for tables
For tables the number of decimal places can be set for each channel
The primary channel can be selected for sensors with multiple channels
Stability and Reliability Improvements:
New: Major improvements for probe/core connections
New: Major improvements for WMI monitoring (WMI engine was completely rewritten for more stability, especially for installations with hundreds and more WMI sensors)
New: Probe and Core service are marked „restart on failure” in service manager to improve uptime
New: Probe automatically performs a service-restart when instabilities occur
Other New Features:
New: Official support for virtualized platforms (PRTG was tested on VMware, XEN Server, Amazon EC2 and Virtuozzo; see blog entry "Official Support for Virtualized Platforms")
New: Added Multi Language Support, added Language "German"
New: Device Templates can be created from existing devices and stored on disk for reuse with the auto discovery features (see blog entry "Copying Devices by Cloning or Using Device Templates")
New: Updated API documentation with more functions documented
New: API supports logging in using username/passhash along with the previous username/password option
New: Tray tool now uses a password hash instead of the password when opening web pages in a browser
New: Divide/Multiply setting for WMI Custom sensors
New: Multiple Custom EXE Sensors can be serialized using a Mutex
New: Event Log sensor can filter events
New: A default report is created for new installations
New: Notifications can now be paused
Notable Changes:
Changed: Updated drivers for SQL monitoring (MySQL, MS-SQL, Oracle)
Changed: Updated SQLite drivers (used for internal databases)
Changed: Public maps are now refreshed by Javascript (instead of META REFRESH tag) to avoid constant reloading of css files and images
Changed: The URL in HTTP sensors can now optionally be entered without a servername (e.g. /home), the device name will automatically be added for sensors checks
Discontinued: Support for SNMP Helper (please switch to its parent product SNMP Informant)

New in PRTG Network Monitor 7.1.1.3000 (Mar 31, 2009)

Overview: Version 7.1 is a major update for PRTG. It includes many new features as well as performance and stability improvements. This update is strongly recommended for all users of previous versions (as soon as the official release version is available).
Improved Web Interface:
New: Massive speed improvements on all browser platforms
New: Groups, devices, and sensors can now be moved using drag&drop
New: Quick edit tools and live graphs pop up when mouse pointer hovers over an object
New: Improved object selection (e.g. for maps, dependencies)
New: Alerts are now shown at the bottom right of the browser window
New: Added various new map object templates, including larger icons and channel list for sensors
Recommended browser for PRTG 7 is now Google Chrome (see blog entry "The Best Browser for PRTG 7")
Automatic Probe Updating for Remote Probes:
Whenever a new version of PRTG is installed on the core server all remote probes will automatically download and install the updated version of the probe as soon as they reconnect to the updated core (see blog entry "Automatic Probe Updating")
When updating from V 7.0.x to V7.1 you must update all remote probes manually for the last time
New Sensor Types:
"Sensor Factory" is the successor to the "Aggregation Sensor" in PRTG 6 (see blog entry "The Sensor Factory")
HTTP Full Page Sensor (uses an instance of Internet Explorer to measure download time for a webpage including all page elements)
SMTP&POP3/IMAP Email Round Trip Sensor (sends an email by SMTP and measures the time until it reaches a POP3/IMAP inbox, see blog entry "Email Round Trip Monitoring")
HDD Health Sensor (uses SMART feature for IDE disk drives to measure drive temperature, drive failures, etc.)
Custom EXE sensor for load testing of available CPU and disk resources (computes 1 Mio primes or reads/writes 1000 files)
HTTP Advanced sensor now also measures "time-to-first-byte", "bytes received" and "download bandwidth" (see blog entry "Monitoring the Available Bandwidth")
Toplists Feature:
For Packet Sniffer and NetFlow sensors PRTG can now display the Top Talkers (IPs that use the most bandwidth), Top Connections (connections that use the most bandwidth) and Top Protocols (most used protocols in the network) as well as customized toplists (see blog entry "Toplists")
Improved Reporting:
Percentile-Calculation
You can now select groups and devices for a report (all their sensors will be dynamically included in the report)
PDF reports are automatically broken into several files when necessary to avoid overload
PDF Reports now include all table columns (by zooming)
Improved Notifications:
Email notifications use HTML format (optional)
Added Syslog Notifications
Added SNMP Trap Notifications (see blog entry "SNMP Trap Notifications")
"Simulate Error" (sensor context menu) switches a sensor to error state in order to test notifications
Channel Settings:
User can change various settings for each channel of a sensor
Editing of channel name, graph color and line width
Editing of axis minimum/maximum per channel
Spike Filter hides impossible values or counter rollovers for delta sensors
Alarm limits and warning limits can now be entered per channel
Enable/disable individual channels for charts and for tables
For tables the number of decimal places can be set for each channel
The primary channel can be selected for sensors with multiple channels
Stability and Reliability Improvements:
New: Major improvements for probe/core connections
New: Major improvements for WMI monitoring (WMI engine was completely rewritten for more stability, especially for installations with hundreds and more WMI sensors)
New: Probe and Core service are marked „restart on failure” in service manager to improve uptime
New: Probe automatically performs a service-restart when instabilities occur
Other New Features:
New: Official support for virtualized platforms (PRTG was tested on VMware, XEN Server, Amazon EC2 and Virtuozzo; see blog entry "Official Support for Virtualized Platforms")
New: Added Multi Language Support, added Language "German"
New: Device Templates can be created from existing devices and stored on disk for reuse with the auto discovery features (see blog entry "Copying Devices by Cloning or Using Device Templates")
New: Updated API documentation with more functions documented
New: API supports logging in using username/passhash along with the previous username/password option
New: Tray tool now uses a password hash instead of the password when opening web pages in a browser
New: Divide/Multiply setting for WMI Custom sensors
New: Multiple Custom EXE Sensors can be serialized using a Mutex
New: Event Log sensor can filter events
New: A default report is created for new installations
New: Notifications can now be paused
Notable Changes:
Changed: Updated drivers for SQL monitoring (MySQL, MS-SQL, Oracle)
Changed: Updated SQLite drivers (used for internal databases)
Changed: Public maps are now refreshed by Javascript (instead of META REFRESH tag) to avoid constant reloading of css files and images
Changed: The URL in HTTP sensors can now optionally be entered without a servername (e.g. /home), the device name will automatically be added for sensors checks
Discontinued: Support for SNMP Helper (please switch to its parent product SNMP Informant)
Plus bugfixes and countless smaller improvements, too many to mention them all

New in PRTG Network Monitor 7.0.9.2193 (Jan 15, 2009)

New in PRTG Network Monitor 7.0.9.2049 (Dec 16, 2008)

New in PRTG Network Monitor 7.0.9.2027 (Dec 9, 2008)

New in PRTG Network Monitor 7.0.9.2016 (Dec 4, 2008)

New in PRTG Network Monitor 7.0.9.1928 (Nov 21, 2008)

New in PRTG Network Monitor 7.0.9.1751 (Oct 23, 2008)

Added support for Apple Safari 3.1 and Google Chrome (Webkit engine)
Added support for Internet Explorer 8 Beta 2
Reports now include more computed information about each sensor:
Averages
Totals (for traffic sensors)
Uptime/downtime (total and percent)
Good and failed requests (total and percent)
Users can now run a report for any custom time span
Sensors can be added to a report using tags (Tags are inherited from parent objects, i.e. if you enter a specific tag into a group's tag setting and into this report setting, all sensors of that group will be included in the report - additionally to the sensors selected manually)
Improved sensor selection
User can select papersize of PDF files (A4, legal, letter)
Printing of HTML reports now works on IE, Firefox, Safari and Chrome
Improved report layout (better page breaks, removed empty last page from reports)
HTML reports now open in a new window
"Clone Group" function duplicates a group with all subgroups, devices and sensors
Devices and groups can be "Folded" and "Unfolded"
Sensor tree remembers "view" setting (S, M, L, XL)
Objects in the sensor tree display an "edit" link when hovered which takes the user directly to their edit page
Improved layout for object settings
Improved menu structure
Cross reference and "Top 10" lists are now also available on group level
Sensors with alarm status are shown on red background in tables
Web browser optionally plays an alarm sound if the number of sensors with "error" state is larger than zero
Added "Dashboard 3" as third dashboard option
More reliability for Ajax features
Better handling of unstable server connections
Updated jQuery Javascript library to V1.2.6. This should provide performance improvements of up to 600% for the web interface
Added two new sensor types: VMware Server Host sensor and VMware Virtual Machine sensor
Both monitor CPU, disk, memory and network
Added new device template for automatic discovery of VMware ESX servers
Requires direct connection to a VMware ESX server
A user account can be set to "read only" mode in the account settings
Read only users can not see all the links to add, modify or delete objects (and they can not access the associated URLs)
New: "File" sensor monitors a file's existence, size, and age and also discovers changes to the file
New: "Folder" sensor monitors a folder's existence as well as the number of files and their ages/sizes and also discovers changes to the folder's content
New: "Share Disk Space" sensor monitors free disk space on SMB shares (e.g. Windows and Samba)
Objects shown in tables of maps can be filtered with tags (see map settings page)
Timezone for a map can be set by the user
Added new map objects (icons with large text, graphs without axis labels, alarm sound)
New: "Change" trigger type sends notifications whenever the monitoring target changes (for WMI File sensor and HTTP Advanced sensor)
New: Custom EXE sensors now support DLLs and can report "warning" states
New: Unusual detection can be enabled/disabled on group level
Changed: New sensors are created when autodiscovery rediscoveres a device and finds ports that had been inactive before
Changed: For SQL sensors the returned value now is primary channel (which means that it is now used for warnings/alarms)
Changed: Windows 2000 is no longer supported as operating system for the core and probe
Changed: Updated setup binaries to latest version
Changed: Updated cache file version number (=> after upgrading the graph data cache will be recomputed in the background)
Changed: Removed the Firebird installer from the PRTG installer (is only needed when upgrading data from IPCheck on a machine that has no IPCheck installation)
Changed: PRTG Import Tool is now always installed
Bugfix: "Re-Discover Now" did not work properly
Bugfix: Fixed instability in SNMP V3 support
Bugfix: Non-Admin users were unable to delete their reports / maps / schedules / notifications
Bugfix: Mobile Dashboard did not automatically reload every 60 seconds
Bugfix: For some device templates the auto discovery re-created some sensors with each run of the auto discovery
Bugfix: "Save To file" icon did not work for Flash graphs
Bugfix: Fixed Javascript exception in the web interface when loading new pages
Bugfix: Could not add SNMP traffic sensors for ports with "" in port names
Bugfix: iPhone user interface only showed sensors of the last probe in the tree
Bugfix: Layout of Top 10 pages was broken
Bugfix: SNMP Counters from OIDLIB files that are marked as "delta" sensors were not evaluated as delta sensors
Bugfix: When cloning a device the manually selected channels were not copied
Bugfix: Heavy use of the search feature could cause instability
Bugfix: Probe connection was dropped when scanning an SNMP device with an OIDLIB that contains many items
Bugfix: Oracle Sensors now support port numbers 1521
Bugfix: Various minor bugfixes

New in PRTG Network Monitor 7.0.8.1426 (Sep 11, 2008)

New: Improved map editor
Map items can now be resized
Content and template of the map items can now be edited
User can add own HTML code to add titles, comments or even images (e.g. a data center webcam) to a map
New: Improved CSS and HTML
Pages now use the full browser window where useful
New design uses fewer graphics for faster page loads
New: PRTG API
This is the first incarnation of the API, more improvements will be available soon
API allows access to PRTG's monitoring results
For details see menu item "Help|API" or this blog post
New: iPhone optimized user interface
Allows read-only access to monitoring results for Apple iPhone users
Your PRTG installation must be accesible from the Internet
Access it with your iPhone at the URL https://yourserver/iphone (where yourserver is the IP or DNS name of your PRTG installation)
Using HTTPS is recommended to secure credentials, but HTTP can also be used
See this blog post for screenshots
New: "Probe Only" installer
Provides faster distribution of the probe installer (only 4 MB) whenever a new software version is installed on the core server
Can be downloaded on probe computer by accessing PRTG's web interface (see item "Downloads" of the "Setup" menu).
New: TEXTLIST Interface
PRTG 7 supports IPCheck Server Monitor 5's "TEXTLIST" interface
This means that custom PHP scripts written by IPCheck 5 users now work with PRTG 7
Also, the Windows Mobile User Interface of IPCheck Server Monitor will now work with PRTG 7
This feature is provided for easier upgrades only and should be considered deprecated (it will not be developed further)
See this blog entry for screenshots and more
New: Sensors, devices and groups can now be paused for 5/15/60/180 minutes or one day (e.g. for maintenance or a reboot). Choose "Resume" to start monitoring before the scheduled pause is over.
New: Improved wording for Notifications (e.g. the subject now shows "UP" instead of "Downstate Ended")
New: Added a less sensitive default setting for the unusual detection
New: Graphs now display the primary channel's minimum and maximum values
New: Live graphs show a red dot for failed requests
New: Added sensor type "SNMP System Uptime" which monitors a SNMP device's uptime
New: Non-admin users are no longer able to see any system administration links and pages in the web-based UI
New: Improved handling of "read only" access rights for users throughout the interface (e.g. if a user does not have "write" access for a device he cannot go through the "Add Sensor" wizard anymore)
New: Added report template "List of Sensors (no graphs)"
New: Notifications can now be paused by schedules
New: For some sensor types (e.g. WMI Diskspace and WMI CPU) the user can now select what channel the warning/error levels are processed for (e.g. to define alarm levels for % free or GB free for disk sensors)
New: Namespace can now be selected for WMI Sensors
New: Reports can now be sent to multiple email addresses
New: HTTP sensors' user agent can be defined by the user (Registry Key: LocalMachinesoftwarePaesslerPRTG Network MonitorV7Serveruseragent)
New: "Sensors by state" counters for groups and devices are now fully-functional links (e.g. top left corner of PRTG's web interface)
New: Added several demo scripts for "Custom EXE" and "Custom WMI" sensors
New: Text messages from Custom EXE sensors are now shown in the web interface
New: "Add Autodiscovery Group" links show the Automatic Network Discovery feature more prominently
New: Added a "XL" view to the sensor tree (shows each sensor in a line of its own)
New: Updated Manual
Changed: Removed Root Group's default notification for new installations
Changed: We had to remove the AIM notifications (PRTG cannot create a connection with their servers)
Changed: User can enter < and > in bodies of notification emails (e.g. to enter XML)
Bugfix: Some Internet protocol sensors (SMTP, IMAP, POP3, FTP) would run into a frozen state
Bugfix: User could not create OIDLIB-based sensors
Bugfix: Weekly reports were sent 1 day too early
Bugfix: Email footer setting in system setup did not work
Bugfix: Maps were broken as soon as a referenced object was deleted
Bugfix: Map refresh did not work correctly on URL /mapshow.htm
Bugfix: Some reports showed empty graphs
Bugfix: In some situations the live graph only showed very few data points
Bugfix: Latencies did not always work correctly for State Triggers
Bugfix: Many small bug fixes and enhancements