New
Itops Board 3.18.0
Improvements and Fixes |
|
Release Notes
for PRTG 24
Software versions in this channel are not
updated anymore.
Please consider upgrading to the latest "stable" version.
Please use the "Auto-Update" feature to update your PRTG installation
with the latest stable version:
In the PRTG web interface, navigate to Setup | Auto Update.
November 12th 2024 - Version 24.4.102.1351
New
Multi-platform probe 3.0.0
Data Buffer |
A new version of the multi-platform probe is now available! With this release the multi-platform probe offers data buffers to store data when a connection drops, in this case, between a remote probe and the PRTG core server, and sends the stored data when the connection is reestablished. Thanks to this feature, data loss due to a dropped connection, a down server, unreliable internet, etc. is minimized.
As the multi-platform probe connects to the PRTG core server via a NATS server, we enabled NATS JetStream, a persistence engine built into the NATS server that stores messages until they can be relayed.
This enhancement aims to provide you with more reliable monitoring and maintain data integrity during connection disruptions. With 1,000 sensors and a scanning interval of 1 minute, the system can buffer data for up to 16 hours.
Important: To utilize this feature, ensure you have the latest versions of the NATS installer, PRTG, and the multi-platform probe. While the multi-platform probe will function with older versions, data buffers will not be available. For more information about this new feature, please see the manual section Data Flow. For detailed release notes about this release, see our Knowledge Base article: What are the release notes for the Multi-Platform Probe?. |
New
Sensors
SNMP Disk Free v2 |
The SNMP Disk Free v2 sensor left its BETA status and is now fully supported. We introduced the SNMP Disk Free v2 as experimental sensor with PRTG version 23.3.86.1520. The SNMP Disk Free v2 sensor monitors the free disk space on a logical disk via the Simple Network Management Protocol (SNMP). |
WMI Microsoft SQL Server 2022 sensor |
To monitor Microsoft SQL Server as of version 2022, we implemented the WMI Microsoft SQL Server 2022 sensor (NEW). The WMI Microsoft SQL Server 2022 sensor monitors the performance of a Microsoft SQL Server via Windows Management Instrumentation (WMI). |
Changed
Server
Geo location maps |
We updated our API for maptiles and geocoding since the API from the location service provider has changed. In previous PRTG versions you would notice that there was no resolution anymore in some cases for your given geo location in the Location (for Geo Maps) and no map was displayed. This could have affected also new set geo locations while the old API was not working anymore. Important: Please note that in certain rare cases you will need to take further action to make your geo location map work again. For example, when you have added a location by address in the Location (for Geo Maps) while the old API was not working, you will need to enter a (space, character) again in the location field and the map is displayed correctly when you update to this PRTG version. However, if you have entered the address as coordinates in the map before, no further action is required. |
Changed
Sensors
Secure Shell (SSH) sensors |
We deprecated the option Run the command as a different user using 'su' in the device settings for Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems for password security reasons. You will receive a corresponding TO DO ticket in PRTG that your action is required when you update to this PRTG version. For the SSH Rights Elevation method, please switch to the option Run the command as a different user using 'sudo' (without password) instead for all affected devices. |
Improved
Security
WebGUI |
We hardened the PRTG web UI against possible Tabnabbing attacks. The CVSS v3.1 score for this vulnerability is 2.6 but specifically for PRTG the severity is calculated as Medium. |
Improved
Server
API Keys |
We added an endpoint to get information about an API key token with Token Type Desktop. The endpoint getdesktoptoken.htm with given authentication credentials will return a configured API key token for the type Desktop. In case there is none configured, the page will return a corresponding error message. In this case, you can also find the following log entry in the CoreWebserverLog: Webserver: Error: no Desktop-type token found. | Single Sign-on |
PRTG now supports the Single Sign-on (SSO) capability through its auto-login function. This allows you to gain access to multiple systems that support Single Sign-on with a single login in the same browser. For example, if you have a PRTG instance configured with Single Sign-on Entra provider and you log in to the portal of your provider by using SSO, no further login (two factor authentication) is required when you want to log in to your PRTG. Upon logout, you will be redirected to the login page. Important: In certain cases you will not see a login page for Single Sign-on although you have configured and enabled it correctly in PRTG to use the new auto-login function. More precisely, this means if you want to log in with a different user account without using Single Sign-on or if the callback URI is wrong or invalid in the portal of the SSO provider (Entra or Okta). You will receive an error message, for example A silent sign-in request was sent but no user is signed in or The redirect URI (URI) specified in the request does not match the redirect URIs configured for the application (applicationID). If that happens, please use /public/local_login.htm for a regular login procedure. Another option would be to disable Single Sign-on in PRTG or to update the callback URIs in the portal of your SSO provider. |
Improved
Sensors
Modbus Custom sensors |
You can now define a scale factor as integer or floating-point number for the Modbus TCP Custom sensor and Modbus RTU Custom sensor in the sensor settings during sensor creation. The setting is available in the Modbus Channel Specific settings and can be defined in the Scale Factor setting of a channel when the Channel Unit is set to custom. The default scale value is set to 1 and can be changed depending on whether you want to scale up or down. You can change this setting later after sensor creation in the Edit Channel settings under Scaling Multiplication. |
OPC UA Custom sensor |
You can now define a scale factor as integer or floating-point number for the OPC UA Custom sensor in the sensor settings during sensor creation. The setting is available in the OPC UA Specific settings and can be defined in the Scale Factor setting of a channel when the Channel Unit is set to custom. The default scale value is set to 1 and can be changed depending on whether you want to scale up or down. You can change this setting later after sensor creation in the Edit Channel settings under Scaling Multiplication. |
SNMP HPE ProLiant Physical Disk |
Your SNMP HPE ProLiant Physical Disk sensor is now able to display an additional status value for the Disk Status channel. Previously, the status for Hot Spare disks was not included in the standard lookup prtg.standardlookups.hp.diskstatus and therefore the sensor reported an error with the message Undefined lookup value - (10) in channel Disk Status. |
Sensor settings |
We improved the wording displayed in the Help text for certain sensor types like Script v2 sensor, HTTP v2 sensor and REST Custom v2 sensor in the sensor Settings. For example, in the Parameters tooltip help text for EXE/Script sensors in the sensor Settings, the examples were previously displayed as %%host or %%sensorid. |
Fixed
Server
API Keys |
We fixed an issue for API keys where it was possible for a user with read-write permission to delete an API key (that has write, acknowledge or read permission) with an API token that only has Acknowledge permission. Now users can only change their own API keys as long as they have the according rights to change it, this means at least write access except for PRTG administrators when additionally the API key has the access level FULL. This fix also applies for the PRTG API v2. |
Graph Settings |
We fixed an issue for Graph Settings in the User Interface section of the PRTG Setup menu that were no longer applied. For example, if you changed the setting of a graph to another value then the default (like for Graph 3 365 days to 400 days), PRTG would not apply the changes after an automatic restart but still display the previous default in the group, device or sensor graphs. |
Logging |
We fixed an issue that was logged in the CoreWebServer.log when you tried to move objects in a device tree in PRTG. The log in the CoreWebServer.log registered the error Webserver: Internal Error C0...Can't upgrade to writelock - lock is not upgradeable. |
Notifications |
We fixed an issue for the Notification template Add Entry to Event Log where PRTG did not add an entry to the PRTG Network Monitor log file under Applications and Services Logs in the Windows event viewer when you have selected the option PRTG Network Monitor for the Log File setting before in the template. However, the issue did not occur when the Log File setting was set to Application, where PRTG successfully added an entry to the Application log file in the event viewer. |
Notification Delivery |
We fixed an issue for Notification Delivery that occurred in certain cases when the Delivery Mechanism was set to Use direct delivery with the built-in email server (default). Additionally you had to use G Suite (googlemail) mailboxes in order to run into this issue. G Suite would reject the incoming messages due to a missing MessageID and would display the error Messages missing a valid messageId header are not accepted in the SMTP logging. As a result, email notifications could not be sent. One possible workaround was to set the Delivery Mechanism to Use one SMTP relay server (recommended in LANs/NATs). |
Maps |
We fixed an issue in the Map designer of PRTG where the Custom HTML property did not work anymore in previous PRTG versions. The changes were not applied when you entered an HTML code in the HTML Before field, for example, to use the Custom HTML element in a map. |
Tags |
We fixed an issue for the usage of tags in PRTG, where quotation marks used in tags were not considered. For example, if you add a tag "hello and world", PRTG would create a single tag instead of two individual ones. This issue occurred also for tags used between the tags with quotation marks where PRTG would integrate them in one single tag only. |
Fixed
Sensors
Oracle Tablespace sensor |
We fixed an issue in the Oracle Tablespace sensor scanning time so that the sensor executes the queries faster without running into timeouts. |
SSL Security Check |
We fixed an issue for the SSL Security Check sensor that reported the status Denied in the channel TLS. 1.0 (Weak) or TLS 1.1 (Weak) although those TLS protocols were still accepted by the webserver. This issue happened in some cases when you updated to the previous PRTG version 24.3.100.1361. |
Fixed
WebGUI
Maps |
|
Multi Edit |
We fixed an issue that occurred in the Device list settings for multiple devices when you tried to edit the Community String in the settings for Inherit Credentials for SNMP Devices. The setting for Community String would be displayed twice in these cases. When you entered and saved a community string in the corresponding field, the change would take no effect afterwards in previous PRTG versions. |
Note
Known Issues
HPE ProLiant Physical Disk sensor |
We face an issue with the HPE ProLiant Physical Disk sensor that you can no longer create and existing sensors may also no longer work in certain cases. When you try to create the sensor, the scan will fail with the message The sensor could not find any disks on the target device. For existing sensors you will notice the error No such instance (SNMP error # 223) and that the disk could not be found in these cases. The issue is located in the HPE Integrated Lights-Out (iLO 5) firmware version as of 3.x due to changes in the OIDs. A possible workaround is to downgrade to an older iLO version (before iLO 3.x). |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.4.102.1351
|
Lab
Sensors
REST Custom v2 |
|
SNMP Custom v2 |
|
SNMP UPS Status sensor |
You can try out the experimental SNMP UPS Status sensor that monitors the status of an uninterruptible power supply (UPS) via SNMP. This sensor comes with the channels Battery Status, Charge Remaining, Current Load and Estimated Time Remaining. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
SSH Meminfo v2 |
You can try out the experimental SSH Meminfo v2 sensor that monitors the memory usage of a Linux/Unix system using Secure Shell (SSH). This sensor comes with the channels Available Memory (bytes) and Percent Available Memory (%). Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
SSH Load Average v2 |
You can try out the experimental SSH Load Average v2 sensor that monitors the load average of a Linux/Unix system using Secure Shell (SSH). This sensor comes with the channels 1 Minute, 5 Minutes, and 15 Minutes that reflect the average system load within a certain scanning interval. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
SSH Remote Ping v2 |
You can try out the experimental SSH Remote Ping v2 sensor that remotely monitors the connectivity between a system running Linux/macOS X and another device, using Internet Control Message Protocol (ICMP) echo requests ("ping") and Secure Shell (SSH). This sensor type comes with the channels Avg. Response, Max Response, Min Response and Packet Loss. The response time is measured from the remote device. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
SNMP Traffic v2 |
We fixed an issue for the SNMP Traffic v2 that failed with the message The interface [interface] was not found in certain cases after sensor creation. In the Result of Sensor log you could also observe the following error message The requested index value [interface] was not found in the SNMP table column Descr. The issue happened in rare cases when the SNMP agent sent strings including the null-termination in its length what led to an error during the sensor scan. We therefore removed any null-termination bytes for table index comparisons. |
Lab
PRTG APIv2
API |
|
Lab
New UI
Context Menu |
We improved the wording used in the New UI context menus for more clarity and visibility. The wording was improved on sensor, device, channel, group and probe actions. Please note that a user without the according rights, for example read-only, will not see the action buttons in the context menu. |
Monitoring |
You will now be able to still navigate through and see the split view with the device tree in case there is a deleted object (group, device, sensor). The split view on the right hand side will display a broken image, for example: oops... the group could not be found. Additionally, there is a redirect link Return to monitoring view. In case the user has no according rights for the relevant object, the page will display an access denied error message. |
PRTG Ticket system |
You are now able to access the PRTG Tickets tab in the new UI if you have the necessary rights. In the Tickets section, you can now assign, edit, resolve, close, change priority of the relevant tickets. |
User Accounts |
We fixed an issue for adding multiple users with the option Add Multiple Users under PRTG System Administration. The issue occurred after a certain time when you not confirmed your changes with OK directly. The page would then report an error in the Users Added pop up window. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German and Spanish language files. |
September 25th 2024 - Version 24.3.100.1361
New
Multi-platform probe 2.1.0+13615
Improvements and Fixes |
A new version of the Multi- platform probe is now available. With this release all sensors supported by the multi-platform probe are device template capable except: Cloud HTTP v2 and Cloud Ping v2. This release includes also a fix the MQTT Subscribe Custom Sensor, where the sensor showed an Unknown status after the sensor was cloned, paused, or un-paused. For more information about the multi-platform probe and how to use it, please see Multi-Platform Probe for PRTG manual. For detailed release notes about this release, see our Knowledge Base article: What are the release notes for the Multi-Platform Probe?. |
Improved
Server
Update to OpenSSL 3.0.14 |
To ensure secure communication furthermore we updated to OpenSSL version 3.0.14 since OpenSSL also retired the 1.1.1 series end of September 2023. The following TLS versions will be supported in the connection security settings for Probe Connection and PRTG Web Server settings: TLS 1.3, TLS 1.2, TLS 1.1, TLS 1.0. Please note when you update to this PRTG version, that you cannot add new installations of mini probes because OpenSSL 1.0.2 is no longer supported. Existing installations of mini probes should not be affected. For more information please see our Knowledge Base article: What security features does PRTG include? |
Changed
Server
Notifications |
We changed the Teams Webhook feature for notifications Send Microsoft Teams Message in PRTG, since Microsoft will retire Office 365 connectors within Microsoft Teams. You can still use the former webhooks until their deprecation in 2025. Microsoft provides the new Workflows app that you can use for a workflow to post messages from a webhook request. With this PRTG version, Send Microsoft Teams Message notifications will now support Workflows webhooks that you can configure in your Microsoft Teams. For more information on how to set up your Teams notification in PRTG please see our Knowledge Base article: How do I create a webhook for the PRTG notifications to Slack and Microsoft Teams? |
Improved
Sensors
Cisco Meraki Network Health sensor |
We updated the API call that is used within the Cisco Meraki Network Health sensor since the formerly used API call /organizations/{organizationId}/devices/statuses was deprecated. |
EXE/Script sensors |
We improved the tooltip text information for the setting Parameters in the sensor Settings for EXE/Script and EXE/Script Advanced sensor types. If you hover over the tooltip icon for Parameters, you can see the following additional information: This setting can pose a security risk because sensitive information in the parameters appear in the sensor log. Use placeholders like %windowspassword or %scriptplaceholder1 to encrypt sensitive information and enable PowerShell Security Enhancement under Setup Monitoring Experimental Features to increase your security. This information is valid for the Result of Sensor [Sensor ID].Data.txt that is created when you have enabled the Result Handling option Store result in the sensor Settings. |
FortiGate VPN Overview sensor |
With this PRTG version we introduce the new Virtual Domain Settings (VDOM) where you can select the virtual domain that this sensor monitors during sensor creation. Existing sensors are unaffected as the setting will show the default value root. |
HTTP v2 |
You are now able to include the HTTP v2 sensor in a device template when you have added the sensor to an appropriately configured device before. The device template is created when the HTTP endpoint returns status 200 (OK), using the same settings as the templated sensor. You can edit the device template afterwards if you need different status codes. |
Probe stability |
We improved the stability on PRTG probe level to avoid the risk of probe issues, such as access violations in the probe.log or a no longer working probe service. |
Fixed
Paessler PRTG Enterprise Monitor
Offline activation |
We fixed an issue that occurred in certain cases for the manual offline activation of PRTG Enterprise and PRTG Subscription license keys. The issue happened if you tried to activate an Enterprise or Subscription license key for your offline PRTG instance new or if you tried to update the license information with an Enterprise or Subscription license key later in the PRTG settings for License Information with Manual (offline activation) selected. However, creating the activation.dat file (license data) was succsessful in these cases. You could also observe an error message in the CoreActivationLog: CoreActivationLog> TCoreLicenseInternalsLicenseV2.VerifyActivationData: returnedFalse and TLicenseLegacy.Activate: not performed - License key is empty. |
Fixed
Server
API keys |
We fixed an issue where changes via PRTG API v2 to any API key were not saved in the History tab of a user account. For example, when you created or modified an API key using /api/v2/users/api-keys/ endpoint, the changes would not be logged in your user account History tab. |
PRTG probes |
We fixed an issue that led to probes being disconnected from time to time when they were connected via communication protocol with very high latency. |
Fixed
Sensors
DNS v2 sensor |
We fixed an issue where the DNS v2 sensor with Query Type Host address IPv6 (AAAA) or Host address IPv4 (A) (default) only considered one IP address returned by a hostname instead of any matching IP address. For example, if you wanted to check entries of a same DNS for IPv4 and IPv6 addresses in separate devices and an entry for IPv6 was missing or invalid, both variants (IPv4 and IPv6) would fail what instead should have been only the sensor running on the IPv6 device. |
MQTT Round Trip sensor |
We fixed an issue for the MQTT Round Trip sensor where the default value was not displayed correctly in the MQTT Specific settings for Topic. Previously, the sensor Topic displayed was PRTG/roundtrip/%%sensorid. |
WMI Event Log sensor |
We fixed an issue for the WMI Event Log sensor where the entry for Log file in the WMI Event Log Monitor settings was missing when you ran an auto-discovery with device template before that included this sensor type. |
Fixed
WebGUI
Maps |
We fixed an issue where the SNMP Uptime v2 sensor was not displayed in the map properties Top 10 lists for Longest System Uptime and Shortest System Uptime in previous PRTG versions. You could observe that other SNMP Uptime and WMI Uptime sensors on your system were shown in the lists but the SNMP Uptime v2 was missing. |
Improved
Multi-Platform Probe
PRTG Setup |
You will now see an additional section under Optional Downloads in the PRTG setup menu for the Multi-Platform Probe. This section can be found in the menu point Remote Probes and contains a link to the Multi-Platform Probe manual with installation guide, a download link for the required NATS server Download NATS Server for PRTG installer and additionally a step-by-step instruction for the Paessler Linux package repository (Debian and Ubuntu and RHEL). The RHEL download link points to the repository setup instructions. You can install the RPM package on a Linux system running Red Hat Enterprise Linux (RHEL) version 9. |
PRTG Status |
We removed the notification on the PRTG Status page under Probes for connected Multi-Platform Probes that you need to install .NET for the Multi-Platform Probe. |
Fixed
PRTG app for Desktop
System information |
We fixed an issue where the System Information page was not displayed for some devices in the PRTG App for Desktop. Also for API calls https:// |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.3.100.1361
|
Lab
Sensors
Cisco WLC Access Point Overview sensor |
You are now able to include the Cisco WLC Access Point Overview (BETA) sensor in a device template when you have added the sensor to an appropriately configured device before. When you run an auto-discovery with the mentioned device template on a new device, the sensor will be created afterwards. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
REST Custom v2 sensor |
You are now able to include the REST Custom v2 (BETA) sensor in a device template when you have added the sensor to an appropriately configured device before. When you run an auto-discovery with the mentioned device template on a new device, the sensor will be created afterwards. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
SNMP Custom v2 sensor |
You are now able to include the SNMP Custom v2 (BETA) sensor in a device template when you have added the sensor to an appropriately configured device before. When you run an auto-discovery with the mentioned device template on a new device, the sensor will be created afterwards. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
SSH INodes Free v2 sensor |
You can try out the experimental SSH INodes Free v2 (BETA) sensor that monitors the free index nodes on disks of Linux/Unix and macOS systems via Secure Shell (SSH) and which was rewritten to work also on the Multi-Platform Probe. This sensor comes with the channels Downtime and Free INodes [Mount], like the former SSH INodes Free sensor. Please note that this sensor does not support the Compatibility mode for SSH Engine anymore. This feature was already deprecated in previous PRTG versions. Additionaly you are able to include the SSH INodes Free v2 sensor in a device template when you have added the sensor to an appropriately configured device before. When you run an auto-discovery with the mentioned device template on a new device, the sensor will be created afterwards. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setup first in order to use this sensor. |
Lab
PRTG API v2
API |
|
Deprecation of endpoints |
With this PRTG version we announce the deprecation of several endpoints in the PRTG API v2. Deprecation for endpoints means, that they will be removed or replaced in the future. For example, the endpoint GET /channels will be replaced by /channels/{id} and /experiemental/channels, whereas the experimental endpoint can still be changed but is aimed to become a stable endpoint as well. In course of this change, we also removed the following experimental endpoints: GET /experimental/devices/id/settings, GET /experimental/sensors/id/settings. In the section /overview for the OpenAPI Documentation, we added detailed information about filtering, include parameters and endpoint maturity. For all relevant documentation, please have a look at Important changes to API v2 in PRTG 24.3.100 |
Swagger UI |
We fixed an issue where the generic autogenerated Examples for any API call did not work anymore and the returned response for those examples was not correct. For example, when you opened the call for GET Channels with the Example Channels you would not get all available fields or correct naming in the Example Value. To open the Swagger UI you need to enter http(s):// |
Lab
New UI
Add group |
You can now create a group in the new UI via context menu and action button on probe and group level with the corresponding user rights. After you have created a group, you will be redirected to the parent object where the group was created. Please note that you cannot add a group on root level. |
Color Mode |
We fixed an issue that occurred when you selected the Color Mode Dark in the PRTG classic interface and opened the new UI afterwards. Previously, not all settings and pages, for example reports and sensor settings, were displayed in Dark mode but still shown as Light (default). |
Edit channel settings |
We adjusted the wording for Edit Settings in the context menu when you opened it for a sensor. The menu option Edit Settings was displayed twice, however, the wording with the wheel icon should have been Edit Channel Settings instead of Edit Settings. |
Login behavior |
We added an automatic login timeout that happens after inactivity for 15 minutes when you are logged in on PRTG and want to navigate to the System Setup pages. You will then be logged out and receive a message Please re-enter your credentials to gain access to admin settings. After you have entered your login credentials again, you will be redirected to the page you wanted to navigate to before the automatic login timeout. |
Maps |
We fixed an issue where linked objects in maps opened in PRTG classic interface. The issue occurred when you used the Select object option in the maps Properties, for example, to create a link. The link will then direct to the PRTG classic interface instead of the new UI. |
Monitoring |
We fixed an issue that occurred in the Firefox browser console when you navigated to or within the Monitoring option. The JavaScript error message displayed was uncaught (in promise). |
Mobile view |
We fixed an issue for lookup bars in the new UI mobile view that were not displayed in the correct color mode like they are shown in the desktop view. |
Navigation |
We added tabs for Logs and Maps to the main menu below the home icon where you are now able to create, edit and view maps within the new UI and where you can also view your logs for objects. When you open the Logs tab, you can see an additional filter option Choose Filter where you can select, for example, Filter: paused/resumed for objects. Please note that the feature for map rotation is currently disabled in the new UI. |
PRTG Setup |
We improved the setup page in the new UI for users without administrative rights. You will now have the sections Account Settings, Optional Downloads and Support on the Settings (setup) page in PRTG. Under Account Settings you now have the option to manage your API Keys and My Account settings. Please note that a user with read only rights is not allowed to access the setup main page and will instead receive a 403 - access denied error. |
Settings |
We fixed an issue where the context menu was available for objects included in iframe pages in the new UI. For example, if you right-clicked on a parent object in settings like the Inherit from location, a context menu opened what should not have been available in this case. |
System Setup |
You are now able to view and edit settings in the PRTG Setup pages within the new UI when you are logged in with an account with administrative rights. This includes all setup pages under System Administration, however, the License Information page will direct you to the classic UI currently when you want to update information on your license in the new UI. |
View settings |
We fixed an issue that occurred when you navigated from the Sunburst view to the Tree view and vice versa with your keyboard arrows and clicked enter to confirm. Previously, you would see an unknown error displayed with the message An unknown error occurred. If necessary, try to reload the page. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German and Spanish language files. |
July 31st 2024 – Version 24.3.98.1210
New
ITOPS BOARD 3.17.0
Improvements and Fixes |
|
New
Multi-platform probe 2.0.0+12481
New Features |
For more information about the multi-platform probe and how to use it, please see Multi-Platform Probe for PRTG manual. For detailed release notes about this release, see our Knowledge Base article: What are the release notes for the Multi-Platform Probe?. |
Improved
Security
Webserver |
With this PRTG version we provide various fixes to improve security and stability. |
New
Sensors
Script v2 sensor |
The Script v2 sensor left its BETA status with this PRTG version and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 23.1.82.2074. The sensor executes a Python script that returns data in JSON format and shows the exit code. This way you can create your own custom script sensors that may not be available in PRTG by default. For available example scripts and how to use them, please see the Knowledge Base article: I want to use the Script v2 sensor example scripts. What do I need to know? |
Improved
Server
API keys |
You are now able to delete created API keys under Account Settings in your PRTG Setup via multi-edit selection. Previously, API keys could only be deleted individually. For every API key that you delete, PRTG will add an entry in the History tab of your User Account settings. |
Auto-discovery |
You can now add multiple subnets to the auto discovery setting. If you want to include multiple addresses and subnets, enter them in the field IPv4 and Subnet (IPv4) as a list separated by a comma. Please note that this feature applies only for IPv4 subnets and does not support IPv6. |
Improved
Sensors
NetApp v2 sensors |
We updated the available lookup values for NetApp v2 sensors that were not supported in previous PRTG versions before. For example, the NetApp System Health v2 sensor now supports the values Tri Path, Tri Path HA and Virtual state for the status Up in the Storage Configuration Path channel. Other NetApp v2 sensors that have now addtional supported lookup values are NetApp SnapMirror v2 for the channels Mirror State and Policy Type and NetApp NIC v2 sensor for the channel State. |
Microsoft Azure |
With this PRTG version we introduce a new setting Microsoft Azure Management Endpoint in the Credentials for Microsoft Azure. This setting allows you to change the API endpoint for your region that can differ from the default URL management.azure.com to use Microsoft Azure sensors, such as Microsoft Azure SQL Database sensor or Microsoft Azure Storage Account sensor in your environment. Please note that this setting is locked by default and can be edited upon request. |
Sensor message |
We improved the error message for certain sensor types that appears when you need to check credentials or logfiles for a sensor. Affected sensors are AWS sensors, EXE/Script sensors, Zoom sensor, Veeam sensors, OPC UA sensors and Cloud sensors. The previous error message did not indicate that the setting for Store Result is not enabled by default and that you first need to enable it and run a rescan of the sensor before you can check the logfiles. An example error message now displays The sensor could not authenticate with AWS. Check your credentials for AWS or select 'Store result' under Debug Options | Result Handling in the sensor settings, rescan, and check the \\Logs\\sensors subfolder of the PRTG data directory on the probe system. |
Changed
Sensors
EXE/Script sensors |
We removed the following libraries from the Sensor System since they are no longer needed: MongoDB.Bson.dll, MongoDB.Driver.dll, Mono.Security.dll. The libraries were a leftover from the MongoDB System Health sensor that we announced as deprecated with PRTG version 16.2.23 and finally removed from PRTG with PRTG version 16.3.25. |
Fixed
Server
API calls |
We fixed an issue where the PRTG Core server generated a high CPU usage when you used an API call for a historic data report with a negative average interval avg=-[interval]. PRTG considered the API call as invalid in these cases and could not respond what caused a timeout and thus lead to a higher usage in CPU. |
API keys |
We fixed an issue for API keys that did not display the correct Access Level when the user to whom the API key was assigned was deleted or moved from the corresponding user group. The API Key List has now an additional column Effective Access Level that displays the up to date and in use access level for the relevant user. |
PRTG Core server |
We fixed an issue that occurred when you updated to the previous PRTG version 24.2.94 where in certain cases the PRTG core server service could not start and could not be restarted as well. The PRTG web interface would report timeouts or load endlessly after login. In some other rare cases, the update to PRTG version 24.2.94 was successful, however, the web interface performance was very slow in loading pages and you also could observe ReadLock entries in the core.log. Rolling back to the former PRTG version 24.1.92.1554 would solve the issue. |
Remote probes |
We fixed an issue where a Core logfile was created on a remote probe after you started the Administration Tool on that relevant remote probe. The logfile was created under C:\ProgramData\Paessler\PRTG Network Monitor\Logs\core. |
Remote Probe Installer |
We fixed an issue where the installer window for a remote probe could not be closed with the x button in certain cases. The issue happened when you changed the Setup in your PRTG installation under Probe Connection Settings to allow probe connections to the core server when you already executed the remote probe installer. The installation process could be finished successfully, however, you were not able to close the dialogue window of the remote probe installer. |
Fixed
Sensors
Auto-discovery |
Running an auto-discovery with a device template that includes the following sensor types will now add these sensor types to your device as expected: Windows Print Queue sensor, VMware Datastore (SOAP) sensor and SMTP&IMAP Round Trip sensor. |
AWS EC2 v2 sensor |
We fixed an issue for the AWS EC2 v2 sensor that reported the error message Channel with ID [ID ]is not defined in very rare cases because the sensor sometimes received zero 0 values for the DiskReadOps (Average) metrics. Since the sensor expects values for every scan, it reported the mentioned error when it received 0 values. The issue occurred when you used the sensor on a Linux instance but could also occur on a AWS EC2 Windows system. |
HPE 3PAR Drive Enclosure sensor |
We fixed an issue for the HPE 3PAR Drive Enclosure sensor that led to several issues when you used multiple sensors of that type on the same device on the same probe. The sensors would report an error with the message that the session could not be started (Cryptographic functions must be set on at least one blocksize). In some cases the sensors would work again if you enabled the Store Result function, but then ran into an unknown state if you disabled it again.
Important:This fix introduces a maximum number of parallel connections to the same device with same credentials. If that limit is reached then you will receive the error too many concurrent connections. This limit is currently hard-coded to 20 concurrent connections with the same credentials/device combination within the HPE 3PAR Drive Enclosure sensor. This issue also occurred on the Multi-Platform Probe. |
Microsoft Azure |
We fixed an issue for Microsoft Azure sensors, like Microsoft Azure Storage Account sensor, Microsoft Azure SQL Database sensor or Microsoft Azure Subscription Cost sensor, where the Result of Sensor log reported the error The sensor could not get a response from the server. 400 (Bad Request) in certain cases. The issue occurred when you used a scanning interval of 12h or 24h because the sensor used an invalid format that could not be handled by the Azure REST API. |
Microsoft Azure/ Microsoft 365 sensors |
Your Microsoft Azure and Microsoft 365 sensors will now use correctly proxy settings when you have configured those on the relevant device. Previously, the proxy settings were displayed correctly in the logs but disregarded for Azure AD login. |
OPC UA Custom sensor |
We fixed an issue for the OPC UA Custom sensor that reported an error with the message No Value is set in certain cases. The issue could happen in cases when the DisplayName, BrowseName or Description attribute was empty. |
POP3 sensor |
You can now create a device template from a device that includes a POP3 sensor and the sensor will be added to the device afterwards. In previous PRTG versions, when you opened the dialogue window Create Device Template, the sensor was not added to the relevant device after you received the success message Create Template Results, although the sensor was listed in the results. |
Probe memory consumption |
We reduced the possibility of a higher memory consumption and a memory leak on the probe that occurred in certain cases when you ran SNMP and HTTP/HTTP Advanced sensors on your local or remote probe. Eventually, the probe would report the status disconnected. Restarting services only helped for a certain while in these cases. |
ProbeWMI.log |
We reduced the risk for PRTG logs to get a large file size when WMI exceptions occur, especially for the ProbeWMI.log. This could lead to a full disk in certain cases since the file size increased very quickly and therefor result in a not working probe system in the worst case. |
Syslog Receiver & SNMP Trap Receiver sensor |
We adapted the information for Result Handling in the Debug Options help tooltip so that it displays the correct file name and subfolder where the sensor result is stored. The file name now is UDP Debug Port [Port][Date].log in the Logs/debug subfolder for both sensor types. |
WMI Event Log sensor |
We fixed an issue for the WMI Event Log sensor where the sensor did no longer display a sensor event message for triggered events. You could observe the missing information in the Message column of the Log tab of the sensor as well as in the sensor status bar below the sensor name. The sensor also only reported the status OK in certain cases. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.3.98.1210
|
Lab
Sensors
Cisco WLC Access Point Overview sensor |
You can try out the experimental Cisco WLC Access Point Overview sensor (BETA) that monitors your access points that are connected to your Cisco Wireless LAN Controller (WLC). The sensor will show the following columns during sensor creation: MAC address, Name, Location, State for the access points as well as IP address, Model, Serial Number and Number of Slots. The Number of Slots represents the number of radios and antennas for an access point. The sensor comes with the channels Operational Status, Admin Status, Max Rx Utilization, Max Tx Utilization, Max Channel Utilization, Client Count and Client Count with Poor SNR (Signal to Noise ratio). |
Fixed
PRTG Multiboard
Template Transfer |
We fixed an issue where the PRTG MultiBoard ran into a timeout in the previous PRTG version 24.2.96.1315 when you used the Template Transfer (BETA) feature in order to move a custom device template from one PRTG server to another. Please note that this feature is only available when you run PRTG with a Paessler PRTG Enterprise license. |
Lab
PRTG API v2
API |
|
Lab
New UI
Edit Settings |
With this PRTG version we introduce the option to edit settings on probe, group and sensor channel level. You can now edit the settings of a group via context menu in the device tree, tables and cards. After you have saved your changes a growl message appears Settings have been saved. It may take a while for the change to apply. Additionally you can edit the settings of your local or remote probe via context menu. When you click on Edit Probe you will be directed to /monitoring/probe/{probeID}/settings. On a channel card of a sensor you will now see an additional Actions button: Edit Settings. This button will open a new dialogue window where you can make changes to the selected channel. If you do not change anything or if you enter invalid values, the Save Settings button will stay inactive. |
Login |
We improved the text message that is displayed when you are logged out due to inactivity. Previously, the message displayed was Your have been logged out due to inactivity. |
Web Interface |
|
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German, Spanish, French, Portuguese, Russian, Japanese, Chinese and Dutch language files. |
Sensor languages |
We updated the German and Spanish language files for certain selected sensor types |
User manual |
|
June 2024 - Version 24.2.96.1346/24.2.96.1375
Improved
Various
Maintenance |
PRTG version 24.2.96.1375 is a maintenance release with several code improvements necessary for upcoming PRTG versions. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.2.96.1375
|
May 28th 2024 - Version 24.2.96.1315
Improved
Security
Webserver |
With this PRTG version we provide various fixes to improve security and stability. |
Improved
Server
Notifications |
We improved the delivery time for HTTP notifications that took longer in certain cases in the previous PRTG versions when you used a HTTP target URL in the Execute HTTP Action section of the notification template. This issue occurred because the PRTG fallback handling for SSL still tried to establish a TLS secured connection what did not lead to an error but to a longer waiting time for PRTG. |
Improved
Sensors
Ping v2 |
You are now able to create the Ping v2 sensor via device template if you select the option Create Device Template on a device where you can select the Ping v2 sensor in the Create Device Template dialogue window. The Ping v2 sensor left its BETA status with PRTG version 24.1.92.1554 and is now fully supported. |
Improved
Multi-Platform Probe
Probe Adapter |
You will now receive a proper error message in the probe adapter log when your NATS server for connection does not offer a secured TLS connection but PRTG is configured to connect with TLS in the Multi-Platform Probe Connection Settings. |
Fixed
Server
Contact support |
We fixed an issue where the button Contact Support was missing in the help bar and also in the Support section on the PRTG Setup page when you ran PRTG with a trial license. This issue also affected Paessler PRTG Hosted Monitor. |
Cluster |
We fixed an issue where the API call for api/health.json reported wrongly a disconnected Cluster probe although the probe was connected at this time. You could also see this behavior on the System Status page in PRTG under Probes where the Cluster Probe was reported as not connected yet. |
Libraries |
You can now filter for a specific sensor type when you select Add Library Node for your library and when you choose the option Show a collection of filtered sensors and Show only specific sensor types for that node. In previous PRTG versions, when you filtered for the sensor type SSL Certificate sensor, the SSL Security Check sensor would be added to the node as well, for example. |
Maps |
We fixed an issue for public maps access that allowed users to see objects in the device tree despite of their assigned security context when you had two or more public maps open in a tab for map rotation view. |
PRTG Administration Tool |
You will no longer receive an error when you click on the button Stop Service or Start Service (ignore changed settings) for the Core and Probe service in the PRTG Administration Tool when you run it as a 64bit version on your system. This issue occurred in the previous PRTG stable version 24.2.94.1400 but did not happen when you run the PRTG Administration Tool in a 32bit mode. The reported error message in this case was One or more required program components of PRTG (PRTG Server.exe, PRTG Probe.exe) could not be found! Please re-run the installation program. |
Search |
You will now receive proper results from our Help documentation when you click on the More button on the Search Results page. This did not work in the previous PRTG versions and returned the message Your search request did not return any results (Help Documents) when you, for example, searched for the term Core Health. You could also see that your seach term was not resolved properly and displayed as core%20health. |
Single Sign-on |
You are now able to send a support bundle with all relevant files via Contact Support button on the Setup page when you are logged in to PRTG with a Single Sign-on user account. In the previous PRTG versions, sending a support bundle as a logged in Single Sign-on user would trigger the overload protection in PRTG and the bundle would not contain any htm files. |
XML tables |
We fixed an issue where the returned table for a queried XML was broken when you had an object, e.g. sensor, with a tag that contained an ampersand & in it. |
Fixed
Sensors
Active Directory Replication Errors |
Your Active Directory Replication Errors sensors will now work properly again when you update to this PRTG version. In the previous PRTG versions, the sensor reported the error Replication Neighbor cannot be found in some cases when you updated to PRTG version 23.1.82.2074 and higher. The issue occurred because we improved the method of password transmission for certain sensor types, which could not be handled by the Active Directory Replication Errors sensors correctly. |
HTTP v2 |
We fixed an issue for the HTTP v2 sensor that appeared during sensor creation process on the Add Sensor dialog. In the section for HTTP Specific the default URL value would display https://%%host/ instead of https://%host/. This issue also occurred when you added the sensor to your Multi-Platform Probe. |
NetFlow sensors |
We fixed an issue where in some cases the remote probe reported the status disconnected from time to time when you moved Flow sensors to that specific remote probe or when you had Flow sensors running on that specific remote probe. The issue occurred for sensors, like NetFlow and sFlow sensors, for example. In the Probe.log you could also observe access violations for the FlowProcessor or the FlowSender. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.2.96.1315
|
Lab
Sensors
SNMP Traffic v2 |
We fixed an issue for the SNMP Traffic v2 sensor that could not be created in some cases and reported the error message The target system did not return a result for the requested OID. |
Lab
New UI
Device settings |
We implemented the sections for Windows Compatibility Options, SNMP Compatibility Options and Proxy Settings in the device settings in the new UI. |
Notifications |
You can now add and edit under Notification settings your notification Schedules, notification Contacts and notification Templates. Please note that this feature is not available on mobile view. |
Notification trigger |
You can now add and edit notification triggers for objects, like probes, groups, devices, and sensors. The notification triggers are available via context menu or Actions button for the relevant object. |
Sensor settings |
You can now edit the settings of a sensor via context menu in the new UI when you right click on the sensor you want to edit. Additionally you can edit the settings of a sensor in the Settings tab or via button Sensor Actions where you can perform actions like Pause Object or Scan Now. After you have saved your changes a growl message appears Settings have been saved. It may take a while for the change to apply. |
Lab
PRTG API v2
API |
|
PRTG application server |
We fixed an issue where the PRTG application server created a panic log file when you uninstalled PRTG. The error message then reported was Error: could not uninstall system service PRTGAppServer: service PRTGAppServer is not installed. This issue occurred when you uninstalled PRTG without having the PRTG application server installed. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German, Spanish, French, Dutch, Portuguese, Japanese, Chinese and Russian language files. |
Sensor languages |
We updated the German and Spanish language files for certain selected sensor types. |
May 2nd 2024 - Version 24.2.94.1424
Fixed
Server
PRTG Probe Service |
We fixed an issue with PRTG version 24.2.94.1400 where the Probe update to this PRTG version failed and therefore the Probe service(s) did not start in some cases. PRTG would report an error message like PRTG probe service could not be started: The service did not respond to the start or control request in a timely fashion or Windows could not start the PRTG Probe Service service on Local Computer Error 1053: The Service did not respond to the start or could request in a timely fashion when you were affected by this issue. In some rare cases also the Core service was affected when you updated to PRTG stable version 24.2.94.1400. The issue occurred because Windows tried to load the certificate cache what took too long for the Probes during startup and caused a timeout. This issue also affected new installations of PRTG. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.2.94.1424
|
April 10th 2024 - Version 24.2.94.1400
Blog article
By Michael Becker • May 6, 2024
A new PRTG release is available in the stable channel!
Paessler PRTG 24.2.94 has been released in the stable channel! This update brings enhancements for Single Sign-on, new settings for multi-platform probe connections, important security...
Read the complete blog post here
Read the complete blog post here
New
ITOPS BOARD 3.15.1
Improvements and Fixes |
ITOps Board version 3.15.1 comes with Notification improvements. Specifically, if you have configured notifications when an alert is raised for a board or business service, you now receive a notification when the alert is resolved. Additionally, the notifications delivered by email are updated to include more detailed information about the change to the related board or business service. This release consolidates the location of user access settings, to improve the workflow of the interface. In this release, the settings are consolidated on a new Authorization tab: Roles, Scope Components by Boards and Services, Saved Search Visibility. This version covers also fixed issues. For more information please refer to the release notes provided with the new version. |
New
Multi-Platform Probe
Multi-Platform Probe Release |
We are happy to announce that the multi-platform probe has entered its stable status after extensive feedback and testing and it's now recommended for productive use. While the classic remote probe is used on Windows systems, the multi-platform probe allows you to deploy probes on various non-Windows systems. These include Debian, Ubuntu, Redhat, and ARM-based systems. Key Features:
For more information about the multi-platform probe and how to use it, please see Multi-Platform Probe for PRTG manual. For detailed release notes about this release, see our Knowledge Base article: What are the release notes for the Multi-Platform Probe?. |
Probe Adapter |
|
Multi-Platform Probe Connection settings |
We added the NATS Connection Security toggle in the Multi-Platform Probe Connection Settings to explicitly set the security schema used.
The configuration for connecting the PRTG core server to a NATS server has changed. The schema is now an explicit toggle instead of encoded into the NATS URL. The NATS URL setting was changed to NATS Server Host, which is made up of the hostname and port of the NATS Server. After this update, the NATS Server Host setting will be reset to the default localhost:23561 value and users will need to reconfigure their NATS server. Important for PRTG Hosted Monitor: This setting is not visible for PRTG Hosted Monitor instances. Customers will be informed separately, as soon as the multi-platform probe can be used with PRTG Hosted Monitor. |
Improved
Security
PRTG configuration file |
Credentials like passwords in the PRTG configuration file are now masked when you use the option Include configuration file (contains passwords) for Send Logs to Paessler in the PRTG Administration Tool in order to send a support bundle. When you have a larger configuration file, e.g. 355 MB and run the PRTG Administration Tool as a 32 bit version, you will receive a message that PRTG was not able to hide encrypted passwords in the configuration file. The same behavior applies when you want to send a support bundle with a broken configuration file. You will then be asked if you still want to include the configuration file containing passwords or not. Please note that currently is not possible to start the Administration Tool for a Remote Probe running on a 64-bit operating system. As a workaround go to the Program Files (x86) folder, open the PRTG Network Monitor folder, and run the 32-bit version of the Administration tool. We will deliver a fix for this issue in the upcoming PRTG versions. |
Sensors |
The behavior of the Environment setting was changed for the EXE/Script and EXE/Script Advanced sensors to prevent remote code execution for Batch (.bat) scripts. Thanks to IT Matters Most GmbH who made us aware of that vulnerability and which can be tracked under CVE-2024-28055, with severity 7.2 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Please note that this change might cause your running custom scripts to fail as it is no longer possible to use the environment variables placeholders in the Parameters setting for Batch (.bat) scripts anymore. |
Webserver |
|
Improved
Server
Logging |
You will now see a log entry in the History tab of a device when you have enabled or disabled the inheritance of an object. For example, if you enable the Inherit From feature toggle for Credentials for Windows Systems, it will be logged as Credentials for Windows Systems: Inherited in the History tab of the device. |
Single Sign-on |
We improved the Single Sign-on handling for PRTG user integration in Microsoft Azure AD to support the Microsoft Graph API for paging when a user is assigned to more than 100 groups. Previously, the issue occurred in certain cases that a user with Microsoft Azure AD integration could not log in to PRTG via Single Sign-on when he was assigned to more than 100 groups. Due to limitations in the Access Token concerning the group memberships we need to switch to Microsoft Graph API for paging what was not yet supported by PRTG. The user would then receive the message that the login has failed. In the Core.log you could also find this error message for the user login: is no member of SSO groups allowed by PRTG. |
Fixed
WebGUI
Find duplicates |
We fixed an issue for the Find Duplicates feature on /api/findduplicates.htm. Previously, if you selected the option Find Duplicates from the device Context menu the result you would have received was empty. |
Note
Sensors
Discontinued sensors with PRTG 24.2.94 |
With this version we discontinue the below already deprecated sensors:
For further information about sensor deprecation and discontinuation in general as well as successor sensors and sensor alternatives please see our Knowledge Base articles: What do deprecation and discontinuation in the context of sensors mean? and What sensors are deprecated and what are their successors or alternatives? |
Changed
Sensors
VMware Datastore (SOAP) sensor |
We changed Bytes (File) to Bytes (Disk) in the Channel Unit Configuration of the VMware Datastore (SOAP) sensor to better match the size of datastores. Please note that this change will come into effect only when you add this sensor type as new and does not affect any existing sensors. |
Fixed
Sensors
HTTP Transaction sensor |
We fixed an issue for the HTTP transaction sensor that could not access a target URL anymore in certain cases and reported the error message String not found in the previous PRTG version, or when you changed to Compatibility engine in the sensor settings the error message was Object reference not set to an instance of an object. |
Memory |
We fixed an issue that could cause a higher memory consumption especially on the Multi-Platform Probe when you ran MQTT sensors and OPC UA sensors on your system. We therefore also updated our MQTT library to version 1.3.13 what patches several issues. |
Microsoft Azure SQL Database sensor |
Your Microsoft Azure SQL Database sensor will now report an according sensor message when the monitored single database or elastic pool is in a different state then Online or Ready. Previously, the sensor reported an error message The queried field "average,count,maximum,minimum,total" is empty. when, for example, the queried database was in status Paused. |
Oracle SQL v2 |
We fixed an issue for the Oracle SQL v2 sensor that reported an error The type initializer for OracleInternal.Common.ProviderConfig threw an exception when Oracle Data Access Components (ODAC) was installed on the system where also the sensor was added, e.g. on a remote probe. The sensor then went into an error state in this case because one of the Oracle assembly references did not match. |
QoS (Quality of Service) One Way sensor |
The QoS (Quality of Service) One Way sensor now no longer displays any IP address in the Quality of Service Measurement section for Target Probe when you are about to create this sensor type. Previously, the sensor displayed 127.0.0.1 for the local probe what did not reflect the actual probe ID being used. |
Sensor logs |
The Result of Sensor.txt file will now be updated again when you have activated the Store result option for Debug Options in the sensor Settings. Updating the Result of Sensor.txt file did not work anymore in the previous PRTG versions for certain sensor types. This issue affected sensor types like Traceroute Hop Count sensor, Windows Print Queue sensor and Active Directory Replication Errors sensor, for example. |
Sensor message |
We fixed an issue where in certain cases the message reported by the sensor suddenly displayed only OK after some time. In these cases the message of the sensor was reverted from the original to OK when the message sent from Probe to Core contained an empty string for some reason. The issue occurred for sensor types like WMI Custom String sensor, SNMP Custom String sensor and REST Custom v2 sensor. |
Sensor settings |
We fixed an issue that occurred for certain sensor types, like the SNMP Custom v2 sensor, where an additional text overlapping the help box was displayed in the section for Schedules, Dependencies and Maintenance Window. Additionally the default dates for Maintenance Begins and Maintenance Ends were not displayed correctly. |
SNMP HPE ProLiant Physical Disk Sensor |
We fixed an issue for the SNMP HPE ProLiant Physical Disk Sensor that reported an error Disk: Required field, not defined when you added multiple disks where at least one disk was defective, e.g. did not report serial number and model values. As a result, the sensor could not be created and additionally the PRTG configuration file could also no longer be saved. You will now be able to save your PRTG configuration file again even if your SNMP HPE ProLiant Physical Disk sensor includes a defective disk. |
SNMP Memory sensor |
We fixed an issue for the SNMP Memory sensor that reported the error message (value)' is not a valid integer value in certain cases. The issue occurred because certain devices falsely returned counter values instead of integer values for the storage size in the OID 'hrStorageSize' (1.3.6.1.2.1.25.2.3.1.5) what the sensor then could not process correctly. |
Windows Print Queue sensor |
We fixed an issue for the Windows Print Queue sensor that did not report the correct sensor message when monitored printers were offline or paused. The sensor wrongly reported the status message up in these cases. |
Fixed
Server
API |
We fixed an issue where in certain cases API calls to PRTG failed with the error Unauthorized although the API token was valid. For example, when you use the API endpoint /api/table.json to reach PRTG with a valid created API key, it could happen that the call resulted in an Unauthorized message. |
Maps |
|
Multi-edit |
You will now be able to save the settings for all your selected sensors when you use the multi-edit function. This did not work properly before in the previous PRTG versions in certain cases. Saving the value Maximum (Mbit/s) for the channel Traffic Total when you have selected several SNMP Traffic sensors would only work for the first sensor in the list, not for all sensors that you selected via multi-edit. |
Notifications |
We fixed an issue for sms notifications that were cut off in the text when you used certain special characters, like for example ampersand &. |
Notification trigger |
We fixed an issue for notification triggers, that is Speed, Volume and Threshold trigger where added values in the PRTG web UI would not be saved correctly in certain cases. It could happen that after you have entered for example a valid value for bit/second in the Speed trigger under Notification Triggers, that the value was saved afterwards with 0 or even an invalid float value. We also fixed this issue for the PRTG App for desktop. |
Remote probes |
We fixed an issue where not all probe Settings were displayed in the previous PRTG versions when you installed a new remote probe on your system. When you have added a remote probe successfully and opened the probe Settings tab you could see that, for example, the Credentials for Cisco Meraki were missing. |
Fixed
PRTG App for Desktop
Access rights |
You can now acknowledge alarms with your read-only user in the PRTG App for Desktop when you have set the according rights for that user in the PRTG web interface before. Previously, when you have created a read-only user in PRTG and afterwards added additional rights Allow user to acknowledge alarms to that user, the settings would not automatically be updated when the user was logged in to the PRTG App for Desktop. As a workaround, you had to restart the Core server or the user had to log in to PRTG App for Desktop again. |
Auto-Discovery |
We fixed an issue where the execution of an auto-discovery with device template on the PRTG App for Desktop produced an access denied message in the CoreWebServer.log. |
Note
Known Issues
PRTG application server |
Currently it is not possible to install or uninstall the PRTG application server via button Install Service or Uninstall Service in the PRTG Administration Tool. The PRTG Administration Tool will execute a Core server restart but the PRTG application server will not be installed or uninstalled afterwards. To install the PRTG application server and make use of the new UI and APIv2, please see our Knowledge Base article: I want to use the new UI and API v2. What do I need to know? |
PRTG Administration Tool |
You will receive an error when you click on the button Stop Service or Start Service (ignore changed settings) for the Core and Probe service in the PRTG Administration Tool when you run it as a 64bit version on your system. The PRTG Administration Tool will then report the following: One or more required program components of PRTG (PRTG Server.exe, PRTG Probe.exe) could not be found! Please re-run the installation program. This issues does not occur when you run the PRTG Administration Tool in a 32bit mode. We will deliver a fix for this issue with the upcoming PRTG versions. Solved with PRTG Stable version 24.2.96.1315 |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.2.94.1400
|
Lab
New UI
Device settings |
You can now configure and manage your Credentials for Windows Systems in the device settings in the new UI and also via API v2. This enables you to use sensors on your device which require windows authentication, like WMI sensors. The available fields are Domain or Computer Name, User Name and Password. You can also see and manage the Inherit From toggle and enable or disable it. The windows credentials will also be visible in the new UI when you set them via APIv2 PATCH request on the endpoint /api/v2/devices/{id}. Additionally you are now able to edit the following device settings in the new UI and APIv2: Credentials for VMware/XenServer, Credentials for AWS, Credentials for Script Sensors, Advanced Network Analysis. |
Mobile view |
We improved the navigation in the mobile view for the new UI. When you click on the menu icon it opens a drawer from the left hand side. The drawer remains open during navigation and you can close it with the x button. Additionally, when you select home in the side bar, you will see links to the sections Welcome and Quickstart. |
Lab
PRTG API v2
API |
|
PRTG application server |
We fixed an issue for the PRTG application server that ran into panic mode when you ran a mini probe on your PRTG installation, for example a Python Mini Probe or a PRTG Mobile Probe for Android. The created panic log would display the error panic: runtime error: invalid memory address or nil pointer dereference in these cases. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German and Spanish language files. |
Sensor languages |
We updated the Spanish language files for certain selected sensor types. |
February 14th 2024 - Version 24.1.92.1554
Blog article
By Michael Becker • Mar 1, 2024
PRTG release 24.1.92 is available in the stable release channel!
The latest version of Paessler PRTG, 24.1.92, is now available through the stable release channel! This version comes with several new sensor types that are now fully supported (like the Ping v2...
Read the complete blog post here
Read the complete blog post here
New
Sensors
Cisco Meraki sensors |
The Cisco Meraki License sensor monitors Meraki licenses of an organization and the Cisco Meraki Network Health sensor monitors the health of Cisco Meraki network devices. Both sensor types use the Cisco Meraki Dashboard API. We released these sensor types as experimental sensors with PRTG version 22.1.74.1869. |
FortiGate VPN Overview sensor |
This sensor monitors VPN connections of your Fortinet FortiGate firewall. The sensor shows the number of connected SSL clients, as well as the number of both up and down IPsec tunnels. We released this sensor type as experimental sensor with PRTG version 22.1.74.1869. |
HTTP v2 sensor |
This sensor allows you to send a HTTP request (HEAD, GET or POST) and use placeholders, similar to the REST Custom v2 sensor. We released this sensor type as experimental sensor with PRTG version 22.4.81.1532. |
Local Folder sensor |
The Local Folder sensor monitors a local folder on a probe system. We released this sensor type as experimental sensor with PRTG version 21.3.70.1629. |
Network Share sensor |
The Network Share sensor monitor a Server Message Block (SMB) or Common Internet File System (CIFS) network share. We released this sensor type as experimental sensor with PRTG version 21.4.73.1656. |
Ping v2 sensor |
The Ping v2 sensor comes with a new setting Inverted Error Status different to its predecessor. If you select Enable for this new setting, the sensor shows a Down status if the target device is reachable. The Ping v2 sensor supports IPv6. We released this sensor type as experimental sensor with PRTG version 22.4.81.1532. |
Redfish Virtual Disk sensor |
his sensor monitors the virtual disks of your Redfish capable servers and shows capacity and status. We introduced this sensor type as experimental sensor with PRTG version 21.3.71.1416. |
SNMP Uptime v2 |
This sensor type comes with the same basic settings as the already existing SNMP System Uptime sensor including the additional Data Source setting under the section SNMP Uptime Specific, where you can select the object identifier (OID) the sensor gets its uptime from. The Data source is also depicted in the sensor status. We released this sensor type as experimental sensor with PRTG version 23.2.84.1566. |
Soffico Orchestra Scenario sensor |
This sensor monitors the status of processes within an Orchestra scenario. Please note that this sensor requires a Soffico license and as of Orchestra 4.8.2.5. We released this sensor type as experimental sensor with PRTG version 23.4.90.1299. |
Improved
Security
API Keys |
We improved the creation of API keys via API call requests to match the given access rights. Previously, it was possible to create an API key for a read/write user with the parameter accesslevel_new=full via GET request, although the user only has write access at the most according to the API key access rights settings. The Access Level for the created API key then wrongly displayed full access. |
Web interface |
We fixed an issue where an authenticated attacker could craft a specific request against the editlicense.htm endpoint and change the license of PRTG partially affecting the availability of PRTG. The severity is 4.3-Medium and calculated as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L. |
Webserver |
We fixed a reflected XSS vulnerability which allowed JavaScript injection. The severity is 6.1-Medium and calculated as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. |
Improved
Server
Notifications |
We added the option for SNMP Trap notifications to include the sensor ID that triggers the notification in the trap message. If you select the option Include sensor ID in the Send SNMP Trap notification template, PRTG will send it on the OID 1.3.6.1.4.1.32446.1.1.5. Previously, parsing the sent trap messages was not possible for certain third party systems due to the missing option. |
Update to OpenSSL 1.1.1w |
To ensure secure communication furthermore we updated to the OpenSSL version 1.1.1w. |
Fixed
Server
Contact Support |
You can now send support bundles with the Contact Support option when you have configured a proxy server in the PRTG Core & Probes settings. Important: The issue still appears in the Paessler PRTG app for desktop. |
Change Password |
You will now receive a proper error message Error (Bad Request) again when you enter an invalid (old) password under My Account in your Account Settings. In the previous PRTG version there was a log entry in the Core webserver log Error: The validation of the data you entered has failed, but no corresponding error message in the web interface. The issue occurred when you selected the option Specify a new password and entered an invalid Old password. |
Device List |
We fixed an issue that caused the inheritance to be disabled for all settings of a device if you changed settings in the Device List before. The issue occurred when you selected several devices in the Device List via Settings option in the multi-edit and saved the changes. The settings of the devices where you made the changes for were set to disabled in the Inherit From toggle. |
Historic Data reports |
We fixed an issue for historic data reports that displayed not all or additional hours in the Date Time table when the user has set a different time zone under My Account in the PRTG Web Interface. For example, when your time zone in your account was set to (UTC -6:00) and you ran a historic data report for 12 hours, the report would in this case substract the hours in the Date Time table from the UTC time zone set under your account.. |
Libraries |
We fixed an issue for an unauthorized Ajax error that occurred in certain cases in the CoreWebServer.log instead of displaying the correct error message Your user account is not allowed to access this information. The issue happened when you were logged in with a user account whose assigned user group has write permissions on a library but who is not allowed to access user information when you clicked on the Security Context link for the user to see the User Account Settings. |
Lookups |
We fixed an issue for lookup files where changes were not reflected in the web interface when you changed values in lookup files after OID library creation. Changes to lookup values were only displayed after a complete PRTG core server restart. The issue affected for example the SNMP Library sensor, but also other sensors that come with value lookups and appeared only for the first modification in the lookup file. |
Maps |
|
PRTG Installer |
We fixed an issue where PRTG stored the data for the Installation Path in the same folder as for the Data Path when you selected to run the PRTG installer in the Custom mode for fresh installations since PRTG version 23.3.88. The issue happened when you changed the Data Path directory in the path field directly. |
Remote Probes |
Your remote probes that you have deleted from the device tree will no longer appear on your PRTG Status Page under the Probes and Database Objects sections, or in the information returned when you execute a query on PRTG Health System Information via an API call /api/health.json?. In the previous PRTG version, a deleted remote probe would still be displayed on the mentioned sections with the status disconnected. |
Reports |
You can now sent reports by email again for scheduled reports in the Report Schedule setting. Previously, when the report schedule sent out an email to a configured email address or PRTG user group you would receive an access violation in the Core.log and in certain cases also the message Error sending Report Email. The issue occurred if you selected a schedule for a report in the Report Schedule setting with Target Email Address and/or Email to User Group. |
Scanning Interval |
We fixed an issue where you could not save your Scanning Intervals in certain cases when you used a regular interval and a UTC interval with the same unit. For example, if you entered 4h and @UTC 4:00 at the same time in the Available Intervals section you would receive a validation error upon saving your changes. |
Fixed
Sensors
Add sensor |
We fixed an issue for certain sensors on addsensor.htm that could be added although the device or group to which you want to add these sensor types did not have corresponding credentials. When you tried to add an AWS sensor, for example, to a device without Credentials for AWS, you received an error message Sorry, the scan for available monitoring items has failed! The AWS sensors will now be displayed as inactive on addsensor.htm with a hint that valid credentials are needed when you try to add them to a device without Credentials for AWS. This issue was also fixed for the Local Folder sensor (BETA) and the Network Share sensor (BETA). |
AWS sensor |
We fixed an issue that caused the environment variable AWS_EC2_METADATA_DISABLED to be leaked into the environment of other sensors. For example, it did not work in cases when you had PRTG installed on an AWS environment and ran a script with a Python Script sensor that pulled credentials from an API although the role on AWS allowed PRTG to authenticate with an AWS SDK. The environmental variable was set to AWS_EC2_METADATA_DISABLED=TRUE in this case. |
AWS RDS v2 sensor |
Your AWS RDS v2 sensors now display the correct values for the channel Database Connections again. The sensors displayed a wrong amount of connections in the mentioned channel with PRTG stable version 23.4.90.1299 since the sensors pulled the metric for 'SUM' and not 'AVG' (average) for Database Connections. |
Veeam Backup Job Status Advanced sensor |
Your Veeam Backup Job Status Advanced Sensor is now able to display the correct value for the channel Job Scheduled when the scheduled job has been disabled. The channel Job Scheduled will now display the value No where previously the channel would have displayed the value Yes. For more information please see our Knowledge Base article:https://kb.paessler.com/en/topic/89136 . |
Fixed
WebUI
Device tree |
We fixed an issue that occurred when you renamed a device or group via context menu in the device tree that contained Credentials for Microsoft 365. The error message was The validation of the data you entered has failed and settings could not be saved when you tried to rename the device or group with right click on edit and rename. The issue also occurred when you tried to edit the access rights in the device tree in these cases. |
Historic Data Tooltip |
We fixed an issue where a second tooltip icon with tooltip text was displayed in the section Percentile Handling in the Historic Data Tab of a sensor. You could observe this behavior when you selected the radio button for Show Percentiles. The second tooltip would be displayed for Percentile Averaging Interval. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.1.92.1554
|
Lab
Multi-Platform Probe
Multi-Platform Probe 0.19.0 release |
The Multi-Platform Probe enables you to deploy probes on platforms not supported by the Remote Probe, including various Linux distributions and ARM hardware.
In this latest release, we provide TLS support, ensuring a secure and encrypted connection to the NATS server. Additionally, we've included a user-friendly setup wizard for the NATS server, streamlining the installation and configuration process. For more information about the Multi-Platform Probe please see our Knowledge Base article: What is the Multi-Platform Probe and how can I use it? For detailed release notes please see our Knowledge Base article: What are the release notes for the Multi-Platform Probe? |
Lab
Sensors
Redfish Virtual Disk Sensor |
The Redfish Virtual Disk sensor (BETA) is now able to handle disks that have one of the following states: Enabled, StandbySpare, InTest, Starting, Quiesced, Updating and Qualified. Previously, the sensor could handle only the state Enabled and would display the status offline for all other states. |
Script v2 sensor |
We improved the security for the usage of Python scripts with the Script v2 sensor. All PYTHON* environment variables that might be set, like PYTHONPATH or PYTHONHOME, will be ignored when you execute scripts with the Script v2 sensor by using the parameter -E. This parameter prevents that a different e.g. PYTHONPATH is set and that Python scripts with potential security issues are run in the Python script directory. |
SNMP Uptime v2 |
We fixed an issue for the SNMP Uptime v2 (BETA) sensor that displayed wrong values in the Live Data section of the sensor in the System Uptime channel. The issue occurred when you added the sensor to your PRTG local probe, however, it displayed the correct values when you have added it to your Multi-Platform Probe. |
Lab
PRTG API v2
API |
|
Devices |
|
PRTG application server |
|
Security |
We fixed an issue where it was possible to escalate privileges for API-Keys. |
Lab
New UI
Web interface |
|
Mobile view |
We introduced a new header for PRTG in mobile view where the menu is positioned on the top left side. The parent breadcrumb will be displayed on the top right side. The main page title Home was removed. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements, updated user manual. |
Languages |
We updated the German and Spanish language files. |
Sensor Languages |
We updated the German and Spanish language files for certain selected sensor types. |
January 10th 2024 - Version 24.1.90.1306
Important
Security
Webserver Security |
CVE-2023-51630 - ZDI-CAN-21182: An XSS vulnerability was identified through the htmclass parameter in the error.htm in PRTG 23.4.90.1299 and earlier versions where an attacker could bypass the authentication by creating a malicious link and luring a PRTG user with an active session to click it. The severity of this vulnerability is high and received a score of 8.8, (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
For further information, please refer to ZDI-24-073 and CVE-2023-51630 We would like to thank n1nj4sec for working with Trend Micro Zero Day Initiative and responsibly reporting this vulnerability. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 24.1.90.1306
|
November 15th 2023 - Version 23.4.90.1299
Blog article
By Michael Becker • Dec 4, 2023
PRTG release 23.4.90 is available in the stable channel
The most recent version of Paessler PRTG, 23.4.90, is now accessible through the stable release channel! This version comes with the experimental Soffico Orchestra Scenario sensor, supported proxy...
Read the complete blog post here
Read the complete blog post here
New
PRTG Data Exporter 2023.11.9.1
General |
|
UI |
Filters page
|
New
PRTG Database Observer 1.60
General |
Small bug fixes and changes |
New
PRTG SLA Reporter 3.40
General |
|
PDF Reports |
|
Planned Downtimes |
Can now be defined by selecting filters, SLAs, and/or individual sensors |
Polling Task |
New setting added that can be used to enable debug logging |
Reporting |
|
UI |
|
Scheduled Reports |
|
New
ITOps Board 3.13
Improvements and Fixes |
ITOps Board version 3.13 comes with accessibility enhancements. In this release, the Explorer tab has been updated for accessibility and now includes text labels to indicate the health state of each component. Additionally this release introduces the use of icons to indicate the health state of components and alerts.
It also covers fixed issues. For more information please refer to the release notes provided with the new version. Important Notice: Upgrade Process. The ITOps Board installer supports an in-place upgrade. If you made manual changes to the web.config file, those changes are not preserved during an in-place upgrade. Any manual changes to the web.config file are saved in a file with a name that uses the following format: Web-YYYY-MM-DD.config. Before you begin an upgrade, save a copy of this file. It is recommended that you use the file as reference to make changes to the new web.config file, which will overwrite the previous file during the upgrade process. Do not overwrite the new web.config file with the old file. This release of ITOps Board requires Elasticsearch version 7.17.6. |
Improved
Security
Forgot Password |
The reset token in the link for setting a new password is now masked in the CoreWebServer.log. It was logged in a readable format before when you clicked on the link for setting a new password with the forgot password option. |
Improved
Sensors
Exchange Database DAG (PowerShell) sensor |
Your Exchange Database DAG (PowerShell) sensor now recognizes newer versions of Exchange Server (>2019) and can distinguish between versions i.e 2010, 2013, 2016 and 2019. Previously the sensor recognized the Exchange Server 2019 version as an older version and tried to use this information, resulting in a Warning status for the Active Copy Channel with the message Could Not Read Activation Preference. |
EXE sensors |
We updated our database connectors for certain EXE sensor types, e.g. Oracle SQL v2 sensor, MySQL v2 sensor and PostgreSQL sensor. Previously, the connection to the corresponding databases failed due to required encryption ciphers that did not match. |
Microsoft Azure sensors |
|
OPC UA Custom sensor |
Your OPC UA Custom sensor now supports more data types, that means enums and single values from array-valued variables. Previously, the sensor supported only string, Boolean, and numeric variables. |
Proxy Settings |
We improved the following sensor types to support the Proxy Settings in the device settings so they are able to use a HTTP proxy server when you have set up one in the device settings:
|
Soffico Orchestra sensors |
You can now create device templates that include the sensor types Soffico Orchestra Channel Health sensor and Soffico Orchestra Scenario sensor (BETA). This enables you to add these sensors via auto-discovery. |
Changed
Sensors
MySQL v2 |
With this PRTG version the MySQL v2 sensor does not support the integrated Windows authentication for MySQL anymore due to a license change in the database connector. The sensor will request the Windows password and username instead. |
Windows IIS 6.0 SMTP Received, Windows IIS 6.0 SMTP Sent |
We renamed the sensor types Windows IIS 6.0 SMTP Received sensor to Windows SMTP Service Received sensor and Windows IIS 6.0 SMTP Sent sensor to Windows SMTP Service Sent sensor to meet the technical requirements. |
Fixed
Server
Access rights |
We fixed an issue that affected the creation of Reports, Notification Templates and Schedules when you were logged in as a user with read/write access. When you were logged in as a read/write user, you would get an Unauthorized ajax error when you tried to create a Report, Notification Template or Schedule. However, the creation was successful in the background and visible to PRTG users with administrative rights afterwards. |
API Keys |
We fixed an issue where the created API key for an active directory user was still valid for a certain period of time even though the active directory user was deleted. Previously, when you created a new user in your active directory and connected it with your PRTG installation and also created an API key for this user, the API key would still be valid for a while even the login credentials were not when you deleted the user afterwards. The API key is now promptly invalid like the credentials when you delete the user from your active directory. |
Map rotation |
Public map rotation is now working again as expected. Previously, if you used the public map rotation feature without login credentials required, only the first map would be displayed or the other maps would be displayed as blank pages instead. |
Reports |
You can now create Historic Data Reports in the Historic Data tab for sensors as .csv file format again with the setting for show percentiles activated. Previously, the historic data report would run into an Ajax Error: timeout when you selected the format .csv file and additionally selected the radio button for show percentiles. |
Scanning Interval |
We fixed an issue for certain selected sensor types that caused the previously set scan interval to be ignored and always run for the default value of 60 seconds. In addition, the interval information was not added to the sensor log in cases where the |
Fixed
Sensors
AWS sensors |
We implemented various improvements for the AWS v2 sensors:
|
EXE sensors |
We fixed an issue for certain EXE sensor types, such as the ADO SQL v2 sensor, where the parsing for arguments failed when the Connection String in the Database Specific setting contained a linebreak. The sensor reported a down status with the message Invalid Authorization Specification in these cases. |
Microsoft 365 Mailbox sensor |
|
MySQL v2 |
We fixed an issue for the MySQL v2 sensor where the executed SQLV2.exe client tool reported an error with the message Parameter -sslmode is missing. With PRTG version 21.2.68.1492 we introduced a dedicated setting for the SSL mode; however, this setting was initially only implemented for the Command Line Interface. The options you could choose are the same as the values of the MySQL sslmode parameter. |
Netflow sensors |
We fixed an issue for certain Flow sensors, like the NetFlow v9 sensor or IPFIX sensor, that led to access violations in certain cases when the data flow contained fields with variable length. |
OPC UA Server Status sensor |
We fixed an issue for the OPC UA Server Status sensor that reported the following error message in certain cases: The sensor could not connect to the OPC UA server (BadConnectionClosed). The issue occurred because the endpoint selection changed with an update of the library open62541 that is used by OPC UA. |
SNMP HPE ProLiant Memory Controller sensor |
We fixed an issue for the HPE ProLiant Memory Controller sensor that in some cases could not be created on a HPE ProLiant Gen10 server when the device type was 1 (other) in the given OIDs. An error with the message The sensor could not find any matching data on the monitored device occurred in these cases during sensor creation. |
SMTP sensor |
We fixed an issue for the SMTP sensors where the HELO ident that you configured in the Authentication setting of the sensor was ignored and instead e.g. the default hostname of the probe was used. This issue affected the SMTP sensor, SMTP&POP3 Round Trip sensor and the SMTP&IMAP Round Trip sensor. |
Note
Paessler PRTG Enterprise Monitor
Offline activation |
With this PRTG version we introduce a solution for offline installations of Paessler PRTG Enterprise Monitor that allows you to use a special Paessler PRTG Enterprise Monitor license for an offline system. You will be contacted by your Paessler Sales representative if this change applies to you. For more information please see our Knowledge Base article https://kb.paessler.com/en/topic/91881. |
Fixed
Paessler PRTG Enterprise Monitor
WebGUI footer |
We fixed an issue where the footer on the PRTG web interface displayed Renew Maintenance when you had an active subscription license and when you were logged in with an account with administrative rights. The button Renew Maintenance appeared regardless of the maintenance days you had left. The footer now displays correctly the Contact Support button. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 23.4.90.1299
|
Lab
Sensors
Script v2 sensor |
You can now create the Script v2 sensor (BETA) when you execute the Run Auto-Discovery with Template function on a device. The sensor will be created only when you have Python installed on the probe system. |
SNMP Disk Free v2 |
We fixed an issue for the SNMP Disk Free v2 (BETA) that displayed wrong values in certain cases when you updated to PRTG version 23.3.88.1393. The issue occurred in cases when you monitored disks with a larger volume. The sensor then reported wrong values like 0% for the percentage channel Free Space and went into error status. Additionally, the absolute values in the channel Total were displayed as negative. The issue happened because the value calculation in the sensor was exceeded by the large values and the sensor could not handle the value overflow correctly. |
SNMP Traffic v2 sensor |
Your SNMP Traffic v2 sensor now includes the tag snmp in the default tags that are automatically predefined in the Basic Sensor Settings when you add the sensor. |
Soffico Orchestra Scenario sensor |
You can try out our experimental Soffico Orchestra Scenario sensor that we introduce with this PRTG version. This sensor monitors the status of processes within an Orchestra scenario. The sensor comes with the channels Aborted Count, Downtime, Finished Count, Paused Count, Running Count and Warning Count. Please note that this sensor requires a Soffico license and as of Orchestra 4.8.2.5. |
Local Folder sensor and Network Share sensor |
You can now add the sensor types Local Folder Sensor (BETA) and Network Share Sensor (BETA) to your device template when you select the function Create Device Template in the device tree. This enables you to create these sensors afterwards with the option Run Auto-Discovery with Template. |
Lab
PRTG API v2
API v2 |
We added a new parameter purpose to the /schemas/{kind} endpoint that supports the values create (for POST), update (for PATCH) or read (for a GET endpoint). The endpoint returns the appropriate schema for a given purpose. |
PRTG application server |
|
Lab
New UI
Channels |
We fixed an issue for the Last Value column in the new UI that displayed 0% as difference value. The Last Value column now no longer show a difference value of '0' in the sensor channel list when the value is 0% as difference between Warning Limit and Last Value. |
Device Settings |
|
Maps |
We fixed an issue that occurred when you deleted devices that were included in a map. Previously after you deleted devices in the new UI that were included in a publicly accessible map you would receive the warning message Monitoring might be incomplete or inaccurate due to fundamental problems in your PRTG installation! Click here for more information! when you opened the map then in the classic UI. In addition, the Core Health sensor displayed a down status with the error message Free Physical memory is below error limit of x in Free Physical Memory. The public access page for the map was also not accessible and reported the error Map Refresh Failed in these cases. |
URL parameter |
|
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements. |
Manual |
We have updated the manual to provide recommendations on how to handle PRTG configuration files in a secure manner, please see the updated manual sections Files and Subfolders in the PRTG Data Directory and Handling Configuration Files. |
Languages |
We updated the Chinese, French, German, Japanese, Portuguese, Russian and Spanish language files. |
Sensor Languages |
We updated the Chinese, German, French, Japanese, Portuguese, Russian and Dutch language files for certain selected sensor types. |
October 16th 2023 - Version 23.4.88.1429
Blog article
By Michael Becker • Oct 25, 2023
New PRTG release 23.4.88 is available!
The latest Paessler PRTG release, 23.4.88, is now available in the stable release channel! This version comes with the experimental SNMP Traffic v2 sensor and improvements for the MQTT Subscribe...
Read the complete blog post here
Read the complete blog post here
Important
Security
Webserver |
We fixed a path traversal vulnerability in the PRTG Webserver that could be leveraged without authentication. The vulnerability can be tracked under CVE-2023-45858. More information will be available as part of a staged disclosure process, for updates please see our Knowledge Base article https://kb.paessler.com/en/topic/91880. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 23.4.88.1429
|
October 2nd 2023 - Version 23.3.88.1421
Fixed
Sensors
SNMP Disk Free |
We fixed an issue for the SNMP Disk Free sensor that displayed wrong values in certain cases when you updated to PRTG version 23.3.88.1393. The issue occurred in cases when you monitored disks with a larger volume. The sensor then reported wrong values like 0% for the percentage channel Free Space and went into error status. Additionally, the absolute values in the channel Total were displayed as negative. The issue happened because the value calculation in the sensor was exceeded by the large values and the sensor could not handle the value overflow correctly. Note: This issue still occurs for the SNMP Disk Free v2 (BETA) sensors that we released as experimental sensors with PRTG version 23.2.86.1520. |
Fixed
Server
Maps |
We fixed an issue that led to a higher memory consumption when you updated to the previous PRTG stable version 23.3.88.1393. The issue was caused by public map displays. You can also recognize an increased Sessions number in the PRTG Core Server System Memory on the setup page in this case. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 23.3.88.1421
|
September 20th 2023 - Version 23.3.88.1393
Improved
Server
Security |
Your API Keys are no longer logged in a readable format in the CoreWebServer.log when you have created an API key before and executed an API call request with it. The issue only occurred for the Log in Debug Level. |
Improved
Sensors
AWS EC2 v2 and AWS RDS v2 sensors |
Your AWS EC2 and AWS RDS v2 sensors will show a warning message if the limit of the channel CPU Credit Balance limit has less than 1 credit available. Previously the sensors were showing an error status. Please note that this change applies only when you add this sensor type as new sensor. |
Microsoft 365 Mailbox sensor |
You can now filter emails that match a defined regular expression. The new filter filters email whose Subject, From or Body fields match the defined regular expression. You can set the new option under the Microsoft 365 Settings. Important: The regular expressions filter will result in the Down status if there are more than 10,000 emails in the mailbox folder you want to monitor. This is because the regular expression filter is applied after the emails are retrieved from the API. The larger the volume of emails, the greater the impact on performance. Enable the Filter by Age setting or use a non-regular expression filter in addition to the regular expression filter to reduce the number of emails. |
MQTT Subscribe Custom sensor |
We added two new options in the MQTT Specific settings of the MQTT Subscribe Custom sensor for a better message handling. The option Add duration since last message will set a threshold alarm that will notify you when no message was received. Previously, the sensor went into unknown status before when no message was received in the scan interval. This default behavior will remain if the setting for Add duration since last message is not enabled. The option Retain last sensor value keeps the last message on the live charts and allows you to monitor specific JSON values of the payload. |
SNMP Buffalo TS System Health Sensor |
Your SNMP Buffalo TS System Health sensor is now able to display an additional status for the channel Firmware Update Available. Previously, the status was not included in the lookup file and therefore displayed an error with the message undefined lookup value (3) when the value 3 was sent to the sensor. The value 3 in this case represents the status latest. |
Fixed
Server
Cluster Setup |
We fixed an issue that caused the Failover node to become unreachable when you added a new contact to the Notification Contacts settings of the Master node. |
Dependencies |
We fixed an issue where dependent objects, like sensors and devices, were not paused if the configured master sensor went into error status due to exceeded limits. When you configured the sensor under Dependency Type as Master sensor for parent then the issue occurred in rare cases when the sensor was not saved to the device tree while the limit status changed. The issue only affected newly created sensors. |
Error messages |
PRTG shows the error dialog Error (Bad Request) in the web interface again when you attempt to save invalid changes to settings. Previously, the error description was not displayed. The page reloaded without any indication when you tried to save your changes with invalid settings. The error was only logged in CoreWebServer.log. |
Libraries |
You can now create libraries again when you are logged in as a user with read/write access. This did not work before in the previous PRTG version 23.3.86.1520 when you were logged in as a read/write user that has full access in the according user group. You would get an Unauthorized ajax error message for adding a new library before. |
Notifications |
|
PRTG Administration Tool |
You can now enter a folder path with a folder that contains ANSI-characters, like umlauts or accents, in the PRTG Core Server Tab of the PRTG Administration Tool. Please note that this change does not work for unicode characters, like the Cyrillic language. If you select a folder path that contains non-ANSI characters or if you enter a folder path name with such in the field for Local Storage of Data Files and Monitoring Database, then an according error message will be displayed. |
PRTG Installer |
During PRTG installation, when the license server is unreachable due to connection or license expiration issues, the following error message will be displayed: Either the license server is not available because you are offline, or you cannot use the current version of installer because your license has expired. Please check your connection or log into the Paessler shop, make sure your maintenance contract is active and restart the installer. Previously, the installation displayed an error with the message that the license is invalid or that maintenance has expired. |
Probe connection |
We fixed an issue where in certain cases the probe service stopped working and caused the probe to disconnect from the PRTG core server. The probe service then reported a high CPU usage in these cases and sometimes access violations were logged in the PRTG probe.log additionally. The issue was probably caused by the DNS v1 sensor that we declared as deprecated with PRTG version 21.3.69.1333 and which was replaced with its successor DNS v2 sensor. For more information about deprecated sensor types and their alternatives please see our Knowledge Base article: https://kb.paessler.com/en/topic/89505. |
Remote probe update |
We hardened the mechanism for the automatic update of remote probes in PRTG with this PRTG version. Previously, sometimes remote probes required a manual update after you auto-updated your PRTG server with a new version due to a connection issue. Please note that this change will take effect when you update from PRTG 23.3.88 to the following version, not immediately after updating to this PRTG version. |
Scanning Interval |
We fixed an issue in the Monitoring settings for the Scanning Intervals section. You can now enter multiple scanning intervals again with the format of Coordinated Universal Time (UTC) points, like @ UTC hh:mm , hh:mm. Previously intervals with the "@ UTC" format were treated as duplicates and the entries could not be saved. Please note that you have to enter different time periods in the scanning intervals when you add multiple intervals in the UTC format. Note:The input validation still incorrectly fails when you add a UTC at a full hour that is already set as hourly scanning interval. For example, @ UTC 06:00 fails to save when there is already a scanning interval with 6h while @ UTC 06:01 would work in this case. |
Single Sign-on |
We fixed an issue where in rare cases the execution of the button Test Single Sign-On Authorization Endpoint led to an access violation. This issue occurred only in very rare cases if your Application (Client) ID for loading the configuration contained a blank space at the end. |
User groups |
We fixed an issue for user groups that had the setting Allow user group members to create certain sensors only enabled. When you created a user group with the mentioned setting and did not select any sensor types in the list, then all the sensor types would be selected after a PRTG core server restart for this user group. |
Fixed
Sensors
Add sensor |
We fixed an issue for certain sensor types that ran into the error no available in the Specific settings of the sensor during sensor creation. The issue happened when a timeout value higher than 300 was set in the registry for the initial sensor scan when you added the sensor. Sensor types affected were Microsoft 365 Service Status Advanced, Veeam Backup Job Status Advanced sensor, for example. |
Beckhoff IPC System Health sensor |
The Beckhoff IPC System Health sensor now supports IPv6 as IP Version connection that you can configure in the Basic Device Settings under IP version of the monitored device. The sensor appeared under Sensor types that are not IPv6 compatible in the previous PRTG versions due to a missing compatibility flag in the sensor library. |
Custom sensor channel names |
We fixed an issue for custom sensor types, like the HTTP Push Data Advanced sensor, where channels were created as duplicate when there was a trailing whitespace behind the relevant channel name. The issue occurred after a PRTG core server restart. The whitespace was removed and since it did not match the previous channel name, the sensor would create a duplicate. |
HL7 sensor |
We fixed an issue for the HL7 sensor in the settings for Message Header where the Default message header was overwritten in certain cases. The issue happened when you entered data for the setting Override message header but you activated the radio button for Default message header afterwards. In those cases, the sensor always took the override parameters instead of the selected default headers from the script. |
HTTP Push Data sensors |
Your HTTP Push Data sensors will show again their values in the Last Value column of the channel list of the sensor as well as in the channel gauges of the sensor Overview tab. The Last Value column did not display any data before in the previous PRTG versions for the HTTP Push Data sensor, HTTP Push Data Advanced sensor and HTTP IoT Push Data Advanced sensor. |
HTTP sensors |
We fixed the handling of HTTP methods that are returned after a redirect to follow the Post/Redirect/Get (PRG) pattern. This prevents the contents of the original POST to be resubmitted by redirecting the client to another location. If you select the Request Method POST, for example, under the HTTP Specific settings of the sensor, then the first request will use this method. If a request is redirected, all further requests will use GET. Redirects of requests that use GET and HEAD will continue to use GET and HEAD, respectively. This change affects all HTTP based sensor types, like the HTTP sensor and HTTP Advanced sensor. |
Microsoft Azure sensors |
Your Microsoft Azure sensors now query data in a slightly longer time span to make sure data is returned from Microsoft Azure and that every time stamp is considered. Previously, it could happen that Azure did not return any value when the queried time span was too close to the present as it would query only the most recent one and not also the latest data.
Note: The Microsoft Azure SQL Database sensor will throw an exception in case no result is returned from timeseries. Microsoft Azure Storage Account and Microsoft Azure Virtual Machine sensors return default value = 0 in case no result is returned from timeseries. |
NetApp I/O v2 sensor |
We fixed an issue for the NetApp I/O v2 sensor that occurred with the ONTAP version update to 9.12.1P3. Due to changes in the API, the sensor received additional unexpected information which resulted in an error with the message The queried field "value" is empty for NetApp Cluster systems. |
OPC UA sensors |
We fixed an issue for OPC UA sensors that could run into a memory leak on the probe system causing the probe service to stop. The issue occurred only in certain cases when you ran a large number of OPC UA sensors, like OPC UA Certificate sensor, OPC UA custom sensor and OPC UA Server Status sensor with a short scan interval. |
Redfish System Health sensor |
We fixed an issue for the Redfish System Health sensor that in certain cases reported an error when the monitored device did not sent a Thermal service. The sensor ran into an exception and reported the error message No 'Thermal' service found in Redfish chassis. The channel for Thermal Status will now report the status Offline/Absent when there is no Thermal data sent by the monitored device. The channel for Thermal Status will not be created if the target system does not support this service determined with the first scan. |
SSL sensors |
We fixed an issue for the SSL Security Check sensor and SSL Certificate sensor that did not work anymore when a SOCKS proxy server for sensor connection was used in the previous PRTG versions. The sensors reported an error with the message The connection has dropped (PE039) in these cases. |
SNMP Cisco System Health sensor |
We fixed an issue for the SNMP Cisco System Health sensor that resulted in sensor logs that were written into the \Logs\sensors folder when you have selected the option Discard result in the Debug options of the sensor. The sensor kept overwriting the log files in this case when the store result option was disabled. Additionally, the sensor disabled the option Store result automatically after writing log files and reset it to Discard result. We also fixed this behavior so that you can now edit the options again manually. |
SNMP Custom String sensor |
We fixed an issue for the SNMP Custom String sensor where the parameter for the setting Interpret Result As was always set to the String (default) option, regardless of the option you set before. This issue occurred when the sensor was used in a device template. |
SNMP Nutanix Hypervisor sensor |
Your SNMP Nutanix Hypervisor sensor will display the speed in the column Last Value (speed) for Bytes Received when you update to this PRTG version. In the previous PRTG versions, the Last Value (speed) for Bytes Received was missing and had the unit Megabyte instead of Mbits configured. |
SNMP sensors |
Your SNMP Disk Free and SNMP Memory sensors now display valid values for monitored disks with a larger size >16 terabyte and memory storage >2 terabyte again. In the previous PRTG versions, these sensor types displayed random values or reported an error code 2003 |
Note
Known Issue
PRTG Installer |
PRTG currently stores the data for the Installation Path in the same folder as for the Data Path when you select to run the PRTG installer in the Custom mode for fresh installations. This issue happens when you change the Data Path directory in the path field directly. We will deliver a fix for this issue in the upcoming PRTG versions. As a workaround, please create a custom folder first if you do not want to install PRTG with the given default Data and Installation Paths. You can then select the folder location with the Browse button in the PRTG installer for the according path. Solved with PRTG Stable version 24.1.92.1554 |
Fixed
PRTG Desktop
Cloning sensors |
We have fixed an issue that prevented a sensor from being cloned to more than one device. The same issue would also occur if you tried to clone another sensor to another device after the first clone attempt. In both cases you would receive an error message stating Invalid operation. You can now clone a sensor (or different sensors) to more than one device. |
Comments |
We fixed an issue that prevented you from saving new or edit existing comments in the Comment tab of a device or a sensor. |
Probe transfer |
We fixed an issue where the transfer of your probes to another server may have failed in certain cases and resulted in a deadlock with the previous PRTG versions. With PRTG version 23.2.84.1566 we announced that you can find the Probe Transfer feature for PRTG Desktop under Probe Connection Settings in the PRTG setup and that it is no longer available in the Experimental Features section. |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 23.3.88.1393
|
Lab
Multi-Platform Probe
Beta release |
The Multi-Platform Probe enables you to deploy probes on platforms not supported by the Remote Probe, including various Linux distributions and ARM hardware. We are happy to announce that the MPP has entered its Beta status with this release. This version brings improvements for various internal processes and includes the SNMP Traffic v2 sensor. For more information about the Multi-Platform Probe please see our Knowledge Base article: What is the Multi-Platform Probe and how can I use it? For detailed release notes please see our Knowledge Base article: What are the release notes for the Multi-Platform Probe? |
Lab
PRTG API v2
Device settings |
We fixed an issue where it was not possible to pause a device via API with /api/v2/devices/40/pause. |
API Keys |
You can now create, read, update and delete API-Keys with HTTP requests via PRTG API v2. For example, a POST request to users/{id}/api-key will create an API key with name, description and access level properties for the user. For more information about how to manage API keys in the API v2, check the Accounts section in your OpenAPI specification at {yourprtgserver}:1616/api/v2/oas/#/Accounts (HTTPS) or {yourprtgserver}:1615/api/v2/oas/#/Accounts (HTTP) . |
PRTG application server |
We fixed an issue for the PRTG application server that ran into panic mode during startup process in certain cases. |
Lab
New UI
Device Settings |
|
Device Tree |
We fixed an issue that resulted in a missing cloned group in the new UI tree when you have cloned the group before in the classic UI and removed one device from the cloned group afterwards. Instead of only missing the deleted device in the new UI the whole group was gone in these cases. |
Web Interface |
We improved the navigation behavior of cards on the device and sensor overview pages. |
Lab
Sensors
REST Custom v2 |
|
SNMP Traffic v2 |
You can try out the experimental SNMP Traffic v2 sensor. The SNMP Traffic v2 sensor monitors bandwidth and traffic on a device via the Simple Network Management Protocol (SNMP). This sensor type has the same basic settings as its predecessor and comes with the additional channels Broadcasts In (number of incoming broadcast packets), Broadcasts Out (number of outgoing broadcast packets), Multicasts In (number of incoming multicast packets), and Multicasts Out (number of outgoing multicast packets). This sensor is not affected by the following SNMP compatibility options set in the parent device: Port Name Template, Port Name Update, Port Identification, Start Interface Index, and End Interface Index. |
HTTP v2 |
We improved the handling of HTTP requests for the HTTP v2 (BETA) sensor to follow the Post/Redirect/Get (PRG) pattern. |
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements. |
Languages |
We updated the German and Spanish language files. |
Sensor Languages |
We updated the Dutch, German and Spanish language files for certain selected sensor types. |
July 25th 2023 – Version 23.3.86.1520
Blog article
By Michael Becker • Aug 14, 2023
New release! PRTG 23.3.86 is now available
Paessler PRTG 23.3.86 is now available in the stable release channel! The main focus of this release is to provide security fixes throughout PRTG. In addition, this release includes the...
Read the complete blog post here
Read the complete blog post here
New
ITOps Board 3.11
Improvements and Fixes |
ITOps Board version 3.11 comes with improvements to accessibility on the boards page and context menu, as well as excluded child boards by default on display and improvements to integration settings. It also covers fixed issues. For integrations that have a large number of components, an internal server error may have occurred in previous ITOps Board versions when you have performed a search. Also boards will no longer remain in maintenance mode when the scheduled maintenance period has ended. Security Update: We updated the ITOps Board to version 3.11.4 to fix an issue in the remote agent installation file where the connection credentials were stored in a readable format and are now masked again. |
Improved
Security
Vulnerabilities |
For further information please also see our Knowledge Base article: https://kb.paessler.com/en/topic/91845 |
Improved
Sensors
Sensor Security |
We fixed a vulnerability that could enable an authenticated and authorized malicious user to write an arbitrary file on the probe system. The issue affected the exe sensors FTP Server File Count sensor and HTTP XML/REST Value sensor. The vulnerabilities can be tracked under CVE-2023-22631 and CVE-2023-22632. For further information please also see our Knowledge Base article: https://kb.paessler.com/en/topic/91756 |
Improved
Web server
Web server Security |
We hardened PRTG against a possible Cross-Site Scripting (XSS) attack where a malicious actor could trick a victim into running injected javascript code over a manipulated link. Specifically, by using the bodyclass as a get parameter in conjunction with specifically encoded javascript, an attacker could trick a victim into running the injected code and disclose information to the attacker. Thanks to Nicolas Verdier for reporting the issue. The vulnerability can be tracked under CVE-2023-28148. |
Fixed
Server
Forgot Password |
Read-only users that do not have the permission to change their password will now receive an email again with the information Subject: Password Reset Failed: Please contact your PRTG administrator. Password Reset Failed: Not allowed. Read-only users without permission to change their password did not receive this email in the previous PRTG version before with the Forgot password? option on the PRTG login page. |
PRTG Configuration file |
Access keys for Probe and PRTG application server are now encrypted in the PRTG configuration file. The mentioned access keys were displayed in a readable format in the previous PRTG versions. |
PRTG installer |
The PRTG installer now validates the access to the selected Installation Path and Data Path on PRTG installation in the Custom mode and resets the path to its default when it is not accessible. Previously, the installation displayed a fatal error with the message PRTG Webserver could not be started properly when the installer failed to write into the path due to access restrictions. |
Notifications |
We fixed an issue for the HTTP notification type when it contained reserved special characters, such as hash symbols (#), in the placeholders of the URL which you can add in the Execute HTTP Action section. The URL string was cut off after the hash symbol in these cases. |
Object naming |
We fixed an issue on group, sensor, device and notifications level that led to several issues in the web interface when you entered an URL as name of the relevant object. |
Fixed
Sensors
DNS v2 sensor |
We fixed an issue for the DNS v2 sensor where the character escaping for curly brackets } in the Filter Value did not work properly. The sensor displayed the error message regex_error(error_brace): The expression contained mismatched { and }. |
HL7 sensor |
We fixed an issue for the HL7 sensor that went into error status with the message Error caused by lookup value 'No' in channel 'Message Control ID OK' (AE:102 Data type error) after running for a certain period of time. The issue was located in the current date and time of the timestamp. |
HPE 3PAR |
We fixed an issue that happened within the parsing of the output for the commands executed by the HPE 3PAR drive enclosure sensor. The sensor then reported the error message Invalid response structure encountered, some data is missing for HPE Primera systems in certain cases. |
HTTP Advanced |
Your HTTP Advanced sensors now can use custom headers again when you have defined them in the setting for Use Custom HTTP Headers of the sensor settings. Previously, the custom headers were ignored and overwritten with a default value. We therefore also fixed an issue with the default HTTP headers where the wrong response format, e.g. XML instead of JSON, was returned in certain cases. |
Microsoft Azure Storage Account Sensor |
We fixed an issue for the Microsoft Azure Storage Account sensor's channel, Used Capacity , which was previously recording 0 values. With this fix the sensor returns the average values. |
NetApp SnapMirror v2 |
Your NetApp SnapMirror v2 sensor is now able to display a correct status for the channel Transfer Status when the reverse lookup value is insync for Snapmirror response protections. Previously, the sensor reported an error with the message The following reverse lookup value is invalid: insync. in this case. |
NetFlow |
We fixed an issue for the NetFlow v5 sensor where the values for Inbound and Outbound Interface were set to 16 bit instead of 32 bit in certain cases. |
OPC UA Sensors |
|
Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor |
We fixed an issue for the Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized |
Windows MSMQ Queue Length sensor |
Your Windows MSMQ Queue Length sensors will now run again when you update to this PRTG version. These sensor types did not work anymore with PRTG version 23.1.82.2175 and reported an error with the message Queuename not found on specified machine in certain cases. The issue occurred on remote systems with a MSMQ service running that could not be queried. |
Fixed
PRTG Mobile Apps
User Login |
We fixed an issue where the login for non admin user accounts did not work anymore when PRTG was updated to version 23.2.84.1566. The issue occurred for both manual and QR code login. The workaround was to log in with an admin user account.
Note: This fixes also an issue for PRTG Desktop where non admin users were also not able to log in anymore with PRTG version 23.2.84.1566. |
Note
Known Issue
PRTG Desktop Probe Transfer |
The transfer of your probes to another server may fail in certain cases and will result in a deadlock. We are currently analyzing the issue. With PRTG version 23.2.84.1566 we announced that you can find the Probe Transfer feature for PRTG Desktop under Probe Connection Settings in the PRTG setup and that it is no longer available in the Experimental Features section. Solved with PRTG 23.3.88.1393 |
Libraries |
You currently cannot add a library with a user account that has read/write access when you update to this PRTG version. When you are logged in as a read/write user that has full access in the according user group you will get an Unauthorized ajax error message for adding a new library. As a workaround, please use an admin user account instead. We will deliver a fix for this issue in the upcoming PRTG versions. Solved with PRTG 23.3.88.1393 |
Microsoft 365 Mailbox sensor |
You currently cannot save changes in the sensor Settings of your M365 Mailbox sensor when you update to this PRTG version 23.3.86. If you change the sensor settings and try to save them, you will receive an Unauthorized ajax error message, the site page will reload, and the settings will revert to the previous state. You can save the settings initially when you add this sensor type as new sensor during the creation process. We will deliver a fix for this issue in the upcoming PRTG versions. Solved with PRTG 23.4.90.1299 |
Note
Installer
Security |
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels: Stable 23.3.86.1520
Important: This PRTG stable version has the sequential build number 23.3.86. We published PRTG 23.3.85 only in the preview release channel due to a change in the release process. |
Lab
Multi-Platform Probe
Second Alpha release |
The Multi-Platform Probe enables you to deploy probes on platforms not supported by the Remote Probe, including various Linux distributions and ARM hardware.
We are happy to announce that this version brings you the most recent sensors in a streamlined installation process, using Linux distributions package managers from Debian, Ubuntu, and RHEL/CentOS.
This release adds the sensors HTTP v2, SNMP Disk Free v2, SNMP Custom v2, and SNMP Uptime v2. With this release the focus is on expanding Linux compatibility. We removed Windows compatibility and will continue to explore supporting Windows. For Windows, please continue to use the remote probe. Important: There have been significant changes in the installation, including changes to the file paths and the exposure of the service. If you already installed the Multi-Platform Probe in the past, then please remove your current installation before you install this release. For more information about the Multi-Platform Probe please see our Knowledge Base article: What is the Multi-Platform Probe and how can I use it? For detailed release notes please see our Knowledge Base article: What are the release notes for the Multi-Platform Probe? |
Lab
Sensors
Cisco Meraki |
We fixed an issue for the Cisco Meraki License Sensor and Cisco Meraki Network Health Sensor that went into an error status when PRTG was updated to version 23.2.84.1566 with the message The sensor could not get a response from the server. 0 (). schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). |
HTTP v2 |
|
SNMP Disk Free v2 |
You can try out the experimental SNMP Disk Free v2 sensor that was rewritten to work on the Multi-Platform Probe. The SNMP Disk Free sensor monitors the free disk space on a logical disk via the Simple Network Management Protocol (SNMP). This sensor type has the same basic settings as its predecessor and comes with the channels Free Space (bytes), Free Space (%) and Total Space (bytes). |
SNMP Uptime v2 |
We fixed an issue for the SNMP Uptime v2 sensor that reported the following error in certain cases: Could not resolve OID for 'iso.org.dod.internet.mgmt.mib-2.host.hrSystem.hrSystemUptime.0'. Either the required MIB file was not found or the name is invalid. The issue occurred only when you have added the sensor to a remote probe. |
Script v2 |
We fixed an issue for the Script v2 sensor where the path to the Script folder was broken. The issue was fixed for the path on Microsoft Windows operating systems. |
Lab
PRTG API v2
PRTG application server |
We fixed an issue that prevented logging in after an automatic logout, for example after a timeout, logout in a different tab or when the PRTG application server was disconnected. |
Lab
New UI
Device settings |
|
Web Interface |
|
Improved
Various
All parts of PRTG |
Various other minor fixes and improvements. |
Languages |
We updated the German and Spanish language files. |