Release Notes
for PRTG 22

FTP sensors

HPE 3PAR Drive Enclosure

HTTP Push Data

MQTT Subscribe Custom

Zoom Service Status

CPU usage

PRTG Administration Tool

Security

Security

• sha256_exe 28F05875EA31067881B2E04B3557F1BBC3D174D2064CCBA3E93BD4F1EC2E7839
• sha256_zip A82725C7C7BBA8E116F31030857BD3DE099FF5B7C40248E04A1DB425A617318E

• sha256_exe 0DD1952B8EE8A56F77FBA968366794BFA58ABEFC38151192D378EAF35607091F
• sha256_zip 64F4918CE265ED58EC98996516D59AA97BB7BBC614AAD644E2F90C9DAB22F106

Discontinued Sensors with PRTG 22.4.81

HTTP v2

Ping v2

Sensors

• The sensor information on the sensor overview page now displays placeholders while the object information is loading.
• We fixed an issue for the Filter by keywords search option on the sensor list.

Channels

• The primary channel of a sensor now has a pin icon indicator in the card for sensor channels.
• We fixed an issue for primary channels that caused an unknown error. The issue occurred only when the primary channel of the sensor had not yet received any data.

Web Interface

• We implemented a new subpage for sensors that shows all limit channels in interactive line graphs. You can select a timespan for the graphs from predefined options: live, short, medium, long.
• We added time ranges to the timeseries interval picker that is available in the Graphs tab of a sensor.
• We fixed an issue where deleting objects, likes sensors, devices and groups, led to an unknown error.
• You will now receive a proper message for objects like sensors, devices and groups when they are moved to a paused status.

API

• We fixed an issue for sensor channels with lookup values that were not correctly formatted. The values are now displayed as percentages. The issue occurred in the /api/v2/experimental/timeseries/{id}/{type} endpoint.
• We fixed an issue for new created devices in the experimental settings endpoints /experimental/devices/ID/settings and /experimental/sensors/ID/settings that led to a 404 not found error when you performed a get request.
• You can now get information about settings and structure of a device with the GET endpoint /api/v2/experimental/devices/{id}/settings that we first introduced with PRTG 22.4.80.1553 for the experimental section.

PRTG application server

All parts of PRTG

Languages

Installer

• sha256_exe D02BE6A5A28ACE2C0EDF905BAFBC54542F5EF067206CE2FBF92E1472E4D6E338
• sha256_zip A2DE8530143F750AEE1429CFF71D408CC9155E01E9E4E6667D9C77F081A6DEC1

• sha256_exe 12092FA3FC6DEDE54B246CFC9C445328862B21E04A3A63B1D79888AC71A37911
• sha256_zip D985BCFD406B498C0D35FB0F2172738A34CCD6C63F5679AF015B85668D201F50

Microsoft 365 Service Status Advanced

Redfish Power Supply

Veeam Backup Job Status

Cloud HTTP sensor, Cloud Ping sensor

NetApp System Health v2

NetApp v2 sensors

• For the NetApp LIF v2 (BETA) sensor we fixed an issue in the Throughput Read, Throughput Total and Throughput Write channel settings that are now configured as counter channels, as well as the NetApp NIC v2 (BETA) sensor channels Link Down Count, Receive Errors and Transmit Errors where you can now also set limits.
• With this version comes the experimental NetApp SnapMirror v2 sensor (BETA) that we introduce additionally to the already released experimental NetApp v2 sensors (BETA) in PRTG 22.3.79.2108. The sensor supports the new ONTAP REST API as of ONTAP 9.6

Port v2

Sensors

• You can now switch between the channels of a sensor via dropdown menu in the channel detail dialog.
• We added an overview tab with channel cards to the sensor view.

API

• The experimental section now includes a GET endpoint for the settings of a device /api/v2/experimental/devices/{id}/settings. This endpoint is still under development and does not include all features yet.
• We fixed an issue where cloned groups with added devices and sensors did not show the correct path for the sensor channels.
• We fixed an issue in the /experimental/timeseries/{id}/live endpoint that in some cases wrongly displayed gaps in graphs for precalculated data.
• We fixed an issue for the channel ID filter where you could not search for comma separated IDs with the endpoint /experimental/timeseries/{id}/{type}.

API Keys

Documentation

PRTG application server

Discontinued Sensors with PRTG 22.x.81

Microsoft 365 Mailbox

PRTG Administration Tool

Security

Zoom Service Status

