Release Notes for the
"Preview" Release Channel

Software versions in this channel are updated about once a week. Please consider these versions as "beta". They have been thoroughly tested in our labs, but there may still be limitations in certain monitoring configurations. Please do not use this version on live systems on which you have to rely on!

Please use the "Auto-Update" feature to update your PRTG installation with the latest preview version: In the PRTG web interface, navigate to Setup | Auto Update.

 

Manual: Using the "Software Auto-Update" Function of PRTG

Other Release Channels


calendar

October 10th 2019 – Version 19.4.53.1869


New

Sensors


SNMP Fujitsu System Health v2

The new SNMP Fujitsu System Health v2 BETA sensor monitors the status of a Fujitsu PRIMERGY server via iRMC. It might also work with the Fujitsu product lines PRIMEQUEST, ETERNUS, and CELSIUS if they have iRMC available. The sensor shows useful metrics for CPU usage, fans, memory modules, battery, and power supply of your Fujitsu servers. We are looking forward to hearing your feedback about this new beta sensor! Please send your feedback to [email protected].

Note: The new SNMP Fujitsu System Health v2 sensor replaces the original SNMP Fujitsu System Health BETA sensor and addresses the feedback we received from you about this sensor type. Please note that any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later. You need to add the new version of the sensor to continue monitoring your Fujitsu servers. To keep historic data, you can pause existing instances of deprecated sensors.

Improved

Security


Login

We improved the security of the password recovery function on the PRTG login page. PRTG will not provide any information about user accounts anymore when you request a new password.

Sensors

We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to benefit from the latest security fixes for Npcap.

Note: Under certain circumstances, the step to install Npcap during the PRTG update is interrupted and Windows shows the error message A LWF & WFP driver installation tool has stopped working. In this case, please manually stop npcapoem.exe (for example, via the Windows Task Manager) to continue the PRTG update process.

Fixed

Server


Active Directory

PRTG automatically clears the cache for Active Directory integration again. In previous versions, the hourly clearing of the cache did not work so old passwords still worked after changing them until you logged in with the new password or manually cleared the cache.

Cloning

Clones of flow sensors (NetFlow, IPFIX, jFlow, sFlow) are now able to automatically receive data after you have resumed them. If you clone a flow sensor to the same probe, the clone will keep the IP selection as defined in the sensor settings to receive flow packets. If you clone a flow sensor to a different probe, the clone will receive flow packets on all available IP addresses of the probe by default.

Dependencies

You can save settings again even if PRTG detects an invalid Dependency Type on the same page, for example, if a sensor is not existing anymore that was selected as dependency type for the current object. In previous versions, you were not able to save the settings in this case—even if you just renamed the object—because data validation failed and you received the message Error (Bad Request) when saving.

Device Tree

We fixed an issue where the PRTG core server was not able to load the device tree anymore. This happened in rare cases if there were inconsistent or pending internal tree states.

Logging

We fixed an issue where PRTG did not correctly recognize the size of log files in corner cases. The issue could result in a steadily increasing log file size instead of making a copy and recreating the file, so that log files could still become very large in such cases.

Notification Triggers

We improved the performance of the Notification Triggers tab. Actions like adding or removing notification triggers provide feedback considerably faster than in the previous PRTG versions 19.3.51 and 19.3.52.

PRTG Status

The PRTG Status page shows the correct value for StateObjects again.

Scanning Interval

Objects now show the selected scanning interval even if you have deleted this interval from the Monitoring settings.

Shutdown

We improved the shutdown process of the PRTG core server. In certain cases, ending the dependency thread took very long. This could result in a failing automatic restart because the check for successful termination of the PRTG server service could not be performed in such cases.

Fixed

WebGUI


Maps

The map object Device Tree (S) now shows the correct color for the status Down (Acknowledged), just like all other device tree map objects.

Tables

We improved the layout of data tables on sensor overview pages by making the alignment of columns more consistent. The Channel column is always left-aligned as before, all other columns are now right-aligned.

Improved

Various


All Parts of PRTG

Various other minor fixes and improvements to all parts of PRTG, updated user manual

Note

Sensors


Python Script Advanced

PRTG version 20.1.55 that we will publish in January 2020 will include a new Python distribution because of the end-of-life announcement for Python 3.4. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.7 when you update to PRTG 20.1.55. You only need to consider the change if you are using the Python Script Advanced sensor. PRTG will also create a ToDo ticket with further information for you in this case.

Note

Clients


Enterprise Console

We do not officially support the Enterprise Console with PRTG version 19.4.53 or later anymore. Please note that your Enterprise Console may stop working in upcoming versions without further notice due to changes to the PRTG server. Please use PRTG Desktop as successor of the Enterprise Console.

calendar

September 30th 2019 – Version 19.3.52.3497


Fixed

Server


Data

We fixed an issue where values of primary sensor channels with negative channel ID were not displayed in some data tables, for example, the Traffic Total channel of SNMP Traffic sensors (channel ID -1). The value of this channel was missing in headers of historic data reports and as Last Value in Cluster Node tables, for example, when set as primary channel in the last PRTG version.

PRTG Core Server

We removed an unnecessary readlock on the PRTG server that could lead to a deadlock with an unintended PRTG server restart in rare cases. Another readlock we fixed was caused by calculations of the Sensor Factory sensor and could prevent the PRTG server to restart.

Logs

The Sensor Factory sensor writes less log messages than in the previous PRTG preview version and behaves as before again. Two lines of INFO logs for each sensor scan was a bit too much and unnecessarily filled up the PRTG core server log depending on your Sensor Factory sensor usage scenario.

calendar

September 13th 2019 – Version 19.3.52.3478


Blog article

All You Need to Know About PRTG Release 19.3.51 and 19.4.52

The PRTG release version 19.4.52 has been available for installation in the stable channel for a few days now. Maybe you already have the version in use, or you are planning the update. As regular...
Read the complete blog post here



New

Sensors


WMI Battery

The new WMI Battery BETA sensor monitors status and available capacity of batteries that are connected to Windows devices. Additional channels of this new sensor type show voltage, time estimations until the battery is full or empty depending on the status charging or discharging, and an overall battery health value.

The sensor makes it possible for you to see the level of batteries in your IT infrastructure at a glance. PRTG alerts you as soon as a battery threshold is breached. You can even generate reports to get to know how much time laptops spend charging, for example.

Please note that the sensor is in beta status and only works if the required WMI battery classes are available on the monitored device. We welcome any feedback about the sensor and what you are trying to monitor. Please send your feedback to [email protected], thank you!

Improved

WebGUI


Device Icons

We added new device icons for several vendors. PRTG will automatically add suitable icons to devices detected via auto-discovery if possible. Of course, you can also manually select any device icon in the device settings, section Additional Device Information. The new set includes icons for the following vendors.
  • Juniper
  • Barracuda
  • Fortinet
  • PaloAlto
  • Kentix
  • Watchguard
  • Oracle
  • Westermo
  • Sophos
  • MikroTik
  • Qnap
  • Cybernetics
  • Brocade
  • Axis Cameras
  • Nimble Storage
  • Checkpoint (Firewalls)
  • Ruckus
  • Kemp
  • Aruba
  • Sonoff
  • Adtran

Improved

Sensors


SNMP Dell PowerEdge Physical Disk

Newly added SNMP Dell PowerEdge Physical Disk sensors now include the enclosure ID in the sensor name if available. For example, a sensor name can be Physical Disk 1:0:0:16, where the first of four numbers is the enclosure ID (here: 1). If there is no enclosure ID available, there will be three numbers in the sensor name, for example, Physical Disk 0:0:16. This improvement will help you to easier find the disk you are looking for in PRTG.

Fixed

Security


PRTG Core Server

We fixed potential reflected XSS vulnerabilities with medium severity on the PRTG core server. The potential vulnerabilities affected tag filters, object IDs, and the contact support/feedback page. Please note that the fixed vulnerabilities required a logged in PRTG user account to be exploited.

Sensors

We fixed a potential Denial of Service (DoS) vulnerability of the HTTP Full Web Page sensor. Please note that the fixed vulnerability required a logged in PRTG user account with elevated rights to be exploited. (CVE-2019-11074)

Fixed

Sensors


Event Log (Windows API)

You can filter for more than two event IDs with the Event Log (Windows API) sensor again. In the previous version, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of more than 2 IDs.

Exchange (PowerShell) sensors

Exchange (PowerShell) sensors now correctly close the runspace. In previous versions, Exchange (PowerShell) sensors sometimes showed a down status with the error message Fail to create a runspace because you have exceeded the maximum number of connections allowed. The fix applies to all Exchange (PowerShell) sensor types, Exchange Backup (PowerShell), Exchange Database (PowerShell), Exchange Database DAG (PowerShell), Exchange Mail Queue (PowerShell), Exchange Mailbox (PowerShell), Exchange Public Folder (PowerShell).

EXE/Script sensors

EXE/Script and EXE/Script Advanced sensors again support the special characters round brackets "()", dot ".", and comma "," in the Parameters field. This allows you to pass arrays from the sensor to the script.

Sensor Factory

We fixed an issue where, in rare cases, modifying the spike filter in combination with Sensor Factory sensors caused issues with the PRTG core server, resulting in gray sensors, for example.

SNMP Cisco System Health

  • 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.

Fixed

Notifications


Notification Delivery

We removed the Test SMTP Settings button in the Notification Delivery settings on PRTG instances that are hosted by Paessler. As PRTG hosted by Paessler customer, you use the email infrastructure of Paessler so that testing the SMTP delivery settings is not necessary for you.

Notification Templates

PRTG user accounts with read/write rights and write or full access rights to a notification template can now change the user group as the recipient of an email, push, or SMS notification.

Logged in read/write users can see and select all user groups they are member of, as well the currently selected user group in the Send to User Group field of a notification template. In the Send to User field, read/write users can see and select all user accounts from all user groups they are a member of, as well as the currently selected user account.

SMS Notifications

  • 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.

Fixed

Reports


PDF Layout

We fixed an issue with PDF reports that erratically caused big gray boxes in generated reports.

PDF Stability

We implemented stability improvements for PDF reports with many sensors, especially regarding timeouts with the error message Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome.

Fixed

Libraries


Node Types

Libraries again only show a subtree if you select Show a subtree of the device tree in the library as Node Type for a library node. In previous versions, library nodes additionally showed an unordered list of sensors included in the subtree.

Usability

The buttons to collapse and expand library nodes are now also available in the smallest view (S).

Fixed

Server


Data

We fixed an issue where values of primary sensor channels with negative channel ID were not displayed in some data tables, for example, the Traffic Total channel of SNMP Traffic sensors (channel ID -1). The value of this channel was missing in headers of historic data reports and as Last Value in Cluster Node tables, for example, when set as primary channel in the last PRTG version.

Logging

  • 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.

Fixed

WebGUI


Dependencies

It is not possible anymore to configure a sensor to be its own dependency. Having a sensor as its own dependency resulted in a situation where a sensor endlessly paused itself when it switched to a down status without the possibility to resume the sensor.

Gauges

The gauge of a sensor's primary channel now always shows the unit for the minimum value. In previous version, the unit for the minimum value was missing if the minimum was 0 and the channel had a custom unit.

Multi-Edit

You can now acknowledge one or more down states on the Alarms tab of probes using the multi-edit menu, as well as open the settings of one or more probes.

Tables

We fixed some layout issues of meta-scan tables in sensor settings so that especially large tables are displayed in a better way.

Firefox

Opening the context menu in the PRTG web interface via right-click now even works if you use Firefox on macOS.

Internet Explorer 11

We fixed some more layout issues that occurred when accessing the PRTG web interface with Internet Explorer 11. For example, the Save button was cut off on some pages, the Hide and Show buttons for master dependencies in the dependencies graph were missing, and tickets sometimes occupied more space than given to them.

Changed

Server


Probes

Connecting remote probes now automatically downgrade to the correct version if the PRTG core server runs an older version than the probe.

Tags

It is not possible anymore to add the same tag to one object in PRTG more than once.

User Accounts

It is not possible anymore to create user accounts with a login name that includes the special characters " / \ [ ] : ; | = , + * ? > <

Note: User accounts that already existed before the update to PRTG 19.3.51 and have a login name that includes one of the outlined special characters will still be able to login after the installation of version 19.3.51. However, affected user accounts will not be able to change and save their account settings without changing the login name.

Improved

Various


All Parts of PRTG

Various other fixes and improvements to all parts of PRTG, updated user manual, updated German and Japanese language files

Note

Sensors


SNMP Fujitsu System Health

The upcoming PRTG version 19.4.53 will include a new, significantly improved SNMP Fujitsu System Health sensor. We already inform you now about the change because any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later and need to be added anew.

Note

Outdated Windows Versions


Outdated Windows Versions

It is not possible anymore to install PRTG on the outdated operating system Windows XP. This is a side-effect of changing the PRTG license check to a 64-bit binary. Please make sure you install PRTG on an officially supported operating system.

Note

Known Issues


Summarized Notifications

In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information.

Status: resolved with PRTG 19.4.52.3515

calendar

July 31st 2019 – Version 19.3.51.2722


Fixed

User Rights


Access Rights

User accounts with restricted access rights to the device tree cannot see groups and devices anymore they are not allowed to. In the last 19.x.51 preview versions there was an issue concerning access rights.

calendar

July 24th 2019 – Version 19.3.51.2712


Important

Known Issue


Access Rights

The current preview version 19.3.51.2712 comes with an issue that affects access rights. User accounts with restricted access rights to the device tree can see groups and devices they are not allowed to. The sensor level is not affected by the issue.

Status: Resolved with PRTG 19.3.51.2722

Improved

Languages


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


WMI Free Disk Space (Multi Disk)

The WMI Free Disk Space (Multi Disk) sensor will not create channels for drives without values for free space and bytes anymore. In previous PRTG 19.2.51 preview versions, the sensor erroneously created a channel for the A:\ drive, for example, when selecting All disks during sensor creation (including sensors created by auto-discovery). This resulted in newly added WMI Free Disk Space (Multi Disk) sensors that did not recover from the unknown status.

Fixed

Server


Cluster

  • Cloning devices to the cluster probe works properly again. In previous PRTG 19.2.51 preview versions, cloning took too long and sensors on the device clone did not receive data in certain cases.
  • Known issue: 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. We are currently investigating the issue. Manually restarting the failover node to trigger a new sync may improve the situation if you encounter issues.

Devices

Overview tabs of devices show data tables and sensor gauges again even if newly added sensors have not yet received data. In previous PRTG 19.2.51 preview versions, sensors were only shown on the tab when the newly added sensors had received data at least once.

Device Tree

PRTG will completely show the device tree again after expanding and collapsing parts of it. In the previous PRTG 19.2.51 preview versions, parts of the tree just vanished in this case until a page reload. This was already partially fixed in preview version 19.2.51.2561.

Memory

We fixed several minor and one bigger memory leaks on the PRTG core server that occurred in previous PRTG 19.2.51 preview versions.

Notifications

  • We fixed an issue with notifications for sensors without a primary channel. In previous PRTG 19.2.51 preview versions, this resulted in access violations when generating the notification.
  • Deleting Notification Triggers and Notification Contacts works again. In previous PRTG 19.2.51 preview versions, this resulted in an error.

Probes

  • We improved the stability of remote probe connections to the PRTG server. In certain 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.
  • 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.

Raw Data Buffer

We fixed an issue that resulted in a full Raw Data Buffer (see the according channel of the Core Health sensor) in certain scenarios with the previous PRTG version 19.2.50. This could happen, for example, when having many remote probes connected. The issue also caused a loss of monitoring data with many sensors in unknown status.

