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


calendar

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.

Improved

WebGUI


Notifications

  • You can now see all defined notification methods in your PRTG user account settings at a glance. The Notification Templates overview table has a new column that shows the Actions a notification template will perform when it is triggered.
  • You can now use a search field to filter for existing notification templates when you add or edit a Notification Trigger.

Maps

We improved the readability of map objects with status-related background colors.

Improved

Server


PRTG Core Server

Several performance and stability improvements for the PRTG core server

Graphs

We updated the engine that PRTG uses to create data graphs. Thanks to the updated graphs engine, stacked graphs look better now!

Logging

This version includes some more improvements for the logging framework.

Improved

Sensors


HTTP Push Data Advanced

The HTTP Push Data Advanced now supports UTF-8 characters in the section of received messages and can display, for example, Chinese, Japanese, or Russian characters in the sensor message.

SNMP Trap Receiver

The SNMP Trap Receiver sensor now supports several modes for bindings that you can use with the syntax bindings[oid,value,mode].

Mode can be:
  • substring: This is the default mode that works like bindings[oid,value].
  • exact: This mode enforces an exact match of a value.
  • equal, greater, greaterorequal, less, lessorequal: This mode compares received numbers with the defined value.

Windows Updates Status (PowerShell)

We changed the approach of the Windows Updates Status (PowerShell) sensor to avoid down states that are not meaningful enough. As of the current PRTG version, the sensor will always create the channel Time since last update. All other channels only show up if the sensor can retrieve according data. Furthermore, the channel value is more accurate now.

Fixed

Server


PRTG Core Server

We fixed an issue with the PRTG core server. In certain cases, the issue lead to access violations in the PRTG server system that could result in issues with sending notifications or unexpected server restarts with sensors in unknown status.

PRTG GUI Starter

We fixed several issues with the PRTG GUI Starter. It will work more reliable now.

Security

We fixed a possible XSS vulnerability.

Server Startup

We fixed an issue with the flowid field in toplists of NetFlow sensors that could result in an exception during the startup of the PRTG server. The PRTG server did not start in such cases.

Fixed

Sensors


Channels

  • You can edit channel names in a sensor's channel settings again (where supported). In previous versions, the Name field in the channel settings often was read-only by mistake.
  • If you select the Data option Display in percent of maximum in the settings of a sensor channel, PRTG will now interpret any set Limits as percentage based on the maximum value to avoid false alarms.

Event Log (Windows API)

The Exclude Filter of the Event Log (Windows API) sensor now correctly disregards all events that you have added to the filter, for example, event IDs.

Flow Sensors

Stability improvements for the sensor types IPFIX, NetFlow V5, NetFlow V9, and sFlow: The fields FlowID, InboundInterface, and OutboundInterface in custom toplists are now stored with their field ID. In previous versions, they were stored as index, which could lead to issues when the list of fields changed.

Lookups

Lists of lookup files are sorted alphabetically again when you select value lookups for a sensor channel. IDs of lookups are also loaded case insensitively again to prevent issues when you override default lookups with customs lookups.

Sensor Factory

PRTG correctly calculates historic data of the Sensor Factory sensor again. In the last preview version, live data was used to calculate historic data instead of averages. This resulted in wrong values.

SNMP Custom String Lookup

We fixed an issue with device templates that include an SNMP Custom String Lookup BETA sensor. When running an auto-discovery with the template, PRTG created an unused channel that was not defined for the sensor.

SNMP sensors

SNMP sensors that support this functionality now only replace text within square brackets in the sensor name if the text is an OID or a defined variable. All other text will appear in the sensor name as it is.

SNMP Trap Receiver

The SNMP Trap Receiver sensor now properly handles quotation marks (") in the filter for bindings and can find strings that contain quotation marks.

UPS Health (Generic) Template

The device template UPS Health (Generic) now also supports Tripp Lite UPS, so running an auto-discovery with the template will create suitable sensors for your Tripp Lite UPS.

WMI Sensors

You can now add the sensor types Windows Physical Disk I/O, WMI Exchange Server, WMI Exchange Transport Queue, WMI Logical Disk I/O, and WMI Vital System Data (V2) using the auto-discovery. The auto-discovery could not successfully add these sensor types in previous versions.

Fixed

Notifications


Amazon SNS

We updated the signature version of Amazon SNS notifications to Signature Version 4, so it is now possible to send SNS notifications from AWS regions that only support this signature version like, for example, Canada (Central) (ca-central-1).

SMS

Using the placeholders %SMSNUMBER and %SMSTEXT in the path of custom URLs for SMS notifications works again. Due to an encoding issue, the placeholders only worked in the query string of a URL since PRTG version 18.3.43 and you received an unknown protocol error if your custom SMS provider requires number and text as part of the path.

Fixed

WebGUI


Credentials

We disabled the browser auto-complete of login and password fields in authentication sections of several sensor types (for example, HTTP Advanced and IMAP sensors). If you have saved your PRTG login credentials in your browser, your browser will not automatically fill in the credentials into PRTG settings sections anymore.

Tables

Paging on large tables and the selection of table items in the Add Sensor dialog works properly again. In previous versions, only sensors selected on the current table page were created.

Various

Several other minor fixes and improvements for the PRTG web interface

Fixed

API


XML

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

Fixed

Various


Language Files

Major update for all language files!

All Parts of PRTG

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

Note

Probe and Sensors


.NET Version

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

calendar

November 20th 2018 – Version 18.4.46.1754


Blog article

All You Need to Know About PRTG Release 18.4.46

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



Fixed

Sensors


SNMP Traffic

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

calendar

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.

calendar

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.

calendar

October 19th 2018 – Version 18.4.45.1898


Blog article

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

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



Fixed

Sensors


VMware Host Performance (SOAP)

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