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



New

Sensors


NetApp Sensors

We have added 8 brand new sensor types for your NetApp monitoring! Set up a complete monitoring of your NetApp cDOT or ONTAP storage system with these sensor types:

  • NetApp Aggregate
  • NetApp I/O
  • NetApp LIF
  • NetApp LUN
  • NetApp NIC
  • NetApp Physical Disk
  • NetApp System Health
  • NetApp Volume
The sensors monitor your NetApp accessing the API via SOAP and support the latest NetApp ONTAP version 9.2, as well as previous versions ONTAP 9.1, ONTAP 9.0, and cDOT 8.3.

Note: The sensor types NetApp cDOT Aggregate (SOAP), NetApp cDOT I/O (SOAP), NetApp cDOT Physical Disk (SOAP), and NetApp System Health (SOAP) are now deprecated. If you have running instances of these sensor types, they will be automatically replaced by according new NetApp sensors after updating PRTG. Usually, monitoring with affected sensors will seamlessly continue. If you run into any issues with the migration path for outdated NetApp sensors, please manually add desired NetApp sensors anew.

REST Custom

The new REST Custom sensor can monitor almost everything! This sensor is a really powerful tool and gives you the possibilities to go far beyond standard monitoring: you can now query any REST API that returns JSON or XML and map the results into sensor channels. Define your own mapping rules in a dedicated REST configuration file using JSON! It just has to follow the PRTG API specification for the JSON return format.

We deliver various REST configuration files for this sensor by default, so you can immediately see and try out what might be possible with your own REST Custom sensor. You can find the samples in the \Custom Sensors\rest folder in the PRTG program directory, including mappings for the REST APIs of KEMP load balancers, Weather Underground, Docker containers, and PRTG itself, ready-to-use for the sensor.

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

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

Changed

Core/WebGUI


File Lists

If you manually add files to the PRTG program directory on the core server while PRTG is running, you now have to manually reload the file lists to immediately show new files in the web interface. For this purpose, use the new Reload File Lists option under Setup | System Administration | Administrative Tools in the PRTG web interface.

This change affects these file lists:
  • Report templates
  • Device templates
  • Device icons
  • SNMP library (oidlib) files
  • Language files

Note: These lists will still be automatically updated after 1 hour and after a server restart. If you save new device templates via the web interface, the template list will be refreshed immediately.

Improved

Sensors


Amazon CloudWatch Sensors

We have added the region EU (London) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors.

Improved

Notifications


Amazon SNS Messages

You can use new locations for the notification method Amazon Simple Notification Service Message: US West (Ohio), Canada (Central), EU (London), Asia Pacific (Seoul), Asia Pacific (Mumbai)

SMTP Delivery

SMTP delivery for email notifications now supports TLS V1.1 and TLS V1.2.


Changed

Sensors


Amazon CloudWatch Sensors

Amazon CloudWatch sensors now require .NET 4.5 or later to be installed on the computer running the PRTG probe you add the sensor to (local or remote probe system; on every node if on a cluster probe). This change affects the following sensor types:

  • Amazon CloudWatch Alarm Sensor
  • Amazon CloudWatch EBS Sensor
  • Amazon CloudWatch EC2 Sensor
  • Amazon CloudWatch ElastiCache Sensor
  • Amazon CloudWatch ELB Sensor
  • Amazon CloudWatch RDS Sensor
  • Amazon CloudWatch SNS Sensor
  • Amazon CloudWatch SQS Sensor

Fixed

Sensors


Windows Updates Status (Powershell)

Several fixes and stability improvements for the Windows Updates Status (Powershell) sensor.

Fixed

Maps


Public Maps

Public maps can display SVG map objects like data graphs again.


Fixed

WebGUI


WebGUI

Fixed memory leak in the PRTG web interface


Fixed

Sensors


Amazon CloudWatch SNS

You can add Amazon CloudWatch SNS sensors again. Previously, when trying to add the sensor, it showed the error message "Could not create the sensor Amazon CloudWatch SNS BETA on device Amazon SNS (8.8.8.8). Operation (ListPlatformApplications) is not supported in this region".

Docker Container Status

If you have defined another port than the default port 2376 to connect to Docker, the Docker Container Status sensor will now really use this port. In previous versions, the port was erroneously reset to default.

Exchange PowerShell Sensors

We have fixed a bug in Exchange PowerShell sensors: they will now show a correct error message instead of a NullReferenceException.

Sensor Factory

We have fixed a bug that sometimes resulted in incorrect historic data graphs of the Sensor Factory sensor if you set the "use zero as source value" option for missing sensor data.

SIP Options Ping