Sensors

We fixed an issue that caused access violations on the PRTG server in previous PRTG 19.2.51 preview versions when there were running sensors without a primary channel.

User Rights

PRTG user accounts with restricted access rights can see the number of sensors by status on the welcome page again, as well as the global sensor status bar, of course only for sensors they have access to. In previous PRTG 19.2.51 preview versions, the numbers were not visible for read/write users, for example.

calendar

June 26th 2019 – Version 19.2.51.2561


Fixed

Sensors


DHCP

The DHCP sensor works again. It showed a down status with an access violation in the sensor message in the previous preview version.

SNMP Library

You can add SNMP Library sensors again. This did not properly work in the previous preview version.

Fixed

Server


Dependencies

Dependencies properly work again with devices created via auto-discovery. Paused by dependency did not work for such devices when the master dependency was down in the previous preview version.

Device Tree

PRTG will completely show the device tree again after expanding and collapsing parts of it. In the previous preview version, parts of the tree just vanished in this case until a page reload.

Sensors

Sensors always have data tables again. In the previous preview version, data tables were not rendered in certain cases. This also lead to failing API calls when requesting data from running sensors.

calendar

June 17th 2019 – Version 19.2.51.2533


Improved

Sensors


Active Directory Replication Errors

The Active Directory Replication Errors sensor now supports different Active Directory naming contexts. When you add the sensor, you can now choose between Configuration (default), Schema, DomainDnsZones, Domain, and ForestDnsZones as Naming Context to check your Windows Domain Controller for replication errors. In previous versions, the sensor always used Configuration as naming context.

Improved

Notifications


Notification Delivery

PRTG will now provide clearer communication in logs and tickets when an SMS notification fails due to a missing definition for an SMS provider in the Notification Delivery settings.

Notification Triggers

You can now directly create a new Notification Template while editing or defining a Notification Trigger without leaving the notification trigger tab. Click the plus symbol (+) in the dropdown list of a trigger to create a new notification template for the notification trigger.

Improved

Server


Active Directory

We improved the login process for Active Directory (AD) users by explicitly requesting read-only access.

Device Templates

If you create a new device template, you now only need to define a name for the template. You do not have to provide a file name anymore, PRTG will automatically create the corresponding template file with the extension .odt.

PRTG Core Server

Performance and memory footprint improvements for the PRTG core server, as well as several other improvements and fixes

Reporter

We added enhanced logging to the new reporter engine to be able to better help you in case of issues when generating reports.

Improved

Security


Maps

We fixed a potential XSS vulnerability in the context of maps. Thanks to Dmitry Galecha from Positive Technologies for reporting the issue.

Notifications

Passwords of Execute Program notifications, webhooks for Slack and Microsoft Teams notifications, as well as the AWS Secret Access Key of Amazon SNS notifications are now masked on the History tab of according notification templates in the PRTG web interface. Notification templates are only accessible for PRTG administrator users and read/write users with access rights for a particular notification template.

We found the issue in internal tests, it was not public before. If your PRTG installation is affected, you will receive a Todo ticket in PRTG. Please follow the instructions there.

Sensors

Passwords of the following sensor types are now also masked in log files when you enable the debug option: FTP Server File Count, HTTP XML/REST Value, SIP Options Ping, Citrix XenServer Host, Citrix XenServer Virtual Machine, IPMI System Health

Improved

Language Files


Language Files

Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG.

Fixed

Sensors


Event Log (Windows API)

You can filter for two event IDs with the Event Log (Windows API) sensor again. In previous versions, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of IDs.

Note: With this version, it is not possible to filter for more than two event IDs. We plan to fully support filtering for multiple IDs again for the next PRTG version 19.3.52.

EXE-based Sensors

Sensors that require .NET version 4.7.2 now actually show the required version number 4.7.2 in the error message if the .NET framework version 4.7.2 is not available on the probe system. The full error message is This sensor requires the .NET Framework version 4.7.2 (code: PE104)

For more details, please see this Knowledge Base article.

Flow Sensors

It is possible again to clone flow sensors and devices on which flow sensors are running (for example, NetFlow sensors). In previous PRTG versions, you received Error (Not Found) when cloning flow sensors.

Note: To receive data with a flow sensor clone, please open the Settings tab of the sensor and click Save.

SNMP Traffic

  • 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: resolved with PRTG 19.3.52.3502

Reports

Big reports with thousands of sensors occasionally time out and are not successfully created. The message in this case is Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome

Status: resolved with PRTG 19.3.52.3502

Spike Filter

In the current version, the spike filter only applies to graphs and tables for live data and 2 days (Graph 1 in graph settings). It is not possible with PRTG 19.3.51 to remove spikes from graphs and tables for 30 days (Graph 2), 365 days (Graph 3), and historic data reports.

Please note that this is a display issue, monitoring data is not affected. As soon as you update to a fixed version, all historic data will be correctly displayed again, respecting optionally set spike filters.

Status: resolved with PRTG 19.3.52.3502

Summarized Notifications

In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information.

Status: resolved with PRTG 19.4.52.3515

Note

PRTG 19.3.51.2725


PRTG 19.3.51.2725

Please note that we took PRTG version 19.3.51.2725 (released on July 31) offline on August 5 as a precaution because some customers reported serious issues after the update to this version. Affected customers reported 100% CPU load and many sensors in gray Unknown status due to a full graph cache recalculation that PRTG must do from time to time.

We found the reason for the misbehavior and were able to resolve the issue. PRTG 19.3.51.2830 includes a fix for this, as well as three other fixes compared to 19.3.51.2725. If you are running the withdrawn version 19.3.51.2725, please update as soon as possible.

Active Directory Replication Errors Sensor

The Active Directory Replication Errors sensor now uses the naming context Configuration as default. This is also the naming context that the sensor used in previous version. With the support of different naming contexts introduced in PRTG 19.3.51.2725, the default was Domain, which, in certain cases, resulted in sensors of this type that did not find the replication neighbor anymore after the update.

Auto-Discovery Groups

Adding an auto-discovery group or editing the settings works properly again. In PRTG 19.3.51.2725, several IP selection methods caused an access violation when saving the settings.

Updating

We fixed an issue where, in rare cases, updating from older PRTG versions like, for example, 17.3.33, failed because of the tree version update in combination with certain history entries in the PRTG configuration file.

calendar

May 13th 2019 – Version 19.2.50.2838


Fixed

Server


Cluster

We improved the stability of PRTG when adding remote probes to failover nodes in a cluster. In previous PRTG 19.2.50 preview versions, this action could cause several access violations.

PRTG Core Server

We improved the stability of PRTG core server restarts. In previous PRTG 19.2.50 preview versions, this action could cause several access violations in certain cases because running threads from the previous PRTG process were not properly stopped.

Fixed

Sensors


DHCP

We fixed an issue with the DHCP sensor that appeared in previous 19.2.50 preview versions of PRTG due to the activation of the Npcap Loopback Adapter (Packet Sniffer sensors use the Npcap library as of this version). In certain cases, the sensor showed a timeout error after updating to PRTG preview version 19.2.50 although there was a valid DHCP available.

It is now also possible to monitor multiple DHCP servers in different networks. The DHCP sensor will send the data packets only via the selected NIC to monitor the DHCP server. If there is no DHCP server available in the specified network, for example, if the NIC has a link-local address, the sensor will time out as expected.

calendar

April 30th 2019 – Version 19.2.50.2807


Fixed

Server


Cluster

  • Cluster probe connection settings like access keys, allow IPs, deny IPs, and deny GIDs are synchronized to the failover node again when you change them. This did not work in the previous preview version 19.2.50.2778.
  • We improved the stability of cluster connections.

License

Activating and deactivating a license in offline installations works again. In the previous preview version 19.2.50.2778, clicking according buttons did not take effect due to an access violation.

PRTG Core Server

We fixed an issue with the message handler of the PRTG core server that could result in access violations.

Fixed

Sensors


Windows IIS Application

We changed the name of the new sensor channel that we introduced in PRTG 19.2.50 to Uptime (because it did not really show system uptime). The new channel Status has now its own lookup file with the states Running and Stopped.

calendar

April 24th 2019 – Version 19.2.50.2778


Blog article

PRTG Release 19.2.50: Measure MQTT Roundtrips with PRTG and Other News about the Release

The PRTG release version 19.2.50 has been available for installation in the stable channel for several days now. Maybe you already have the version in use, or you are planning the update. As...
Read the complete blog post here



New

Sensors


MQTT Round Trip

This PRTG version comes with the new MQTT Round Trip sensor! You can now monitor the availability of an MQTT broker to ensure your IoT devices can deliver their data at all times. Use the MQTT Round Trip sensor to check if a connection to the broker can be established, if the broker accepts messages via publish, if the broker forwards a message to a matching subscriber, and measure either the connection times or the round trip time from publishing a message until receiving it back on a subscribed topic.

The sensor shows the message round trip time, the round trip status, the publisher connection time, and the subscriber connection time in different sensor channels. Keep a close eye on your IoT infrastructure - with PRTG and the new MQTT Round Trip sensor!

Improved

Sensors


DHCP

You can now monitor multiple DHCP servers in different networks. The DHCP sensor will send the data packets only via the selected NIC to monitor the DHCP server. If there is no DHCP server available in the specified network, for example, if the NIC has a link-local address, the sensor will time out as expected.

FTP Server File Count

The FTP Server File Count sensor now supports TLS 1.2 connections.

Oracle SQL

We updated the Oracle library that Oracle SQL v2 and Oracle Tablespace sensors use to monitor your Oracle databases. We have seen that both sensor types cause less CPU load on the PRTG probe system compared to previous versions when using the updated library.

VMware Host Hardware Status (SOAP)

You can now define Known Warnings and Known Errors in the settings of the VMware Host Hardware Status (SOAP) sensor that include angle brackets (<>) to ignore messages that include such characters.

VMware Host Performance and VMware Virtual Machine (SOAP)

The sensor types VMware Host Performance (SOAP) and VMware Virtual Machine (SOAP) can now inherit the Channel Unit Configuration settings from the parent device. Please note that this still is not possible for certain units like bandwidth, for example.

Windows IIS Application

We added two new channels to the Windows IIS Application sensor. The channels show status and system uptime of a monitored web service. If the web service is not available, the sensor will show a down status.

Improved

Notifications


Amazon SNS Notifications

The Location setting of the notification method Send Amazon Simple Notification Service Message now shows all available SNS locations in a dropdown list instead of a bullet list for a better usage of the available space.

Execute Program

Notifications that execute programs now show a meaningful message in notification related logs instead of an access violation if the defined credentials are incorrect.

Notification Templates

On the Notification Templates tab in your account settings, you can now directly test an existing template, pause or resume it, and open a list of objects that use the template. The functionalities are accessible in the notification templates table without the need of using the multi-edit menu.

Notification Triggers

Notification templates that you select for a notification trigger now show the actions they perform with an according icon in the dropdown before the template name.

SMS Notifications

  • Ampersands (&) are now correctly URL-encoded (%26) in SMS notifications even if you use a custom URL for SMS delivery. In previous versions, the encoding was missing in this case so that the notification messages were truncated to everything before the ampersand.
  • PRTG will now create a meaningful ticket if sending an SMS notification fails due to connection issues.

Improved

WebGUI


Multi-Edit

  • You can now acknowledge one or more down states on the Alarms tab of the root group, of a group, and of a device using the multi-edit menu.
  • We improved the usage of the available space when editing multiple tickets at once.

Reports

We changed the rendering engine for PDF reports. PRTG now uses Chromium instead of the deprecated PhantomJS to be able to generate PDF reports in a more reliable way. Screenshots that you generate for the support bundle also use Chromium now.

Known issue: Please ensure port 9222 is not blocked on the PRTG core server system to generate PDF reports and screenshots. This only affects PRTG version 19.2.50.

Tags

Clicking a tag in the settings of a Notification Template or Map now opens a list with all accordingly tagged objects.

Improved

Server


Cluster

We slightly improved the cluster performance.

Probe Connections

We slightly improved the performance of probe connections by introducing a threadpool instead of using two dedicated threads for each probe. You will especially notice the improvement if you have many remote probes connected.

Changed

Sensors


Packet Sniffer

Packet Sniffer and Packet Sniffer (Custom) sensors now use the Npcap library instead of the deprecated WinPcap to monitor your traffic.

Note: If you need to downgrade from PRTG 19.2.50 or later to a PRTG version 19.2.49 or previous for some reason, please first stop the PRTG services and manually uninstall Npcap before you install an older PRTG version.

Loopback Adapter

PRTG now installs a loopback adapter as part of the Npcap library for Packet Sniffer sensors.

Note: If your remote probe runs additional services, for example a DHCP server, this adapter might have an effect on these services. If you experience issues, we recommend that you disable the adapter. This will not affect PRTG.

Changed

WebGUI


Device Icons

We replaced the previous SVG device icons with new TinySVG 1.2 compliant icons.

Fixed

Sensors


Cisco IP SLA

