Fixed
WebGUI
Maps |
We fixed some issues with maps.
|
Release Notes for the
"Stable" Release Channel
Software versions in this channel are updated about once a month. In this most conservative channel you receive the best tested versions. We recommend that you use PRTG's stable versions for live environments.
Please use the "Auto-Update" feature to update your PRTG installation: In the PRTG web interface, simply navigate to Setup | Auto Update. You can also obtain the latest version from the PRTG download page!
Go to Download Page Manual: Using the "Software Auto-Update" Function of PRTG Previous Versions and other Release Channels
Fixed
Probe
Memory Leak |
We fixed a memory leak on the PRTG probe system caused by running SNMP Fujitsu System Health BETA sensors. |
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. |
Blog article
|
Have you all recovered from our release of last month? In May we introduced the PRTG version 18.2.40, presenting our new Fujitsu sensor. This new SNMP Fujitsu System Health BETA sensor monitors... Read the complete blog post here |
New
WebGUI
Maps |
We added the donut charts from the PRTG welcome page as map objects, so you can now use donut charts with current sensor states on your dashboards! |
Reports |
The Sensor Status History section in historic data reports now shows more precise values and always displays the statistics down to seconds. In previous versions, PRTG rounded the values to units that were too large in certain cases and so did not add up to the values in the heading of the report. |
Changed
WebGUI
Context Menus |
We removed the right-click context menus from the overview pages of libraries, maps, and reports. |
Settings |
We removed the user account settings Max. Groups/Devices per Group and Max. Sensors per Device that defined when to collapse nodes in the device tree, because PRTG automatically handles this. |
Fixed
Security
API |
We fixed a vulnerability where certain API calls could result in a stack overflow on the PRTG server. We'd like to give the research credits of the issue to Positive Technologies, especially to Dmitry Galecha. Thank you! |
Reports |
We fixed an issue that allowed access to reports under certain circumstances without according permissions. |
Fixed
Sensors
Business Process |
Configuration reports for the Business Process sensor work again. |
HL7 |
We improved the order of HL7 sensor settings. |
HTTP Advanced |
The HTTP Advanced sensor now also supports TLS 1.1 and TLS 1.2 connections when using the compatibility mode as monitoring engine. |
Oracle SQL v2 and Oracle Tablespace |
We fixed an issue with device templates that prevented Oracle SQL v2 and Oracle Tablespace sensors from being added via auto-discovery. |
REST Custom |
The REST Custom sensor now works when a proxy server is defined in the Proxy Settings for HTTP Sensors settings. In previous version, the sensor returned an error with the codes PE233 and PE231 when using a proxy. |
SNMP Custom Advanced |
In certain cases, the SNMP Custom Advanced sensor showed incorrect values when very large values were returned by the target device. We fixed the issue. |
SNMP Library |
SNMP Library sensors correctly take custom units from OID libraries again. |
SNMP Sensors |
SNMP sensors will not terminate the scan for available monitoring items during sensor creation anymore when the scan for an entry fails because of an OID that is too long. |
Windows IIS Application |
The Windows IIS Application sensor now supports 32-bit unsigned integer values (UInt32), so it can handle values greater than 2147483647, the maximum value for a 32-bit signed integer. |
Fixed
WebGUI
Context Menus |
Manually executing sensor scans from context menus works again. Please note that we renamed Check Now to Scan Now to better reflect what this function actually does, which is executing a sensor scan. |
Email Notifications |
Links to your PRTG installation in email notifications work again. |
Management Tab |
We fixed an issue where acknowledging the deletion of many objects at once on the Management tab was not possible because of a cropped window. |
Object Selector |
Changing dependencies to other objects, changing related objects in filters for lists, and changing linked objects in library node settings work again. |
Reports |
|
Tables |
Various performance and layout improvements for tables in the web interface |
Fixed
Various
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
Fixed
Sensors
Event Log (Windows API) |
Filtering by event ID with the Event Log (Windows API) sensor works again. Due to a change in the Windows API the sensor was not able to find events by ID in previous versions. |
Exchange Database DAG (Powershell) |
The Active Copy channel now shows correct data when monitoring Exchange Server 2010. |
HTTP Advanced |
The request method HEAD now properly works with the HTTP Advanced sensor. The channels Bytes received and Download bandwidth only showed 0 values in previous versions. We also improved the bandwidth calculation and the way the sensor monitors really fast connections (for example, LAN or localhost) that sometimes caused the error message "Potential error during bandwidth calculation. (Loading time below 0.1 ms)". |
NetFlow V9 and IPFIX |
We fixed an issue that caused in and out traffic to be assigned in the wrong direction (switched source and target) in certain cases when monitoring a Cisco ASA. The issue affected the sensor types NetFlow V9, NetFlow V9 (Custom), IPFIX, IPFIX (Custom) and was visible when using toplists or filters. |
REST Custom |
|
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 |
|
Reports |
|
Tables |
Changing object priorities in tables will not result in expanding table rows anymore. |
Fixed
Various
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
Blog article
|
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. |
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
|
Reports |
We improved the readability of historic data reports reports, including a corrected position of percentiles. |
Tables |
Paging on large tables and the selection of table items work properly again, for example, in the Add Sensor dialog, in user group settings for allowed sensor types, and in the dialog for running an auto-discovery with template. We also improved the readability of column headers in data tables. |
User Rights |
PRTG user accounts with read/write user rights are allowed to view dependencies again. |
Various |
Several other small fixes and improvements for the PRTG web interface |
Fixed
Server
Performance |
We fixed some more issues that caused performance losses and resulted in PRTG core server timeouts in certain cases. |
Fixed
Various
Various |
Several other minor improvements and fixes, updated user manual, updated language files |
Blog article
|
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 give the research credits of the issue to STO LABS, especially to Lucas Carmo, Edward Toledano, and Ricardo Fajin. Thank you! |
Outgoing Connections |
Outgoing connections from the PRTG core server to Paessler servers for activation, update check, and downloads now use HTTPS. |
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!
|
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. |
Blog article
|
Last month we had to deal with some highly exciting but also time-consuming code enhancements within PRTG Network Monitor. Our development team implemented an important security fix, made... Read the complete blog post here |
Important
Security
Security |
PRTG 18.1.38 contains an important security update for your PRTG installation. There is a security issue that affects PRTG versions 17.4.35.3326 through 18.1.37.13946. Previous versions are not affected.
The error that causes the issue does not occur on every PRTG instance. If your installation is affected, PRTG will create a ToDo ticket for PRTG administrators that contains more information. PRTG will create this ticket after you have installed the secure version and only if you were affected by the issue. We strongly recommend that you immediately update to the latest PRTG version in any case. Note: In certain cases, the Windows Defender interferes with the PRTG installer. This might cause high CPU load on the PRTG server, which might prevent a successful installation of the update. Please temporarily disable the Windows Defender if you have issues installing the update. |
New
Sensors
DICOM and HL7 Sensors |
You can now monitor your medical IT on Digital Imaging and Communications in Medicine (DICOM) and Health Level-7 (HL7) out of the box! The new PRTG version 18.1.38 includes 4 new sensor types that show you important information about your DICOM and HL7 capable systems and devices.
|
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.
|
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 |
|
SNMP Linux Meminfo |
The SNMP Linux Meminfo sensor channel Percent Available Memory has no predefined limits anymore to better reflect the behavior of Linux systems. If you need the removed limits, please manually add them again in the channel settings after the update to this PRTG version. By default, the new primary channel of the SNMP Linux Meminfo sensor is Physical Free Percent. |
SSH Disk Free |
The SSH Disk Free channel includes all selected partitions in one sensor again. In previous versions, PRTG erroneously created one sensor for each selected partition with the content of both selected partitions. |
SSL Security Check |
We removed the SSL 2.0 channel. The OpenSSL component that PRTG uses does not support SSL 2.0, so the channel result was incorrect. |
VMware Sensors |
VMware sensors now work on Windows machines with the Federal Information Processing Standard (FIPS) mode enabled. Please note that PRTG still does not support the FIPS mode on Windows systems running the PRTG core server or probe service. |
Fixed
Security
Sensors |
Passwords in debug files will not appear in clear text anymore when you enable the option to write the sensor result to disk. |
Fixed
WebGUI
Auto-Discovery |
It is possible again to start an auto-discovery on multiple devices in the device list. The option Run Auto-Discovery is now available in the multi-edit context menu. |
Desktop Notifications |
We fixed an issue where desktop notifications did not work when they were temporarily disabled and the last saved alarm count was great than the new count. Also note that Google Chrome requires HTTPS to use desktop notifications since one of its latest updates, so please switch the PRTG web server to SSL if you enable desktop notifications. |
Geo Maps |
In certain cases, Geo Maps were not correctly displayed but shown as JSON code or not at all. We fixed this issue. |
Graphs |
Graphs throughout the PRTG web interface are now better readable. This especially affects colors as well as transparency. For example, the Primary Channel of a sensor is more clearly visible again. Also Maps benefit from these improvements. |
Libraries |
It was mistakenly possible to switch the device tree view on the Management tab of a library. We removed the option. The device tree on this library tab has the default size M. |
Main Menu Structure |
We have removed the entry Tickets | All from the main menu bar. |
Maps |
Previews of graph map objects are displayed again. |
Mobile View |
We fixed an issue with scrolling in the mobile view. |
Reports |
Faster rendering of very long reports |
Search |
Performance improvements for the device tree search. PRTG will show you search results in the device tree much quicker than before. We also fixed some issues with the advanced search. |
Tables |
Several improvements and fixes for the display of tables (both data tables and sensor selection tables in the Add sensor dialog) in the PRTG web interface and in Maps |
Tags |
Several fixes to the usage of new tags |
Various |
Many other minor fixes and improvements to the new PRTG web interface |
Fixed
Server and Probes
API |
It is now possible to use API calls like setobjectproperty.htm on the Total channel of traffic sensors that have channel ID -1 (subid=-1). |
Clone Objects |
Cloning groups and devices that have an auto-discovery setting enabled or that currently have an auto-discovery running will not result in duplicated sensors on the new group or device anymore. |
Remote Probes |
We fixed an issue where approving remote probes resulted in timeouts when the geo location server for Geo Maps was not reached. In certain cases, the PRTG web interface was frozen or the PRTG core server was not reachable when this happened. |
Fixed
Various
All Parts of PRTG |
Various other fixes and improvements, updated user manual, updated language files. |
Changed
Tree Version
Tree Version Update |
The configuration file of this version is not downwards compatible with previous PRTG versions. |
Fixed
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. |
Fixed
Sensors
SNMP Library |
This version includes several fixes for the SNMP Library sensor. The sensor correctly uses the Scale (multiplication and division) from the imported OIDLIB again to show expected values. Custom units are imported and displayed correctly again. |
Blog article
|
|
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:
|
Changed
Sensors
Exchange Backup (Powershell) |
Stability improvements for the Exchange Backup (Powershell) sensor. It also includes two new channels that show the passed time since the last differential backup and since the last incremental backup. After the update to PRTG 18.1.37, please create your Exchange Backup (Powershell) sensors anew. Existing sensors of this type might show incorrect data! |
Exchange Public Folder (Powershell) |
The Exchange Public Folder (Powershell) sensor can now monitor subfolders. After the update to PRTG 18.1.37, you must create all Exchange Public Folder (Powershell) sensors anew. Existing sensors of this type will stop working! |
Exchange (Powershell) |
Stability improvements for all Exchange (Powershell) sensors. Note: The Execution Time channel of running Exchange (Powershell) sensors will not show any data after the update to PRTG 18.1.37 and will be completely removed in future versions. It was still available in some older running Exchange sensors. |
Improved
Sensors
NetApp LIF |
The NetApp LIF sensor has a new channel Is home that shows if the logical interface is at the home port. |
NetFlow V9 and IPFIX |
Performance improvements for NetFlow V9, NetFlow V9 (Custom), IPFIX, and IPFIX (Custom) sensors |
SNMP QNAP Logical Disk |
The SNMP QNAP Logical Disk sensor has a new lookup status Synchronizing in channel Volume Status that maps to the sensor status warning. |
Improved
Server
Date Format |
We added the date format YYYY-MM-DD HH:MM:SS to make more people feel at home when using PRTG. You can choose your preferred date format in your PRTG user account settings. |
Fixed
Sensors
Business Process |
Adding objects to channels in the Business Process Specific Settings works again. |
Cloud HTTP and Cloud Ping |
Cloud HTTP and Cloud Ping sensors now use the Proxy Settings for HTTP Sensors from the parent device (or inherited from other objects higher in the hierarchy). In previous versions the sensors used the proxy configuration for Core & Probes as defined in the PRTG System Administration. |
Common SaaS |
The Common SaaS sensor is now available when filtering for Cloud Services in the Add Sensor dialog. |
FTP Server File Count |
We added passive connection mode support to the FTP Server File Count sensor. You can choose the required FTP Mode in the sensor settings. |
HTTP Push Sensors |
Stability improvements for HTTP Push sensors (HTTP Push Count, HTTP Push Data, HTTP Push Data Advanced) |
Hyper-V Virtual Machine |
The Hyper-V Virtual Machine sensor shows more expressive error messages in case of sensor failures. |
NetApp NIC |
The NetApp NIC sensor can now monitor all physical and logical ports on any node in your NetApp cluster and correctly provides all available monitoring items in the Add Sensor dialog. |
NetApp Sensors |
In certain cases, NetApp sensors for cDOT and ONTAP storage systems failed because of corrupted cache files. We fixed this issue. |
NetFlow V9 and IPFIX |
In certain cases, NetFlow V9 and IPFIX sensors could not collect data. We fixed this issue. |
Probe Health |
The Probe Health sensor will now reset the error message for the Data Storage Free channel when the disk has enough space again. |
REST Custom |
Some more fixes and improvements for the REST Custom BETA sensor, including support for Boolean values |
SNMP Custom sensors |
We changed the naming of the Value Type options of SNMP Custom, SNMP Custom Advanced, and SNMP Custom Table sensors. This will make it clearer what value type you have to choose, absolute or delta values. |
SNMP Traffic |
In certain cases, SNMP Traffic sensors showed access violation errors. We fixed this issue. |
SSL Certificate |
The SSL Certificate sensor now correctly categorizes the key length of ECC certificates in case of compressed coordinates. If you have changed the lookup file to manually avoid issues with the key length of ECC certificates, please choose the original lookup file again after the update. For details, please see this Knowledge Base article: SSL Certificate Sensors and ECC Certificates: Fix for Public Key Length Monitoring |
VMware Sensors |
VMware sensors support TLS 1.2 only connections if required by the target VMware host. |
VMware Virtual MAchine (SOAP) |
If you create a device template that includes a VMware Virtual Machine (SOAP) sensor and run an auto-discovery with the template, discovered VMware Virtual Machine (SOAP) sensors will now have a correct sensor name (was erroneously "Host Performance" in previous versions) and correctly take the Handling of "Powered Off" VM setting. |
Windows Updates Status (Powershell) |
You can add Windows Updates Status (Powershell) sensors via Auto-Discovery again. |
WSUS Statistics |
The WSUS Statistics sensor can handle untrusted certificates when using SSL to connect to the WSUS server. |
Sensor Channels |
Decimal places were not correctly displayed in certain cases, for example when decimal places were set to Automatic in the sensor channel settings with a Custom unit and no custom unit string. We fixed this issue. |
Various Sensors |
In newly created sensors you must select the Value Type "Integer" to use a lookup because lookups only properly work with integer values. This was not validated in previous versions and lead to inconsistencies. This change affects the sensor types ADO SQL v2, Google Analytics, MySQL v2, Microsoft SQL v2, SNMP Custom Advanced, SNMP Custom Table. |
Fixed
WebGUI
PRTG Web Interface |
We fixed various issues with the new PRTG web interface and further improved usage and appearance.
|
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 |
|
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 |
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. |
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) |
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:
|
Fixed
Sensors
Common SaaS |
The Common SaaS sensor now uses the Proxy Settings for HTTP Sensors from the parent device (or inherited from other objects higher in the hierarchy). In previous versions the sensor used the proxy configuration for Core & Probes as defined in the PRTG System Administration. |
Exchange Database DAG (Powershell) |
The Exchange Database DAG (Powershell) sensor is now compatible with the Cumulative Update 4 for Exchange Server 2016 (Exchange 2016 CU4). |
Exchange Public Folder (Powershell) |
The Exchange Public Folder (Powershell) sensors now supports Microsoft Exchange Server 2013 and Microsoft Exchange Server 2016. |
Hyper-V Cluster Shared Volume Disk Free |
The Hyper-V Cluster Shared Volume Disk Free sensor supports UTF-8 characters in volume names, including German umlauts. In previous versions, the sensor could not monitor volumes with umlauts in their name. |
NetApp LUN |
The Bytes free % channel now shows correct values. |
NetApp Volume |
The NetApp Volume sensor now properly handles more than 20 snapshots. In previous versions, the sensor showed a wrong number of snapshots and wrong values for the oldest and newest snapshot age channels if there were more than 20 snapshots. |
Share Disk Free |
The Share Disk Free sensor now correctly calculates free disk space on a share. In some cases, the sensor used the free disk space of a whole disk instead of only the share to calculate free space, which resulted in values greater than 100% free disk space, for example. |
SNMP Traffic and SNMP RMON |
When monitoring certain devices (for example, Fortinet FortiSwitch) with SNMP Traffic or SNMP RMON sensors, the automatic sensor name update (if set in the SNMP Compatibility Options) caused a sensor error in the last PRTG version. We fixed this issue. |
SSL Certificate |
Fix for the Certificate Name Validation of the SSL Certificate sensor: In certain cases, the sensor check failed although CN/SAN matched the SNI. |
Windows Updates Status (Powershell) |
Stability improvements for the Windows Updates Status (Powershell) sensor |
Fixed
Server
PRTG Core Server Service |
In rare cases when running a PRTG update, the PRTG Core Server service got removed and could not be installed again. We fixed this issue. |
Reports |
Double quotes in report names resulted in timeouts while PDF creation in some cases. We fixed this issue. |
System Information |
We fixed an exception that was caused when a vendor was not available for a Software table entry. |
Tickets and Auto-Discovery |
PRTG will now only create one ticket for a completed auto-discovery when at least one new device or sensor has been discovered. |
Fixed
Security
Amazon SNS Notifications |
The AWS Secret Access Key for Amazon Simple Notification Service notifications is not readable anymore in the PRTG web interface. |
Maps |
We added a check for the file format of background images that you can upload for maps. It is only possible to use the file formats .jpg, .png, and .gif for background images. |
Fixed
Remote Probes
Cluster |
Access keys for remote probes will be automatically synchronized on all cluster nodes for both newly installed remote probes and removed remote probes. |
Installation |
We fixed a small issue affecting the installation of a remote probe via the context menu in the device tree. |
Fixed
Various
All Parts of PRTG |
Various other fixes and improvements, as well as an updated user manual |
Improved
WebGUI
PRTG Web Interface |
Major improvements to the new PRTG web interface! We implemented a lot of your feedback to give you an even better experience with PRTG. |
Improved
Sensors
NetApp LUN |
The NetApp LUN sensor has a new channel Mapped that shows whether the LUN is mapped or not. |
NetApp Volume |
We added 8 new channels to the NetApp Volume sensor for a even more detailed view on your NetApp storage system:
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. |
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
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!
|
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
Security |
This version includes general security enhancements for PRTG and the configuration file. |
Improved
System Information
System Information |
System Information via SNMP returns more data for the tables System, Processes, and Hardware from a wide variety of Linux machines and a lot of generic network devices. |
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 |
|
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 |
|
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. |
Kostenlos testen
Jetzt kaufen