The SIP Options Ping sensor now recognizes all returned status codes and shows the correct status.

SNMP Custom and SNMP Custom Advanced

We have fixed a bug that caused a lowercase conversion of strings in OIDs requested by SNMP Custom and SNMP Custom Advanced sensors. This bug resulted in broken OIDs and so prevented the sensors from finding instances (error message: "No such instance").

SNMP NetApp Sensors

We have fixed a bug in the NetApp device template that resulted in an interrupted auto-discovery.

SNMP Traffic

  • The auto-discovery now works when using a generic metascan with the SNMP Traffic sensor.
  • Data graphs of SNMP Traffic sensors have an improved scaling when showing in and out traffic as positive and negative area chart.

SNMP Trap Receiver

Improved filtering for string bindings

Windows Updates Status (Powershell)

The Windows Updates Status (Powershell) supports the Windows 10 Creators update. It now requires at least .NET 4.5 on the probe system and PowerShell 3.0 on both the probe system and target system.

WMI Sensors

Stability improvements for WMI multi-query sensors, for example, the Windows Physical Disk I/O sensor

Fixed

Security


Security

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

Fixed

WebGUI


Data Graphs

Improved chart rendering for data graphs in the PRTG web interface and in historic data reports. In particular, several PRTG language versions like Korean will benefit from this improvement.

Geo Maps

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

Fixed

Server and Probes


Stability

  • In rare cases, the PRTG server performed an unexpected restart because of a deadlock event when scheduling reports. We have fixed this potential deadlock cause.
  • Stability improvements for the PRTG core server and probe system

Fixed

Auto-Discovery


Device Templates

When you create a device template, the object setting When a Sensor Reports an Error in the Scanning Interval section will now be stored in the new template.

Fixed

Notifications


Email Notifications

We have fixed some broken links in email notifications.

Notification Trigger

Changing the internal type of a sensor's down status (down due to limits or scan error) will not prevent PRTG from sending notifications anymore.The notification trigger was not provoked in rare cases because the internal status change (from down by scan error to down by limit to down by scan error) has reset the trigger timer.

Fixed

Various


Various

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


Fixed

Russian Language File


Device Templates

Device templates in the Russian language version of PRTG will be shown again in the "Auto-Discovery with Template" window and device settings.

Fixed

Sensors


Sensors with Lookups

Sensors with lookups can now use the full 32-bit unsigned integer range. This will prevent affected sensors from returning the error 'Value is out of 32-bit integer bounds'.


Fixed

Server


Core Service

We fixed an issue that caused a memory leak on explicit logon.

Fixed

PDF Reports


PDF Reports

We fixed an issue with PDF reports showing the error "%1 is not a valid Win32 application. (0xC1)".


Fixed

Sensors


Various

We fixed an issue that resulted in sensors going into a warning state due to an undefined lookup value.


Fixed

Security


Generic Security Files

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

Fixed

Sensors


WMI Sensors

Major stability and performance improvements for WMI sensors.


Fixed

Sensors


Common SaaS

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

Dell PowerVault MDi Logical Disk

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

DHCP

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

Folder

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

HTTP Sensors

HTTPS POST requests with NTLM authentication work again.

NetFlow

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

PostgreSQL

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

Sensor Factory

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

sFlow

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

SMTP&IMAP and SMTP&POP3 Round Trip Sensors

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

Fixed

Sensors


SNMP Cisco UCS System Health

We have removed the 'failure predicted' channels from the SNMP Cisco UCS System Health sensor:
  • Fan Failure Predicted
  • Fan Module Failure Predicted
  • Power Supply Failure Predicted
These channels do not return the expected values from the target device.

Note: Sensors of this type that have already existed before updating to this PRTG version will not show values in these channels anymore. Please add the sensor anew to avoid empty channels. For details, please see this Knowledge Base article: Why are some SNMP Cisco UCS System Health sensor channels not showing any information anymore?

SNMP HP ProLiant Network Interface

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

SQLv2 Sensors

  • The setting "Use Data Table Value in Sensor Message" of SQLv2 sensors will now be saved when you create a device template with these sensors.
  • Several fixes for processing block comments in SQL scripts.
  • We have improved the handling of DECLARE statements for SQLv2 sensors. For example, you can now use DECLARE without semicolons (;). This allows you to copy&paste SQL queries directly from your SQL Server Management Studio, for example, into your .sql file that you use with your SQL sensor.

SSH Script and SSH Script Advanced Sensors

Security fix for SSH Script and SSH Script Advanced sensors: we have improved the parameter check for SSH script sensors.

Syslog Receiver

Summarized email notifications triggered by Syslog Receiver sensors showed a broken header. We have fixed this issue.

