Welcome to the first PRTG Release News on the blog in 2019. I hope you had a fantastic start to the new year and have bravely stuck to your good intentions so far. Our developers are already...
Read the complete blog post here
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!
Manual: Using the "Software Auto-Update" Function of PRTG
Previous Versions and other Release Channels
March 4th 2019 – Version 19.1.48.2929
Blog article
Fixed
Server
Cluster and Reports |
Reports contain data from failover nodes again if defined in the report settings. |
Cluster and Sensors |
It is possible to add meta-scan sensors to devices on the cluster probe again. In previous 19.1.48 versions, the meta-scan did not work and never finished on the cluster probe so that you could not add any meta-scan sensors. |
Dependencies |
Dependencies work as expected again when a master object returns from a down status, so that all dependent sensors will automatically resume monitoring as soon as the master object comes back. In previous 19.1.48 versions, dependent sensors did not resume in some cases but showed a paused by dependency status even if the target device was reachable again. |
Fixed
Probe and Sensors
Probe and Sensors |
We fixed a potential memory leak that occurred when using many SNMP sensors with multi get as request method. |
.NET Tickets |
We reduced the amount of created PRTG ToDo tickets that inform about the required update to .NET 4.7.2 on a probe system. PRTG will now only create a new ticket when there is not an open ticket about .NET 4.7.2 on the probe yet. |
Note
Known Issue: Down (Acknowledged)
Acknowledged by |
In current versions, PRTG does not show the user account who acknowledged the down status of a sensor. The user name is missing in the sensor message and in the log of a sensor in Down (Acknowledged) status. Status: resolved with PRTG 19.1.49.1916 |
February 19th 2019 – Version 19.1.48.2891
Fixed
Sensors
SNMP Dell PowerEdge Physical Disk |
The SNMP Dell PowerEdge Physical Disk sensor lists all available disks again when you add a new sensor of this type. In the previous 19.1.48 versions, it only showed one disk after the meta-scan in the Add Sensor dialog. |
SNMP HP BladeSystem Enclosure System Health |
The SNMP HP BladeSystem Enclosure System Health sensor works again. In the previous 19.1.48 versions, sensors of this type always failed with the error message Duplicates not allowed. |
Fixed
Server
Dependencies |
Master dependencies work again when they were taken over by cloning a device, so that all dependent sensors will automatically pause by dependency as soon as the master object fails. In the previous 19.1.48 versions, dependent sensors on cloned devices did not pause by dependency but showed a down status if the target device was not reachable, which could result in receiving many unnecessary notifications, for example. |
February 14th 2019 – Version 19.1.48.2876
Fixed
Server
Sensor Graphs |
We fixed an issue with the PRTG graph data cache recalculation. After updating to PRTG version 19.1.48.2868, historic data graphs did not show data in certain cases because of the issue. If you were affected by the issue, please don't panic, your data is not lost. Your data will be shown again after installing the new PRTG version 19.1.48.2876. |
Fixed
Sensors
SNMP Linux Disk Free |
The SNMP Linux Disk Free sensor works as expected again. In the previous PRTG version 19.1.48.2868 it failed when monitoring certain Linux distributions like, for example, Debian 6, Debian 7, and CentOS 6. Affected sensors showed an error with the message List index out of bounds (0). |
February 11th 2019 – Version 19.1.48.2868
Important
Known Issues
SNMP HP BladeSystem Enclosure System Health |
SNMP HP BladeSystem Enclosure System Health sensors will show an error with the message Duplicates not allowed after the update to PRTG version 19.1.48.2868 in certain cases. We recommend that you wait with the update of your PRTG installation until we publish a fix for the issue if you are using SNMP HP BladeSystem Enclosure System Health sensors. Status: resolved with PRTG 19.1.48.2891 |
Sensor Graphs |
After updating to PRTG version 19.1.48.2868, historic data graphs will not show data in a few cases. This happens due to an issue with the PRTG graph data cache recalculation. If you are affected, please don't panic, your data is not lost. We will provide a fix for the issue as soon as possible and your data will be shown again. Status: resolved with PRTG 19.1.48.2876 |
SNMP Linux Disk Free |
SNMP Linux Disk Free sensors will show an error with the message List index out of bounds (0) after the update to PRTG version 19.1.48.2868 when monitoring certain Linux distributions. Affected are, for example, Debian 6, Debian 7, CentOS 6, Mandriva Linux 7.2 Odyssey, Ubuntu 12.04. Please note that these are affected distributions from which we only know right now. We are currently working on a fix and recommend that you wait with the update of your PRTG installation until we publish it if you are using SNMP Linux Disk Free sensors. Status: resolved with PRTG 19.1.48.2876 |
Improved
Sensors
Lookups |
We added two new standard lookup files to PRTG that reflect the Boolean values 1 (true) and 0 (false). Use prtg.standardlookups.boolean.statetrueok as lookup if you want to have an up status for true (returned 1), use prtg.standardlookups.boolean.statefalseok if you want to have an up status for false (returned 0). |
SNMP HP ProLiant System Health |
We added the lookup status noPowerInput(17) to the standard lookup file prtg.standardlookups.hp.powersupplystatus of the SNMP HP ProLiant System Health sensor. The sensor will now show an according down status if your target device returns this value. |
SNMP Sensors |
We changed the method that SNMP sensors use on creation to search for available monitoring items on the target device ("meta-scan"). SNMP sensors will now use GETBULK requests during meta-scan instead of GETNEXT. With SNMP GETBULK, the sensors request 10 OIDs at a time by default, which leads to performance improvements in comparison to GETNEXT that requests only 1 OID at a time. The change also affects the System Information feature, so that the DDoS protection of QNAP devices should report alerts less often because of PRTG. Note: Only SNMP v2c and SNMP v3 support GETBULK, for SNMP v1 you still have to use GETNEXT. You can change the setting in the SNMP Compatibility Options of the target device in PRTG, section Walk Mode. |
Improved
Server
PRTG Core Server |
This version includes various minor and major performance improvements, especially for the handling of a lot of remote probes. We also improved the scalability of the server with CPU cores and memory, the server startup times, and the post-processing of configuration changes (special thanks to electromichi for pointing us to this issue!). |
Improved
WebGUI
Maps |
The Top 10 lists Longest System Uptime and Shortest System Uptime are now available as map objects. |
Notification Delivery |
You can now directly test your SMTP and SMS settings on the Notification Delivery tab to check immediately if your settings work without changing pages and losing your context. Just click the button Test SMTP Settings or Test SMS Settings and see if your delivery settings work. |
Object History |
The object history of a notification template now indicates if settings of this template have been changed, Also, resuming an object like a sensor or device from paused status appears in the object history as of this version. |
Fixed
Sensors
Business Process |
Saving the settings of a Business Process sensor is now also possible when you only remove an object from the channel definition because the Save button is now active after the change. Also, when deleting an object from the channel definition, all objects are still shown and not only the first 7 entries so that you can easier delete more than 1 object. |
File and Folder |
File sensors and Folder sensors now use a negative value to indicate when the timestamp of a modified file is in the future. This approach will prevent the sensors from showing false warnings in such scenarios. |
File Content |
You can now add File Content sensors with the auto-discovery using your own device template. In previous versions, PRTG erroneously added File Content sensors as File sensors to newly created device templates, so that an auto-discovery with this device template only added File sensors. |
IMAP |
You can now use the setting Check connectivity only, do not process emails without providing credentials for the monitored mailbox. Credentials are not required in this scenario but were requested when you have manually added the sensor in previous versions. |
Sensor Factory |
The Sensor Factory sensor handles angle brackets (<>) in the channel definition in a better way now. The sensor overview tab will not appear broken anymore if you use these characters, but please note that the sensor gauge still will not look perfect in such cases. |
SNMP Cisco System Health |
The SNMP Cisco System Health sensor now shows a down status with error code PE268 if the sensor runs against an invalid OID. The sensor will show a down status with error code PE269 if there are one or more channels for which the sensor cannot query data. In previous versions, the sensor status was not expressive enough in such cases because it only showed unknown (gray color) or up with empty channels. |
SNMP IBM System X System Health |
We fixed the appearance of the gauge for the Overall Status channel of the SNMP IBM System X System Health sensor. The gauge did not properly appear because the sensor used a unit type not supported by lookups. The sensor now also shows the return message if the target device returned an invalid value (sensor value -1). Important: To apply the fix, please add the sensor anew. |
SNMP Linux Disk Free |
The SNMP Linux Disk Free sensor now creates channels for all disks on the target device. In previous versions, the sensor stopped searching for available disks during sensor creation as soon as there was a missing OID in the index table and so did not create channels for each disk on the target system. |
SNMP Synology Logical Disk |
The SNMP Synology Logical Disk sensor is now able to recognize when the order or name of a volume changes. In previous versions, it was possible that the sensor monitored an incorrect volume in such cases, which resulted in wrong monitoring data. |
Windows Updates Status (PowerShell) |
We fixed an issue with the Time since last update channel of the Windows Updates Status (PowerShell) sensor that still showed incorrect values in certain use cases after the improvements in the previous PRTG version 18.4.47. |
Fixed
Security
Login |
|
Reports |
We removed PRTG credentials (login name and passhash) from the URL of HTML reports that appeared in certain cases. |
Fixed
Server
Auto-Discovery |
We fixed an issue with the custom meta-scan that you can use with the auto-discovery but did not work as expected in certain cases. Please note that this functionality is still not officially supported. |
Installer |
PRTG now correctly switches from the 32-bit version to 64-bit after a server restart when the machine on which PRTG runs upgraded from less to more than 6GB RAM. This did not work in previous versions when a server restart was pending (status "PendingReboot") because of some Windows update or similar. |
Logging |
Several fixes and improvements for the logging framework |
PRTG Administration Tool |
If you change the Local Storage of Data Files and Monitoring Database folder on the Core Server tab in the PRTG Administration Tool, PRTG will also restart the local PRTG probe service along with the PRTG core server service now to immediately apply the changes. This is necessary to write data into the correct folder. |
Server Startup |
We fixed an issue that occurred when adding or editing a Sensor Factory sensor using Internet Explorer 11 or Edge. In this case, some control characters were wrongly added to the PRTG configuration file, which resulted in a failing start of the PRTG server. The error message in this case was: Sorry, could not start PRTG Core Server (Web server) [...] Formula empty. |
Updating from Version 18.1.37 or Older |
Direct updates from PRTG version 18.1.37 and previous versions to the current PRTG version 19.1.48 do work. It was not possible to directly update from these older versions to the previous PRTG version 18.4.47 because the PRTG server was not able to start in this case. |
Fixed
Notifications
Slack and Teams |
Slack and Microsoft Teams notifications now recognize line breaks within placeholders and show the whole content in a received notification. |
Teams |
The message when pausing a monitoring object like a sensor for 60 minutes via a received notification in Microsoft Teams now correctly is Paused via Microsoft Teams. In previous versions, PRTG showed the wrong pause message Paused via Slack. |
Fixed
WebGUI
Dark Theme |
|
Graphs |
|
Maps |
|
Multi-Edit |
|
Sensor Gauges |
Sensor channels that show data as percentage now show gauges with minimum 0% and maximum 100% by default and appropriately display set limits. |
Tables |
Improved table layout and usage on various places, for example:
|
Tickets |
|
Top 10 Lists |
Top 10 lists of sensors will not show sensors without current last value anymore. |
Various |
This version includes dozens of other minor fixes and improvements for the PRTG web interface. This will remarkably improve your overall experience with PRTG! The fixes and improvements affect the following parts of the web interface, among others.
|
Fixed
Various
All Parts of PRTG |
Various other fixes and improvements to all parts of PRTG, updated user manual, updated language files |
Note
Probe and Sensors
EXE-based Sensors |
Future versions of PRTG will need .NET version 4.7.2 installed on all computers running a probe for all sensor types that require the .NET framework. You will receive a ToDo ticket in PRTG for each affected probe after each probe update if .NET 4.7.2 is missing. For more details, please see this Knowledge Base article. |
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 |
|
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 |
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:
|
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 |
|
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
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
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. |
KOSTENLOSER DOWNLOAD
Jetzt kaufen
