February 4th 2016 - Version

  • Important: We renewed the certificates with which we sign PRTG. We strongly recommend that you update to this version to be able to seamlessly update to future versions of PRTG.
  • Improved [Security]: We fixed the root cause for the security issue that has been hotfixed with PRTG version This version also contains various optimizations in context of this security flaw.

January 25th 2016 - Version

Important: Critical security update for PRTG! During our internal tests we discovered a possible vulnerability in PRTG versions through In these versions a "path traversal attack" was possible under certain circumstances. This vulnerability is very unlikely to be exploited and we do not know of any case where this has actually happened. We will not publish technical details to not put the affected versions at risk.

To secure your PRTG server please update to PRTG version or later immediately! Of course, you can contact our Customer Service team if you need assistance.

November 2015–January 2016 - Version 15.4.21/16.1.21

  • Changed [Sensors]: The HTTP sensor and the HTTP Advanced sensor now properly work with Server Name Indication (SNI).
    Important: Depending on the current endpoint configuration of the target webpage, this change can result in malfunctioning sensors that worked correctly so far. Please see this Knowledge Base article for details: https://kb.paessler.com/en/topic/67398
  • New [Sensors]: You can now use 4 different sensor types to monitor your NetApp clustered Data ONTAP (cDOT) storage system. They access the cDOT web API via SOAP and can monitor your
    • NetApp cDOT Aggregate
    • NetApp cDOT I/O,
    • NetApp cDOT Physical Disk,
    • and NetApp cDOT System Health.
  • New/Changed [Emails]: PRTG sends out emails in beautiful HTML now, for example, email notifications. With this improvement we also removed the “email options” in the notification delivery settings for the ease of use. You can include your custom logo and footer now using the delivered HTML template file. For details, please see this article: https://kb.paessler.com/en/topic/65782

    Important note: Previous changes to the message (email body) part of your email templates will be lost when you update to this version.The email body will be replaced by PRTG's new standard content! You can change the content of plain text emails in the email notification settings. If you use one of the "comments" placeholders in an email notification, resolved placeholders will have an according heading as of this version (see this article for details about placeholders).

    Important note: Custom email headers and footers that you have defined in the email options of previous PRTG versions will not be used anymore! Please edit the new HTML email template files to add your custom header and footer to PRTG's emails, as described in the article linked above.
  • New [WebGUI]: The PRTG welcome page and the help and support center come with a new fresh design! The welcome page is now similar to a dashboard and shows for example, all current alarms, open tickets, and information about your license. It is now an even better starting point for your everyday network monitoring! If you have any questions about, for example, your license, you can now also directly send a message to our customer support using a contact form on the help center.
  • Improved [Sensors]:
    • SSL Certificate sensor shows a warning if the certificate revocation list cannot be queried.
    • SNMP Cisco System Health sensor has a better logic for the naming of fans and system health components.
    • Syslog and SNMP Trap Receiver sensors are not in beta status anymore.
    • SIP Options Ping sensor has a new channel using lookups for status codes.
  • Improved [Notifications]: You can enable notification delivery debug logging also for Amazon SNS notifications. For details, please see this article: https://kb.paessler.com/en/topic/55363
  • Security fix regarding user rights
  • Changed [Sensors]: We renamed the HP BladeSystem sensors to SNMP HP BladeSystem Enclosure System Health and SNMP HP BladeSystem Blade. The channel “Enclosure Condition” of the system health sensor includes the new status “failed”.
  • Changed [Mobile GUI]: The Mobile Web GUI is deprecated as of now so we will remove this user interface from PRTG soon. For details, please see the article https://kb.paessler.com/en/topic/66920
  • Several fixes and improvements for lookups
  • Updated language files
  • Updated user manual

January 18th 2016 - Version

  • Hotfix for EXE notifications and PDF reports
  • WMI Service sensors receive data again after executing the automatic "Start/restart service" option.
  • Updated language files: Brazilian, Chinese, French, Spanish

December 14th 2015 - Version

  • Changed [Email Notifications]: For text only email notifications, you can enter custom text with placeholders. In the email notifications settings, choose the option "Text with custom content" for the setting "Format" and provide custom content in plain text format.
  • Bugfixes [Email Notifications]:
    • PRTG sends plain text emails with the correct 'text/plain' content type now.
    • Forwarding HTML emails with Outlook caused broken links in these emails. This works correctly now.
      Note: If you have already installed a previous 15.4.21 version, please adjust header_custom.htm manually as described in https://kb.paessler.com/en/topic/65782 
  • Change [Sensors]: The HTTP sensor and the HTTP Advanced sensor now properly work with Server Name Indication (SNI). For details, please see above.

December 2nd 2015 - Version

  • Creating Toplists works again.
  • Saving changes to the settings of Ping sensors works again.

November 30th 2015 - Version

  • Bugfixes [Sensors]:
    • WMI Microsoft SQL sensors can now monitor instances with an underscore (_) symbol in the name.
    • Cloud sensors retry requests for each response code that is not 200 and the read timeout is now 10 seconds.
    • Radius v2 sensor can now use passwords that include double quotes (“)
    • The DNS sensor properly compares the IP address again.
    • SSL Security Check sensor: Fix for “connection refused” errors.
    • Amazon CloudWatch RDS sensor now shows correct values for “Free Storage Space” (average instead of sum).
    • SMTP&POP3 Roundtrip sensor: Fix for the “log file is open” error that occurred when the debug option has been enabled.
    • Exchange Database (Powershell) sensor uses the correct lookup file automatically if you add this sensor anew. For details, please see https://kb.paessler.com/en/topic/66875
    • Oracle Tablespace sensor now handles auto-extensible files properly.
  • Many other improvements and bugfixes for the Enterprise Console and all other parts of PRTG