Cache recalculation

Tree version update

All parts of PRTG

Languages

FortiGate System Statistics sensor

Microsoft 365 Mailbox sensor

• The filter option in the Microsoft 365 Mailbox Settings is now divided into Contains All and Contains Any to enable a filter for different words in mails. Please note that already created sensors that had the filter option Contains will have the option Contains All after updating to this version.
• You can now choose different folders in your mailbox to monitor when you add the Microsoft 365 Mailbox sensor.
• We removed an empty settings field for Microsoft OAuth 2.0 Specific that appeared when you added a Microsoft 365 Mailbox sensor. You can see the following information for the Microsoft OAuth 2.0 specific field when the sensor has been added in the sensor settings: The OAuth 2.0 authorization renew feature is currently under development. If you change OAuth 2.0 settings in Microsoft Azure that require a reauthorization, you must add the sensor anew.
• On creation of the Microsoft 365 Mailbox sensor you will see a dialogue for the Shared Mailbox User where you can add a mailbox account from a different user.

API

Modbus sensors

NetFlow sensors

Sensor Security

• Exchange Backup (PowerShell) sensor
• Exchange Database (PowerShell) sensor
• Exchange Database DAG (PowerShell) sensor
• Exchange Mail Queue (PowerShell) sensor
• Exchange Mailbox (PowerShell) sensor
• Exchange Public Folder (PowerShell) sensor
• Citrix XenServer Host sensor
• Citrix XenServer Virtual Machine sensor
• Hyper-V Cluster Shared Volume Disk Free sensor
• RADIUS v2 sensor
• SIP Options Ping sensor
• HTTP Advanced sensor
• HTTP Transaction sensor

Script sensors

Server

EXE/Script sensors

AWS Cost sensor

Core Health (Autonomous)

• We improved the stability of the Core Health (Autonomous) sensor. Under certain circumstances, the sensor wrote error messages to the core.log file with each sensor scan.
• The Core Health (Autonomous) sensor as well as the Application Server Health (Autonomous) sensor show the correct status again when you deactivate the new UI and new API instead of remaining in status Unknown.

FTP sensor

HTTP sensors

• We fixed an issue with SNI inheritance affecting HTTP sensors. In previous versions, HTTP sensors showed a down status if the parent device had an IP address as host and the affected sensor was set to Inherit SNI from parent device. The error message in this case was Error connecting with SSL or similar.
• We improved the compatibility of HTTP sensors with certain web servers. HTTP sensors now only set the content-type application/x-www-form-urlencoded on POST requests because using it with GET requests resulted in a down status in some cases.

HTTP Transaction

Microsoft Azure Virtual Machine

NetApp LUN

SSL Certificate

Sensor creation

Login

Memory usage

Security

Start-up

Contact Support

Cisco Meraki sensors

FortiGate VPN Overview sensor

NetApp v2 sensors

Controls

• The back button now works as expected again on all pages in the new PRTG web interface.
• When the Show all sensors view on a Device Overview is selected, the view is now kept when opening a sensor and using the back button to navigate back to the Device Overview.
• You can now scroll horizontally and vertically on object information cards as expected again.

Errors

Sensors

Web interface

• Breadcrumbs are now dynamic and will be truncated if they exceed a certain length.
• Items in the Device List are now sorted as expected again.
• The URL of a device tree now reflects the filter status of the device tree to allow users to share specific device tree views.

Web interface

• We have improved the visibility of the buttons in the filter bar on small screens.
• We have improved the Reset filter button icon to clarify its function.
• The new PRTG web interface now displays the correct error page if the PRTG application server is not available.
• The Overview, Device List, and Sensor List tabs are now in horizontal orientation.
• You can now see all details about an object on its Object Information page.
• We updated and improved the layout of object headers.
• You can now right-click any sensor and select Show Channel Details to see the current measurement, limits, minimum and maximum measurements, and lifetime average or the lookup definition and status of the primary channel of the selected sensor. You can also click any channel on the sensor's Overview tab to open the channel details.

Documentation

PRTG application server

• The results returned by the /settings/public endpoint now contain graph setting data.
• We fixed a bug that caused an internal error if the ExecutionTimeoutInSecond was set to -1.
• We moved the /sensors/{id}/settings endpoint from the sensors section to the experimental section. The new URL path is now /experimental /sensors/{id}/settings.
• We improved the security of the PRTG application server.

Languages

All parts of PRTG

AWS RDS v2 sensor