VMware (SOAP) Sensors

We have fixed a timeout bug that occurred in certain cases when adding a VMware (SOAP) sensor.

VMware Datastore (SOAP)

In PRTG language versions other than English, the VMware Datasore (SOAP) sensor created the Free Space channel twice while one of these channels (the one with the name in the selected language) did not show any data. We have fixed this issue. If you use another language version than English, please add running sensors of this type anew after updating to this version to benefit from the fix.

WMI Vital System Data (V2)

We have removed the option to add a WMI Vital System Data (V2) sensor for CLR Memory: % Time in GC because the returned value appeared to be meaningless.

Fixed

Notifications


SMS Notifications

PRTG will not log errors for custom SMS notifications anymore if the HTTP response of the provider is in the 200 range. This fix will also prevent PRTG from re-sending SMS notifications that already have been successfully delivered.

Fixed

Cluster


Failover Nodes

We have fixed a bug that caused objects on failover nodes to not synchronize and update in a timely manner in certain cases.

Fixed

Server


API

  • The API call /api/discovernow.htm will correctly return an error if a non-existing device template is passed with the call instead of just returning OK.
  • The columns "datetime" and "timeonly" will now return the same, correct time.
  • The API call /api/getsensordetails.json will now return a value (true or false) for the "favorite" property.

Fixed

Various


Various

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


Changed

Login


Default Login

We have removed the Default Login button. If you use the default credentials of PRTG, the login fields are now pre-filled:
  • Login Name: prtgadmin
  • Password: prtgadmin
Use the Login button to proceed. If you have changed the default credentials (which we strongly recommend!), the login works as before: just enter your PRTG user account credentials and log in.

Improved

Device Templates


Create Device Template

PRTG will now show the names of the sensors that were added to a device template as result of the Create Device Template function.

Improved

Sensors


Amazon CloudWatch

We have added the region Canada (Central) to the Amazon CloudWatch Alarm, EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS sensors. You can now monitor all your instances in Canada (Central)!

HTTP Data Advanced

We have added advanced options to the HTTP Data Advanced sensor: you can now specify the protocol version (HTTP 1.0 or HTTP 1.1), define the user agent, and use custom HTTP headers.

HTTP Push

HTTP Push Count, HTTP Push Data, and HTTP Push Data Advanced sensors support TLS 1.2 encryption (lower TLS/SSL versions are not supported).


Important

Server


Auto-Update

We have fixed a bug that prevented the PRTG server from notifying you about the availability of a new version and performing a full automatic update. This bug was introduced with PRTG version 16.4.28 (November 2016), so you might have missed all intermediate versions until now. You could still manually check for the latest update and download and install it on the auto-update page in the PRTG web interface.

Please install the new PRTG version 17.2.31.2153 now. PRTG will then again be able to perform unattended updates for future versions. You can use the Auto-Update function of your PRTG installation for the update. In the PRTG web interface, choose Setup | Auto-Update from the main menu bar and click Check for Latest Update and Download. As soon as the update is ready, click Install Update 17.2.31.2153.

See also PRTG Manual: PRTG Status—Auto-Update


Fixed

PDF Reports


PDF Reports

PDF reports work properly and show header, graphs, and tables correctly again.


Fixed

Server


User Rights

On cluster installations, PRTG user accounts with read-only or read/write rights were not able to access sensor overview pages anymore. We have fixed this issue.


Fixed

Sensors


APC UPS Health Template

Several fixes to the APC UPS Health device template

Business Process

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

SSH Disk Free

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

Fixed

Reports


PDF Reports

We have fixed a bug that caused empty graphs in PDF reports in certain cases.

Fixed

Server


Installer

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

Fixed

Various


Various

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


Fixed

Server


Core Server

In certain cases, the update of PRTG to one of the previous 17.x.30 versions caused an access violation if a Windows Updates Status (Powershell) sensor had more than 17 channels. This could prevent the PRTG server from starting. We have fixed this issue.


Fixed

Sensors


SSH Sensors

su and sudo will correctly run commands with elevated rights if you set it in the "Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems" settings.

APC UPS Health

When running the auto-discovery with the APC UPS Health device template, the Run Time Remaining channel of the sensor that is added by the template will now show the correct value.


Fixed

Probe


Security Token

We have fixed a bug that occurred with some sensor types where refresh tokens of the impersonation were acquired with the wrong session type. This could result in timeouts in scan threads.

Fixed

Server


Core Server

We have fixed a bug that caused toplist data files to be corrupted on PRTG core server shutdown.


Fixed

Reports


PDF Reports