October 2015 - Version 15.4.20

  • New [Sensor]: The new Business Process BETA sensor is a powerful and very flexible sensor that allows you to give a summary status of whole business processes while monitoring several process components. This means that you can create your very own and individual sensor with channels based on data from other sensors ("source sensors") that are specific to your network and show a cumulated sensor status.
  • Improved [Sensors]:
    • We changed the approach that the Cloud HTTP and Cloud Ping sensors use to show data. For example, the Cloud Ping sensor now uses TCP ping which works faster than the previously used ICMP method.
    • The Packet Sniffer sensor uses new libraries and drivers to improve compatibility and performance.
    • WMI HDD Health sensor uses now the channel unit “Custom” so that you can use lookups.
  • Changed [Server]: We use a different JSON library for custom sensors that return data in JSON format.

  • Changed [PRTG Cloud]: The PRTG cloud is now reachable under https://api.prtgcloud.com:443. Please ensure your PRTG server can reach this address to use Cloud HTTP and Cloud Ping sensors as well as push notifications.
  • The option „Load Lookups" which we temporarily removed is reachable again under Administrative Tools.
  • Stability improvements
  • Updated user manual
  • Many minor improvements and fixes to the Enterprise Console and all other parts of PRTG

November 11th 2015 - Version

  • Email activation did not work properly.

November 9th 2015 - Version

  • Fix for the SSL Security Check BETA sensor

November 2nd 2015 - Version

  • Minor bugfixes

October 27th 2015 - Version

  • Bugfixes [Sensors]: Minor fixes for Cloud HTTP and Cloud Ping sensors, for the Packet Sniffer sensor, and for the DNS sensor
  • Security fix for the web interface and other minor fixes

October 21st 2015 - Version

  • Bugfix [WebGUI]: Dropdown menus in tables (for example, on the "Notifications" tab of a monitoring object) did not work properly in Firefox.
  • Several other minor fixes

October 19th 2015 - Version

  • Bugfixes [Sensors]
    • MongoDB System Health sensor now supports 64 bit return values.
    • Common SaaS sensor sporadically showed an access violation.
    • Dell PowerVault MDi Logical Disk sensor could not read disk 0 properly.
    • Oracle Tablespace sensor: Fix for the error "Parameter -isdif is missing or Parameter -channelnames is missing"
    • WMI Security Center sensor showed a warning status for “up to date, on access scan running”.
    • HTTP Data Advanced sensor occasionally showed an error when processing JSON data.
    • Fixed a potential memory leak caused by the SSL Certificate sensor
  • Bugfix [WebGUI]: Automatic logout timer did not work correctly.

September 2015 - Version 15.3.19

  • New [Sensors]:
    • The Common SaaS BETA sensor monitors the response times of several common Software as a Service providers like Google Apps, Office 365, Salesforce, and GitHub. PRTG adds this sensor to each probe device automatically, so you get alerts immediately if your cloud services are not reachable anymore.
    • This version also includes 4 new sensor types to monitor the cloud services Dropbox, Microsoft OneDrive, Google Analytics, and Google Drive.
    • We replaced the Amazon CloudWatch sensor. You can now choose between 7 CloudWatch BETA sensors, each one dedicated to one CloudWatch service: EBS, EC2, ElastiCache, ELB, RDS, SNS, and SQS.
    • The new Python Script Advanced sensor can execute a Python script that returns valid JSON or XML and show values in different channels.
    • The SSL Certificate BETA sensor monitors the certificate of a secure SSL/TLS connection. This sensor type supersedes the outdated HTTP SSL Certificate Expiry sensor.
    • The VMware Datastore (SOAP) sensor monitors the disk usage of a VMware data store. This sensor type supersedes the outdated SSH VMWare ESX(i) Disk sensor. The VMware (SOAP) sensors now also support session pooling. You can define session pooling in the device settings.
  • New [WebGUI]: New installations of PRTG will automatically show an initial device tree with devices and sensors in the network. PRTG starts creating it already during the install process of the PRTG server. This happens super-fast so you can see monitoring data at the first start without filling out any forms or going through any detailed setup steps!
  • Improved [Notifications]: You can now specify the encoding for syslog messages. Choose between UTF-8 or ANSI for this notification type.
  • Improved [Libraries]: The libraries overview now shows the security context for each library, which is the user account that created the library.
  • Improved [Server]: Stability and performance improvements for lookups.
  • Changed [WebGUI]: We replaced the Configuration Guru from PRTG with a new setup assistant. This Smart Setup is less complex than the "old" guru and helps creating an initial monitoring setup that already shows interesting data about a network.
  • Changed [Security]: If the port that is originally configured for the PRTG webserver is not available when using a secure SSL connection, the server now tries port 8443 as fallback to keep the secure connection. If this port is also not available, PRTG tries from port 32000 on until it finds an available port and keeps the SSL connection.
  • Changed [WebGUI]: New installations do not have an automatic object numbering anymore. If you add new sensors, reports, maps, or libraries, the object name will not get a number appended. For details, see this article: https://kb.paessler.com/en/topic/53903
    Note: Existing installations which update to this version are not affected. If you want this behavior, you have to edit the Windows registry manually as described in the article linked above.
  • Changed [Maps]: We replaced existing default icons (PNGs) with SVGs for a better scaling. This changes also the icons in already existing maps. Note that this might affect the look of your existing maps, so please check them after the update.

  • Improved/Changed [Sensors]:
    • The minimum scanning interval for the Windows Updates Status (Powershell) sensor is now fixed at 60 minutes (1 hour).
    • Oracle SQL v2 and Oracle Tablespace sensors support the service name in addition to the SID to identify the target instance.
    • SNMP Custom Table sensor has two new placeholders for name templates: [tablename] and [rowidentifier]
    • The VMware Host Hardware Status (SOAP) sensor can now ignore known warnings and errors from the VMware host.