PRTG will not create an instance of the Cisco IP SLA sensor for an OID anymore if the target device does not return values for this OID. In such cases, the Cisco IP SLA sensor immediately showed a down status with the message No such object (SNMP error # 222) after sensor creation in previous versions.

HTTP

The auto-discovery creates working HTTP sensors again even if the target device only runs on HTTP (ports 80, 8080). In previous versions (since PRTG 18.3.42), the auto-discovery only created properly working HTTP sensors for HTTPS devices (port 443).

HTTP Advanced

The HTTP Advanced sensor can monitor a website over a proxy server with basic access authentication (HTTP) now. In previous versions, it returned an error with the message Unauthorized (HTTP error # 401) when using a proxy.

IMAP

We improved the message filtering of the IMAP sensor. In previous versions, the IMAP sensor only recognized the content types text/html and text/plain if the attributes were written in lowercase. Depending on the configuration of your email server, they can be written in different casing, so that the sensor could not find matching messages. This will now work.

NetApp NIC

NetApp NIC BETA sensors that you add to a NetApp cDOT or ONTAP with a version earlier than 9.2 will not create the Healthy channel anymore. NetApp versions previous to 9.2 do not return according data so the Healthy channel just remained empty after sensor creation.

Sensor Factory

We fixed several issues with the Sensor Factory sensor. Reports and graphs now include all data without gaps that occurred in certain cases, and the error handling as well as the no data behavior realize your defined options more reliably.

SNMP Cisco System Health

PRTG again only creates one instance of an SNMP Cisco System Health sensor per selected item in the Add Sensor dialog. In browsers other than Chrome (for example, Firefox and Internet Explorer 11), each selected measurement of the SNMP System Health sensor was added twice in previous versions.

SNMP Custom Table

The column headers in the Table Specific settings in the Add Sensor dialog of the SNMP Custom Table sensor are now always aligned with their columns so you can easier identify which data belongs to which column. In previous versions, the column headers did not scroll sideways with the table content.

SNMP Windows Service

The table of Windows services in the Add Sensors dialog of the SNMP Windows Service sensor has now paging so you do not have to scroll down through all the services anymore.

WMI Microsoft SQL Server

We removed the obsolete setting SQL Server Version from the sensor types WMI Microsoft SQL Server 2017, WMI Microsoft SQL Server 2016, WMI Microsoft SQL Server 2014, WMI Microsoft SQL Server 2012, WMI Microsoft SQL Server 2008, WMI Microsoft SQL Server 2005.

Fixed

Server


Images

We fixed an issue with images in PRTG that were not correctly loaded (for example, graphs in reports) when the port to publish PRTG via NAT or on a load balancer did not match the port of the web server.

Search

We fixed an access violation that appeared in certain cases on the PRTG core server and resulted in a malfunctioning PRTG search, not returning any search results.

Fixed

WebGUI


Dark Theme

  • Data graphs in HTML email notifications will now always appear in light theme style, even if you use the dark theme of the PRTG web interface. The same applies to graphs in reports that you generate via the historic data tab of a sensor. In previous versions, graphs in emails and historic data appeared dark when using the dark theme.
  • Dialog windows and context menus are now better distinguishable from the background when using the dark theme.

Dropdown Menus

Entries in dropdown menus are better readable again. In previous versions, some dropdown menus like, for example, the report templates list appeared with blurred section headings in Google Chrome.

Graphs

Zoomed graphs automatically refresh their data again, as well as the according page footer shows up again. You can open a zoomed graph via the button Zoom graph in new window on several pages in the PRTG web interface.

Maintenance Window

If a sensor, device, group, or probe has the inheritance of the Schedules, Dependencies, and Maintenance Window setting enabled, PRTG will not validate the values (for example, start and end time of the maintenance window) anymore when you click Save. In case of enabled inheritance, the settings on this device tree level are inactive anyway. The previous behavior resulted in unnecessary error messages in certain cases.

Mobile Android Probe

We removed the last remaining links from the PRTG web interface that lead to the download page of PRTG Mobile Probe for Android. The app is not official supported and was removed from the Google Play Store some months ago.

Multi-Edit

The multi-edit menu is always available now if you have selected at least one item in a list (for example, a list of devices, sensors, reports, maps, libraries). In previous versions, the menu disappeared after cancelling the delete dialog while one or more items were still selected.

Page Refresh

The pause and resume buttons for the automatic page refresh in the page footer now always show the correct status, indicating if a click will pause or resume the refresh countdown.

Quick Ranges

We improved the filtering with quick range buttons, for example, for logs. The filters now better correspond to what the buttons say.

Reports

Data table entries in reports with a downtime greater than 0% are highlighted in red color again. We also improved the layout of reports with very long names and report related pages.

Search

The item count selector on the detailed search page now shows the current number of shown results per page without hovering over the selector.

Smart Setup

If you skip single steps or the the whole introduction, the setup assistant on a new PRTG installation will keep your decision and does not show up unwanted anymore.

User Rights

Only PRTG user accounts with administrative rights can download remote probes now. Read/write users and read-only users do not have the option anymore to open the Remote Probe Installer tab under Setup | Downloads and Tools, nor have the permission to do so on other places in the PRTG web interface. Read-only rights for remote probe downloads also apply to failover nodes in a PRTG cluster.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements to all parts of PRTG, updated user manual

Note

Known Issue: Reports


Report Period in Chrome

In the current version, manually defining a date range (Period) with Start Date and End Date is not possible if you access the Report page with Google Chrome and your currently logged in PRTG user account uses the date format DD.MM.YYYY (24h or AM/PM). The date validation fails in this case.

Workaround: Because the issue only exists in Chrome, you can use another browser like Firefox, Internet Explorer 11, or Edge to manually define a report period.
Another option is to temporarily change the Date Format of your PRTG user account to MM/DD/YYYY or YYYY-MM-DD (24h or AM/PM). You can do so under Setup | Account Settings | My Account, section Web Interface.

calendar

March 14th 2019 – Version 19.1.49.1909


Fixed

Server


Dependencies

We fixed another issue with dependencies where pausing by dependency did not work as expected in certain cases. If a sensor is set as master dependency, the sensor shows a down status in case of an error again instead of a paused status as it sometimes happened in PRTG 19.1.48.

Down (Acknowledged)

PRTG shows the user account who acknowledged the down status of a sensor again. As usual, the name will appear in the message as well as in the log of a sensor in status Down (Acknowledged). In PRTG version 19.1.48, the name of the acknowledging user account was missing.

Unknown Status

We fixed an issue where the system time of PRTG probe and server ran out of synchronization, which could result in grey sensors (for example, Ping sensors) in PRTG 19.1.48.

You also might have noticed the issue if you use the WMI UTC Time sensor that showed a steadily increasing value in the Difference channel (time difference between PRTG system time and monitored device), which is also fixed with this new PRTG version.

Improved

Language Files


German

We updated the German language file.

calendar

March 7th 2019 – Version 19.1.49.1876


Blog article

PRTG Release 19.2.49 News Roundup – PRTG Desktop, .NET 4.7.2 and More…

For a few days now, the PRTG release 19.2.49 has been available for download on the stable release channel. The current release contains a lot of improvements, including improved performance of...
Read the complete blog post here



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.

For more information and a direct download link, see the PRTG Desktop app webpage.

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

Note

PRTG 19.1.49.1916


Memory Leak

Please note that we took PRTG version 19.1.49.1916 (released on March 19) offline on March 21. The PRTG core server included a memory leak in version 19.1.49.1916. Depending on your monitoring scenario, this could lead to critical memory consumption on your PRTG server.

The new PRTG version 19.1.49.1966 includes a fix for the memory leak. If you are running the withdrawn version 19.1.49.1916, please update as soon as possible.

calendar

February 7th 2019 – Version 19.1.48.2865


Fixed

Server


PRTG Core Server

We fixed an issue that occurred in the previous preview version when PRTG was accessing historic data. This could result in deadlock events, followed by restarts of the PRTG server.

Fixed

Probe and Sensors


Memory Leak

We fixed several minor memory leaks and a bigger one on the PRTG probe system. The memory leaks were caused by SNMP monitoring and resulted in steadily increasing memory usage on affected probe systems in the previous preview version.

Meta-Scan

The meta-scan of SNMP Windows Service and SNMP Fujitsu System Health BETA sensors works properly again. In the previous preview version, the sensors did not find all available services and counters on sensor creation.

calendar

January 31st 2019 – Version 19.1.48.2811


Fixed

Security


Login

We fixed a reflected XSS vulnerability on the login page of the PRTG web interface. Special thanks to Damian Schwyrz for reporting the issue!

Fixed

Server


Historic Data

The Sensor Status History section in HTML reports generated via a sensor's Historic Data function shows each entry only once again. In the last preview version, each status change erroneously appeared several times.

Probes

We fixed an issue with probe requests that were lost when the probe reconnected, which resulted in grey sensors (status unknown) on affected probes because they did not receive data.

We also fixed scan thread timeouts that occurred in the context of System Information, which could result in unwanted probe restarts.

PRTG Core Server

We fixed an issue that lead to an access violation when deleting a sensor from PRTG.

Fixed

WebGUI


Maps

Public maps that contain the Data Tables map object Alarms (gauges) work again. In the previous preview version, such maps constantly reloaded when accessed without login.

calendar

January 22nd 2019 – Version 19.1.48.2756


Important

Known Issues


SNMP HP BladeSystem Enclosure System Health

SNMP HP BladeSystem Enclosure System Health sensors will show an error with the message Duplicates not allowed after the update to PRTG version 19.1.48.2868 in certain cases. We recommend that you wait with the update of your PRTG installation until we publish a fix for the issue if you are using SNMP HP BladeSystem Enclosure System Health sensors.

Status: resolved with PRTG 19.1.48.2891

Sensor Graphs

After updating to PRTG version 19.1.48.2868, historic data graphs will not show data in a few cases. This happens due to an issue with the PRTG graph data cache recalculation. If you are affected, please don't panic, your data is not lost. We will provide a fix for the issue as soon as possible and your data will be shown again.

Status: resolved with PRTG 19.1.48.2876

SNMP Linux Disk Free

SNMP Linux Disk Free sensors will show an error with the message List index out of bounds (0) after the update to PRTG version 19.1.48.2868 when monitoring certain Linux distributions. Affected are, for example, Debian 6, Debian 7, CentOS 6, Mandriva Linux 7.2 Odyssey, Ubuntu 12.04. Please note that these are affected distributions from which we only know right now. We are currently working on a fix and recommend that you wait with the update of your PRTG installation until we publish it if you are using SNMP Linux Disk Free sensors.

Status: resolved with PRTG 19.1.48.2876

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.

Improved

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!).

Improved

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 Linux Disk Free

The SNMP Linux Disk Free sensor now creates channels for all disks on the target device. In previous versions, the sensor stopped searching for available disks during sensor creation as soon as there was a missing OID in the index table and so did not create channels for each disk on the target system.

SNMP Synology Logical Disk

The SNMP Synology Logical Disk sensor is now able to recognize when the order or name of a volume changes. In previous versions, it was possible that the sensor monitored an incorrect volume in such cases, which resulted in wrong monitoring data.

Windows Updates Status (PowerShell)

We fixed an issue with the Time since last update channel of the Windows Updates Status (PowerShell) sensor that still showed incorrect values in certain use cases after the improvements in the previous PRTG version 18.4.47.

Fixed

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.

Fixed

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.

Fixed

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.

Fixed

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

Fixed

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. For more details, please see this Knowledge Base article.

calendar

December 12th 2018 – Version 18.4.47.1961


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.

Fixed

Sensors


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.

calendar

November 30th 2018 – Version 18.4.47.1926


Improved

Languages


Language Files

Major update for all language files!

Fixed

Server


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.

Fixed

Sensors


Device Templates

The sensor requirements for the .NET framework are correctly checked again in the PRTG auto-discovery, as defined in the applied device template. In the last preview version, .NET sensors were always created, no matter if the .NET version on the probe system matched the required version.

Lookups

Lists of lookup files are sorted alphabetically again when you select value lookups for a sensor channel. IDs of lookups are also loaded case insensitively again to prevent issues when you override default lookups with customs lookups.

Sensor Factory

PRTG correctly calculates historic data of the Sensor Factory sensor again. In the last preview version, live data was used to calculate historic data instead of averages. This resulted in wrong values.

Fixed

WebGUI


Notification Triggers

This version includes some fixes for the appearance of the new notification template filter on the notification triggers tab that we introduced in the last PRTG preview version.

Fixed

Enterprise Console


Enterprise Console

The Enterprise Console loads and displays all pages again. In the last PRTG preview version, the Enterprise Console was not able to load several pages.

calendar

November 23rd 2018 – Version 18.4.47.1867


Important

Known Issue: PRTG Update


Updating from version 18.1.37 or older

Please note that direct updates from PRTG version 18.1.37 and previous versions to the current PRTG version 18.4.47 do not work. Please wait with an update of your PRTG instance if you are currently running 18.1.37 or an older version until we publish PRTG 19.1.48. This version will include a fix for the issue.

If you update from PRTG 18.1.37 or previous, the PRTG server will not be able to start. It will show an access violation in this case. If you are affected by the issue, please contact our technical support team.

Status: resolved with PRTG 19.1.48.2868

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.

Improved

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.

Improved

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.

Fixed

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.

Fixed

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.

Fixed

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

Fixed

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.

Fixed

Various


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

Note

Probe and Sensors


.NET Version

Please note that we will upgrade our system requirements for the .NET framework in upcoming versions. Sensors that require the .NET framework will need at least .NET version 4.7.2 on all computers running a probe in the next PRTG version 19.1.48 that we plan to release in the first quarter of 2019.

calendar

November 2nd 2018 – Version 18.4.46.1687


Fixed

WebGUI


Icons

We fixed an issue with icons that were not correctly loaded throughout the web interface in certain cases after installing the update to PRTG preview version 18.4.46.1638. The icons only were correctly loaded after clearing the browser cache.

Support Bundle

Screenshots in the support bundle are rendered and sent again. In the last PRTG preview version 18.4.46.1638, the screenshot function did not work.

Fixed

Server


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.

Fixed

Enterprise Console


Enterprise Console

The Enterprise Console loads and displays all pages again. In the last PRTG preview version 18.4.46.1638, the Enterprise Console was not able to load several pages.

calendar

October 25th 2018 – Version 18.4.46.1638


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

Note

Installer


Trial Installation

If you download a PRTG trial version from paessler.com and run the installer on a fresh machine, you will not have to manually enter trial key and license name anymore.

calendar

October 12th 2018 – Version 18.4.45.1882


Fixed

Sensors


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.

Fixed

WebGUI


Language

This version includes a substantial update of the German language file.

License Update

Updating license information in the PRTG web interface works fine again. In the last preview version, a saving window appeared and did not automatically disappear when updating the license.

Reports

When saving a new report, the Select Sensors Manually tab will automatically open again so that you are able to immediately add sensors to the report. In the last preview version, you mistakenly landed on the Run Now tab after saving.

calendar

September 28th 2018 – Version 18.3.45.1847


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.

calendar

September 20th 2018 – Version 18.3.44.2053


Fixed

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.

Fixed

Web Server


Web Server Starter

We fixed a timing issue that resulted in failing automatic starts of the web server in certain cases.

Port Fallback

We fixed an issue with the URL of the PRTG web interface. The URL was incorrect in case of forwarding to an SSL fallback port.

calendar

September 13th 2018 – Version 18.3.44.2043


Fixed

Various


Various

Minor PRTG internal improvements

calendar

September 11th 2018 – Version 18.3.44.2037


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.

Maps

We fixed an issue with the Map Designer that affected the previous preview version 18.3.44.1971. Object names appeared as "not found" in the Map Designer when moving an object from the device tree on the left onto the map and replacing it with a status icon from the right.

Fixed

Server


Auto-Discovery

We fixed some internal errors that occurred during auto-discovery in certain cases.

Logging

We fixed an issue with the new logging framework. The issue prevented PRTG from writing web server logs in certain cases.

calendar

August 31st 2018 – Version 18.3.44.1971


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

A report can be run another time when changing Run Report settings without reloading the page.

User Group Settings

Improved performance for loading Active Directory groups on the setting pages of PRTG user groups

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 on 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.

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

Fixed

Sensors


Exchange (Powershell) Sensors

Stability improvements for Exchange (Powershell) sensors

NetApp NIC

The NetApp NIC BETA sensor now shows correct traffic values.

NetFlow v9

NetFlow v9 sensors now correctly handle IPv6 flows instead of just showing 0.0.0.0 for IP addresses.

Sensor Factory

  • 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


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.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files

calendar

August 13th 2018 – Version 18.3.43.2312


Fixed

Various


WebGUI

In the last preview version, context menus did not properly work in some cases. We fixed this.

Logging

Some fixes for the new logging framework

calendar

August 7th 2018 – Version 18.3.43.2298


Fixed

Various


Enterprise Console

Starting a standalone Enterprise Console works again. In the last preview version of PRTG, the Enterprise Console only could be started on the PRTG server itself.

Languages

We updated the language files for German and Dutch.

calendar

July 31st 2018 – Version 18.3.43.2263


Blog article

PRTG Version 18.3.43 Released with a New IoT Sensor, Simplified Notifications and a Faster Manual

Do you remember the previous stable release? In version 18.3.42 there was a lot to discover. But time does not stand still, and we can already look at the innovations of version 18.3.43 - while we...
Read the complete blog post here



Important

Known Issue: NetFlow


NetFlow Sensors

In certain configurations, NetFlow sensors do not properly work with the current PRTG versions 18.3.43.2317 and 18.3.43.2323. If an installation is affected, the sensor types NetFlow V5, NetFlow V5 (Custom), NetFlow V9, and NetFlow V9 (Custom) do not receive data anymore after you have updated to the current PRTG version. They will turn gray and show the message "No data received since x minutes." in this case.

The issue does not affect every configuration, but we strongly recommend that you do not install the update if you use NetFlow sensors. We are currently working on a fix with high priority. Please bear with us!

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.

Improved

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.

Improved

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 (invalidated CVE-2018-17887).

Search

We improved the search speed in the manual that is delivered with your PRTG installation.

Improved

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.

Fixed

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

Fixed

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.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files

Note

Outdated Windows Versions


Windows Server 2003 R2 and Older

PRTG does not start and run on outdated Windows versions like Windows Server 2003 R2 anymore as of the current PRTG versions 18.3.43.2317 and 18.3.43.2323. Please make sure you install PRTG on an officially supported operating system!

calendar

July 31st 2018 – Version 18.3.43.2263


Blog article

PRTG Release 18.3.42 Is about Notifications, SQL Server 2017 and Shiny Map Objects

I'm sure most of you are already using our PRTG release 18.2.41. Have you tried the donuts?
Read the complete blog post here



Fixed

WebGUI


Maps

We fixed some issues with maps.

  • The map object "Name and status (sizeable, status-related background)" shows correct status colors again.
  • We fixed the appearance (including font colors) of text labels that was broken on some map objects.
  • We fixed an issue where some elements on maps overlapped the expanded PRTG main menu.

Fixed

Probe


Memory Leak

We fixed a memory leak on the PRTG probe system caused by running SNMP Fujitsu System Health BETA sensors.

calendar

July 4th 2018 – Version 18.3.42.1711


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. For details, please see the Knowledge Base article How do I get a Google Maps API key for use in PRTG?

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.

WebGUI

  • We added the Scan Now button to hover popups again. It was not available in previous versions by mistake.
  • Various minor fixes for the PRTG web interface

Enterprise Console

We fixed some layout issues of the Enterprise Console that appeared in the last preview version of PRTG.

calendar

June 18th 2018 – Version 18.2.42.1618


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.

Note: Please note that proxy usage is not supported in this initial release of the new notification types.

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

Internet Explorer 11

We fixed the position of several buttons (for example, in reports and the Add Sensor dialog) in the PRTG web interface for Internet Explorer 11.

Maps

We fixed an issue with public maps that failed to refresh when including the Data Tables object Tickets.

System Information

You can select the text in System Information tables with your mouse again to copy and paste the entries.

Fixed

Various


Various

Several other minor improvements and fixes, 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.

calendar

May 30th 2018 – Version 18.2.41.1636


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!

calendar

May 28th 2018 – Version 18.2.41.1624


Fixed

Various


Reports

We fixed a possible issue with access rights for reports.

Various

This version also includes updated language files and some other minor fixes.

calendar

May 24th 2018 – Version 18.2.41.1591


Blog article

Mmm…Donuts! PRTG Release 18.2.41 Comes with a New Map Chart Object

Have you all recovered from our release of last month? In May we introduced the PRTG version 18.2.40, presenting our new Fujitsu sensor. This new SNMP Fujitsu System Health BETA sensor monitors...
Read the complete blog post here



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

The Sensor Status History section in historic data reports now shows more precise values and always displays the statistics down to seconds. In previous versions, PRTG rounded the values to units that were too large in certain cases and so did not add up to the values in the heading of the report.

Improved

Notifications


SMS Delivery

We added the Windows registry option to use basic authentication for SMS delivery. This may be helpful when you use custom URLs for SMS delivery and your provider requires basic authentication. For details see the article https://kb.paessler.com/en/topic/79575 in our Knowledge Base.

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! (CVE-2018-19203, CVE-2018-19410)

Reports

We fixed an issue that allowed access to reports under certain circumstances without according permissions.

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

Fixed

Various


Various

Several other minor improvements and fixes, updated user manual, updated language files

calendar

April 25th 2018 – Version 18.2.40.1658


Fixed

Sensors


Event Log (Windows API)

Filtering by event ID with the Event Log (Windows API) sensor works again. Due to a change in the Windows API the sensor was not able to find events by ID in previous versions.

Exchange Database DAG (Powershell)

The Active Copy channel now shows correct data when monitoring Exchange Server 2010.

HTTP Advanced

The request method HEAD now properly works with the HTTP Advanced sensor. The channels Bytes received and Download bandwidth only showed 0 values in previous versions.

We also improved the bandwidth calculation and the way the sensor monitors really fast connections (for example, LAN or localhost) that sometimes caused the error message "Potential error during bandwidth calculation. (Loading time below 0.1 ms)".

NetFlow V9 and IPFIX

We fixed an issue that caused in and out traffic to be assigned in the wrong direction (switched source and target) in certain cases when monitoring a Cisco ASA. The issue affected the sensor types NetFlow V9, NetFlow V9 (Custom), IPFIX, IPFIX (Custom) and was visible when using toplists or filters.

REST Custom

  • We fixed an issue with escaping quotation marks (") in the postdata field of the REST Custom sensor. The issue resulted in cut off data.
  • We fixed an issue with the REST Custom sensor where values were mapped to the wrong channels when the number of channels changed between two sensor scans.
  • Stability improvements for the REST Custom sensor

SNMP Custom and SNMP Custom Advanced

SNMP Custom and SNMP Custom Advanced sensors show correct values again when the requested OID returns negative values. In certain cases, the sensors only showed the value -1 for returned negative values.

SNMP Traffic

We improved the compatibility of the SNMP Traffic sensor with certain target devices that have issues with their current firmware version. In certain cases, the SNMP Traffic sensor could not properly finish requests, which resulted in many log entries on the target device.

Windows Update Status (Powershell)

Stability improvements for the Windows Updates Status (Powershell) sensor

Channel Limits

Using decimal separators in channel limits works properly again. Saving the settings will not reset entered values to 0 anymore when using decimal separators.

Fixed

Security


Sensors

Security improvements for debug log files that several sensor types can write using the option "write result to disk"

Fixed

WebGUI


Maps

  • The object Map of category Cluster is correctly displayed again on maps. The cluster nodes are not overlapping anymore.
  • In the Map Designer, previews of the map objects Globe and Geo Map in section Geo Maps, as well as Map in section Cluster work again.
  • The status count in the heading of the map object Alarms small now only applies to the selected object. In previous versions, this map object showed the status count of the whole PRTG installation.

Reports

  • The Today button on the Run Now tab of reports will use the expected timespan for monitoring data again. Generated reports mistakenly included data for the day after "today" in previous versions.
  • Improved layout of sensor details in reports

Tables

Changing object priorities in tables will not result in expanding table rows anymore.

Fixed

Various


Various

Several other minor improvements and fixes, updated user manual, updated language files

calendar

April 2018 – Version 18.2.40


Blog article

PRTG Release 18.2.40 Comes with Native Fujitsu Sensor (and a Lot More)!

In PRTG Release 18.2.39, which we released last month, our focus was primarily on improvements in security and stability. Besides PowerShell fixes and improvements to the PRTG API, we explained...
Read the complete blog post here



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.

Please note that the IPv6 support for these sensor types is included as experimental feature. We welcome any feedback on the IPv6 functionality, just send it to [email protected]!

SMB-based Sensors

The sensor types File, File Content, Folder, and Event Log (Windows API) handle impersonation in a better way and mitigate potential error sources. The sensors now first try to access the target share as LOCAL_SYSTEM Windows user. If they do not succeed, they try impersonation with the Windows credentials defined in the device settings.

SNMP Custom String and WMI Custom String

SNMP Custom String and WMI Custom String sensors now show the retrieved string message even when the sensor status is unusual.

WMI HDD Health

We improved the naming of the WMI HDD Health sensor channels. The names of the several sensor channels are more meaningful now and will not show just "unknown".

Improved

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.

calendar

March 29th 2018 – Version 18.1.39.1648


Changed

Sensors


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.

Fixed

Security


Security

We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to STO LABS, especially to Lucas Carmo, Edward Toledano, and Ricardo Fajin. Thank you!

calendar

March 23rd 2018 – Version 18.1.39.1612


Improved

User Rights


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.

Improved

Sensors


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.

Fixed

Security


PowerShell

We fixed a potential security issue with command line parameters for PowerShell scripts that affected EXE/Script sensors, EXE/Script Advanced sensors, as well as Execute Program notifications (CVE-2018-9276). We also fixed a potential security issue with sample custom notifications (CVE-2018-9278).

Note: The fix required changes to the handling of command line parameters. In certain cases, it will be necessary to adapt quoting with backticks (``) in the parameters field because PRTG will process quotes more accurately.

Outgoing Connections

Outgoing connections from the PRTG core server to Paessler servers for activation, update check, and downloads now use HTTPS.

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.

Fixed

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

Fixed

Server


Performance

We fixed some more issues that caused performance losses and resulted in PRTG core server timeouts in certain cases.

Fixed

Various


Various

Several other minor improvements and fixes, updated user manual, updated language files

calendar

March 2018 – Version 18.1.38


Blog article

Security, Healthcare and Much More! Why You Should Update to PRTG Release 18.1.38.11934

Last month we had to deal with some highly exciting but also time-consuming code enhancements within PRTG Network Monitor. Our development team implemented an important security fix, made...
Read the complete blog post here



Important

Security


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.

New

Sensors


DICOM and HL7 Sensors

You can now monitor your medical IT on Digital Imaging and Communications in Medicine (DICOM) and Health Level-7 (HL7) out of the box! The new PRTG version 18.1.38 includes 4 new sensor types that show you important information about your DICOM and HL7 capable systems and devices.
  • The DICOM Bandwidth BETA 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 BETA 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 BETA 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 BETA sensor monitors the availability of HL7 interfaces. It sends an HL7 message to the target device and checks for a valid response.

Improved

Sensors


WMI Event Log

You can now use negative filtering in WMI Event Log sensors! This means that you can exclude specific event sources, IDs, categories,users, computers, and messages from monitoring. Events that you exclude via the sensor settings will not be processed by the event log sensors.

Lookups and Alerting

You can now explicitly define when sensor channels that use lookups will show a down status and alert you, either based on the lookup definition or based on numerical limits for returned values. You will find the new setting Value Lookups and Limits in the settings of custom channels instead of the Limits settings where you can decide which method is best for your setup. Please keep in mind that only one option will apply! So, if you choose limits as alerting method, an error status as defined in the lookups will not show up.

After you have updated PRTG to this version, existing custom channels will be provided with an appropriate default automatically. If you had set alerting by limits and lookups simultaneously before the update, the limit setting will apply after the update and values will not appear as lookup channels, but your notifications still work as expected. Please check that your custom channels still have an alerting method that is suitable in your scenario after the update.

NetApp System Health

The NetApp System Health sensor has a new channel Storage configuration path. The channel monitors the current configuration path that describes the connection of the node (multi_path, multi_path_ha, single_path, single_path_ha, mixed_path, mixed_path_ha).

Changed

Sensors


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!

calendar

March 7th 2018 – Version 18.1.38.11937


Note

Known Issue


Event Log (Windows API) and WMI Event Log

There is a known issue in this version: Event Log (Windows API) and WMI Event Log sensors have a new option to exclude certain events from monitoring (see section Improvements below). By default, the sensors will set the new option to Exclude Filter for each available filter after the update to this PRTG version. This causes the sensors to disregard events that you actually want to monitor and filtered for in previous versions. For example, if you defined to filter for a certain event ID, this ID will now be excluded but all events with another ID will be counted.

Please manually correct the sensor filter settings after installing the update.

Note: The Event Log (Windows API) sensor shows settings for exclude filters, but the filters are not functional yet. You can only use include filters. We will add the functionality to use exclude filters with the Event Log (Windows API) sensor in one of the next PRTG versions.

Fixed

Sensors


Business Process

Several fixes for the display of Business Process Specific Settings

Custom Sensors

You can specify a scaling factor (multiplication and division) in the channel settings of custom sensors again, including channels of SNMP Library sensors. Scaling factors defined by meta-scan, OID libraries, and PRTG backend results will also apply again. This did not work for non-custom units (for example, bytes/s) in previous versions.

Exchange (Powershell) Sensors

As announced in the release notes of PRTG 18.1.37, we removed the Execution Time channels from Exchange (Powershell) sensors. The channel was only delivered in PRTG 17.4.36 and was not functional.

Folder

The Folder sensor can now access folders on a network share when the share has specific credentials. If the Windows user account that runs the PRTG probe service has no access rights on the Windows share but there are correct Windows credential defined in PRTG, the sensor will be able to monitor the share.

SNMP HP ProLiant System Health

We removed the Integrated Management Log Status channel from the SNMP HP ProLiant System Health sensor because the OID that the sensor used no longer exists.

SNMP Library

  • In certain cases, when you added multiple sensors via the SNMP Library sensor at once, the sensors used random OIDs and so displayed wrong values. We fixed this issue.
  • SNMP Library sensors correctly apply value types from the OID library again. In certain cases, delta values and absolute values were incorrectly defined in the value type settings.
  • You can configure the scaling factor (multiplication and division) in SNMP Library sensor channel settings again, even if there was no scaling factor defined in the OID library. The scaling factor also works for non-custom units (for example, bytes/s) again.

SNMP Linux Meminfo

The SNMP Linux Meminfo sensor channel Percent Available Memory has no predefined limits anymore to better reflect the behavior of Linux systems. If you need the removed limits, please manually add them again in the channel settings after the update to this PRTG version.

By default, the new primary channel of the SNMP Linux Meminfo sensor is Physical Free Percent.

SSH Disk Free

The SSH Disk Free channel includes all selected partitions in one sensor again. In previous versions, PRTG erroneously created one sensor for each selected partition with the content of both selected partitions.

SSL Security Check

We removed the SSL 2.0 channel. The OpenSSL component that PRTG uses does not support SSL 2.0, so the channel result was incorrect.

VMware Sensors

VMware sensors now work on Windows machines with the Federal Information Processing Standard (FIPS) mode enabled. Please note that PRTG still does not support the FIPS mode on Windows systems running the PRTG core server or probe service.

Fixed

Security


API

It is not possible anymore to perform certain actions via API calls without having according user rights. Thanks to Positive Technologies for reporting the issue! (CVE-2018-19411)

Sensors

Passwords in debug files will not appear in clear text anymore when you enable the option to write the sensor result to disk.

Fixed

WebGUI


Auto-Discovery

It is possible again to start an auto-discovery on multiple devices in the device list. The option Run Auto-Discovery is now available in the multi-edit context menu.

Desktop Notifications

We fixed an issue where desktop notifications did not work when they were temporarily disabled and the last saved alarm count was great than the new count. Also note that Google Chrome requires HTTPS to use desktop notifications since one of its latest updates, so please switch the PRTG web server to SSL if you enable desktop notifications.

Geo Maps

In certain cases, Geo Maps were not correctly displayed but shown as JSON code or not at all. We fixed this issue.

Graphs

Graphs throughout the PRTG web interface are now better readable. This especially affects colors as well as transparency. For example, the Primary Channel of a sensor is more clearly visible again. Also Maps benefit from these improvements.

Libraries

It was mistakenly possible to switch the device tree view on the Management tab of a library. We removed the option. The device tree on this library tab has the default size M.

Main Menu Structure

We have removed the entry Tickets | All from the main menu bar.

Maps

Previews of graph map objects are displayed again.

Mobile View

We fixed an issue with scrolling in the mobile view.

Reports

Faster rendering of very long reports

Search

Performance improvements for the device tree search. PRTG will show you search results in the device tree much quicker than before. We also fixed some issues with the advanced search.

Tables

Several improvements and fixes for the display of tables (both data tables and sensor selection tables in the Add sensor dialog) in the PRTG web interface and in Maps

Tags

Several fixes to the usage of new tags

Various

Many other minor fixes and improvements to the new PRTG web interface

Fixed

Server and Probes


API

It is now possible to use API calls like setobjectproperty.htm on the Total channel of traffic sensors that have channel ID -1 (subid=-1).

Clone Objects

Cloning groups and devices that have an auto-discovery setting enabled or that currently have an auto-discovery running will not result in duplicated sensors on the new group or device anymore.

Remote Probes

We fixed an issue where approving remote probes resulted in timeouts when the geo location server for Geo Maps was not reached. In certain cases, the PRTG web interface was frozen or the PRTG core server was not reachable when this happened.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements, 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.

calendar

February 2nd 2018 – Version 18.1.37.11737


Fixed

Sensors


EXE Sensors

Sensor types that use EXE files for monitoring did not correctly handle invalid JSON and XML responses. We fixed this issue.

Windows Updates Status (Powershell)

The auto-discovery added Windows Updates Status (Powershell) sensors to devices that do not run Windows. Because this was not a good idea, we changed the according device template to add sensors of this type only to Windows devices.

Fixed

WebGUI


PRTG Web Interface

We fixed some more issues with the new PRTG web interface, for example:
  • The paging of tables in sensor settings did not work properly when adding sensors.
  • The option "Make this my homepage" works again.

Fixed

Server


PRTG Core Server

In certain cases, the PRTG server did not start after the installation of updates or after installing a new PRTG instance. We fixed this issue.

calendar

January 25th 2018 – Version 18.1.37.10374


Fixed

Sensors


SNMP Library

This version includes several fixes for the SNMP Library sensor. The sensor correctly uses the Scale (multiplication and division) from the imported OIDLIB again to show expected values. Custom units are imported and displayed correctly again.

calendar

January 2018 – Version 18.1.37


Blog article

What You Miss If You Don’t Update! - PRTG Release 18.1.37.12158

We just released PRTG Network Monitor stable version 18.1.37.12158 some days ago. It includes the brand-new REST Dell EMC Storage BETA sensors, stability improvements for Exchange sensors, and...
Read the complete blog post here



New

Sensors


REST Dell EMC BETA

We added 5 new sensor types that enable you to monitor your Dell EMC storage systems out of the box! The sensors use the REST API of Dell EMC devices to show you health status and other important measurements of your Dell EMC storage components. PRTG 18.1.37 comes with the following Dell EMC sensors:
  • The REST Dell EMC Capacity BETA sensor monitors disk usage.
  • The REST Dell EMC File System BETA sensor monitors the health of an EMC file system.
  • The REST Dell EMC LUN BETA sensor monitors an EMC logical unit number (LUN).
  • The REST Dell EMC Pool BETA sensor monitors an EMC storage pool.
  • The REST Dell EMC System Health BETA sensor monitors the EMC health status.
The new REST Dell EMC BETA sensors support various EMC storage systems that provide a REST API, for example, EMC Unity Family, EMC Unity All Flash, EMC Unity Hybrid, and EMC UnityVSA.

Changed

Sensors


Exchange Backup (Powershell)

Stability improvements for the Exchange Backup (Powershell) sensor. It also includes two new channels that show the passed time since the last differential backup and since the last incremental backup. After the update to PRTG 18.1.37, please create your Exchange Backup (Powershell) sensors anew. Existing sensors of this type might show incorrect data!

Exchange Public Folder (Powershell)

The Exchange Public Folder (Powershell) sensor can now monitor subfolders. After the update to PRTG 18.1.37, you must create all Exchange Public Folder (Powershell) sensors anew. Existing sensors of this type will stop working!

Exchange (Powershell)

Stability improvements for all Exchange (Powershell) sensors. Note: The Execution Time channel of running Exchange (Powershell) sensors will not show any data after the update to PRTG 18.1.37 and will be completely removed in future versions. It was still available in some older running Exchange sensors.

Improved

Sensors


NetApp LIF

The NetApp LIF sensor has a new channel Is home that shows if the logical interface is at the home port.

NetFlow V9 and IPFIX

Performance improvements for NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors

SNMP QNAP Logical Disk

The SNMP QNAP Logical Disk sensor has a new lookup status Synchronizing in channel Volume Status that maps to the sensor status warning.

Improved

Server


Date Format

We added the date format YYYY-MM-DD HH:MM:SS to make more people feel at home when using PRTG. You can choose your preferred date format in your PRTG user account settings.

calendar

January 25th 2018 – Version 18.1.37.10374


Fixed

Sensors


Business Process

Adding objects to channels in the Business Process Specific Settings works again.

Cloud HTTP and Cloud Ping

Cloud HTTP and Cloud Ping sensors now use the Proxy Settings for HTTP Sensors from the parent device (or inherited from other objects higher in the hierarchy). In previous versions the sensors used the proxy configuration for Core & Probes as defined in the PRTG System Administration.

Common SaaS

The Common SaaS sensor is now available when filtering for Cloud Services in the Add Sensor dialog.

FTP Server File Count

We added passive connection mode support to the FTP Server File Count sensor. You can choose the required FTP Mode in the sensor settings.

HTTP Push Sensors

Stability improvements for HTTP Push sensors (HTTP Push Count, HTTP Push Data, HTTP Push Data Advanced)

Hyper-V Virtual Machine

The Hyper-V Virtual Machine sensor shows more expressive error messages in case of sensor failures.

NetApp NIC

The NetApp NIC sensor can now monitor all physical and logical ports on any node in your NetApp cluster and correctly provides all available monitoring items in the Add Sensor dialog.

NetApp Sensors

In certain cases, NetApp sensors for cDOT and ONTAP storage systems failed because of corrupted cache files. We fixed this issue.

NetFlow V9 and IPFIX

In certain cases, NetFlow V9 and IPFIX sensors could not collect data. We fixed this issue.

Probe Health

The Probe Health sensor will now reset the error message for the Data Storage Free channel when the disk has enough space again.

REST Custom

Some more fixes and improvements for the REST Custom BETA sensor, including support for Boolean values

SNMP Custom sensors

We changed the naming of the Value Type options of SNMP Custom, SNMP Custom Advanced, and SNMP Custom Table sensors. This will make it clearer what value type you have to choose, absolute or delta values.

SNMP Traffic

In certain cases, SNMP Traffic sensors showed access violation errors. We fixed this issue.

SSL Certificate

The SSL Certificate sensor now correctly categorizes the key length of ECC certificates in case of compressed coordinates. If you have changed the lookup file to manually avoid issues with the key length of ECC certificates, please choose the original lookup file again after the update. For details, please see this Knowledge Base article: SSL Certificate Sensors and ECC Certificates: Fix for Public Key Length Monitoring

VMware Sensors

VMware sensors support TLS 1.2 only connections if required by the target VMware host.

VMware Virtual MAchine (SOAP)

If you create a device template that includes a VMware Virtual Machine (SOAP) sensor and run an auto-discovery with the template, discovered VMware Virtual Machine (SOAP) sensors will now have a correct sensor name (was erroneously "Host Performance" in previous versions) and correctly take the Handling of "Powered Off" VM setting.

Windows Updates Status (Powershell)

You can add Windows Updates Status (Powershell) sensors via Auto-Discovery again.

WSUS Statistics

The WSUS Statistics sensor can handle untrusted certificates when using SSL to connect to the WSUS server.

Sensor Channels

Decimal places were not correctly displayed in certain cases, for example when decimal places were set to Automatic in the sensor channel settings with a Custom unit and no custom unit string. We fixed this issue.

Various Sensors

In newly created sensors you must select the Value Type "Integer" to use a lookup because lookups only properly work with integer values. This was not validated in previous versions and lead to inconsistencies. This change affects the sensor types ADO SQL v2, Google Analytics, MySQL v2, Microsoft SQL v2, SNMP Custom Advanced, SNMP Custom Table.

Fixed

WebGUI


PRTG Web Interface

We fixed various issues with the new PRTG web interface and further improved usage and appearance.
  • Date Time Picker: The first week of a month is correctly displayed again in date time pickers and calendars, the date matches the correct weekday.
  • Dashboards: We removed the outdated default dashboards (Dashboard 1, Dashboard 2, Dashboard 3) that were still delivered in long-standing PRTG installations from the main menu of the PRTG web interface. Please create a map with your desired data if you miss the default dashboards. You can still add a map to the Home menu: Give a map a 5***** priority and it will appear in the menu. You can include up to 10 map entries here. For more details, see PRTG Manual: Maps.
  • Device Tree: The device tree was cut off on some views. We fixed this issue.
  • Graphs: Better visibility of the primary channel in data graphs
  • Maps: Public Maps are displayed properly again when using Internet Explorer.
  • Maps: Connection lines again show the correct color for the states down by limit, simulated error, and unknown.
  • Smart Setup: Skipping the Smart Setup works again.
  • Syslog Receiver and SNMP Trap Receiver: Improved layout of Syslog Receiver and SNMP Trap Receiver tables that contain received messages
  • Tables: More improvements for the display of tables, including a clearer display of the down status in all tables and lists in the PRTG web interface (for example, in maps and reports) and a better performance when loading large tables
  • Tags: Changing tags on monitoring objects like sensors is possible again.

Memory Leak

We fixed a memory leak caused by historic data graphs.

Fixed

Server and Probes


Auto-Discovery

The History tab of a device or sensor now correctly shows the PRTG user account who started an Auto-Discovery that created a sensor.

PRTG Core Server

In certain cases, the PRTG server did not start after the installation of updates or after installing a new PRTG instance. We fixed this issue.

Reports

The last day of a report time span was not included in the report if you changed the start date without editing the end date. We fixed this issue, the day of the defined end date will now also be included in the report in such cases.

Stability

  • We fixed an issue where a time difference of more than 5 minutes between the PRTG core server and remote probe system or a transmission time longer than 5 minutes would cause connection resets.
  • In certain cases, when running a PRTG update to 17.4.35 or 17.4.36, the PRTG Core Server service would not start. We fixed this issue.

Fixed

Security


Maps

It is not possible anymore to create objects like maps with a PRTG read-only user account (CVE-2017-15917).

Debug Files

All passwords in debug and log files are now masked. This affects, for example, passwords in files that sensors create when you enable the option "Write sensor result to disk" in sensor settings.

Fixed

Enterprise Console


Libraries

Libraries and the Management tab of libraries can be viewed again in the Enterprise Console. The pages did not correctly load in the previous PRTG version.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements, updated user manual, updated language files

calendar

December 8th 2017 – Version 17.4.36.3584


Fixed

WebGUI


PRTG Web Interface

This version includes some more fixes and improvements for the new PRTG web interface, among others:

  • 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.
  • Reports: General layout fixes and improvements, for example, tables now use the full paper width.

Fixed

Sensors


Exchange (Powershell) Sensors

Exchange (Powershell) sensors work on Exchange Server 2010 again.

Exchange Backup (Powershell)

The Exchange Backup (Powershell) sensor will now warn you if there was no backup performed instead of showing an up status.

Fixed

Various


All Parts of PRTG

Some other minor fixes

calendar

November 30th 2017 – Version 17.4.36.3506


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

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

Fixed

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.

Fixed

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.

Fixed

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.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements, as well as an updated user manual

calendar

November 2017 – Version 17.4.36


Improved

WebGUI


PRTG Web Interface

Major improvements to the new PRTG web interface! We implemented a lot of your feedback to give you an even better experience with PRTG.

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 %


Important: Because of required changes to the volume detection approach of this beta sensor, existing instances of the NetApp Volume sensor will stop working after updating to this PRTG version. Please add your NetApp Volume sensors anew. To keep monitoring data of existing NetApp Volume sensors, you can pause them. It is also not possible anymore to add sensors for volumes that are offline.

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.

Note: Existing REST configuration files using the outdated JSON format (.json files) will continue to work after updating to this version, but please be aware that they will not be compatible with PRTG versions in the near future. We recommend that you convert existing REST configuration files to .template files using JSONPath as soon as possible.

calendar

November 15th 2017 – Version 17.4.35.3318


Fixed

WEBGUI


Geo Maps

This version includes another fix for Geo Maps.

calendar

November 2017 – Version 17.4.35


Important

Known Issue


SNMP Sensors

Some customers have experienced issues with SNMP sensors in this PRTG version. These issues might result in a damaged PRTG configuration file. We will provide a fixed version as soon as possible.

New

Sensors


NetApp SnapMirror

We are further enhancing the NetApp monitoring capabilities of PRTG: You are now able to monitor SnapMirror relationships with PRTG and the new NetApp SnapMirror sensor!

The sensor accesses the NetApp API via SOAP and supports the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3. Always see the health and relationship status of a SnapMirror, the relationship type (mirror and vault), the mirror state, and important parameters about SnapMirror transfers and failures. This is really great news for all NetApp customers!

Improved

Sensors


Adding Sensors

We improved the PRTG internal sensor creation process to speed up things. You will especially benefit from this improvement when adding many sensors at once. This is the case, for example, when sensor types scan for available monitoring items on the target device before the sensors are actually created (meta-scan).

PRTG will now create the sensors in background tasks and show the progress to keep you informed—you don't have to wait anymore for the sensors and can continue your business.

SNMP Library

We considerably improved the way PRTG creates SNMP Library sensors from an imported MIB (OIDLIB)! When you add the SNMP Library sensor, it will now automatically create SNMP Custom Advanced sensors with up to 10 channels for single values returned by OIDs, SNMP Custom Table sensors with up to 10 channels for returned table rows, and SNMP Custom String sensors for OIDs that return string values instead of creating a lot of single value SNMP Library sensors.

This makes adding custom sensors much easier, because you do not have to enter the OIDs manually to start monitoring but just select desired items from an OIDLIB in the PRTG web interface. With the SNMP Library sensor switching to automatically create custom table and advanced sensors, we also eased the process of creating device templates that include custom SNMP sensors.

And that's not all: The created sensors will also take the descriptions of used OIDs and add them to the according sensors' Comments tabs.

SNMP Dell PowerEdge Physical Disk

We added some new states to the Disk State channel of the SNMP Dell PowerEdge Physical Disk sensor to cover all states returned by the target device.

Improved

System Information


System Information

System Information via SNMP returns more data for the tables System, Processes, and Hardware from a wide variety of Linux machines and a lot of generic network devices.

Changed

Languages


Czech Language File

We removed the Czech language file from PRTG. Existing PRTG installations that use the Czech language file will switch to English after the update to this version.

calendar

November 7th 2017 – Version 17.4.35.3266


Fixed

Server


Data

We fixed an issue that occasionally caused missing monitoring data in sensors and empty sensor messages after a PRTG server restart.

Device Templates

The device template Buffalo TeraStation NAS now also works in Spanish language versions of PRTG.

Email Delivery

We have removed an internal comment part in emails to prevent security software from classifying emails from PRTG as insecure (of course, PRTG will never send you insecure emails!).

License

Stability improvements for the PRTG licensing system

Schedules

Changing and assigning schedules works more reliably.

Security

We fixed two minor potential security issues.

Fixed

Sensors


Folder

The Change Trigger for notifications of the Folder sensor is working again.

SNMP Printer

The SNMP Printer sensor will now correctly interpret negative values as well as 0 values returned by the printer. Such values resulted in unintended sensor warnings and errors in some cases.

SNMP Traffic

Some devices have a blank interface description in SNMP v1 (empty ifDescr and ifAlias), so the SNMP Traffic sensor was not able to use the description of such devices for the sensor name. The SNMP Traffic sensor will now take values from SNMP v2 ifXName in this case to avoid an empty name.

SSL Certificate

The SSL Certificate sensor comes with predefined limits for the Days of Expiration channel again. PRTG will warn you if your certificate expires in 28 days (keep in mind: it will not warn you about other, even worse "28 days later" scenarios) and show a down status if there are less than 7 days left.

Windows Updates Status

Passwords will not be logged in clear text anymore when using the Windows Updates Status (Powershell) sensor.

WMI Sensors

Values with data type UInt32 or UInt64 were not converted correctly when monitoring via WMI and resulted in an integer overflow in certain cases. We fixed this issue.

Fixed

WebGUI


Device Tree

Deleting objects while the Auto-Discovery was running on the deleted object resulted in an inconsistent or empty device tree in some cases. We fixed this issue.

Graphs

  • You can download graphs as PNG again. The PNG button of graphs erroneously delivered an SVG in previous versions.
  • Historic data graphs will now show a text label for the maximum value even when the primary channel is the only displayed channel (except for a maximum value of 100%).

Memory Leaks

We fixed two memory leaks, one caused by Geo Maps, one caused by data tables.

Fixed

Various


Various

Various other fixes and improvements, updated user manual, updated language files

calendar

November 7th 2017 – Version 17.4.35.3266


Fixed

Sensors


REST Custom

The REST Custom BETA sensor now works properly on 32-bit builds and on cloud probes.

Fixed

Core


Reports

In certain cases, CSV report files could not be generated properly. We fixed this issue.

Fixed

WEBGUI


Geo Maps

We have fixed the issue with Geo Maps. PRTG now uses HERE Maps as provider so you are able to correctly view Geo Maps again.

calendar

October 13th 2017 – Version 17.4.34.3097


Fixed

Server and Probes


Probe Connection

Occasionally, probes could not successfully connect to the PRTG core server. This happened when the .NET requirement (.NET 4.5 or later) was not fulfilled. We have fixed this issue.

calendar

September 28th 2017 – Version 17.3.34.3007


Fixed

Sensors


REST Custom

Several fixes and stability improvements for the REST Custom BETA sensor.

SNMP Cisco System Health

Custom tags for SNMP Cisco System Health sensors in device templates will now be added to the deployed sensors when running the auto-discovery. In previous versions, the tags have been overridden by default tags.

SNMP Library

In certain cases, using the SNMP Library sensor with an imported OID library that contained strings resulted in a huge PRTG configuration file. We have fixed this issue.

SNMP SonicWALL VPN Traffic

When running an auto-discovery with a template that contains a SNMP SonicWALL VPN Traffic sensor, PRTG will now always use the identification method for connections defined in the sensor settings. In previous versions, the sensor erroneously used "By index" in certain cases, which resulted in multiple re-added sensors for the same connection.

Fixed

Reports


Report Graphs

When adding a sensor to a report multiple times, the graphs in the report did not show any data. We fixed this issue.

Fixed

Server


API

The API call /api/table.xml?content=sensortree now returns the correct lastvalue_raw. Raw data differed from the correct value by factor 10.

Schedules

We fixed an issue with schedules in timezones without daylight saving time. Schedules will now also correctly work in such timezones.

Tickets and Auto-Discovery

When running an auto-discovery on group level, PRTG will now only create one ticket for the complete auto-discovery. In previous versions, PRTG was a bit chatty and created a ticket for each detected device.

Fixed

Various


All Parts of PRTG

Various 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.

calendar

September 2017 – Version 17.3.34


New

WebGUI


WebGUI

Completely revised and updated look&feel of the PRTG web interface! The new, modern PRTG web interface comes with a cleaner look and many improvements to the usability. You will now find what you need more easily!

  • Add buttons in the device tree are now bundled into one central location, the + button.
  • The Edit function in table lists always works like the former Multi-Edit function. Select the object(s) you want to edit and the menu appears on the right.
  • Floating Save button: On forms, for example, settings pages, the Save button will always stay on the current page segment. Once you have changed something, it will turn blue and you can save at any time.
  • You have the option to use a dark theme for the PRTG web interface, see your account settings.
  • And we have tidied up everywhere in the PRTG web interface!
  • Note: If you have customized the PRTG web interface using one of the dedicated files, all your modifications will be lost after installing PRTG version 17.3.34. There is still an option to modify the appearance of PRTG, but please note that this is an unsupported and deprecated feature. For details, see the Knowledge Base.

Changed

Sensors


EXE-based Sensors

All sensor types that require the .NET framework will need .NET version 4.5, 4.6, or 4.7 on your PRTG server and on all computers running a probe after installing PRTG version 17.3.34. By default, required .NET versions are included in Windows 8 or later and Windows Server 2012 or later. For details, see the Knowledge Base.

Changed

Core/WebGUI


File Lists

We refined the change from the last PRTG version 17.3.33 and made the handling of file lists in the web interface more comfortable. File lists will now automatically refresh as soon as you open the according page in PRTG to immediately display newly added files like SNMP libraries, device icons, or report templates.

Manually reloading file lists will not be necessary anymore in most cases, but if you have to do so for some reason, you can use the (partly) new Load Lookups and File Lists option under Setup | System Administration | Administrative Tools.

Improved

Security


Security

This version includes general security enhancements for PRTG and the configuration file.

Improved

Sensors


HTTP XML/REST Value

We added TLS 1.2 support for the HTTP XML/REST Value sensor. Because this improvement makes the "SSLv3 Connection" setting obsolete, we removed it from the sensor settings. We also fixed a possible stack overflow caused by this sensor.

SNMP HP ProLiant Physical Disk

We added two new states to the Disk Status channel of the SNMP HP ProLiant Physical Disk sensor: SSD Wear Out and Not Authenticated

calendar

August 18th 2017 – Version 17.3.33.2654


Fixed

Security


Security

We have fixed a possible XSS vulnerability (CVE-2017-12879).

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.

NetApp System Health

The NetApp System Health sensor will now correctly handle partitioned spare disks and not only show 0 GB.

Various Sensors

In previous preview versions 17.3.33.2559 and 17.3.33.2599, "last value" in tables and API calls was empty when the sensor was down due to a breached limit.

Fixed

WebGUI


Geo Maps

When you change geo locations for objects in the device tree, Geo Maps will accordingly update and show the defined location again.

calendar

August 10th 2017 – Version 17.3.33.2599


Fixed

Server and Probes


Stability

Stability improvements for the PRTG core server and probe system

Fixed

Sensors


NetApp System Health

The NetApp System Health sensor now shows the correct number of spare disks even if the NetApp reports low spare disks. With this fix we also introduced a new sensor channel that shows when spare disks are low. Additionally, the usable spare size channel will now report the correct value and not just 0 if there are disk partitions.

Fixed

Apps


Enterprise Console and PRTG for iOS

In the last PRTG preview release, the Save button was missing on various pages in the PRTG Enterprise Console and in the iOS app. We have found it again in the latest preview version 17.3.33.2599.

calendar

August 2017 – Version 17.3.33


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 Sensors\rest folder in the PRTG program directory, including mappings for the REST APIs of KEMP load balancers, Weather Underground, Docker containers, and PRTG itself, ready-to-use for the sensor.

And the REST Custom sensor is also smart: you do not necessarily have to write a REST configuration file in JSON format to get sensor values when querying some REST endpoint. The sensor comes with an automatic detection feature for JSON or XML responses and creates suitable channels on its own! Choose channelDiscovery as REST Configuration setting of the sensor and it will parse the JSON or XML response of the REST query to automatically create channels for all available number and boolean values (including strings if convertible into numbers).

You have some cool idea for this sensor or have already implemented a REST configuration file? Great, let us know if you want to share it!

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

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

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.

Improved

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.

calendar

August 3rd 2017 – Version 17.3.33.2559


Fixed

Sensors


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

Server


Server Stability

In rare cases, the PRTG server performed an unexpected restart because of a deadlock event when scheduling reports. We have fixed this potential deadlock cause.

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

calendar

June 14th 2017 – Version 17.2.32.2206


Fixed

Sensors


Common SaaS

The Common SaaS sensor can check Bing again. Microsoft has deprecated the used URL so you might have seen the sensor message Bing API not available. We have fixed this issue.

Dell PowerVault MDi Logical Disk

The Dell PowerVault MDi Logical Disk sensor will now show all available disks on a PowerVault system when adding the sensor. We have fixed a small bug that prevented the sensor from finding all disks during the metascan.

DHCP

We have fixed a bug where an overflow could prevent the DHCP sensor from showing the correct results.

Folder

We have improved the stability of the Folder sensor when monitoring folders that contain a large number of files and added a proper timeout handling for folder scans. For debugging purposes, the sensor now also provides the option to write the sensor result to disk.

HTTP Sensors

HTTPS POST requests with NTLM authentication work again.

NetFlow

We have fixed an issue that caused missing data for NetFlow sensors.

PostgreSQL

We have fixed an encoding issue to correctly display PostgreSQL sensor error messages.

Sensor Factory

If a Sensor Factory sensor included source sensors with delay (like xFlow and Packet Sniffer sensors) and the option use zero as source value was enabled for the setting If a Sensor Has No Data, the Sensor Factory only showed 0 values. We have fixed this behavior.

sFlow

Data graphs of the sFlow and sFlow (Custom) sensors showed gaps in certain cases because of wrong assignments to scanning intervals. This was caused by a workaround for buggy target devices that we have implemented in a previous PRTG version. We have fixed this behavior.

SMTP&IMAP and SMTP&POP3 Round Trip Sensors

We have fixed a small security issue: passwords in logfiles of SMTP&IMAP Round Trip and SMTP&POP3 Round Trip sensors are now masked when authentication is enabled.

Fixed

Sensors


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: Why are some SNMP Cisco UCS System Health sensor channels not showing any information anymore?

SNMP HP ProLiant Network Interface

We have fixed an issue with 0 bytes that resulted in error The network adapter with mac address [mac] could not be found (code: PE157) when using the SNMP HP ProLiant Network Interface sensor.

SQLv2 Sensors

  • 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.

Fixed

Notifications


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.

Fixed

Cluster


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.

Fixed

Server


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.

Fixed

Various


Various

Various minor fixes and improvements, updated user manual, updated language files

calendar

June 2017 – Version 17.2.32


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
  • 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

Device Templates


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.

Improved

Sensors


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).

calendar

March 28th 2017 – Version 17.1.31.1691


Fixed

Sensors


Business Process

Searching by object ID when defining channels for the Business Process sensor works better now.

SSH Disk Free

The SSH Disk Free sensor can show up to 100 channels (99 partitions). Previously, the default limit for channels applied so the sensor only added up to 50 channels.

Fixed

Server


Installer

When installing or updating PRTG, the installer will not start the PRTG core and probe services anymore if a reboot of the computer is required. This fix prevents inconsistent file states and according errors.

Fixed

Various


Various

Various minor fixes and improvements, updated user manual, updated language files

calendar

March 28th 2017 – Version 17.1.31.1691


Fixed

Reports


PDF Reports

Creating PDF reports works again.

Fixed

Auto-Discovery


Buffalo Device Template

The Buffalo device template works properly again and does not discover too much anymore.

Fixed

Sensors


SNMP Custom Table

You can add the SNMP Custom Table sensor again.

SQL Sensors

Comments with a # in the query do not cause an error anymore.

calendar

March 13th 2017 – Version 17.1.30.1557


Important

Server


Historic Data Reports

We have fixed a bug where short outages were not correctly recognized as downtime in historic data reports.

Changed

Sensors


Windows Sensors

Windows sensors on new PRTG installations will now use WMI only as Preferred Data Source by default (see the Windows Compatibility Options in the device settings) to query monitoring data instead of the hybrid approach (Windows Performance Counters as default, WMI as fallback). The latest major performance and stability improvements for WMI sensors with PRTG version 17.1.28.1341 have such a positive effect on your monitoring experience, so we recommend that you keep the new default setting!

Note: This update does not automatically migrate the setting on existing PRTG installations. If you encounter issues with Windows sensors that use Performance Counters by default, please manually change to WMI only as Preferred Data Source.

Fixed

Sensors


Active Directory Replication Errors

Adding the Active Directory Replications Errors sensor to device templates now works.

Event Log (Windows API) and WMI Event Log

The Event Log (Windows API) sensor and the WMI Event Log sensor support up to 2,000 characters in the message. Previously, the message was cut off after 1,024 characters.

HTTP Push Sensors

HTTP Push sensors now clear error PE206 if the set port is available again and show the correct status. In previous versions the HTTP Push sensors never came back if the port was blocked once.

SNMP Custom String

The SNMP Custom String sensor can now show backslashes (\) in the sensor message.

SNMP Custom Table

Creating a device template including several SNMP Custom Table sensors and running the auto-discovery with this template works more reliably. PRTG will now create sensors for all available entries in the SNMP table. We have also fixed a PE247 error that occurred in some cases in the previous PRTG version when auto-discovering SNMP Custom Table sensors.

SNMP HP ProLiant Network Interface

The SNMP HP ProLiant Network Interface sensor now also works if there are 0 bytes in the MAC address of the target interface. The error message in this case was: "The network adapter with mac address [mac] could not be found (code: PE157)"

VMware Datastore (SOAP)

The VMware Datastore (SOAP) sensor now has predefined channel limits to automatically warn you if your disk is running full. If this change does not apply to your scenario (because of thin provisioning, for example), please adjust the limits in the channel settings.

Windows Updates Status (Powershell)

Channel names of the Windows Updates Status (Powershell) sensor are now more appropriate and show the correct severity for updates. We have also added new sensor channels for hidden updates.

Fixed

Server


API

The API call for historic data provides correct raw values again.

PhantomJS

We have updated PhantomJS to the current version. PRTG uses PhantomJS to generate PDF reports and screenshots for the HTTP Full Web Page sensor and support bundles. This update will improve and fix some smaller issues regarding these functionalities.

Schedules

PRTG will now validate the syntax of period lists for schedules to prevent access violations and resulting failures when starting the PRTG server.

Security

We have fixed a small security issue that could result in an access violation showing passwords in clear text in certain cases.

Uptime Threshold

In certain cases, the uptime threshold in the Monitoring settings reverted to the default value after a PRTG server restart. PRTG will now keep your individually set desired minimum uptime.

Fixed

Cluster


Cluster

"Check Now" on failover nodes works again. In previous versions, the action was only executed on the master node.

Fixed

Various


All Parts of PRTG

Various fixes and improvements to all parts of PRTG, including more performance improvements

Manual Update

Updated user manual

Changed

Tree Version


Tree Version Update

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

calendar

February 22nd 2017 – 17.1.29.1402


Fixed

Notifications


Push Notifications

Push notifications in PRTG freeware versions work again. PRTG did not send them out anymore after the trial period has expired.

calendar

February 20th 2017 – 17.1.29.1359


Fixed

Sensors


Citrix XenServer Sensors

Citrix XenServer Host and Citrix XenServer Virtual Machine sensors now close their sessions on the target device to avoid potential instabilities on the XEN host.

Custom Script Sensors

For custom script sensors like the EXE/Script Advanced sensor, you can now provide special characters in custom unit and last message as escape sequences in the returned XML.

NetApp cDOT Sensors

The NetApp cDOT sensors support ONTAP 9.

Python Script Advanced

The Python Script Advanced sensor correctly replaces parameters again.

sFTP Secure File Transfer Protocol

The sFTP Secure File Transfer Protocol now supports the new SSH engine which we introduced with PRTG version 16.2.24 (May 2016).

Note: You can still use the old SSH engine as legacy version by selecting the deprecated “Compatibility Mode” in the sensor or device settings, but we will remove this option soon.

SNMP Custom String

String search in SNMP Custom String sensor results also works for raw bytes (like MAC addresses).

SQL Sensors

The change trigger on the notifications tab of SQL sensors is now available. This means that you can actually use the Trigger 'change' notification setting of SQL sensors in combination with a change trigger to receive notifications if the sensor message changes.

SSH Sensors

We have implemented several important fixes and improvements for the default SSH engine that the SSH sensors use to retrieve monitoring data from target devices. SSH sensors will now run more stable and available options like SSH rights elevation will work more reliable. This fix also includes support for special characters (like North Germanic characters) in username and password.

If an SSH sensor returns the error read_password_prompt timeout or read_paessh timeout after you have updated to PRTG 17.1.29, please check your SSH Rights Elevation settings in section Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems of the affected device. Ensure you use the setting that your target device requires and enter your password for 'sudo' or 'su' anew. See this Knowledge Base article for details: https://kb.paessler.com/en/topic/73353

Fixed

Licensing


License Activation

Stability improvements for the changed license activation system

Fixed

WebGUI


Find Duplicates

The Find Duplicates function for devices will not find false positives anymore when the last octet of the IP address has three digits.

Maps

Fixed a small security issue with inactive user accounts

Fixed

Notifications and Schedules


Tags

Tags of notifications and schedules work again, for example, if you use these tags to filter for notifications and schedules in tables. Important: You will lose existing tags (which did not work anyway) for notifications and schedules with this update so you will have to define them anew.

Fixed

Emails


Content-Type

Emails are now delivered with a correct Content-Type. This will help to prevent anti-spam software from blocking emails from PRTG that include PDF reports, for example.

Fixed

Various


All Parts of PRTG

Many other minor improvements and fixes to all parts of PRTG

User Manual

Updated user manual

calendar

February 2017 – 17.1.29


New

Sensors


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.

Improved

Sensors


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.

calendar

December 20th 2016 – Version 16.4.28.7442


Fixed

Sensors


WMI Sensors

Stability improvements for WMI sensors

Fixed

Licensing


License Activation

Stability improvements for the changed license activation system

calendar

November 2016 – Version 16.4.28


Changed

Licensing


License Activation

In this version, we have changed the technology of how PRTG servers are licensed. Most customers will not see any difference. However, as an experienced PRTG user you will notice some improvements and changes.

  • If you want to migrate your installation to another hardware, please deactivate your license first on the existing installation to allow for a hassle-free activation on the new hardware. To do so, go to Setup | License in your PRTG web interface.
  • There is only one PRTG installer now which works for both Freeware/Trial editions and commercial editions, so all editions will have the same version number as of the current version 16.4.28.7260 (as of 16.4.28.7199 in the Preview release channel). Before, the numbers have differed in fourth place (you have seen version information with a slash symbol to reflect this difference between Freeware/Trial and commercial editions in previous release notes).
  • If you run a Freeware or Trial now and you want to upgrade to a commercial edition, you do not have to download and run a commercial installer anymore. Just provide your new commercial license key in the PRTG web interface to upgrade your running PRTG instance to a paid license.
  • We reworked the License page under Setup in PRTG and simplified the process to change and activate a license.
  • If your PRTG server is offline, you can now activate your license immediately and do not have to wait for an email activation response. Offline activation is necessary once in each maintenance period.
  • You cannot run PRTG without activation any more, not even for 10 days.

Improved

Remote Probes


Remote Probe Install

We considerably simplified the installation and configuration process for new remote probes! The remote probe installer will now complete almost all steps automatically.

Just make sure your PRTG core server accepts incoming probe connections, download and run the installer on your remote system, approve the connection, and enjoy your new remote probe in PRTG!

calendar

November 25th 2016 – Version 16.4.28.7199


Fixed

Sensors


DNS

The DNS sensor query type Host address IPv6 (AAAA) works again. This option caused the error message “Record not found (PE112)” in some cases. We also improved IPv6 parsing in general.

EXE/Script and EXE/Script Advanced

The JSON result parser correctly evaluates the ShowChart and ShowTable values and sets these options as returned by your script.

Oracle Tablespace

The Oracle Tablespace sensor now uses the identifier you have set when adding the sensor. You can also define if you want to use SERVICE_NAME as sensor name prefix to distinguish sensors for several databases on the same server more easily.

SNMP Printer

On some HP printer types, adding SNMP Printer sensors could lead to null byte errors in rare cases. This should not happen again.

SSL Certificate

The SSL Certificate sensor can now evaluate Subject Alternative Names (SAN) additionally to the Common Name (CN). Just choose the new option Compare and show 'down' status if common name/alternative names and address/SNI do not match for the Certificate Name Validation sensor setting.

WMI Sensors

Stability improvements for WMI sensors. Timeouts in meta-scans of WMI sensors should not result in crashes anymore.

Fixed

Server


Core/Server

We have fixed a load configuration error that occurred in rare cases when starting PRTG.

Email Delivery

Enhanced error handling in case of failed email delivery

Fixed

Reports


PDF Generation

PRTG uses a correct fallback port now if the default PDF port 8085 is blocked at startup.

Fixed

WebGUI


Tree Map

The Tree Map view refreshes automatically again.

Maps

Stability improvements for maps and the Map Designer

Various

We fixed several other minor issues in the PRTG web interface.

Fixed

Various


Languages

Updated language files

User Manual

Updated PRTG user manual

All Parts of PRTG

Many other minor improvements and fixes which didn’t make it on this page.

calendar

October 4th 2016 – Version 16.3.27.6635/6636


Fixed

Security


Core/Server

Minor security fix

calendar

October 2016 – Version 16.4.27


Important

Sensors


SSL Security Check

We changed the behavior of the SSL Security Check sensor and adjusted its TLS 1.0 security rating! It will show a warning status (weak security) for accepted TLS 1.0 connections as of the previous PRTG version 16.3.26.

Please see this article for more information: How do you determine the protocol security ratings of the SSL Security Check sensor?

Improved

Sensors


Removed Beta Status

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

  • Business Process Sensor
  • Common SaaS
  • HTTP Data Advanced
  • HTTP Push Data Advanced
  • NetApp cDOT I/O (SOAP)
  • NetApp cDOT Physical Disk (SOAP)
  • NetApp cDOT System Health (SOAP)
  • Oracle Tablespace
  • SNMP Cisco UCS Physical Disk
  • SNMP Custom Advanced
  • SNMP Custom Table
  • SNMP Dell EqualLogic Logical Disk
  • SNMP Dell EqualLogic Member Health
  • SNMP Dell EqualLogic Physical Disk
  • SNMP Juniper NS System Health
  • SNMP Printer
  • SSL Security Check

Improved

Server


Core/Server

Performance and stability improvements for large PRTG installations

calendar

September 29th 2016 – Version 16.3.27.6608/6609


Fixed

Sensors


Cisco IP SLA

The Cisco IP SLA sensor shows correct values again.

EXE/Script

Security fix for the EXE/Script sensor

GitLab Build Status

Several improvements and fixes for the GitLab Build Status sensor

NetApp cDOT

Several improvements and fixes for the NetApp cDOT sensors

SNMP NetApp Disk Free

The Inodes Free channel shows correct values now. Under some conditions, this channel displayed wrong values due to an overflow in the calculation.

Fixed

WebGUI


Sunburst

You can zoom in and out the sunburst view again. Additionally, you can change the position of the sunburst via drag and drop.

Fixed

Maps


Map View

Fixed potential “line too long” errors which have occurred in some scenarios

Fixed

Various


Various

Several other minor fixes and improvements to all parts of PRTG, as well as an updated user manual

calendar

September 9th 2016 – Version 16.3.26.6159/6160


Fixed

Sensors


Channels

Rounding small channel values is more accurate now.

Cisco IP SLA

Stability improvements

Citrix XenServer

Citrix XenServer Host and Citrix XenServer Virtual Machine sensors support Xen7.

HTTP Advanced

The HTTP Advanced sensor uses correct decimal separator also in compatibility mode.

HTTP Push

Stability improvements for HTTP Push Count, HTTP Push Data, and HTTP Push Data Advanced sensors.

HTTP Transaction

The HTTP Transaction sensor now sets the correct status derived from the keyword check.

Hyper-V Cluster Shared Vol. Disk Free

Stability improvements

NetFlow Sensors

NetFlow sensors now support flow traffic from ASA version 9.1 and higher.

Python Script Advanced

Security fix for the Python Script Advanced sensor

SNMP Cisco System Health

The SNMP Cisco System Health sensor shows correct values which match the values from the target device.

SNMP Dell EqualLogic Logical Disk

The SNMP Dell EqualLogic Logical Disk sensor finds now also volumes without assigned groups/members.

SQL v2

SQL v2 sensors support whitespaces and tabulators in declare queries.

In the sensor message of SQL v2 sensors, the placeholder {0} is replaced by the defined table value again and will not just return "Ok".

SSH INodes Free

The SSH INodes Free sensor shows now an error message instead of 0% in case of an error.

Windows Physical Disk I/O and WMI Logical Disk I/O

Both sensor types now show decimal places. The unit of the channel values has changed to ms to receive more detailed values. Please add the sensor anew to see this change.

Fixed

Server


Config

Stability improvements for the configuration file. In certain cases, the PRTG server could not start because of NULL bytes in the config.

Tickets

PRTG will now check the ticket database on startup and once a day, try to repair it if it is corrupted, and tell you about such an event.

Changed

Tree Version


Tree Version Update

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

Fixed

Various


All Parts of PRTG

Many other minor improvements and fixes to all parts of PRTG!

calendar

September 2016 – Version 16.3.26


Important

Sensors


SSL Security Check

We changed the behavior of the SSL Security Check sensor and adjusted its TLS 1.0 security rating! It will show a warning status (weak security) for accepted TLS 1.0 connections as of this version.

New

Sensors


GitLab Build Status

The new GitLab Build Status BETA sensor monitors the status of the latest build on one specific branch. You can monitor your builds in either your own GitLab environment or on GitLab.com!

WMI Microsoft SQL 2016

You can now use the new WMI Microsoft SQL Server 2016 sensor to monitor the performance of your MS SQL Server 2016 instance!

New

WebGUI


Logout Countdown

If you have defined an automatic logout from the PRTG web interface for PRTG user accounts because of inactivity, the logout countdown appears now with a nice graphical display one minute before the actual logout.

Improved

Maps


Map Designer

You can now undo and redo up to 50 changes when working on a map. Changes are saved persistently in your configuration, so you can even revert changes later.

Public Maps

You can now disable links on public maps with a dedicated maps setting.

Improved

Sensors


Amazon CloudWatch

Amazon CloudWatch sensors include the AWS region Asia Pacific (Mumbai).

Folder

We improved the sensor usability: The down and warning states for the file age check are now based on channel limits so the sensor will still receive data if this check fails by definition. You can still define the setting for the file age check when adding the sensor, but for existing sensors please use channel limits.

IMAP

We changed the way settings look like for a better understanding of their functionalities. Note that we did not change any functionality.

Meta-Scans

As an advanced PRTG user, you can now write your own generic meta-scan for any sensor type. For details, please see this article: https://kb.paessler.com/en/topic/70882

SSL Certificate

The SSL Certificate sensor supports SOCKS5 proxy. We also improved the certificate validation and the sensor shows Common Name and certificate thumbprint in the sensor message.

SSL Security Check

The SSL Security Check sensor supports SOCKS5 proxy. TLS 1.0 is now considered to be insecure.

WMI Sensors

Various performance and stability improvements for WMI sensors.

WMI Volume

Template support for the WMI Volume sensor.

Improved

Notifications


HTTP-based Notifications

HTTP notifications and notifications based on custom SMS providers support SNI.

Improved

Security


Encryption

Improved encryption for PRTG connections with a fallback mechanism for some sensor types to support stricter configurations which exclude TLS 1.0 entirely.

PRTG Administration Tool

Files are uploaded via FTPS now.

Changed

Mobile Web GUI


Removed Mobile GUI

As announced in previous versions, we have finally removed the Mobile Web GUI from PRTG. After you have updated to this version, you will not be able to access PRTG via this interface. Please see this article for details: https://kb.paessler.com/en/topic/66920

calendar

September 5th 2016 – Version 16.3.25.6069/6070


Fixed

Sensors


SNMP Trap Receiver

Bugfix for problematic UDP messages.

Fixed

Core


Reports

In some configurations, graphs where missing in (historic data) reports.

Core

Stability improvements.

calendar

July 27th 2016 – Version 16.3.25.5335/5336


Important

Maps


Geo maps

We are currently rerouting the map requests from MapQuest to Nokia Maps.

Fixed

Security


Server

We fixed a potential CBC cipher vulnerability (CVE-2016-2107) by disabling the AES-NI extension ("Intel Advanced Encryption Standard Instructions"). Older browsers and other clients which do not use GCM ciphers may lose performance per CBC calculation because of this fix. This fix also includes the library update to OpenSSL version 1.0.1t

Webgui

We fixed a potential XSS vulnerability: This XSS exploit has been only possible when accessing the PRTG web interface with Firefox. See this article for details about Firefox and security: How secure is it to access the PRTG web interface with Firefox?

Fixed

Sensors


SSL Certificate

The SSL Certificate sensor shows a down status now if "Certificate Name Validation" fails (common name check).

SNMP Trap receiver

SNMP Trap Receiver sensors display received trap messages with line breaks and final 0 correctly again. As before, zeros within texts will be displayed as hexcode.

Fixed

Maps


Access rights

PRTG users with sufficient access rights can view maps correctly again. The map refresh caused an incorrect access rights error for certain PRTG user groups before.

Fixed

Probe System


Stability

Several minor fixes and improvements for probe stability and WMI

Changed

Licenses


License Names

We changed the license name of PRTG Unlimited to PRTG XL1 and replaced the license PRTG 5 Core Global with PRTG XL5. PRTG XL1 allows an unlimited number of sensors on 1 core server installation, PRTG XL5 on 5 core servers worldwide. Please consider the PRTG system requirements for installations with many sensors.

calendar

June 29th 2016 – Version 16.2.25.4709/4710


Fixed

Probe System


Performance

Optimized pipe handling of EXE based sensors

SSH Engine

Fixed AV in SSH dll

Fixed

Reports


Graphs

Historic data reports display graphs again. In certain cases PRTG used an incorrect address to load graphs.

Fixed

Sensors


Cisco IP SLA

Fixed an error that caused a down status of the Cisco IP SLA sensor in certain cases.

HTTP Advanced

HTTP Advanced sensor now correctly escapes quotation marks when used in the sensor settings.

Oracle SQL v2

Fixed an issue caused by the connection encryption of the Oracle SQL v2 sensor.

SNMP Custom Table

SNMP Custom Table sensors now use the correct identification column even if you add them via auto-discovery without having an MIB available.

SNMP SonicWALL VPN Traffic

Fixed auto-discovery with the default device template for the SNMP SonicWALL VPN Traffic sensor.

SNMP Synology System Health

The SNMP Synology System Health sensor works also on target devices with missing temperature OID.

SNMP Traffic

Improved port name update and handling of very large traffic counters.

SQL v2 Sensors

SQL v2 sensors can handle float values. Furthermore, the enabled “Count table row” option does not cause an error anymore when 0 rows are returned.

Various Sensors

Fixed debug option (“Write Result to Disk”) for several sensor types.

Various Sensors

Improved encoding method for various sensor types:
  • Amazon CloudWatch sensors
  • NetApp cDOT sensors
  • Radius v2
  • SQL v2 sensors

Improved

Various


All Parts of PRTG

Many other minor improvements and fixes to all parts of PRTG

SNMP Sensors

We removed the “SNMP Debug Log” option to avoid filling the whole disk on the probe system by accident.

calendar

August 2016 – Version 16.3.25


Important

Sensors


Deprecated Sensors

As announced in previous PRTG versions, we have removed deprecated sensor types from PRTG. Running sensors of this type will stop monitoring and show a down status as soon as you update to this version. Please see this article for details: The PRTG Sensor Cleanup
Note: The deprecated sensor types ADO SQL, Microsoft SQL, MySQL, and Oracle SQL will continue monitoring (now using the new SQL engine in the background) and keep their configuration. Please see this article for details: Migration Path for Deprecated SQL Sensors

Changed

Notifications


Notification Summarization

PRTG collects up to 25 email notifications per defined gathering interval and sends the summarization as soon as this number is reached. Because of this, you may receive more than one summarization per gathering interval. The reason for this change is that some email clients have issues with long (HTML) emails.

Improved

Sensors


HTTP Sensors

HTTP sensors added by the auto-discovery are now named HTTP, HTTP (8080), or HTTPS depending on the connection to the target device. This helps to distinguish automatically added HTTP sensors at one look.

Oracle Tablespace

The Oracle Tablespace sensor includes new channels for “Database Size” (current size of the database) and “Database Size on Disk” (managed tablespace).

SQL v2 Sensors

You can now use placeholders in SQL query files of SQL v2 sensors (@prtg for Microsoft SQL, MySQL, PostgreSQL, :prtg for Oracle SQL, ? (question mark) for ADO SQL). Provide the input parameter in the sensor settings and PRTG will replace the placeholder in the SQL query. This is a great option if you use many SQL sensors where the queries differ in only one parameter!
Furthermore, a change trigger is available for changing sensor messages of SQL v2 sensors.

Windows Network Card

The Windows Network Card sensor can show more data now, including 64-bit counters, virtual network interfaces, teamed adapters, and virtual connections (for example, VPN).

Improved

System Information


Software Table

The software scan now always uses credentials set for the device’s parent probe.

Hardware Table

The hardware table shows the RAM of the device.

Improved

Maps


Maps Design

Connection lines between objects on maps can now show colors for all object states.

calendar

June 8th 2016 – Version 16.2.24.4281/4282


Fixed

Various


SSH Sensors

Major fixes for the new SSH engine

Syslog Sensor

Fixed potential deadlock of Syslog sensor

calendar

May 30th 2016 – Version 16.2.24.4105/4106


Fixed

Various


SSH Sensors

Compatibility fixes for the new SSH engine

Probes

Stability improvements for PRTG probes

Security

Fixed a potential XSS vulnerability and other minor security fixes

WebGUI

Several minor fixes for the PRTG web interface

Notifications

Stability improvements for email notifications

calendar

May 13th 2016 – Version 16.2.24.3809/3810


Fixed

Sensors


SQL v2

SQL v2 sensors work again when you use SQL server authentication. These sensors showed an error in the previous PRTG version.

Cisco IP SLA

ECHO monitoring with the Cisco IP SLA sensor works again. These sensors showed an error in the previous PRTG version.

Fixed

Auto-Discovery


Performance

Fixed performance impact that occurred in certain cases when running the auto-discovery

Fixed

WebGUI


Login

Auto-complete of username and password on the login page works again.

Various

Several other minor fixes for the PRTG web interface

calendar

May 4th 2016 – Version 16.2.24.3623/3624


Fixed

Various


Core/Server

Several minor fixes

calendar

May 2016 – Version 16.2.24


New

System Information


System Information

You can now view system information for all devices that PRTG monitors (when PRTG has the appropriate credentials). The devices can be either a supported Windows version or they have SNMP enabled to get information data.

Open the "System Information" tab on a device overview page and see what hardware and software is installed, what processes and services run on this computer and which user accounts are logged in. Together with your day-to-day monitoring you get a really profound knowledge about your IT infrastructure by using only one source—your PRTG Network Monitor!

New

Sensors


SNMP Dell EqualLogic

This version comes with three new sensor types for EqualLogic monitoring! Native support for EqualLogic monitoring has been demanded by many of our customers so we are glad that we can offer this feature to you now. You can monitor logical disks, physical disks, and the health of storage array members with three dedicated sensor types:

  • SNMP Dell EqualLogic Logical Disk
  • SNMP Dell EqualLogic Member Health
  • SNMP Dell EqualLogic Physical Disk

ADO SQL v2

The new ADO SQL v2 sensor can monitor any data source that is available via OLE DB or ODBC. It is the successor of the deprecated ADO SQL sensor.

Windows Physical Disk I/O

The new Windows Physical Disk I/O sensor monitors input/output operations on a disk.

Important note: This sensor type supersedes the Windows Physical Disk sensor which is deprecated as of now and will be removed with the next PRTG version. Please replace the deprecated sensor with the new Windows Physical Disk I/O sensor!

WMI Logical Disk I/O

The new WMI Logical Disk I/O sensor monitors logical disks on a Windows device.

Important note: This sensor type supersedes the WMI Logical Disk sensor which is deprecated as of now and will be removed with the next PRTG version. Please replace the deprecated sensor with the new WMI Logical Disk I/O sensor!

Improved

Sensors


SSH Sensors

SSH sensors use a new SSH library to provide best performance and security.

Note: You can still use the old SSH engine as legacy version by selecting the deprecated “Compatibility Mode” in the sensor or device settings, but we will remove this option soon.

Beta Sensors

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

  • Cloud HTTP
  • Cloud Ping
  • SSL Certificate
  • VMware Datastore (SOAP)

Amazon CloudWatch

Amazon CloudWatch sensors support the region Asia Pacific (Seoul).

SNMP CPU Load

You can now store limits of the SNMP CPU Load sensor's “Total” channel into device templates.

SQL v2

SQL v2 sensors have now the option to count table rows which a SELECT statement returns. You can also use @-variables in your SQL statements as of this version.

Changed

Placeholders


Status Placeholder

We removed the %state placeholder because it duplicated the %status placeholder. Please check your notifications and change this placeholder to %status if necessary.

calendar

May 3rd 2016 – Version 16.2.24.3615/3616


Improved

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.

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

calendar

April 14th 2016 – Version 16.2.23.3265/3266


Fixed

Core/Server


Setup

We fixed the PRTG setup that crashed under certain circumstances.

Fixed

Sensors


WMI Free Disk Space (Multi Disk) Sensor

Limits that you define in the sensor settings work again.

calendar

April 8th 2016 – Version 16.2.23.3163/3164


Improved

Languages


Updated Language Files

Updated language files for French, Chinese, Russian, Spanish, and Brazilian

Fixed

Various


Server/WebGUI

Various minor fixes and improvements

calendar

April 2016 – Version 16.2.23


Changed

Sensors


Deprecated Sensors

The following sensor types are deprecated as of now, you cannot add them any more, and they will be completely removed with the upcoming PRTG version 16.x.25, due out in about 2 months. Sensor types which have been deprecated already before will be removed as well.

  • ADO SQL
  • AVM FRITZ!Box WAN Interface v2
  • INI File Content Check
  • Microsoft SQL
  • MongoDB System Health
  • MySQL
  • Oracle SQL
  • Passive Application Performance
  • Pingdom
  • POP3 Email Count
  • SCVMM Host
  • SCVMM Virtual Machine
  • SNMP GSA System Health
  • Virtuozzo Container Disk
  • Virtuozzo Container Network
  • WBEM Custom
  • Windows Last Update (Remote Registry)
  • Windows Logged In Users
  • Windows Registry
  • Windows Scheduled Task
  • WMI Volume Fragmentation
  • WMI Windows Version

Please see this article for details: The PRTG Sensor Cleanup

SNMP Custom Lookup

We renamed the sensor type "SNMP Custom Lookup" to SNMP Custom String Lookup sensor. The new name indicates the intended usage of this sensor in a better way.

Improved

Sensors


Core Health

The Core Health sensor includes two new channels that will help you to keep your PRTG installation up-to-date (and safe, for example, by always having all security updates installed):

  • The number of days until your software maintenance expires
  • The number of days since the last update of your PRTG installation

Beta Sensors

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

  • Enterprise Virtual Array
  • Microsoft SQL v2
  • MySQL v2
  • Oracle SQL v2
  • PostgreSQL

SSL Security Check

The SSL Security Check sensor supports SNI: You can define it in the sensor settings.

HTTP Sensors

For HTTP sensors you can now define if you want to inherit the SNI from the parent device or if you want to determine the SNI from the sensor URL setting only. For more information about SNI handling in PRTG, please see this article: https://kb.paessler.com/en/topic/67398

Improved

Maps


Maps Designer

We added a new icon set for maps and HTML settings are now better reachable in the maps designer.

calendar

March 22nd 2016 – Version 16.1.23.2839/2840


Fixed

Sensors


Exchange Database/SQL v2

Channel Unit Configuration for Exchange Database (Powershell) and SQLv2 sensors is now available.

Exchange Database DAG

Exchange Database DAG (Powershell) sensors now properly work on Exchange 2010 and Exchange 2013 with the latest updates.

EXE/Script Advanced

Metascans for custom EXE/Script Advanced sensors support PowerShell scripts in addition to exe-files.

HTTP XML/REST Value

  • Security fix for the HTTP XML/REST Value sensor
  • To support whitespaces in nodes of JSON files they are now converted to underscores (_). For example, if you want to search for "some node", you need to enter "some_node" into the node setting field.

jFlow

jFlow sensors correctly use the fields SenderIP, InboundInterface, OutboundInterface, SourceASI, and DestinationASI again.

Microsoft SQL v2

Microsoft SQL v2 sensor interprets Boolean values correctly.

Oracle Tablespace

Oracle Tablespace sensor now uses the timeout setting in the parent device (section “Credentials for Database Management Systems”).

SNMP Cisco System Health

SNMP Cisco System Health sensor can recognize 64-bit memory counters.

SNMP Custom String

SNMP Custom String sensor supports 0 bytes in MAC addresses.

SNMP Custom Table

SNMP Custom Table sensor supports custom OIDs in the name template.

SNMP Linux Disk Free

SNMP Linux Disk Free sensor supports very large partitions/volumes.

SNMP Printer

SNMP Printer sensor no longer duplicates channels after a PRTG server restart.

SNMP RMON

Improved handling of SNMP v1 by the SNMP RMON sensor

SNMP Traffic

SNMP Traffic sensors update interface names correctly if the target device returns "No such object" instead of "No such name"

SNMP Trap Receiver

SNMP Trap Receiver sensor now supports hex content (MAC addresses). The sensor did not show trap content in this case before.

VMware Virtual Machine

VMware Virtual Machine sensor shows latency channels again. These channels were missing on some systems.

Channels

Difference channels of sensors show correct historic data when the probe reconnects instead of zero values. Recalculate the PRTG graph data cache under "Administrative Tools" in the PRTG web interface to fix affected historic data.

Templates

Device templates include value lookups of multi-channel sensors now.

Fixed

Various


Auto-Discovery

Several improvements and fixes for auto-discovery groups

Notifications

Several improvements and fixes for email notifications

Lookups

Fixed historic data for range-based lookups

Maps

Public maps which use the data table map object "Tickets" are now accessible.

Security

Access rights for manually added objects are now shown correctly in the PRTG web interface. Display and actually used rights were inconsistent in some cases.

WebGUI

Many small fixes for the PRTG web interface

Improved

Various


API

We added the new API calls getticketstatus.htm and getticketmessage.htm. You can now also use the parameter subtype for the API call setobjectproperty.htm to set, for example, channel properties.

Manual

Updated user manual

Core/Server

Many other minor improvements and fixes

calendar

March 14th 2016 – Version 16.1.22.2681/2682


Fixed

Various


Cluster

Sensors with dynamic channels show data again when you add them to remote probes with enabled cluster connectivity.

Enterprise Console

The Enterprise Console shows its usual performance again.

Core/Server

Various minor fixes and improvements

calendar

March 2nd 2016 – Version 16.1.22.2415/2416


Improved

Languages


Updated Language Files

Updated language files for Brazilian, French, Russian, Chinese, Spanish

Fixed

Enterprise Console


Favorite Sensors

Fix for traffic and trap sensors that are flagged as "favorite" in the Enterprise Console

Fixed

Various


Core/Server

Several minor fixes

calendar

February 24th 2016 – Version 16.1.22.2267/2268


Fixed

Various


Notifications

Channel tables and icons in HTML email notifications are shown correctly again.

Reports

Scheduled reports are sent out to PRTG user groups again.

Packet Sniffer/Flow Sensors

Filters for Packet Sniffer and Flow sensors work correctly again.

WMI Sensors

Fixed scan exception in ntdll for WMI sensors

Core/Server

Improved scheduler

calendar

February 15th 2016 – Version 16.1.22.2015/2016


Fixed

Core/Server


Minor Fixes

This is a maintenance release with several minor fixes.

calendar

February 12th 2016 – Version 16.1.22.1983/1984


Fixed

Core/Server


Minor Fixes

This is a maintenance release with several minor fixes.

calendar

February 11th 2016 – Version 16.1.22.1919/1920


New

Reports


Data Files

You can now generate CSV and XML data files along with the PDF file of a report for its data tables. This is a great option to import data into other programs!

PDF Generator

We added a new PDF generator for reports to PRTG.


New

Sensors


Docker Container Status BETA

The new Docker Container Status BETA sensor monitors status, uptime, exit code, CPU usage, and memory of a Docker container.
Note: To use this sensor type in PRTG, you have to provide certificate and private key to request data from your Docker instance. Please see this article for details: https://kb.paessler.com/en/topic/67250

Amazon CloudWatch Alarm BETA

The new Amazon CloudWatch Alarm BETA sensor monitors the status of configured alarms for CloudWatch services via the AWS CloudWatch API.


Improved

Server


Web Server

Performance improvements for the web server

Changed

Core/Server


Certificates

Important: We renewed the certificates with which we sign PRTG. We strongly recommend that you update to this version to be able to seamlessly update to future versions of PRTG.


Improved

Security


Optimizations

We fixed the root cause for the security issue that has been hotfixed with PRTG version 16.1.21.1441/1442. This version also contains various optimizations in context of this security flaw.

Improved

Sensors


Sensor Channels

You can now define a scaling factor (multiplication and division) for values of sensor channels with custom units. You can find this option in the respective channel settings. Note: Sensors with a scaling option in the sensor settings do not provide this option in channel settings. There are also some other sensors with custom units that do not support this feature.

EXE/Script Advanced

The EXE/Script Advanced sensor can now make use of a meta-scan functionality. For details please see this article: https://kb.paessler.com/en/topic/68109

HTTP Transaction

HTTP Transaction sensor shows the URL of the page that provokes a warning or error status in the sensor message.

SSL Certificate

Newly added SSL Certificate sensors have limits for the “Days to Expiration” channel by default. This sensor type has also an improved logging (“Write result to disk”). With this option enabled certificates of the cert chain are additionally logged for better debugging possibilities, especially for the “Root Authority Trusted” channel.

SNMP Cisco System Health

Improved performance for the SNMP Cisco System Health sensor

SNMP Sensors

SNMP sensors now use paging for SNMP requests to improve their stability.

Windows Updates Status (Powershell)

You can define a custom port for the Windows Updates Status (Powershell) sensor.

WMI/Windows Sensors

All WMI/Windows sensors provide a debug option.


Changed

WebGUI


Options

We removed the outdated option to automatically refresh whole PRTG pages from the account settings. By default, PRTG only refreshes single page elements. You can still disable auto refresh completely.

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.

SNMP Custom Advanced

OIDs for the SNMP Custom Advanced sensor support can start with points (.)

SSL Certificate

Adding the SSL Certificate sensor using a device template works correctly.

SNMP Cisco System Health

SNMP Cisco System Health can show negative values.


Fixed

Notifications


Placeholders

Placeholders in notification emails were not replaced correctly in certain cases.


Improved

Various


Lookups

Stability improvements for custom lookups

Manual

Updated user manual

Languages

Updated language files

All Parts of PRTG

Many small fixes and improvements for web interface, Enterprise Console, and all other parts of PRTG