IMAP & POP3 Roundtrip sensors

AWS EC2 v2 sensor

Cloud v2 sensors

• We fixed an issue for the Cloud HTTP v2 sensor and Cloud Ping v2 sensor that caused the sensors to run into an error with the message The queried field "response_time" is empty.
• The Cloud HTTP v2 sensor now inherits the Proxy Settings for HTTP Sensors that are given in the parent device.

FTP sensor

HTTP Advanced sensor

HTTP Apache sensor

Redfish System Health sensor

SSH sensors

SNMP Fujitsu System Health v2 sensor

WMI Vital System Data Sensor

API

• You can set the geolocation for your probes again with API call /api/setlonlat.htm.
• In very rare cases, acknowledged alarms for sensors that exist on a remote probe which is added to a cluster system and which reports to both nodes were not synced to the master node. The issue occurred with api call /api/acknowledgealarm.htm. Your acknowledged alarms will now be synced to the master node if you use the api call for down sensors on a remote probe within a cluster system.

Stability

Passwords

Common SaaS sensor

Python Script Advanced

Tree Version Update

FortiGate VPN Overview sensor

Microsoft 365 Mailbox sensor

NetApp

Controls

Device tree

Device list

Sensors

• We fixed an issue where objects were not paused and alarms were not acknowledged if the entered message exceeded the maximum message length.
• We added a validation for the pause message field and acknowledge message field that does not allow messages that exceed the limit of 1,500 characters.
• You can now pause large numbers of sensors as expected again.

Web interface

• We have improved the visibility of the buttons in the filter bar on small screens.
• We have improved the Reset filter button icon to clarify its function.
• The new PRTG web interface now displays the correct error page if the PRTG application server is not available.
• The Overview, Device List, and Sensor List tabs are now in horizontal orientation.
• You can now see all details about an object on its Object Information page.
• We updated and improved the layout of object headers.
• You can now right-click any sensor and select Show Channel Details to see the current measurement, limits, minimum and maximum measurements, and lifetime average or the lookup definition and status of the primary channel of the selected sensor. You can also click any channel on the sensor's Overview tab to open the channel details.

Documentation

PRTG application server

• The PRTG application server now returns the correct error response if the duration in the request exceeds the maximum duration.
• Pending requests no longer prevent the PRTG application server from stopping.

Swagger UI

All parts of PRTG

Discontinued Sensors with PRTG 22.x.81

Gitlab Build Status sensor

Microsoft 365 Service Status sensor

Map backgrounds, Device templates

Elasticsearch Upgrade

New SLA Report

Enhancements to Boards

Maps

Command line parameters

Python Script Advanced

Auto-Discovery

Channels

HTTP sensors

Microsoft Azure SQL Database

Modbus sensors

Redfish sensors

SNMP sensors

SSL Security Check

VMware Host Performance (SOAP)

Configuration

Notifications

Reports

Cisco Meraki Network Health

PowerShell Security Enhancement

REST Custom v2

• The REST Custom v2 (BETA) sensor now supports arrays in the request URL. Previously, the sensor shortened the arrays so that it did not return the desired values.
• Placeholders in the POST Body setting of the REST Custom v2 sensor now properly work. Previously, the resolution did not work after a first successful sensor scan.

Web interface

• We added a new and revised device overview.
• We improved the visuals of the device overview.
• We overhauled the lookup bars, added new styles, and updated their behavior.
• We added gauges to the device overview that display the channel limits.
• We improved several features in the device list view.

Device tree

Navigation

• Switching from the sensor overview to the mobile web interface no longer causes unknown errors.
• The dropdown list that opens when you click a breadcrumb now shows all child objects of the object again.

Controls

Filters

• Filters set when viewing further sensor results on sensor status cards are now reset again if you use the go back function of your browser.
• Filters set for a probe now persist when switching between the overview, device list, and sensor list.

PRTG application server

• The system startup screen now shows the correct IP address or DNS name when the TCP port for the PRTG web server was changed. In previous version, an incorrect port was displayed when the PRTG application server was running.
• We improved stability and performance of the PRTG application server.

Languages

All parts of PRTG

StartTLS connectivity

Access rights

HTTP Apache sensors

Okta

AWS Alarm v2

AWS EBS v2

AWS EC2 v2

AWS ELB v2

HPE 3PAR Drive Enclosure

HPE 3PAR Virtual Volume

Redfish Power Supply

Redfish System Health

SNMP Rittal CMC III Hardware Status