October 6th 2015 - Version

  • Bugfixes [Sensors]:
    • Some fixes for the SNMP RMON sensor
    • Adding sensors with an OIDlib containing lookup definitions failed with "invalid pointer operation".
    • Port sensor could show strange values in some scenarios.
  • Updated language files

September 21st 2015 - Version

  • Saving sensor settings did not work when section Schedules, Dependencies, and Maintenance Window was open (inheritance unmarked).
  • Some other minor fixes.

September 14th 2015 - Version

  • Bugfix [Probes]: The PRTG Probe service does not change the timezone value in the Windows registry anymore.
  • Bugfixes [WebGUI]: Security fix for the web interface.

  • Bugfixes [Sensors]:
    • SNMP RMON sensor: Port name update with ifalias did not work and the channel mask mechanism “32bit only” did not work.
    • SNMP Custom Table sensor: Default selection for the channel column field caused an OID error.
    • SNMP LenovoEMC Physical Disk sensor: We adjusted the used OID to the new Lenovo version.
    • SNMP Dell PowerEdge Physical Disk sensor used the wrong lookups for iDrac
    • Event Log (Windows API) could not use more than one EventID erroneously.
    • SNMP Cisco System Health sensor: We fixed a bug that caused an error with the message “[number] is not a valid integer”.
    • Dell PowerVault MDi Logical Disk sensor could not find virtual drives.
    • SSH sensors support the symmetric ciphers AES192 and AES256
    • SNMP HP ProLiant Network Interface sensor could not find network adapters because of incorrect MAC addresses.
    • SQL v2 and HTTP Data Advanced sensors did not calculate difference channels correctly.
    • We fixed a bug in the Sensor Factory that might have caused strange sensor behavior.
    • HTTP sensors: SNI domain was not set correctly
  • Bugfixes [API]:
    • The API call duplicateobject.htm creates a default name if the name parameter in the call is not defined.
    • Change trigger (<NotifyChanged>) did not work properly in custom sensor scripts.
  • Bugfixes [EC]:
    • Table requests (for example, sensor lists, alarms) did not work when there was a proxy between EC and PRTG core server.
    • Many other fixes and improvements.
  • Tree version update: The configuration file of this version is not downwards compatible with previous PRTG versions.
  • Updated user manual
  • Many other fixes and improvements to all parts of PRTG.

July/August 2015 - Version 15.3.18

  • New [Sensors]:
    • The SNMP Custom Advanced BETA sensor can monitor numerical values from up to 10 custom OIDs in different channels.
    • The SNMP Custom Table BETA sensor can monitor numerical values from an OID that returns an SNMP table.
    • The Oracle Tablespace BETA sensor can monitor a tablespace on an Oracle server. It shows the online status, the overall status, as well as free space and blocks.
    • The Exchange Database DAG (Powershell) sensor can monitor the DAG status of a database on an Exchange server via PowerShell and shows the status of the cluster and replications.
    • The SNMP HP BladeSystem Server Blade sensor and the SNMP HP BladeSystem System Health sensor monitor status and system health of HP BladeSystems via SNMP.
  • Improved/Changed [Sensors]:
    • Windows Network Card sensor can recognize more network cards.
    • Traceroute Hop Count sensor needs .NET 4.0
    • WMI Terminal Services (Windows 2008+) supports higher operating systems than Windows 2008 so we added a + sign to its name
  • Changed [Browsers]: The PRTG web interface does not officially support Internet Explorer 10 anymore. You can still access PRTG with IE10 but you might not be able to display and use the full featured Ajax web interface.

August 19th 2015 - Version

  • Bugfix [Sensors]: Toplists for Flow and Packet Sniffer sensors contained empty rows (saving an empty selection could corrupt the PRTG configuration)

August 18th 2015 - Version

  • Bugfix [Sensors]: SNMP Cisco System Health Sensor showed "Memory is not a valid integer value" in some cases

August 12th 2015 - Version

  • Bugfixes [WebGUI]:
    • Security fix for the web interface
    • Object selection did not work when editing dependencies and library nodes
    • Dropdown lists did not work properly when using Firefox.
    • User access rights to the "Map Designer" did not work correctly.
  • Bugfix [Lookups]:
    • Changing channel settings of custom sensors with lookups caused a damaged display of sensor and channel gauges.
    • We temporarily removed the option „Load Lookups" from Administrative Tools. It will back in an upcoming version. Until then, please restart your PRTG server manually to (re-)load lookups.
  • Updated user manual

