Release Notes
for PRTG 18

Software versions in this channel are not updated anymore.
Please consider upgrading to the latest "stable" version.

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

Manual: "Software Auto-Update" · Other Release Channels

December 11th 2018 – Version 18.4.47.1962

Important

Known Issue: PRTG Update

Updating from version 18.1.37 or older

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

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

Status: resolved with PRTG 19.1.48.2868

Improved

WebGUI

Notifications	You can now see all defined notification methods in your PRTG user account settings at a glance. The Notification Templates overview table has a new column that shows the Actions a notification template will perform when it is triggered. You can now use a search field to filter for existing notification templates when you add or edit a Notification Trigger.
Maps	We improved the readability of map objects with status-related background colors.

Improved

Server

PRTG Core Server	Several performance and stability improvements for the PRTG core server
Graphs	We updated the engine that PRTG uses to create data graphs. Thanks to the updated graphs engine, stacked graphs look better now!
Logging	This version includes some more improvements for the logging framework.

Improved

Sensors

HTTP Push Data Advanced	The HTTP Push Data Advanced now supports UTF-8 characters in the section of received messages and can display, for example, Chinese, Japanese, or Russian characters in the sensor message.
SNMP Trap Receiver	The SNMP Trap Receiver sensor now supports several modes for bindings that you can use with the syntax bindings[oid,value,mode]. Mode can be: substring: This is the default mode that works like bindings[oid,value]. exact: This mode enforces an exact match of a value. equal, greater, greaterorequal, less, lessorequal: This mode compares received numbers with the defined value.
Windows Updates Status (PowerShell)	We changed the approach of the Windows Updates Status (PowerShell) sensor to avoid down states that are not meaningful enough. As of the current PRTG version, the sensor will always create the channel Time since last update. All other channels only show up if the sensor can retrieve according data. Furthermore, the channel value is more accurate now.

Fixed

Server

PRTG Core Server	We fixed an issue with the PRTG core server. In certain cases, the issue lead to access violations in the PRTG server system that could result in issues with sending notifications or unexpected server restarts with sensors in unknown status.
PRTG GUI Starter	We fixed several issues with the PRTG GUI Starter. It will work more reliable now.
Security	We fixed a possible XSS vulnerability.
Server Startup	We fixed an issue with the flowid field in toplists of NetFlow sensors that could result in an exception during the startup of the PRTG server. The PRTG server did not start in such cases.

Fixed

Sensors