Modbus sensors

MySQL v2

PostgreSQL

SSH sensors

Sensor security

Microsoft Azure SQL Database

Veeam Backup Job Status Advanced

XML

Cisco Meraki Network Health

NetApp Volume v2

Administration

Improvement

Objects

PRTG application server

Performance

All parts of PRTG

Python Script Advanced

Signature

• Signature of \Program Files(x86)\PRTG Network Monitor\32 bit\PRTG Server.exe is not valid or
• Signature of \Program Files (x86)\PRTG Network Monitor\64 bit\PRTG Server.exe is not valid

Server

Server

Packet Sniffer

Single sign-on

• You have now the option to use GraphQL to retrieve group claims from Microsoft Graph when you integrate Azure Active Directory for single-sign on (SSO) in PRTG. With GraphQL, you can also properly create SSO user accounts that are member of more than 200 groups. The default approach for group claim retrieval is using an Access token as before.
• The login with a new SSO user account now succeeds even if there already is a user account with the same login name that only differs in upper case and lower case letters.

HTTP Push Data Advanced

Microsoft Azure sensors

SQL v2 sensors

Syslog Receiver

Historic data

Stability

Cisco Meraki sensors

• We improved the connection stability of the Cisco Meraki License (BETA) and Cisco Meraki Network Health (BETA) sensors. The sensors now also handle HTTP response code 429 that returns in case of breached request limits in a more comprehensible way.
• The meta-scan for available monitoring objects when adding the Cisco Meraki Network Health (BETA) sensor now succeeds even if the API access is disabled for some organizations so that you can still add the sensor in such cases.

NetApp System Health

Redfish sensors

• The experimental Redfish Power Supply (BETA) sensor can also monitor devices that return null for non-existent values. In previous versions, the sensor showed a down status in such cases.
• You can easier find Redfish sensors in the Add sensor dialog when you look for sensors that monitor devices of a specific vendor because the sensor descriptions now show supporters of the Redfish standard like Broadcom, Dell, Emerson, HPE, Intel, Lenovo, Microsoft, Supermicro, and VMware.

REST Custom v2

Device list

Web interface

• The Welcome page and the page footer now contain information about the installed PRTG version and the selected release channel.
• Down (Acknowledged) status icons on the monitoring overview are no longer cropped.

Controls

Tables

POST Requests

Sensors

• The Core Health (Autonomous) sensor now keeps working as expected if you deactivate the new UI and API.
• The Sensor Factory sensor now sends added and deleted channels to the sensor data and overview endpoints of the new API as expected.

Certificates

Performance

Documentation

Probe transfer

Languages

All parts of PRTG

Server

AWS Cost

DNS v2

• The DNS v2 sensor now also considers the authority section of the DNS response when counting and matching DNS records.
• Monitoring PTR records now works the same way as with the DNS v1 sensor. You can only provide the IP address as Domain Name and do not need to manually add .in-addr.arpa anymore.

Veeam Backup Job Status Advanced

• You can now also monitor file share backup jobs with the Veeam Backup Job Status sensor and with the Veeam Backup Job Status Advanced sensor. The sensors did not support this job type before. We also fixed the monitoring of replica and immediate backup copy jobs for which the sensors showed incorrect data in previous versions.
• We renamed the default primary channel Status of the Veeam Backup Job Status Advanced sensor to Last Result, which makes it clearer that this channel shows the status of the last backup job run. The separate Status channel that now appears shows the overall status of the backup job.

Oracle Tablespace

SSL Security Check

Channel Unit Configuration

• Bytes (Bandwidth): MB and Mbit/sec
• Bytes (Memory): GB
• Bytes (Disk): GB
• Bytes (File): MB

SNMP Cisco CBQoS

API

Cluster

Down (Acknowledged)

Installation

Libraries

Limits

Cisco Meraki License

Cisco Meraki Network Health

FortiGate VPN Overview

REST Custom v2

• The REST Custom v2 (BETA) sensor now supports Boolean values. If you select content type JSON and value type Integer, the sensor can map a Boolean value (false or true) to 0 or 1. Use Boolean lookups to get a neat display of the channel on the sensor overview tab.
• You can now also use email addresses in the Request URL of the REST Custom v2 (BETA) sensor. In previous versions, the sensor did not work with such URLs.

Context menus

Devices

Notifications

Sensors

Documentation

PRTG application server