Fixed a bug that caused reports to be incomplete depending on the system's DPI settings where the core server is located.

Fixed

Sensors


HTTP Push Sensors

Fixed a regression that broke multiple HTTP Push based sensors running on the same listening port.


Fixed

Reports


PDF Reports

Creating PDF reports works again.

Fixed

Auto-Discovery


Buffalo Device Template

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

Fixed

Sensors


SNMP Custom Table

You can add the SNMP Custom Table sensor again.

SQL Sensors

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


Important

Server


Historic Data Reports

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

Changed

Sensors


Windows Sensors

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

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

Fixed

Sensors


Active Directory Replication Errors

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

Event Log (Windows API) and WMI Event Log

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

HTTP Push Sensors

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

SNMP Custom String

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

SNMP Custom Table

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

SNMP HP ProLiant Network Interface

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

VMware Datastore (SOAP)

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

Windows Updates Status (Powershell)

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

Fixed

Server


API

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

PhantomJS

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

Schedules

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

Security

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

Uptime Threshold

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

Fixed

Cluster


Cluster

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

Fixed

Various


All Parts of PRTG

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

Manual Update

Updated user manual

Changed

Tree Version


Tree Version Update

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


Fixed

Server


Update

In rare cases, the update installer invalidated the license. We have fixed this issue.

Core Server

We have fixed a core server crash due to probe connections being denied because of IP filter, access key, or incorrect security protocol.


Fixed

Notifications


Push Notifications

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


Fixed

Sensors


WMI Sensors

Major stability and performance improvements for WMI sensors! Special thanks to Colby for all the help with this!

WMI Microsoft SQL Server Sensors

You can add WMI Microsoft SQL Server 2008 - 2016 sensors again!


Fixed

Sensors


Citrix XenServer Sensors

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

Custom Script Sensors

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

NetApp cDOT Sensors

The NetApp cDOT sensors support ONTAP 9.

Python Script Advanced

The Python Script Advanced sensor correctly replaces parameters again.

sFTP Secure File Transfer Protocol

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

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

SNMP Custom String

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

SQL Sensors

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

SSH Sensors

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

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

Fixed

Licensing


License Activation

Stability improvements for the changed license activation system

Fixed

WebGUI


Find Duplicates

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

Maps

Fixed a small security issue with inactive user accounts

Fixed

Notifications and Schedules


Tags

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

Fixed

Emails


Content-Type

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

Fixed

Various


All Parts of PRTG

Many other minor improvements and fixes to all parts of PRTG

User Manual

Updated user manual


New

Sensors


SNMP Buffalo TS System Health

We are glad to present the first dedicated PRTG sensor for Buffalo storage systems with this version! The new SNMP Buffalo TS System Health sensor monitors your Buffalo TeraStation NAS and can show you important system health values like memory and CPU usage, uptime, number of errors and warnings, failover status, firmware update availability, and the RPSU status.

To monitor even more data of your Buffalo TeraStation, we also deliver the new device template Buffalo TeraStation NAS. Run an auto-discovery with this template to automatically create SNMP Custom Table sensors with additional useful information, for example, array status. disk smart status, and iSCSI status. Of course, this device template will also create sensors for traffic, memory and load average on your TeraStation.

Improved

Sensors


Docker Container Status

The Docker Container Status sensor provides the option to choose the container name as identification method instead of the container ID. In some cases, the ID of the target container changes regularly so that the name might be a better identification method to ensure seamless monitoring.

GitLab Build Status

Several improvements and fixes for the GitLab Build Status sensor: for example, you can identify projects and branches more easily.

SNMP SonicWALL VPN Traffic

The SNMP SonicWALL VPN Traffic sensors provides the option to use IP ranges as identification method for connections.

SSH Disk Free

When adding the SSH Disk Free sensor, you can now select up to 100 disks you want to monitor with one sensor. For the sake of stability and performance, this approach ensures that the sensor will not create too many channels.

SSL Certificate

The SSL Certificate sensors supports Elliptic Curve Cryptography (ECC) certificates in addition to RSA certificates. Depending on the used cryptosystem, the sensor will show suitable security ratings for the public key length.


Fixed

Sensors


WMI Sensors

  • The connection to the target device now also works if you use the external IP address of the probe system as device address while defining Windows credentials.
  • Stability fixes for connection establishment for all WMI sensor types
  • WMI Event Log sensor will not cause probe restarts because of timeouts anymore.

Fixed

Licensing


License Activation

Stability improvements for cluster failover activation with the changed license activation system

Fixed

PRTG Administration Tool


Logs

Sending logs via FTP when using the PRTG Administration Tool works again.

Copyright © 1998 - 2017 Paessler AG