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



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.


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.


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!


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.


Blog article


By Sascha Neumeier • Jun 18, 2018
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.

Changed

WebGUI


Context Menus

We removed the right-click context menus from the overview pages of libraries, maps, and reports.

Settings

We removed the user account settings Max. Groups/Devices per Group and Max. Sensors per Device that defined when to collapse nodes in the device tree, because PRTG automatically handles this.

Fixed

Security


API

We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to Positive Technologies, especially to Dmitry Galecha. Thank you!

Reports

We fixed 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


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


Blog article


By Sascha Neumeier • May 21, 2018
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.


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!


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


Blog article


By Sascha Neumeier • Mar 28, 2018
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!


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


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.


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.


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.


Blog article


By Sascha Neumeier • Feb 27, 2018
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.


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


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


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


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.


Fixed

WEBGUI


Geo Maps

This version includes another fix for Geo Maps.


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.


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


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.


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.


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.


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


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.


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.


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.


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


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


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


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


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.


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.


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.


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


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.


Fixed

Sensors


WMI Sensors

Stability improvements for WMI sensors

Fixed

Licensing


License Activation

Stability improvements for the changed license activation system


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!


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.


Fixed

Security


Core/Server

Minor security fix


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


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


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!


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


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.


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.


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.


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.


Fixed

Various


SSH Sensors

Major fixes for the new SSH engine

Syslog Sensor

Fixed potential deadlock of Syslog sensor


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


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


Fixed

Various


Core/Server

Several minor fixes


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.


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


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.


Improved

Languages


Updated Language Files

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

Fixed

Various


Server/WebGUI

Various minor fixes and improvements


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.


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


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


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


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


Fixed

Core/Server


Minor Fixes

This is a maintenance release with several minor fixes.


Fixed

Core/Server


Minor Fixes

This is a maintenance release with several minor fixes.


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