• The PRTG application server can now always establish a connection to a PRTG core server via the default IP address 127.0.0.1:23580.
• Incoming channel information do not longer cause out-of-memory errors that led to crashes of the PRTG application server.
• We fixed an issue that caused high memory consumption by the PRTG application server.

Sensor Factory

Channels

Supported platforms

Probe transfer

Cache recalculation

Tree version update

All parts of PRTG

OPC UA

Business Process

DNS v2

Modbus sensors

Lookups

Microsoft 365 Service Status sensors

Scanning interval

Microsoft Azure Virtual Machine

Channel Unit Configuration

AWS v2 sensors

• The metric channel of the AWS Alarms v2 (BETA) sensor now shows a proper unit.
• The AWS EC2 v2 (BETA) sensor now only creates the channels Disk Read, Disk Read Ops, Disk Write, and Disk Write Ops if they receive values.
  Note: Running sensors of this type will show a down status after updating to PRTG 21.4.73 due to this change. Please add affected sensors anew.
• We added a lower error limit to the CPU Credit Balance channel of the AWS EC v2 (BETA) and AWS RDS v2 (BETA) sensors. Channel values below 1 will now trigger a down status because they indicate low performance.
• We generally hardened the approach how AWS v2 sensors retrieve data to avoid gaps in the sensor data.

AWS EBS v2

FortiGate System Statistics

Network Share

Redfish Power Supply

Initial alpha release

Initial alpha release

Initial alpha release

All parts of PRTG

Event Log (Windows API)

Server

Sensors

Microsoft Azure SQL Database

Microsoft Azure SQL Database

API

History

Probe connections

Stability

Startup

User accounts

AWS Alarm v2

AWS RDS v2

HPE 3PAR Drive Enclosure

HPE 3PAR Virtual Volume

All parts of PRTG

Beckhoff IPC System Health

Modbus RTU Custom

MQTT Subscribe Custom

API

Reports

Common SaaS

DNS v2

EXE/Script sensors

Flow and Packet Sniffer sensors

HPE 3PAR sensors

Modbus sensors

NetApp LUN

VMware Virtual Machine (SOAP)

Sensor creation

User accounts

Version number

Cluster

User accounts

AWS ELB v2

AWS RDS v2

Local Folder

• We added the option to define whether the Local Folder (BETA) sensor monitors only the specified folder (default) or all subfolders as well. You can define this behavior with the Recurse Subfolders setting.
• You can filter for specific files that you want to monitor. Enable the Filter by File Name setting, define if you want to include or exclude specific file names and file types, and so keep an eye on your most important files.
• You can now filter files by age. With this option you can monitor, for example, the success of certain automatic processes that create or modify files.
• We added a timeout setting, which is useful for larger filesystems to avoid a potential probe overload, and prevent defining UNC paths, which are not supported by the sensor.

Redfish Virtual Disk

REST Custom v2

Languages

All parts of PRTG

HPE 3PAR Common Provisioning Group

Microsoft Azure SQL Database

Microsoft Azure Storage Account

Microsoft 365 sensors

Modbus TCP Custom

OPC UA Custom

WMI Event Log

Zoom Service Status

MySQL (v1)

SNMP Custom Table

Active Directory

Cluster

Device templates

Single sign-on

Time zones

Home page URL

Internet Explorer

AWS EC2 v2 and AWS ELB v2

Local Folder

Redfish System Health

Languages

All parts of PRTG

Veeam Backup Job Status Advanced

• Adding a new Veeam Backup Job Status Advanced sensor works more reliably now. In certain scenarios, you could not add the sensor and received the error message An error occurred. The queried field is empty.
• We added the new lookup value None so that the sensor can now handle the combination job status idle and job result none. Previously, the sensor showed a down status with the error message An error occurred: Bad optional access in such cases.

Dell EMC Unity Enclosure Health v2

Modbus TCP Custom

• You can now select single bits of input and holding registers to monitor them with the Modbus TCP Custom sensor. This is useful for monitoring Modbus devices that report the on/off status of several inputs as one register, for example.
• You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently.

MQTT Subscribe Custom

SNMP sensors

Active Directory

Microsoft Azure sensors

DNS v2

Microsoft 365 Service Status sensors

SNMP Printer

API

Auto-Discovery

Graphs

Single sign-on

Maps

AWS EC2 v2

AWS ELB v2

HPE 3PAR sensors

REST Custom v2

SNMP Rittal CMC III Hardware Status

All parts of PRTG

DNS sensor

SNMP sensors