Channels	You can edit channel names in a sensor's channel settings again (where supported). In previous versions, the Name field in the channel settings often was read-only by mistake. If you select the Data option Display in percent of maximum in the settings of a sensor channel, PRTG will now interpret any set Limits as percentage based on the maximum value to avoid false alarms.
Event Log (Windows API)	The Exclude Filter of the Event Log (Windows API) sensor now correctly disregards all events that you have added to the filter, for example, event IDs.
Flow Sensors	Stability improvements for the sensor types IPFIX, NetFlow V5, NetFlow V9, and sFlow: The fields FlowID, InboundInterface, and OutboundInterface in custom toplists are now stored with their field ID. In previous versions, they were stored as index, which could lead to issues when the list of fields changed.
Lookups	Lists of lookup files are sorted alphabetically again when you select value lookups for a sensor channel. IDs of lookups are also loaded case insensitively again to prevent issues when you override default lookups with customs lookups.
Sensor Factory	PRTG correctly calculates historic data of the Sensor Factory sensor again. In the last preview version, live data was used to calculate historic data instead of averages. This resulted in wrong values.
SNMP Custom String Lookup	We fixed an issue with device templates that include an SNMP Custom String Lookup BETA sensor. When running an auto-discovery with the template, PRTG created an unused channel that was not defined for the sensor.
SNMP sensors	SNMP sensors that support this functionality now only replace text within square brackets in the sensor name if the text is an OID or a defined variable. All other text will appear in the sensor name as it is.
SNMP Trap Receiver	The SNMP Trap Receiver sensor now properly handles quotation marks (") in the filter for bindings and can find strings that contain quotation marks.
UPS Health (Generic) Template	The device template UPS Health (Generic) now also supports Tripp Lite UPS, so running an auto-discovery with the template will create suitable sensors for your Tripp Lite UPS.
WMI Sensors	You can now add the sensor types Windows Physical Disk I/O, WMI Exchange Server, WMI Exchange Transport Queue, WMI Logical Disk I/O, and WMI Vital System Data (V2) using the auto-discovery. The auto-discovery could not successfully add these sensor types in previous versions.

Fixed

Notifications

Amazon SNS	We updated the signature version of Amazon SNS notifications to Signature Version 4, so it is now possible to send SNS notifications from AWS regions that only support this signature version like, for example, Canada (Central) (ca-central-1).
SMS	Using the placeholders %SMSNUMBER and %SMSTEXT in the path of custom URLs for SMS notifications works again. Due to an encoding issue, the placeholders only worked in the query string of a URL since PRTG version 18.3.43 and you received an unknown protocol error if your custom SMS provider requires number and text as part of the path.

Fixed

WebGUI

Credentials	We disabled the browser auto-complete of login and password fields in authentication sections of several sensor types (for example, HTTP Advanced and IMAP sensors). If you have saved your PRTG login credentials in your browser, your browser will not automatically fill in the credentials into PRTG settings sections anymore.
Tables	Paging on large tables and the selection of table items in the Add Sensor dialog works properly again. In previous versions, only sensors selected on the current table page were created.
Various	Several other minor fixes and improvements for the PRTG web interface

Fixed

API

XML	We fixed an issue with invalid XML returned by the PRTG API. For example, if a sensor included non-XML compliant characters in the sensor or log message and you requested the sensor via the PRTG API, this resulted in an error with the message cannot convert value.

Fixed

Various

Language Files	Major update for all language files!
All Parts of PRTG	Various other fixes and improvements to all parts of PRTG, updated user manual

Note

Probe and Sensors

.NET Version

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

November 20th 2018 – Version 18.4.46.1754

Blog article

By Sascha Neumeier • Nov 30, 2018

All You Need to Know About PRTG Release 18.4.46

The closer we get to the end of the year, the faster time seems to fly. It feels like just the other day we were stumbling over pumpkins and being scared by our next-door children with "trick or...
Read the complete blog post here

Fixed

Sensors

SNMP Traffic

We fixed an issue with the SNMP Traffic sensor that could lead to false spike values in certain cases. Please update your PRTG installation if you run one of the affected PRTG versions 18.4.46.1706 or 18.4.46.1736.

November 14th 2018 – Version 18.4.46.1736

Fixed

Sensors

SNMP System Uptime

The SNMP System Uptime sensor shows correct uptime values again. In the previous PRTG version 18.4.46.1706, uptime values were wrong by the factor of 10 in certain cases.

November 7th 2018 – Version 18.4.46.1706

Improved

Server

PRTG Status	You can now see the names of all PRTG user accounts that are currently logged in to your PRTG instance! Open the PRTG System Status page in the web interface via the main menu (Setup \| PRTG Status) and look at section Software Version and Server Information. There is the new entry Active User Sessions that shows all currently logged in PRTG users.
Remote Probes	Remote probes now always keep their defined names. In certain cases, the name of a remote probe changed to the host name after manually updating the probe.
PRTG Server	This version includes several stability and performance improvements for the PRTG server. For example, we dramatically improved the startup time especially with bigger configuration files, we reduced the memory usage of the core server after startup and after the configuration was saved, and we improved the performance of the website response a little.
Web Server Connections	The PRTG web server will now keep the option that you defined as IP address for the web server even if no IPs were found on the stack after a PRTG core server restart. In certain cases, usually after Windows updates, this resulted in the error No IPs could be found on the stack - reverting web server to local host after the core server started and the web server connection setting permanently switched to localhost.

Improved

Sensors

Amazon CloudWatch

We added the new regions US East (Ohio), EU (Paris), and Asia Pacific (Osaka-Local) to all Amazon CloudWatch sensors. You can use the new regions with the sensor types Amazon CloudWatch Alarm, Amazon CloudWatch EBS, Amazon CloudWatch EC2, Amazon CloudWatch ElastiCache, Amazon CloudWatch ELB, Amazon CloudWatch RDS, Amazon CloudWatch SNS, Amazon CloudWatch SQS.

SNMP System Uptime

We improved the fallback mechanism of the SNMP System Uptime sensor. The sensor uses the hrSystemUptime OID to retrieve the uptime value and uses sysUpTimeInstance as fallback if hrSystemUptime is not available (see also this article).

If both are not available, the sensor will show a down status until at least one uptime OID is available. If both are available again, the sensor will use the preferred hrSystemUptime. In previous versions, the sensor used the fallback sysUpTimeInstance in this case.

Changed

API

JSON

PRTG now returns strings from _raw columns surrounded by quotation marks ("") when you request JSON output, numbers still will be returned without quotation marks. In previous versions, quotation marks were missing for strings, which resulted in some issues because this was not common JSON. Please adapt your usage scenario of the PRTG API if necessary.

Example: "uptimetime":"642 d","uptimetime_raw":55492731

XML

The PRTG API now returns the correct response content-type header text/xml when you request XML output. In previous versions, the content-type was erroneously set to text/html.

Fixed

Sensors

Amazon CloudWatch Alarm	The Amazon CloudWatch Alarm BETA sensor now shows all configured alarms in the Add Sensor dialog. In previous version, some alarms were missing and could not be selected for monitoring.
Debug Options	We fixed an issue with the debug option Write sensor result to disk. In certain cases, some sensors continued writing the log files although the option was turned off again with "Discard sensor result".
DHCP	The DHCP sensor now correctly applies changes to settings. In previous versions, the check for server IP or client IP was still applied if you switched the option to Don't check but kept the entries in the include or must not include fields.
DICOM Bandwidth	The DICOM Bandwidth BETA sensor now shows the correct C-STORE size and correctly calculates the bandwidth usage of sent files.
SNMP NetApp Network Interface	The SNMP NetApp Network Interface sensor now applies the Unit for Bytes (Bandwidth) that you selected in the Channel Unit Configuration settings of the sensor's parent device. In previous versions, the sensor always showed traffic in MByte/s.
SNMP Traffic	We fixed an issue with SNMP Traffic sensors that were not addable to Cisco devices if selected additional channels were not available. PRTG showed the SNMP error #2003 in this case.
SSH Script and SSH Script Advanced	We fixed an issue with the search for scripts when adding an SSH Script or SSH Script Advanced sensor. The sensors were not able to find scripts and show them in the Add Sensor dialog when having certain localizations on target systems, for example, Italian.
WMI HDD Health	We fixed an issue with the WMI HDD Health sensor that occurred when parsing the instance name. The sensor returned an error message like "The query was not syntactically valid." if the WMI property InstanceName included certain characters.

Fixed

WebGUI

IE11 and Edge	Saving changes on setting pages when using Internet Explorer 11 or Edge is possible again. In the previous PRTG version 18.4.45, clicking save resulted in a saving window that did not disappear and the settings could not saved.
Various	Several minor fixes for the PRTG web interface

Fixed

Various

Lookups	We fixed an issue with the PRTG server where access violations regarding lookups resulted in missing channels of some sensors. This only happened under certain circumstances.
All Parts of PRTG	Various other fixes and improvements to all parts of PRTG, updated user manual (including API documentation for System Information), updated language files

Note

Installer

Trial Installation

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

October 19th 2018 – Version 18.4.45.1898

Blog article

By Sascha Neumeier • Oct 31, 2018

PRTG Release 18.4.45 Offers More Tasteful Donuts, Various Improvements and No Halloween Surprise

We are posting this on the 31st of October, so one could generously call the PRTG release 18.4.45 a Halloween special. Of course, that's not quite right, because when we do a blog about a stable...
Read the complete blog post here

Fixed

Sensors

VMware Host Performance (SOAP)

The VMware Host Performance (SOAP) sensor now works with VMware 6.7 Update 1. The VMware update included a change in the API version that VMware Host Performance (SOAP) sensors could not correctly process. Affected sensors showed a down status with the error message Input string not in a correct format.

October 17th 2018 – Version 18.4.45.1889

Improved

WebGUI

Notifications	When you are on the Notification Triggers tab in the device tree, you can now directly open a dialog window to edit a selected Notification Template. This way you stay on the same page if you want to change the properties of a notification, so you do not have to leave the current context or lose settings that you already changed on the triggers tab.
Status Donuts	The legends of status donuts on the PRTG Welcome page and on map objects are now interactive. Click a status icon to directly open a list of sensors filtered by this status!

Improved

Sensors

Oracle Sensors

The sensor types Oracle SQL v2 and Oracle Tablespace now support secure connections to your database system and are compatible with Oracle network encryption.

Improved

Server

Encryption	The encryption method that PRTG uses now supports unicode (UTF-8 characters), for example, in fields for passwords, comments, and for the payload of HTTP notifications. In previous versions, the characters were converted to question marks (??) as soon as they were written to the configuration file (for example, after server restarts).
Logging	This version includes some minor improvements for the new logging framework introduced in PRTG 18.3.43.

Fixed

Sensors

Common SaaS	You can now define the inheritance of Notification Triggers of the Common SaaS sensor. In previous versions, the message (Property not found) was displayed instead of the settings.
Flow Sensors	We fixed an issue with flow sensors. If received flow packets were too big, it was possible that they dropped. In this case, you encountered an increased value of the Probe Health sensor's Lost Flow Packets channel. This issue especially affected IPFIX sensors monitoring a Sophos UTM after an update of the target device.
HTTP IoT Push Data Advanced	The HTTP IoT Push Data Advanced sensor on PRTG hosted by Paessler instances works again.
Sensor Factory	The Sensor Factory sensor will now notify you with an error message if the sensor could not created due to a syntax error in the channel definition. In previous versions, you might not have noticed it when the sensor creation failed.
SNMP Library	PRTG creates tickets again to notify you about newly created lookups when adding SNMP Library sensors.

Fixed

WebGUI

Add Sensor Dialog	The Cancel button in the SNMP Help and WMI Help dialogs that you can open when adding according sensor types fails now works as expected and closes the dialog window without getting stuck.
Map Designer	The scissor symbol in the Map Designer to drop connection lines is available again.
Maps	We fixed an issue with maps that were added to the Home menu using a 5-stars priority and contained a sunburst element. The sunburst was not shown on such "home" maps. We also further improved the appearance of status background colors.
Reports	When selecting sensors manually in the report settings, the channels will now keep their selection even if you change the order of selected sensors. In previous version, the channel selection was reset when moving sensors.
Sensor Gauges	Sensor gauges are now properly displayed when the sensor is paused. In previous versions, the gauges erroneously still showed values and remained green when the sensor, device, or group was paused for x minutes.
Sensor Lists	Mini graphs in sensor lists are immediately displayed again and do not require a page refresh anymore.
Similar Sensors	Similar sensors will not show up anymore on a sensor's overview tab if you have disabled the functionality.
System Administration	Settings on PRTG system administration pages in the PRTG web interface that require a server restart to apply now are only saved if you confirm the server restart when saving changes to the settings. If you cancel the restart when PRTG asks for it, the settings will not be saved. This new behavior will prevent some unwanted side-effects that sometimes occurred when cancelling the restart.
Tables	More improvements for tables: The Messages tab of SNMP Trap and Syslog Receiver sensors now always shows the complete messages without the need to hover over each message. Access rights tables that have more than 1 page because of many PRTG user groups work properly again. In previous versions, saving access rights on page 2 and onward resulted in a reset to None for each group.

Fixed

Various

All Parts of PRTG

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

Changed

Tree Version

Tree Version Update

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

September 26th 2018 – Version 18.3.44.2059

Fixed

Sensors

Exchange Backup (Powershell)

We fixed an issue with the Exchange Backup (Powershell) sensor that resulted in wrong sensor channel values. The issue only occurred in the last PRTG version 18.3.44.2054.

September 24th 2018 – Version 18.3.44.2054

Blog article

By Sascha Neumeier • Oct 8, 2018

PRTG Release 18.3.44 - xFlow Working Again PLUS Numerous Improvements

As promised in the blog post for version 18.3.43, our development team is working diligently on the upcoming releases of PRTG. Since a few days ago, version 18.3.44 is available in the stable...
Read the complete blog post here

Improved

Security

Connections

You can now block TLS 1.0 connections for the PRTG web server. You can also explicitly define a security level for probe connections.

With the high security option for web server connections, only TLS 1.1 and TLS 1.2 connections are allowed for clients, whereas default security additionally allows TLS 1.0. You can define the Connection Security level for the web server in the User Interface settings, section Web Server.

With the high security option for probe connections, only TLS 1.2 connections are allowed for PRTG remote probes, whereas default security additionally allows TLS 1.1. If you update from an older PRTG version to the current PRTG version and your remote probes cannot connect anymore, you can temporarily allow TLS 1.0 and SSL V3 connections as well until all probes are updated. You can define the Connection Security level for probe connections in the Core & Probes settings, section Probe Connection Settings.

By default, all PRTG installations are set to default security that allows TLS 1.0, TLS 1.1, and TLS 1.2 for web server connections and TLS 1.1 and TLS 1.2 for probe connections.

Note: If you have set a registry key in previous PRTG versions to override the SSL version and cipher of PRTG web server connections, the High security setting will override the registry key setting and only TLS 1.1 and TLS 1.2 will be allowed. If you select the Default security setting, the registry key will override the default security setting and the connection security that you have defined in the registry will apply.

Improved

Sensors

Core Health	The Core Health sensor has a new channel Configuration Last Saved that will warn you if PRTG was not able to save the configuration for 26 hours.
NetApp Sensors	The NetApp System Health sensor now supports the storage configuration paths quad_path and quad_path_ha. All NetApp sensors that use SOAP to retrieve monitoring data now support NetApp ONTAP version 9.4.

Improved

WebGUI

Notifications	The "clear condition" for the State Trigger now denotes more clearly in which cases the rule will apply.
Reports	You can run a report another time when you change Run Report settings without reloading the page.
User Group Settings	Improved performance for loading Active Directory groups on the setting pages of PRTG user groups

Improved

Server

API	The API call /getobjectproperty.htm now supports subnodes like, for example, channels, notification triggers, and notification contacts. For example, the call /api/getobjectproperty.htm?id=&subtype=channel&subid=0&name=limitwarningmsg&show=nohtmlencode returns the warning message that is defined for a channel limit.
Auto-Discovery	We improved the device rescan functionality of the auto-discovery. If you have selected the option Skip auto-discovery for known devices/IPs, PRTG will recognize more devices that were already discovered as known and skip the rescan. The improvement is especially useful if host names can be resolved to more than one IP address. You can now start the auto-discovery with template on multiple devices at the same time via device lists and the multi-edit menu. We also fixed some internal errors that occurred during auto-discovery in certain cases.
Logging	This version includes some more improvements for the new logging framework. For example, we fixed an issue that prevented PRTG from writing web server logs in certain cases.
Maintenance	This version comes with a major maintenance increment including multiple changes in all areas of the PRTG core server. The changes lead to minor performance improvements on resource allocation within the data layer of the core server and reduction of file access while serving html pages on the web server.
Security	We fixed the field type of the proxy port field of HTTP sensors and several cases that potentially allowed a malicious administrative user to download content into the filespace of the PRTG probe system. The fixes of these minor issues improve the overall security of PRTG. Special thanks to Anton Vaychikauskas and Dmitry Galecha from Positive Technologies for finding and sharing the issues! (CVE-2018-19204)
Shutdown	Improved shutdown procedure of the PRTG server
Web Server Starter	We fixed a timing issue that resulted in failing automatic starts of the web server in certain cases.

Fixed

Sensors

Exchange (Powershell) Sensors	Stability improvements for Exchange (Powershell) sensors
Flow Sensors	We fixed an issue with xFlow sensors that occurred in PRTG 18.3.43. In certain configurations, the sensor types NetFlow V5, NetFlow V5 (Custom), NetFlow V9, NetFlow V9 (Custom), jFlow V5, jFlow V5 (Custom), sFlow, sFlow (Custom), IPFIX, IPFIX (Custom) did not receive data anymore after you have updated to PRTG version 18.3.43. They turned gray and showed the message "No data received since x minutes." in this case.
NetApp NIC	The NetApp NIC BETA sensor now shows correct traffic values.
NetFlow v9	NetFlow v9 sensors now correctly handle IPv6 flows instead of just showing 0.0.0.0 for IP addresses.
Sensor Factory	The Sensor Factory sensor now correctly calculates values even if the source sensor has been down for some time. In previous versions, the sensor sometimes used very high source values to calculate values according to the formula instead of correctly using 0 values. The Sensor Factory sensor now shows data in graphs and reports even if source sensors are paused for a longer time. In previous versions, graph data was missing in such cases.
sFlow	We fixed an issue with sFlow sensors that did not properly process very high traffic values of inbound and outbound interfaces.
SNMP Sensors	The SNMP timeout of SNMP sensors works again. The OID that you can use as variable in the name of custom and generic SNMP sensors will be replaced with its value again.
SNMP Traffic	The quick action buttons Select all connected interfaces and Select all disconnected interfaces when adding the SNMP Traffic sensor work again.
SSL Certificate	The SSL Certificate sensor now compares the SAN/CN and the device name in a case insensitive way as defined by the RFC. The fix will prevent the sensor from showing false positives when monitoring a certificate.
VMware Datastore (SOAP)	We changed the handling of regional system settings on the Windows system that runs the PRTG probe service with the VMware Datastore (SOAP) sensor. If the decimal symbol defined in the system settings differed from the decimal separator defined by Windows regional settings (for example, comma in number formats but dot via the region format), disk space values were not correctly shown in previous versions.
Windows IIS Application	We fixed an issue with the Windows IIS Application sensor that, in certain cases, resulted in sensor errors after restarting the PRTG server or monitored devices.
Windows Updates Status (Powershell)	Stability improvements for the Windows Updates Status (Powershell) sensor

Fixed

WebGUI

Dependencies Graph	The dependencies graph correctly shows dependencies again. In previous versions, the graph erroneously showed every dependent object as deleted. The functionality of dependencies was not affected by the issue.
Device Tree	Moving devices and groups to other groups via the right-click context menu in the device tree properly works again. You will stay on the current page after the moving action and PRTG will not mistakenly redirect you to an error page anymore.
Internet Explorer 11	Checkboxes in live graphs are correctly displayed again in Internet Explorer 11.
Maps	We did some minor improvements for the layout of device tree map objects and the appearance of status background colors.
Reports	We fixed an issue where volume showed incorrect first and last values in historic data reports if the interval of the report was set too close to the scanning interval of the sensor.
Security	The re-auth dialog on settings pages now appears more reliably and always asks to re-enter credentials after 15 minutes.
Tables	Layout fixes for tables on various places throughout the web interface
Ticket Notification Template	You can properly edit the last line in the Content field of the Assign Ticket notification template again. Clicking the last line will not mistakenly set the default content anymore.

Fixed

Various

All Parts of PRTG

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

August 20th 2018 – Version 18.3.43.2323

Fixed

Update

Direct updates from PRTG version 18.1.37 and previous versions to the current PRTG version work again. It was not possible to directly update to the last PRTG version 18.2.43.2317 from PRTG 18.1.37 or previous because of an issue with the tree version.

August 14th 2018 – Version 18.3.43.2317

Blog article

By Sascha Neumeier • Aug 31, 2018

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

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

Important

Known Issue: NetFlow

NetFlow Sensors

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

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

New

Sensors

HTTP IoT Push Data Advanced

The new HTTP IoT Push Data Advanced BETA sensor displays data from XML encoded messages that are pushed via an HTTP request to the PRTG server, including PRTG hosted by Paessler instances.

It works very similar to the HTTP Push Data Advanced sensor, but we adapted the concept so that you can now push your messages to the hosted probe of PRTG hosted by Paessler. This is especially useful in the context of Internet of Things (IoT), for example, if you want to monitor your Sigfox infrastructure.

Improved

Sensors

NetApp SnapMirror

The NetApp SnapMirror BETA sensor has a new channel that shows the end timestamp of the last transfer. Furthermore, you can now add a NetApp SnapMirror BETA sensor even if there exist relationships that have the same source, which resulted in an error when trying to add the sensor in previous versions.

Improved

Notifications

Notifications	We improved the wording of notifications and notification triggers to help you to better distinguish between the different parts of the PRTG notification system. Notification Templates is the new wording for the section in your PRTG user account settings where you define notification methods and their content (before: "Notifications"). "Triggers" are now called Notification Triggers, for example, the triggers tab on a sensor's or device's page. On the Notification Triggers tab of a monitoring object, triggers now have a Rule that provokes a trigger (the according table heading was "Notifications" before).
Notification Triggers	You can now use Up and Unknown states with the State Trigger.
SMS Delivery	Whitespaces in custom URLs for SMS delivery will now be automatically URL encoded. Important: If you have manually encoded the whitespaces with %20 in previous PRTG versions, you will have to replace %20 with whitespaces for working custom SMS notifications after updating to PRTG 18.3.43.
SMTP Relay Server	It is not possible anymore to explicitly set SSL V2 for SMTP delivery of notifications when using an SMTP relay server. The SSL method will be automatically set to SSL V2 or V3 after updating to PRTG 18.3.43 if you had selected SSL V2 before.

Improved

Server

Logging	We massively improved the logging framework of PRTG to be able to even better support you if you have issues with PRTG. This includes the option to log unusual events (unusual detection) and a change of the logging directory structure (invalidated CVE-2018-17887).
Search	We improved the search speed in the manual that is delivered with your PRTG installation.

Improved

WebGUI

Main Menu	If you use more than 1,000 tags in your PRTG installation, the main menu (Sensors \| By Tag) of the PRTG web interface will not show your tags anymore to improve the performance. You will see an according note in this case and you can still use tags, for example, for filtering and searching.
Maps	You can now control the color mode of public maps via the security context of the map. The public map either uses the light theme or the dark theme depending on the user account that you choose in the map setting Security Context and Color Mode. The Color Mode that this user account has set in the account settings will apply to the public map.
Passhash	PRTG user accounts that were added via Active Directory can now show their passhash in their account settings.

Fixed

Sensors

NetApp System Health	The NetApp System Health sensor now shows the usable spare size and the spare disk count 0 if a NetApp node has no spare disks instead of showing an error.
sFlow and sFlow (Custom)	We improved the handling of incorrectly reported "sample pool" values that caused 0 values for traffic.
SNMP Fujitsu System Health	We fixed an issue that caused SNMP Fujitsu System Health BETA sensors to show an unknown status (gray) in certain cases after running a while. We also fixed minor memory leaks in parts of the SNMP engine used by this sensor type.
SNMP Custom and SNMP Custom Advanced	SNMP custom sensors correctly return negative values again. SNMP custom sensors correctly display speed values again when using delta as value type.

Fixed

WebGUI

Account Settings	The Save button to change the password when logged in with a read-only user account shows up again if the account is allowed to change the password. The button was missing in the last version.
Geo Maps	If you disable the Geo Maps feature, it will now be disabled in all parts of the PRTG web interface. In previous versions, this was not the case and caused timeouts in the web interface when your PRTG server or client was offline.
Internet Explorer 11	Toplists will correctly appear again when you switch time slots. Internet Explorer 11 had issues with that.
Reports	We fixed an issue with CSV reports that caused an empty line at the beginning and at the end of a CSV report for timeframes that were not selected in the settings.
Tables	Access Rights tables on several pages in the PRTG web interface work properly again even if you have a lot of user groups.
Various	Several other minor fixes and improvements for the PRTG web interface

Fixed

Server

API	You can set limits via the according API call again. The API call getsensordetails.json will now return valid JSON even if there are quotes in object names (like sensors, devices, groups, probes).
Security	In certain cases, the passhash appeared in the URL when switching cluster nodes. We fixed the issue.

Fixed

Various

All Parts of PRTG

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

Note

Outdated Windows Versions

Windows Server 2003 R2 and Older

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

July 18th 2018 – Version 18.3.42.1748

Blog article

By Sascha Neumeier • Aug 1, 2018

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

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

Fixed

WebGUI

Maps

We fixed some issues with maps.

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

Fixed

Probe

Memory Leak

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

July 11th 2018 – Version 18.3.42.1727

New

Sensors

WMI Microsoft SQL Server 2017

You can now monitor your Microsoft SQL Server 2017 with PRTG! The new WMI Microsoft SQL Server 2017 sensor monitors your database performance and shows values from SQL General Statistics, Access Methods, the Buffer Manager, the Memory Manager, the Locks Manager, and SQL Statistics.

New

Notifications

Slack and Teams

We introduce two new notification types with this version. You can now send notifications to your Slack and Teams channels! Choose the notification type Send Slack Message or Send Microsoft Teams Message in your notification settings, provide the URL of the webhook you set up, and receive your PRTG notifications with all important information directly in your messenger.

Changed

Geo Maps

Map Service Provider

Google will forbid a keyless access to the geocoding API in future, so PRTG will now use the geocode of HERE Maps by default. Geocoding is used to convert the addresses that you enter in the Location (for Geo Maps) settings into geographic coordinates to show the position of your monitoring objects on the geo map.

If you still want to use the geocoding API of Google, you have to enable your Maps Static API access key for the Geocoding API in the Google console as well. For details, please see the Knowledge Base article How do I get a Google Maps API key for use in PRTG?

Improved

Notifications

Send Email

You can now individually define custom sender email addresses and names per email notification! By default, email notifications use the global sender setting that you define in the Notification Delivery settings. Now you have the option in the settings of a notification to use a custom sender that overrides the global sender settings for this notification.

Please note that the outgoing SMTP server must allow the custom email address to deliver the email.

Execute HTTP Action

The notification type Execute HTTP Action now also supports the HTTP methods PUT and PATCH in addition to GET and POST. Choose your preferred HTTP method in the notifications settings and enter the payload that PRTG will transmit to the target URL.

Improved

Sensors

Event Log (Windows API)

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

Improved

Server and Probes

Libraries	You can now individually change the Security Context of your libraries in the library settings. In previous versions, the security context was always defined by the PRTG user account that created the library. The security context will now also apply to notification triggers of libraries, so they only will be provoked for monitoring objects for which the security context is defined.
Monitoring Data	We reduced cases where monitoring data and sensor messages were missing after PRTG server restarts.
System Information	Stability improvements for the System Information feature

Improved

WebGUI

Maps	We updated older map objects to fit better with the new style of the PRTG web interface.

Fixed

Sensors

sFlow	We fixed an issue that resulted in sFlow sensors showing incorrect data. In certain cases, the issue appeared because of an ignored "subid" of the agents.
SNMP CPU Load and Windows CPU Load	SNMP CPU Load and Windows CPU Load sensors correctly show the Total channel as line in the data graph again when using the Graph Type option Stack channels on top of each other. The channel was erroneously stacked as well in newly created sensors of previous versions.
SNMP Sensors	Stability improvements for SNMP sensors: In some cases, SNMP sensors (for example, SNMP RMON, SNMP Cisco System Health) were successfully created but sensor scans failed with SNMP error #223 (no_such_instance). PRTG will handle such cases better now.

Fixed

WebGUI

Buttons	We made functionality and naming of buttons throughout the PRTG web interface more consistent.
Dark Theme	Several fixes for the dark theme of the PRTG web interface, for example, better readable texts in filters and toplists
Hover Popups	We added the Scan Now button to hover popups again. It was not available in previous versions by mistake.
Internet Explorer 11	We fixed the position of several buttons (for example, in reports and the Add Sensor dialog) in the PRTG web interface for Internet Explorer 11.
Maps	We fixed an issue with public maps that failed to refresh when including the Data Tables object Tickets.
System Information	You can select the text in System Information tables with your mouse again to copy and paste the entries.

Fixed

Various

Placeholders	We fixed the resolution of the %home placeholder that did no longer add a slash to the URL of the PRTG server when appending one or more characters. The issue resulted in broken URLs in certain cases, for example, in notifications.
Various	Several other minor improvements and fixes, updated user manual, updated language files

Changed

Tree Version

Tree Version Update

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

June 6th 2018 – Version 18.2.41.1652

Blog article

By Sascha Neumeier • Jun 18, 2018

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

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

New

WebGUI

Maps	We added the donut charts from the PRTG welcome page as map objects, so you can now use donut charts with current sensor states on your dashboards!
Reports	The Sensor Status History section in historic data reports now shows more precise values and always displays the statistics down to seconds. In previous versions, PRTG rounded the values to units that were too large in certain cases and so did not add up to the values in the heading of the report.

Improved

Notifications

SMS Delivery

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

Changed

WebGUI

Context Menus	We removed the right-click context menus from the overview pages of libraries, maps, and reports.
Settings	We removed the user account settings Max. Groups/Devices per Group and Max. Sensors per Device that defined when to collapse nodes in the device tree, because PRTG automatically handles this.

Fixed

Security

API	We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to Positive Technologies, especially to Dmitry Galecha. Thank you! (CVE-2018-19203, CVE-2018-19410)
Reports	We fixed an issue that allowed access to reports under certain circumstances without according permissions.

Fixed

Sensors

Business Process	Configuration reports for the Business Process sensor work again.
HL7	We improved the order of HL7 sensor settings.
HTTP Advanced	The HTTP Advanced sensor now also supports TLS 1.1 and TLS 1.2 connections when using the compatibility mode as monitoring engine.
Oracle SQL v2 and Oracle Tablespace	We fixed an issue with device templates that prevented Oracle SQL v2 and Oracle Tablespace sensors from being added via auto-discovery.
REST Custom	The REST Custom sensor now works when a proxy server is defined in the Proxy Settings for HTTP Sensors settings. In previous version, the sensor returned an error with the codes PE233 and PE231 when using a proxy.
SNMP Custom Advanced	In certain cases, the SNMP Custom Advanced sensor showed incorrect values when very large values were returned by the target device. We fixed the issue.
SNMP Library	SNMP Library sensors correctly take custom units from OID libraries again.
SNMP Sensors	SNMP sensors will not terminate the scan for available monitoring items during sensor creation anymore when the scan for an entry fails because of an OID that is too long.
Windows IIS Application	The Windows IIS Application sensor now supports 32-bit unsigned integer values (UInt32), so it can handle values greater than 2147483647, the maximum value for a 32-bit signed integer.

Fixed

WebGUI

Context Menus	Manually executing sensor scans from context menus works again. Please note that we renamed Check Now to Scan Now to better reflect what this function actually does, which is executing a sensor scan.
Email Notifications	Links to your PRTG installation in email notifications work again.
Management Tab	We fixed an issue where acknowledging the deletion of many objects at once on the Management tab was not possible because of a cropped window.
Object Selector	Changing dependencies to other objects, changing related objects in filters for lists, and changing linked objects in library node settings work again.
Reports	We improved the graph alignment in PDF reports. We fixed some corner cases that caused wrong time spans in historic data reports when using quick range buttons.
Tables	Various performance and layout improvements for tables in the web interface

Fixed

Various

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

May 7th 2018 – Version 18.2.40.1683

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

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

May 2018 – Version 18.2.40

Blog article

By Sascha Neumeier • May 21, 2018

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

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

New

Sensors

SNMP Fujitsu System Health

We added the first native Fujitsu sensor to PRTG! The new SNMP Fujitsu System Health BETA sensor monitors the status of Fujitsu PRIMERGY servers via the iRMC. With this new sensor type you will have an overview about the iRMC status, CPU status, available memory, status of power supplies, the current temperature, the temperature status, and more.

Improved

Sensors

NetFlow V9 and IPFIX	NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors now support IPv6 flows. Please note that the IPv6 support for these sensor types is included as experimental feature. We welcome any feedback on the IPv6 functionality, just send it to [email protected]!
SMB-based Sensors	The sensor types File, File Content, Folder, and Event Log (Windows API) handle impersonation in a better way and mitigate potential error sources. The sensors now first try to access the target share as LOCAL_SYSTEM Windows user. If they do not succeed, they try impersonation with the Windows credentials defined in the device settings.
SNMP Custom String and WMI Custom String	SNMP Custom String and WMI Custom String sensors now show the retrieved string message even when the sensor status is unusual.
WMI HDD Health	We improved the naming of the WMI HDD Health sensor channels. The names of the several sensor channels are more meaningful now and will not show just "unknown".

Improved

WebGUI

Desktop Notifications	PRTG will now ask you when you access the PRTG web interface with a Firefox or Google Chrome browser for the first time if you want to allow Desktop Notifications from PRTG. Because you can directly enable and disable Desktop Notifications from PRTG via your browser, we also removed the Desktop Notification tab from PRTG Setup.
Quick Action Buttons	We removed the delete icon (trash can symbol) from the quick action icons of probes, groups, devices, and sensors to avoid deleting objects by accident. Please use the context menu next to the quick action icons to delete objects. The Acknowledge indefinitely quick action icon will now always appear as first icon, so its appearance will not change the order of the buttons anymore to avoid clicking the wrong icon by accident.
Tables	We changed the order of columns in sensor tables to improve the readability. The Message column now comes after the Status and Last Value columns so that the available table space is used in a better way.

April 11th 2018 – Version 18.2.39.1661

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

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

April 2018 – Version 18.2.39

Blog article

By Sascha Neumeier • Apr 20, 2018

All about PRTG Release 18.2.39 + a Sneak Peek into Our Version Numbers

You probably already know pretty much everything about the PRTG release 18.1.38, which was released on our stable channel in March. If not, please read the article "Security, Healthcare and Much...
Read the complete blog post here

Improved

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. Please use single or double quotes to escape special characters and whitespaces in the parameters fields.
API	We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to thank STO LABS (especially to Lucas Carmo, Edward Toledano, and Ricardo Fajin) and Positive Technologies for researching and reporting the issue. (CVE-2018-19203, CVE-2018-19410)
Outgoing Connections	Outgoing connections from the PRTG core server to Paessler servers for activation, update check, and downloads now use HTTPS.

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.

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.

March 19th 2018 – Version 18.1.38.11958

Fixed

Sensors

Custom Sensors

The limit mode setting defined in the returned JSON/XML of custom sensor types like EXE/Script Advanced, Python Script Advanced, SSH Script Advanced, and HTTP Data Advanced works properly again. In the previous PRTG version, these sensor types ignored the defined limit mode and always disabled limits.

WMI Event Log

WMI Event Log sensors now set filter options for events to Include Filter by default. In the last PRTG version the newly introduced exclude filters were erroneously defined as default.

If you update from a PRTG version 18.1.37 or previous to the current PRTG version, your event log filters will work as before after installing the update. If you already have installed PRTG version 18.1.38.11934, your filter options will not automatically change after installing the update. Please manually correct the sensor filter settings in this case.

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

WebGUI

Table Lists

The automatic refresh of table lists throughout the PRTG web interface works properly again. in the previous PRTG version, lists like Alarms, for example, only refreshed when there were more than 50 entries available in the list.

Fixed

Server

Performance

We fixed an issue that caused performance losses in certain cases.

March 2018 – Version 18.1.38

Blog article

By Sascha Neumeier • Mar 28, 2018

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

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

Important

Security

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!

March 7th 2018 – Version 18.1.38.11934

Note

Known Issue

Event Log (Windows API) and WMI Event Log

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

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

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

Fixed

Sensors

Business Process	Several fixes for the display of Business Process Specific Settings
Custom Sensors	You can specify a scaling factor (multiplication and division) in the channel settings of custom sensors again, including channels of SNMP Library sensors. Scaling factors defined by meta-scan, OID libraries, and PRTG backend results will also apply again. This did not work for non-custom units (for example, bytes/s) in previous versions.
Exchange (Powershell) Sensors	As announced in the release notes of PRTG 18.1.37, we removed the Execution Time channels from Exchange (Powershell) sensors. The channel was only delivered in PRTG 17.4.36 and was not functional.
Folder	The Folder sensor can now access folders on a network share when the share has specific credentials. If the Windows user account that runs the PRTG probe service has no access rights on the Windows share but there are correct Windows credential defined in PRTG, the sensor will be able to monitor the share.
SNMP HP ProLiant System Health	We removed the Integrated Management Log Status channel from the SNMP HP ProLiant System Health sensor because the OID that the sensor used no longer exists.
SNMP Library	In certain cases, when you added multiple sensors via the SNMP Library sensor at once, the sensors used random OIDs and so displayed wrong values. We fixed this issue. SNMP Library sensors correctly apply value types from the OID library again. In certain cases, delta values and absolute values were incorrectly defined in the value type settings. You can configure the scaling factor (multiplication and division) in SNMP Library sensor channel settings again, even if there was no scaling factor defined in the OID library. The scaling factor also works for non-custom units (for example, bytes/s) again.
SNMP Linux Meminfo	The SNMP Linux Meminfo sensor channel Percent Available Memory has no predefined limits anymore to better reflect the behavior of Linux systems. If you need the removed limits, please manually add them again in the channel settings after the update to this PRTG version. By default, the new primary channel of the SNMP Linux Meminfo sensor is Physical Free Percent.
SSH Disk Free	The SSH Disk Free channel includes all selected partitions in one sensor again. In previous versions, PRTG erroneously created one sensor for each selected partition with the content of both selected partitions.
SSL Security Check	We removed the SSL 2.0 channel. The OpenSSL component that PRTG uses does not support SSL 2.0, so the channel result was incorrect.
VMware Sensors	VMware sensors now work on Windows machines with the Federal Information Processing Standard (FIPS) mode enabled. Please note that PRTG still does not support the FIPS mode on Windows systems running the PRTG core server or probe service.

Fixed

Security

API	It is not possible anymore to perform certain actions via API calls without having according user rights. Thanks to Positive Technologies for reporting the issue! (CVE-2018-19411)
Sensors	Passwords in debug files will not appear in clear text anymore when you enable the option to write the sensor result to disk.

Fixed

WebGUI

Auto-Discovery	It is possible again to start an auto-discovery on multiple devices in the device list. The option Run Auto-Discovery is now available in the multi-edit context menu.
Desktop Notifications	We fixed an issue where desktop notifications did not work when they were temporarily disabled and the last saved alarm count was great than the new count. Also note that Google Chrome requires HTTPS to use desktop notifications since one of its latest updates, so please switch the PRTG web server to SSL if you enable desktop notifications.
Geo Maps	In certain cases, Geo Maps were not correctly displayed but shown as JSON code or not at all. We fixed this issue.
Graphs	Graphs throughout the PRTG web interface are now better readable. This especially affects colors as well as transparency. For example, the Primary Channel of a sensor is more clearly visible again. Also Maps benefit from these improvements.
Libraries	It was mistakenly possible to switch the device tree view on the Management tab of a library. We removed the option. The device tree on this library tab has the default size M.
Main Menu Structure	We have removed the entry Tickets \| All from the main menu bar.
Maps	Previews of graph map objects are displayed again.
Mobile View	We fixed an issue with scrolling in the mobile view.
Reports	Faster rendering of very long reports
Search	Performance improvements for the device tree search. PRTG will show you search results in the device tree much quicker than before. We also fixed some issues with the advanced search.
Tables	Several improvements and fixes for the display of tables (both data tables and sensor selection tables in the Add sensor dialog) in the PRTG web interface and in Maps
Tags	Several fixes to the usage of new tags
Various	Many other minor fixes and improvements to the new PRTG web interface

Fixed

Server and Probes

API	It is now possible to use API calls like setobjectproperty.htm on the Total channel of traffic sensors that have channel ID -1 (subid=-1).
Clone Objects	Cloning groups and devices that have an auto-discovery setting enabled or that currently have an auto-discovery running will not result in duplicated sensors on the new group or device anymore.
Remote Probes	We fixed an issue where approving remote probes resulted in timeouts when the geo location server for Geo Maps was not reached. In certain cases, the PRTG web interface was frozen or the PRTG core server was not reachable when this happened.

Fixed

Various

All Parts of PRTG

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

Changed

Tree Version

Tree Version Update

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

February 19th 2018 – Version 18.1.37.13946

Fixed

Server

Proxy	We fixed an issue where proxy settings were not correctly applied so that outgoing HTTP calls of the PRTG core server did not work. In certain cases, this caused hanging background threads, which resulted in memory leaks and missing configuration savings.
PRTG Core Server	We fixed an issue that caused a deadlock in rare cases.

January 23rd 2018 – Version 18.1.36.3733

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.

February 2018 – Version 18.1.37

Blog article

By Sascha Neumeier • Feb 27, 2018

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

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

New

Sensors

REST Dell EMC BETA

We added 5 new sensor types that enable you to monitor your Dell EMC storage systems out of the box! The sensors use the REST API of Dell EMC devices to show you health status and other important measurements of your Dell EMC storage components. PRTG 18.1.37 comes with the following Dell EMC sensors:

The REST Dell EMC Capacity BETA sensor monitors disk usage.
The REST Dell EMC File System BETA sensor monitors the health of an EMC file system.
The REST Dell EMC LUN BETA sensor monitors an EMC logical unit number (LUN).
The REST Dell EMC Pool BETA sensor monitors an EMC storage pool.
The REST Dell EMC System Health BETA sensor monitors the EMC health status.

The new REST Dell EMC BETA sensors support various EMC storage systems that provide a REST API, for example, EMC Unity Family, EMC Unity All Flash, EMC Unity Hybrid, and EMC UnityVSA.

Changed

Sensors

Exchange Backup (Powershell)	Stability improvements for the Exchange Backup (Powershell) sensor. It also includes two new channels that show the passed time since the last differential backup and since the last incremental backup. After the update to PRTG 18.1.37, please create your Exchange Backup (Powershell) sensors anew. Existing sensors of this type might show incorrect data!
Exchange Public Folder (Powershell)	The Exchange Public Folder (Powershell) sensor can now monitor subfolders. After the update to PRTG 18.1.37, you must create all Exchange Public Folder (Powershell) sensors anew. Existing sensors of this type will stop working!
Exchange (Powershell)	Stability improvements for all Exchange (Powershell) sensors. Note: The Execution Time channel of running Exchange (Powershell) sensors will not show any data after the update to PRTG 18.1.37 and will be completely removed in future versions. It was still available in some older running Exchange sensors.

Improved

Sensors

NetApp LIF	The NetApp LIF sensor has a new channel Is home that shows if the logical interface is at the home port.
NetFlow V9 and IPFIX	Performance improvements for NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors
SNMP QNAP Logical Disk	The SNMP QNAP Logical Disk sensor has a new lookup status Synchronizing in channel Volume Status that maps to the sensor status warning.

Improved

Server

Date Format

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

February 6th 2018 – Version 18.1.37.12158

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

January 9th 2018 – Version 18.1.36.3728

Note

Known Issue

SNMP Library Sensor

There is a known issue in this version: In certain cases, newly created SNMP Library sensors display data with the wrong scaling. This issue does not affect SNMP Library sensors that you added in PRTG version 17.4.33 or before.

For more details, please see the Knowledge Base article Known Issue: Wrong Data Scaling in SNMP Library Sensors

Fixed

Sensors

SNMP Custom Sensors	We fixed a divergence in signed integer values in the SNMP Custom Advanced and SNMP Custom sensors.
EXE Sensors	EXE sensors now work properly again. This fix affects the following sensor types: Amazon CloudWatch sensors, NetApp sensors (using ONTAP), Exchange (Powershell) sensors, Hyper-V Cluster Shared Volume Disk Free, Windows Updates Status (Powershell), HTTP Advanced, HTTP Transaction, VMware sensors, IPMI System Health, SIP Options Ping, SQL sensors, Citrix XenServer sensors, Radius v2.
Probe Health	We fixed an issue with the new Data Storage channel limits introduced in 17.4.36.
SNMP Library	We fixed SNMP access violations that could cause non-functioning sensors after creation or missing sensors in Libraries.

December 19th 2017 – Version 17.4.36.3670

Fixed

Sensors

Exchange (Powershell) Sensors

In certain cases, the Exchange (Powershell) sensors showed incorrect errors (for example PE233 and PE231) and duplicated existing channels. The sensors also erroneously required PowerShell 3.0 although PowerShell 2.0 is sufficient. We fixed the issues and implemented some stability improvements.

Affected sensor types are: Exchange Backup (Powershell), Exchange Database (Powershell), Exchange Database DAG (Powershell), Exchange Mail Queue (Powershell), Exchange Mailbox (Powershell), Exchange Public Folder (Powershell)

December 12th 2017 – Version 17.4.36.3595

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

December 2017—January 2018 – Version 17.4.36/18.1.36

Improved

WebGUI

PRTG Web Interface

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

Improved

Sensors

NetApp LUN

The NetApp LUN sensor has a new channel Mapped that shows whether the LUN is mapped or not.

NetApp Volume

We added 8 new channels to the NetApp Volume sensor for a even more detailed view on your NetApp storage system:

Compression savings bytes
Compression savings bytes %
Deduplication savings bytes
Deduplication savings bytes %
Total savings bytes
Total savings bytes %
Files free
Files free %

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

Changed

Sensors

REST Custom

The REST Custom sensor now uses JSONPath in the REST configuration file to map the retrieved JSON into sensor channels and values. To reflect this change, names of REST configuration files now have the ending .template instead of .json. Please consider this when adding new REST configuration files to PRTG. We also implemented some fixes and improvements for this beta sensor.

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

November 2017 – Version 17.4.35

Note

PRTG in the Cloud

Cloud Rollout

We roll out this version on PRTG in the cloud in stages. PRTG 17.4.35 will be available on your own cloud instance soon!

New

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

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!

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

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.

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

Improved

Security

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

Improved

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.

November 27th 2017 – Version 17.4.35.3441

Fixed

Sensors

Folder	The Change Trigger for notifications of the Folder sensor is working again.
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 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 Sensors	Stability improvements and major fixes for all SNMP sensors
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.
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

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.
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
Monitoring Data	We fixed an issue that occasionally caused missing monitoring data in sensors and empty sensor messages after a PRTG server restart.
Schedules	We fixed an issue with schedules in timezones without daylight saving time. Schedules will now also correctly work in such timezones. Changing and assigning schedules works more reliably.
Security	We fixed two possible XSS vulnerabilities (CVE-2017-15008 and CVE-2017-15009). Thank you Edward Amaral Toledano, Ricardo Fajin, and Wen Bin Kong for reporting CVE-2017-15009!
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

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

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

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.

Previous Versions
and other Release Channels

Release Notes for PRTG 18

December 11th 2018 – Version 18.4.47.1962

Important

Known Issue: PRTG Update

Updating from version 18.1.37 or older

Improved

WebGUI

Notifications

Maps

Improved

Server

PRTG Core Server

Graphs

Logging

Improved

Sensors

HTTP Push Data Advanced

SNMP Trap Receiver

Windows Updates Status (PowerShell)

Fixed

Server

PRTG Core Server

PRTG GUI Starter

Security

Server Startup

Fixed

Sensors

Channels

Event Log (Windows API)

Flow Sensors

Lookups

Sensor Factory

SNMP Custom String Lookup

SNMP sensors

SNMP Trap Receiver

UPS Health (Generic) Template

WMI Sensors

Fixed

Notifications

Amazon SNS

SMS

Fixed

WebGUI

Credentials

Tables

Various

Fixed

API

XML

Fixed

Various

Language Files

All Parts of PRTG

Note

Probe and Sensors

.NET Version

November 20th 2018 – Version 18.4.46.1754

Blog article

All You Need to Know About PRTG Release 18.4.46

Fixed

Sensors

SNMP Traffic

November 14th 2018 – Version 18.4.46.1736

Fixed

Sensors

SNMP System Uptime

November 7th 2018 – Version 18.4.46.1706

Improved

Server

PRTG Status

Remote Probes

PRTG Server

Web Server Connections

Improved

Sensors

Amazon CloudWatch

SNMP System Uptime

Changed

API

JSON

Release Notes
for PRTG 18