August 3rd 2015 - Version

  • Bugfix [Sensors]: Exchange sensors did not work on probe systems that run on 32-bit Windows versions
  • Bugfix [GUI]: Date/time picker did not work properly

July 28th 2015 - Version

  • Bugfixes [Sensors]:
    • Exchange Database and Exchange Mailbox (Powershell) sensors: With this version we provide some important fixes for these sensor types. To take full advantage of these fixes, please add these sensors anew to your PRTG installation! The parent device has to be the Exchange server that hosts the database you want to monitor.
      • In PRTG language versions other than English these sensors created additional English channels and sent data to these channels. This resulted in a "gray" sensor status because translated channels did not get data. We fixed this issue but you have to add affected sensors anew.
      • You could not change the "Channel Unit Configuration" settings (unit for returned file size) for these sensor types. We fixed this issue but you have to add affected sensors anew.
    • DNS sensor now sends the DNS query to the port that you specify in the sensor settings.
    • Stability improvements for channel definitions in SQL v2 sensors
    • SNMP Physical Memory sensor recognizes changing indexes to avoid No Such Name (SNMP error #2) errors
    • Auto-discovery for SSH sensors on Linux systems works with private key
    • Microsoft SQLv2 sensor works with SQL servers that use automatic port assignment
    • Fixed a parsing error of the MongoDB System Health sensor ("Could not convert variant of type (Null)")
    • SNMP Traffic sensor supports angle brackets in ifdescr
  • Bugfix [Reports]: Corrected sorting of sensors filtered by tag
  • Updated Chinese language version
  • A lot of other improvements and fixes to all parts of PRTG.

June/July 2015 - Version 15.2.17/15.3.17

  • New [WebGUI/Server]: You can set up sensors to run at a specific time (or at various specific times) on a day. Using a special syntax, you can define the desired point(s) in time in the "Scanning Interval" settings of the PRTG System Administration. For details, please see the Knowledge Base: https://kb.paessler.com/en/topic/3723
  • New [Freeware]: There are no restrictions for scanning intervals anymore in the PRTG freeware edition. Like in commercial and trial versions of PRTG, you can now use scanning intervals below 60 seconds (we recommend that you do not use less than 10 second intervals).
  • New [Remote Probes/Cluster]: PRTG now includes Cluster support for Remote Probes! If you run a PRTG cluster, all your remote probes can now send their monitoring data to all your cluster nodes. As soon as you acknowledge a new remote probe connection to your PRTG core server, the connected remote probe will be visible on all your master and failover node(s). The probe connects automatically to the correct IPs and ports of the cluster nodes. You can define the cluster connectivity of each remote probe in its "Administrative Probe Settings". This way, you can still see monitoring data of remote probes even when your master node fails. Note: For existing remote probes in a cluster installation, your action is required to activate this new feature. For more details, please see our blog article Cluster Support for Remote Probes: Failover Nodes Show Remote Probe Data
  • Changed [WebGUI/Administration]: You cannot change the Probe Connection Port anymore via the PRTG web interface or via the PRTG Administration Tool. The communication between probes and PRTG server runs on port 23560 by default. Because this standard port is sufficient in most cases, we removed the option to change it in a GUI. If you changed the probe port previously, PRTG will keep this port for probes also after you update to this PRTG version.
    Note: If you need to change the probe connection port, please do so in the Windows registry. For details, please see this article: https://kb.paessler.com/en/topic/65084
  • Improved/Changed [WebGUI/Server]:
    • Probe Connection IPs are editable again via the PRTG web interface.
    • PRTG now creates a log file "mibparser.log" for better debugging of MIB imports.
    • It is now possible to allow PRTG user accounts with read-only rights to change their passwords by themselves. You can define this option in the corresponding user account settings.
    • Read-only users cannot view names of security related fields in settings anymore (for example, names of credentials, domains).
    • Some minor security improvements and fixes.
    • Stability improvements for Active Directory integration
    • Maximum length of one entry in summarized email notifications is now 1000 characters (was more limited before).
    • Access keys for Remote Probes support angle brackets < >
    • Debug logs for notification delivery (https://kb.paessler.com/en/topic/55363) create one log file for each sent notification.
    • Performance improvements for libraries.

  • Improved/Changed [Sensors]:
    • We removed the Google Analytics sensor because Google does not support the API that this sensor uses anymore. We will work on a new version of this sensor type.
    • Proxy support for Cloud Ping and Cloud HTTP sensors: These sensor types can use the proxy server as defined in the "Core & Probes" settings of PRTG.
    • We renamed the SNMP Juniper System Health sensor to SNMP Juniper NS System Health sensor, where "NS" is for NetScreen, to indicate supported devices in a better way.
    • Update of the SSH library to support additional key exchange mechanisms (diffie-hellman-group14-sha1).
    • Several improvements to the IP on DNS Blacklist sensor: As of this version, this sensor type follows the RFC 5782 where IPv4-based DNSxLs (blacklists and whitelists) must contain an entry for for testing purposes. In previous versions the sensor did not check this, providing a false sense of security when using non (or no longer) existing DNS blacklist servers which always report that the IP is not listed. Because of this change, you might get errors now that were not there previously if you request outdated blacklist servers.
    • SNMP Cisco ASA VPN Users sensor is limited to 50 users: https://kb.paessler.com/en/topic/64053
    • SNMP Cisco System Health sensor gets more specific tags to describe the type of the monitored system health parameters in a better way. Note: This results in losing custom tags when saving this sensor as template.
    • Channel names of SNMP Printer sensor have changed, so existing sensors will have unused "undefined" channels after updating. Please add affected sensors anew to get rid of gray channels.
    • SNMP Custom String Sensor with improved warning and error messages when using keyword search.
  • Updated user manual

July 1st 2015 - Version

  • Bugfixes [Sensors]:
    • Fix for SNMP sensors: Interface names that start with spaces caused issues (for example, when using the SNMP Traffic sensor)
    • Fixed an issue with HTTP sensors that caused the error "No mapping for the Unicode character exists in the target multi-byte code page"

June 16th 2015 - Version

  • Bugfix [Sensors]: Windows Network Card sensor now works with teamed network cards
  • Bugfix [Notifications]: Stability improvements for push notifications
  • Minor improvements and fixes

June 9th 2015 - Version

  • Bugfixes [Sensors]:
    • Debug setting of MySQL v2 sensors works now. Time format in logs is changed to 24h.
    • SNMP Juniper System Health now shows correct values for memory/session usage.
    • Port sensor show a "Read Timed Out" error when using the options to send commands and check response.
    • Fix for custom units of the Sensor Factory sensor.
    • SNMP SonicWALL VPN Traffic sensor supports angle brackets < > in policy names.
    • SNMP Disk Free sensor could not be added to a device via auto-discovery if it had been added and deleted manually before.
    • PerfCounter Custom sensor supports angle brackets < > in Performance Counters.
    • HTTP sensors support special characters in the keyword check option.
    • SQL v2 sensors re-load the query file when it changes.
    • Fix for the SNMP HP ProLiant Network Interface sensor: This bug caused a "MAC address not found" error.
    • We improved the memory usage of the HTTP Transaction sensor.
    • SSH sensors can now also scan for available monitoring items if you use a private key for the login into the target device.
    • Windows Network Card sensor: Teamed network adapters with multiple configurations appeared only once when scanning for available monitoring items.
  • Bugfix [Maps]:
    • Links using the IM protocol work now.
    • Links from public maps to sensors did not work properly.
  • Bugfix [Libraries]: Filtering by tags with + and - works as expected again.
  • Updated user manual
  • Various fixes and improvements to the Enterprise Console 
  • Many other minor fixes and improvements to all parts of PRTG

April 2015 - Version 15.2.16

  • New [Sensors]:
    • The HTTP Data Advanced BETA sensor can access a web server and retrieve data in XML or JSON encoded format.
    • The SNMP Juniper System Health BETA sensor can monitor the system health of a Juniper device.
  • Improved/Changed [WebGUI/Server]
    • Speed improvements for the auto-discovery
    • Proxy support for push notifications
    • Improvements on security, performance, and stability
    • Improved memory usage for probes
    • You can disable auto-scaling of PRTG Maps if you append the parameter &noautoscale to a Map's URL
    • Settings tabs of sensors and add sensor error dialogs now directly show you sensor requirements, tips, and links to useful articles in the Knowledge Base.
    • We limited scanning intervals to max. 10 days for better stability
    • PRTG does not start auto-update downloads anymore if there is less than 500 MB disk space available.
    • You can now review the history of changes to the settings in the PRTG Administration Tool via the log file \Logs (Debug)\PRTG Administration Tool Changelog.log
    • We increased the data purging timeout so that purging a huge amount of data works more reliably.
    • Improved downtime calculation
  • Improved/Changed [Sensors]
    • All sensors that use the .NET framework now need .NET 4.0. This affects these sensor types: FTP Server File Count Sensor, IP on DNS Blacklist Sensor, Pingdom Sensor, PING Jitter Sensor, Traceroute Hop Count Sensor, Windows Logged In Users Sensor, Windows MSMQ Queue Length Sensor
    • You can now create SSH VMware ESX(i) Disk sensors on vSphere 6.0 (ESXi 6.0)!
    • WMI Custom sensor supports the expression SELECT COUNT(*). You can use this statement if you want the number of entries in the result set to be returned alternatively to a direct value from a field. For example: SELECT COUNT(*) FROM Win32_Process WHERE Name='explorer.exe'
    • EXE/Script Advanced sensor: If the <error>-tag in the custom script contains 0 (<error>0</error>), the sensor does not show an error anymore (Before the value was ignored and the existance of the <error> tag itself triggered an error). Note: All other content with the tag still causes an error, including <error/> and <error></error>
    • When channel limits are reached, sensors now show the "last message" in addition to the threshold sensor message.
    • DHCP sensor now uses "Option: (54) DHCP Server Identifier" as server address, if available
    • Dell MDi Physical Disk sensor supports additional Dell MDi devices; stability improvements
    • You can now enforce encryption for the Microsoft SQL v2 sensor.
    • IMAP Roundtrip sensor now supports the IMAP search command which leads to better performance. It also deletes the roundtrip email more reliably now.
    • FTP sensor shows the answer of the target server in the sensor message.
    • SSL Security Check sensor is now part of the auto-discovery.
    • RDP sensor support IPv6.
    • SNMP HP ProLiant System Health sensor has the new channel "Integrated Management Log Status". This channel helps to find out why the sensor throws an error.
    • You can now use SQL v2 sensors in custom device templates.
    • RADIUS V2 sensor is not "beta" anymore. The previous RADIUS sensor is now deprecated.
    • File Content sensor with enhanced settings for encoding and debugging
    • SSH sensors with improved debug setting
    • Windows Registry sensor reads the (default) entry if you leave "Value Name" empty.
    • SSH SAN Physical/Logical Disk sensors provide now an "advanced" command mode to query additional device statistics.
    • We added a globe to all cloud sensors to indicate the sensor status in a nice way.
    • Stability improvements for flow sensors that use a buggy customflowrules.osr
    • SNMP Custom String sensor now always uses its own settings to interpret a value retrieved via Regular Expressions instead of the "Windows Format" settings.
    • PerfCounter IIS Application Pool sensor shows the pool status "unavailable" now as an error. We removed the "beta" status for this sensor.
    • EXE/Script Advanced sensors now keep all white spaces in channel names which are defined in the returned XML code. Previously this sensor type reduced the number of white spaces in channel names automatically to one. This new behavior might result in new channels for your existing EXE/Script Advanced sensors while older channels do not get data anymore.
  • New/Improved [EC]
    • We made the Enterprise Console more compatible to PRTG servers that differ in version: It can now connect to every server where the third number in the version number is equal to the third number of the EC version. For example, EC version can now connect to any server with the version 15.1.16.xxxx
    • Enhanced filter options for log tables
  • Updated language files
  • Updated user manual

April 28th 2015 - Version

  • Bugfixes [WebGUI/Server]
    • Adding groups to libraries caused an Ajax error
    • "Size by Sensors/Priority" for sunburst and treemap view is working again
    • Reports were not created for the correct time in certain cases when using "Current Period".  We also improved the order of sensors in a report and you can add the same sensor several times to a report.
    • You can now sort sensor data tables correctly by channel IDs.
    • In some cases, downtime values were calculated incorrectly in table rows.
    • Fixed sorting of objects in reports
  • Bugfixes [Sensors]
    • NetApp sensors showed "invalid data" errors if less thresholds than measurements were returned
    • IMAP sensor could not handle multipart emails properly
    • Quality of Service (QoS) Roundtrip sensor shows correct values for the RTT (Minimum) channel
    • Fixed proxy usage for the HTTP SSL Certificate Expiry sensor
    • SSH SAN sensors: Scanning for available items sometimes caused memory leaks and the scan did not find a single "drive" without the plural -s.
    • SQL v2 sensors: Better handling of special characters.
    • Microsoft SQL v2 sensor in some cases used the default port instead of the port configured.
    • WMI Custom String sensor: Change Trigger did not work in some cases.
    • Syslog and SNMP Trap Receiver sensors with better error handling in case ports are already in use.
    • Stability improvements for the Windows Scheduled Task sensor.
    • SNMP RMON sensor uses 64 bit counters if available.
    • INI File Content Check sensor supports float numbers.
  • Many other minor improvements and fixes to all parts of PRTG.

February/March 2015 - Version 15.1.14/15.1.15

  • New [Freeware]: You can now use 100 sensors for free with the Freeware Edition!
  • New [Sensors]
    • SNMP Cisco UCS Blade sensor: monitors the health status of a blade server in a Cisco UCS device.
    • SNMP Custom Lookup (BETA) sensor monitors a string value returned by a specific OID and maps it to a sensor status.
    • Cloud HTTP (BETA) sensor monitors the loading time of web servers from various locations worldwide via HTTP using the new PRTG cloud
    • Cloud Ping (BETA) sensor monitors the ping time to a target device from various locations worldwide using the new PRTG cloud
      Note: You can only use a certain number of Cloud HTTP and Cloud Ping sensors per PRTG installation (currently 5 each). For details, please see this article.
  • Improved/Changed/Bugfixes [Sensors]
    • FTP Server File Count sensor with a dedicated port setting
    • SNMP Cisco ASA VPN Traffic sensor has now the option to keep the "Up" status if there is no active connection. You can specify this behavior in the sensor settings.
    • QNAP Physical Disk: Damaged disks now result in a "Warning" status of the sensor (instead of an error); this allows to continue monitoring of other values.
    • Fixed keyword check of the HTTP Transaction sensor, response strings did not trigger status changes ("response must include"/"response must not include")
    • SCVMM sensors: Improvements to version check for add-snapin / import modules
    • Various fixes to the "Custom HTTP Headers" function of the HTTP XML/REST Value sensor.
    • Debug options ("write result to disk") for HTTP Push Data sensors and Windows Terminal sensors
    • Windows Last Update sensor showed a false error message that said that Windows Registry Service is not running in some cases
    • SNMP Custom String sensor threw an error for an empty string when triggering a change notification.
    • Fixed Smart URL Replacement for HTTP Advanced Sensor in compatibility mode
    • More descriptive channel names for Cisco System Health sensors
    • MySQL v2 sensor could not process a specific data type ("System.UInt64")
    • SSH SAN sensors with better differentiation between "wrong data format" and "timeout" errors
    • SNMP Dell PowerEdge System Health sensor could not process channel masks
    • Windows Performance Counter sensors sporadically showed an error when a PerfCounter connection had to be re-created
    • WMI SQL sensors shows incorrect values for the category "locks"
    • File Content sensor with better error handling and transmitting only new lines now optimized also for very large files
    • SSH SAN System Health sensor now supports devices that provide no other information than name, value, and status.
    • Windows Registry sensor correctly queries its parent device again. It mistakenly queried the parent probe before.
    • SNMP Windows Service sensor had problems to show service names correctly in some Windows language versions (for example, Russian, Japanese)
    • Sensor channels that show if something (for example, a service or device) is on/off or successful/failing have now a more beautiful and comprehensive graphical display.
    • WMI Microsoft SQL sensors does not round values of channels with "per second" units to integers anymore. This caused incorrect sensor results for some metrics (for example, for "deadlocks per second") previously.
  • New/Improved/Changed [WebGUI/Server]:
    • Speed optimizations for auto-discovery
    • New API call shows the legend of data graphs (ID, name, unit, color): /api/chartlegend.json?id=[sensor_id]
    • New API call /api/getsensordetails.json?id=[sensorid] is the JSON equivalent to the existing XML call.
    • Stability improvements to location resolution in Geo Maps
    • "Quick ranges" on historic data pages set incorrect dates
    • Stability improvements for Toplists
    • Restructured "Setup" menu
    • Library triggers are now completely independent from the "inherit trigger" switch on the "Notifications" tab of objects in the device tree.
    • PRTG Administration Tool does not allow any more to enter used ports when defining ports for web server and probe connections. Improved server restart rules.
    • Notifications: Logs now show when a notifications was triggered but could not be delivered because there is no corresponding active notification contact for the target user.
    • Libraries: We preset the filter for „Linked Object" in the Node Display Settings with „Root" for your convenience.
    • The PRTG Status page now shows how busy PRTG was for you in the new "Activity History".
    • Geo Maps zoom fixed.
    • You can make the passhash of your PRTG user account visible with a "Show Passhash" button. We previously removed the passhash display for security reasons.
    • Amazon SNS notifications did not work when containing the special characters * or § in subject or message.
    • Buttons in the "Compare Sensors" dialog did not work.
    • Library node filter "by status" did not work.
  • Updated user manual: Now with a neat overview of available channels and screenshots in all sensor chapters!
  • Updated language files
  • Deeper integration of the online help into the PRTG web interface
  • "Configuration Guru" enhanced with helpful video tutorials

March 31st 2015 - Version

  • Bugfix [Sensor]: Improvements for SSH SAN sensors
  • Updated language files for Czech

March 31st 2015 - Version

  • New [Freeware]: You can now use 100 sensors for free with the Freeware Edition!
  • Fixed sensor status for SSL Security Check Sensor
  • Minor improvements

March 16th 2015 - Version

  • Bugfix [Server/Probes]: Fixed a bug in SSL/TLS connections that could cause very high memory consumption in some cases
  • Bugfix [Cluster]: Re-joining a cluster did not work properly if the failover node was in a cluster before and reverted to standalone temporarily
  • Several stability improvements and fixes

March 10th 2015 - Version

  • Bugfix [Sensors]: Bugfix for QoS Sensors
  • Bugfix [Sensors]: Table lists of Syslog and SNMP Trap Receivers are sorted correctly again
  • Bugfix [Toplists]: Cloning sensors with Toplists works correctly again
  • Bugfixes [EC]: Sorting of table lists works again, as well as generating historic data HTML reports
  • Updated language files for German, Chinese, Brazilian, Dutch, French, and Spanish
  • Minor improvements and fixes

February 25th 2015 - Version

  • Bugfixes [Core/Server]
    • When using the historic data function for "all nodes" in a cluster, percentiles were incorrect.
  • Bugfix [MiniProbes]: Stability improvements for connections via PRTG's mini probe interface
  • Bugfixes [EC]:
    • Fixed an error when deleting active server connections
    • Now showing better default values for start date in date time picker for "Acknowledge Until" and "Pause Until"
    • Some minor fixes and improvements to the Enterprise Console.
  • We also implemented various other minor fixes and improvements to all parts of PRTG that did not make it onto this page.

December 2014/January 2015 - Version 14.4.13/15.1.13

  • New: Free-to-Use Push Notifications
    With this update, we introduce a great new notification option: You can now send push notifications to your Android or iOS devices—for free, included in every PRTG version, even in the PRTG Freeware! This is a very comfortable way to get alerts from PRTG. All you need is PRTG for Android or PRTG for iOS and you can set up your free push notifications within seconds. Please see the Knowledge Base article How can I send push notifications with PRTG? for details.
  • New [WebGUI/Server]:
    • PRTG introduces responsive design so that the webGUI automatically adjusts to the size of your screen. This allows you to see even more information at a glance!
    • To get a much better and more detailed picture about your devices, PRTG now analyzes the devices you add and recommends appropriate sensor types on the device overview page. Only one click to add a sensor suggestion directly to the device and you never miss important information about your equipment again!
    • Together with push notifications, we introduce notification contacts. PRTG users can now define and edit their own dedicated ways to get notifications to email address(es), phone number(s), and push device(s). For the notifications types "Send Email", "Send SMS/Pager Message", and "Send Push Notification" you can now choose a user or user group from a list to send a notification to the current notification contacts of the according recipient(s).
    • You can now generate configuration reports for various objects in PRTG like users, user groups, maps, reports, and system configuration. This function is available under Reports | Configuration Reports in the main menu bar.
    • You can now specify the channels you want to show in historic data graphs that you generate via the "Historic Data" tab of a sensor.
    • You are now able to zoom into data graphs and to scroll on the time axis with according control buttons to analyze your monitoring data even smarter.
    • Maps ('dashboards') have an auto-scaling option to adapt automatically to your screen size.
    • You can now enter your PRTG license key directly into the webGUI so you do not need to use the Administrator tool for this purpose anymore.
    • You can now define a custom port for your Mini Probe connections.
    • PRTG removes masked passwords that you entered into settings pages from the support bundle and does not send them.
  • New [Sensors]:
    • The Dell PowerVault MDi Physical Disk sensor show statistics for a physical drive on a Dell PowerVault storage system. Note: We renamed the existing Dell PowerVault MDi sensor to Dell PowerVault MDi Logical Disk sensor because of this.
    • The WMI Microsoft SQL Server 2014 sensor monitors the performance of a database
    • The MongoDB System Health sensor monitors the status of a MongoDB server via HTTP and the admin web console
  • New [EC]:
    • Facelift: The new appearance of the Enterprise Console comes with a fresh and clear user interface and new graphics, similar to the webGUI
  • Improved [WebGUI]:
    • Map editor with better performance and new map objects "QR codes" and "traffic lights"
    • PRTG notifies you if Similar Sensors analysis is off
    • You can filter device lists by tag
    • You can use the logical operators + (must have) and - (must not have) in library and table tag filters, e.g., -windows would show all sensors/devices that do not have "windows" as tag, +A;B-C would mean "objects with the tags A and B but not with the tag C"
    • Added a quick print button for QR codes on device lists
    • Tables have more columns to show more information
    • The "Compare Sensors" feature has more options to analyze compared data
  • Improved [Sensors]:
    • SNMP Traffic sensors with new option to ignore 'deactivated' (ifAdminStatus=down) status
    • WMI Security Center sensor now uses lookups
    • Channel names of probe and system health sensors are now more meaningful
    • SNMP Linux Disk Free sensor enhanced with a channel for free INodes
    • SNMP QNAP sensors use more appropriate OIDs now, including fallback. Note: If you already use QNAP sensors and experience strange values now, please add the sensors anew.
    • Google Analytics sensor has new metrics (exceptions, fatalExceptions, exceptionsPerScreenview, fatalExceptionsPerScreenview) and allows special characters in the password field.
    • Hyper-V Virtual Storage Device sensor supports Hyper-V on Windows Server 2012 R2
    • HTTP XML/REST Value sensor supports Smart URL Replacement and has an optional setting to define custom HTTP headers
    • Various sensors have now an optional debug log setting
    • FTP Server File Count sensor supports SSL connections and can count the files in a specific folder or in all subfolders. It also supports port definitions: When monitoring via a URL, you can add the port number with ":[port]", and when checking a folder on the parent device, the sensor provides an extra port setting
    • EXE/Script Advanced, SSH Scrip Advanced, and HTTP Push Data Advanced sensors support now JSON results
    • Windows Network Card sensor supports teamed adapters on Windows Server 2012
    • Amazon CloudWatch sensor with additional channels for averages and with more expressive error messages
    • SNTP sensor supports IPv6 devices and we improved its stability
    • HTTP Advanced sensor with new authentication method "Digest Access Authentication" and the option to check for keywords in the response
    • SNMP Custom String sensor has a new setting that allows you to define the format of the result value: String, hexadecimal bytes (e.g., MAC addresses), or decimal bytes (e.g., IP addresses)
    • Windows MSMQ Queue Length sensor can show the number of messages in outgoing queues
    • AVM FRITZ!Box WAN Interface sensor asks for credentials when you add it manually. Note: If an existing sensor shows an error after a Fritz!OS update, please add the sensor anew to see the new credentials option.
    • Complete rework of the RADIUS sensor: better performance and compatibility with RADIUS servers
    • SNMP Linux Meminfo sensor has 6 new channels to monitor used physical memory, used swap memory, and used memory on the whole system (percentage and absolute values)
    • SNMP RMON sensors use the "Port Name Template" of the SNMP Compatibility Options of the parent device
  • Improved [Security]:
    • We implemented further improvements to the overall security of PRTG for a better protection against potential attacks.
    • Account pages and QR codes do not include the password hash anymore. Note: If you need a user account's passhash for API programming, please use the according API function to query a passhash using username and password.

February 11th 2015 - Version

  • Updated language files for English, Czech, and Japanese
  • Minor fixes

February 3rd 2015 - Version

  • Minor fixes

January 28th 2015 - Version

  • Updated [Language]: New Japanese language version
  • Bugfix [MiniProbes]: Stability improvements for connections via PRTG's mini probe interface
  • Several minor improvements and fixes

January 13th 2015 - Version

  • Bugfix [Sensors]: Registry Sensor did not work in some cases
  • Several minor improvements and bugfixes