PRTG Release Notes:
Stable Channel

• On Environment level we fixed an issue where using a PowerShell script with a remote agent led to access denied errors if your script included commands that require Administrator priviledges.
• We fixed an issue for Application where an error was displayed PRTG [SensorID] can not be found when you acknowledged an alert from PRTG.
• The PowerShell Integration stopped working after upgrading from the previous release of ITOps Board. We fixed this issue with this ITOps Board version 3.18.0.

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?.

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).

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).

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.

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.

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.

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.

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.

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.

Various other minor fixes and improvements, updated user manual.

We updated the German and Spanish language files.

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.

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.

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.

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.

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.

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.

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).

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.

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.

We fixed an issue in the Oracle Tablespace sensor scanning time so that the sensor executes the queries faster without running into timeouts.

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.

• You are now able to navigate through the pages when you have many entries in a map or when you use data tables in a map. In previous PRTG versions, the pagination in maps did not work.
• We fixed an issue that occurred when you had only one map available in PRTG, for example, after PRTG installation if you have deleted other maps except for one. In these cases, the clone button for the existing map was missing in the menu.

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.

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 happens for the HPE Integrated Lights-Out (iLO 5) firmware version as of 3.x due to changes in the OIDs.

Please note that we are not able to deliver a fix for this issue since it is not located within the PRTG software, but within HPE Integrated Lights-Out. To avoid that you run into this issue, please downgrade to an older iLO version (before iLO 3.x).

We currently face an issue that occurs for the Modbus TCP Custom sensor, Modbus RTU Custom sensor, SNMP Custom v2 sensor (BETA), MQTT Subscribe Custom sensor, REST Custom v2 sensor (BETA), and OPC UA Custom sensor that will report an error with the message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. (code: PE270) in certain cases and when you update to this PRTG version. The sensors will work again, if you follow the error message instructions, however they will go into the same error when you change and save settings. In this case, please perform a restart of the PRTG core server. We will deliver a fix for this issue in the upcoming PRTG versions.

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

• sha256_exe 8C175D97D0AD6C4C0664336C68DAD4BF8D873720B8215BD3B68CA0DF3CA48D6D
• sha256_zip B0D22BF05641AA138E7E45FD1E915C10E94D3D52ABCEC093460EC92466265421

• We improved the sensor message that is displayed for the REST Custom v2 sensor to have a better readability. There was previously no separation with commas if, for example, more channels were displayed in the message as information.
• You can now define a scale factor as integer or floating-point number for the REST Custom v2 sensor in the sensor settings during sensor creation. The setting is available in the Channel Settings and can be defined in the Scale Factor setting of a channel when the Channel Unit can be 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.

• The SNMP Custom v2 sensor now supports up to 10 channels in the SNMP Custom Specific settings to match the former SNMP Custom and SNMP Custom Advanced sensors. Like the previous SNMP Custom Advanced sensor, the SNMP Custom v2 sensor now also supports Lookups as Channel Unit. You will see a drop down list with available lookups when you create this sensor type and select Lookups as channel unit. This setting can only be changed after sensor creation via Edit Channel button.
• You can now configure a change notification for the SNMP Custom v2 sensor. In the SNMP Custom Specific settings there is a new option to Trigger change notification for the setting If Value Changes. Additionally, select Add Change Trigger in the Notification Triggers tab of the sensor to define a notification method. PRTG will then notify you when the value of or service monitored by this sensor changes.
  
  Important:Please note that you need to create this sensor type new when you update to this PRTG version, as existing SNMP Custom v2 sensors will stop working upon updating. During sensor creation, you will see the Enable Channel option for all other additional channels.

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.

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.

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.

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.

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.

• You can now check the health values of the application server via the API call /api/health.json. The result will now show all the information about the application server, for example APIRequests, Health, MemoryUsed etc. It will also show a State field that indicates if the application server is running or down. Please note that health data is only updated every 10 minutes in the PRTG core.
• You can now receive and edit the Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems, Credentials for Cisco Meraki and Credentials for Microsoft 365 settings under device Settings with an according GET and PATCH request on the devices/{id} endpoint.
• You can now send GET requests to the following experimental endpoint /experimental/objects/types to receive a list of all the possible objects that can be created for a given parent device.
• We updated our PRTG API v2 Reference documentation in the OpenAPI Specification with a table for Experimental endpoints. You will find this table under Overview: Maturity of endpoints.
• We updated the endpoint /api/v2/settings/public to receive and display information about Single Sign-on login in PRTG. When you execute a GET request on the mentioned enpoint, you will see additional information if Single Sign-on in PRTG in used (has_sso: true) or not. The information also displays the given provider, for example name: okta.
• We fixed an issue for the endpoint GET /users/{id}/api-keys that retured an integer value for the API key access level instead of a string. For example, access level was returned as access-level: 1 instead of read, acknowledge, write, full.
• You are now able to receive commentgroup settings via the devices endpoint /schemas/{kind} with kind=device via GET request. The settings are not included by default, only when you use the include parameter in the request URL. You can also edit the commentgroup settings with a PATCH request on /devices{id}.
• We fixed an issue for the endpoint /schemas/{kind} when kind=device that returned a false response body when you executed a GET request with the purpose create and without any given value in the parent field. The message returned would be The resource could not be found in this endpoint. Check the ID of the object. Cause: the parent ID is mandatory for schema device and purpose create. The message that will be displayed now in such cases is The resource could not be found in this endpoint. Check the ID of the object.

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.

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.

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.

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.

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?.

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?

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.

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.

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.

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.

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.

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.

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.

Various other minor fixes and improvements, updated user manual.

We updated the German and Spanish language files.

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?

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.

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.

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.

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.

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.

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.

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.

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:///api/table.json?id= with parameters like Serial Number, the value was returned as NULL. The issue happened because the PRTG App for Desktop interpreted the returned JSON table as a numeric value instead of a string what resulted in an empty system information field.

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

• sha256_exe B25CCF26E64890D53F26B5FF2F438864D07F6C4C5CA612053F6E709074488AD8
• sha256_zip BC6A5EEE27CEA8D9B30EA903A3E7FC2834F393D77C9FAAA6B86E0FFEB8E8AAEA

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.

You can try out the experimental Data Hub Process (BETA) sensor that monitors the health status of your PRTG Data Hub instance. This sensor comes with the channels CPU Usage, Memory Consumption and Process Uptime. Please note that you need to configure credentials and port for the new setting Credentials for PRTG Data Hub on the relevant device first in order to make this sensor work.

You can try out the experimental Data Hub Traffic (BETA) sensor that monitors data flow traffic through your PRTG Data Hub instance. This sensor comes with the channels Messages In, Traffic In, Last Message In, Messages Out, Traffic Out, Messages Accepted by Rules, Messages Rejected by Rules, Messages Dropped by Rules. Please note that you need to configure credentials and port for the new setting Credentials for PRTG Data Hub on the relevant device first in order to make this sensor work.

You can try out the experimental Data Hub Rule sensor that monitors your data flow traffic by rules. During sensor creation, you can select the Rule to be monitored in the Sensor Specific Settings, for example forward-traps-to-prtg. This sensor comes with the channels Messages In, Traffic In, Last Message In, Messages Out, Traffic Out, Messages Accepted, Messages Rejected, Messages Dropped. Please note that you need to configure credentials and port for the new setting Credentials for PRTG Data Hub on the relevant device first in order to make this sensor work. Please note that this sensor type cannot be selected in the Exclude Sensors list when you want to create a device template.

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.

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.

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.

• You can now edit the Scanning Interval for a sensor in the PRTG APIv2 via GET or PATCH request in the /devices/{id} endpoint.
• We fixed an issue where the device settings were not available when you executed a GET request on the schema endpoint /schemas/kind when kind=device with the purpose create under parent object. The sections which are marked as inheritable should be displayed, what was not the case in previous PRTG versions. The following device settings are now available when you execute the mentioned API call: cloudcredentials, dbcredentials, paessler-http-credentials_section, paessler-microsoftazure-azure_credentials_section, paessler-rest-authentication_section, scriptplaceholdergroup, vmwareconnection and windowsconnection.
• We added the settings section Schedules, Dependencies, and Maintenance Window that is now available in the device schema API. You can edit and view the according settings via the GET and PATCH endpoints over /devices/. Date and time indication will be displayed in UTC format, for example 2024-07-04T19:58:00Z. With GET device/id you are also able to fetch the inherited settings via scheduledependency_inheritance: true.
• We fixed an issue for the GET /experimental/devices endpoint that did not return the value for parenttags of a group if the group or devices within that group were paused.
• We fixed an issue for the GET /probes/id endpoint that did not return a value for the status_info field when you have paused the local probe with message before via POST request on /probes/{probeId}/pause.
• You are now able to receive and edit information for and on the /devices/{id} endpoint via GET or PATCH request. For example, lookups for usergroupid are shown under GET endpoint /api/v2/setting-lookups/usergroupid. For a PATCH request, use the /devices/{id} endpoint. Please note that the PATCH request must contain the same number of elements in the array and the same usergroupids as the GET request to get proper results.
• We fixed an issue that occurred when you executed a GET request on the endpoint /experimental/channels for a certain sensor ID where the sensor did not have an active Scanning Interval, for example inactive sensors. Instead of a 200 (OK) response you would get a runtime error: invalid memory address or nil pointer dereference in the Server.log.

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

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)://:Port/api/v2/oas/.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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.

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.

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.

• This release introduces the ability to configure notifications based on saved searches. For example, you can use the saved search for "Critical Computers" and be notified whenever the search finds results. To use this feature, each search must be pinned to its own board. You can then configure a notification that is triggered whenever the search criteria is met.
• A new navigation menu improves the usability of the interface by organizing data according to how you use it. The following menus are available: Data Analysis, Explore, Settings, Help.
• If you deploy a remote agent, you must upgrade it for this release. To obtain the latest remote agent, you need to click the Download Agent button in the Agents tab and click Save afterwards to download the installer zip file. This procedure must be performed by an administrator.

• This release introduces the device template capability for the multi-platform probe for certain sensors types. The device template file can only contain the sensors supported by the multi-platform probe and are device template capable, with some exceptions.
• You can now use the feature Add Auto-Discovery Group on the multi-platform probe with the option Auto-Discovery with specific device templates or use the Run Auto-Discovery with Template on a certain device. This feature is only available for sensors supported by the multi-platform probe and for those that are device template capable, with a few exceptions.
• You can now download and install the RPM packages directly from the package repository with your package manager. You can find the Paessler Linux package repository at Paessler Linux package repository.
• With this release the multi-platform probe supports the experimental Cisco WLC Access Point Overview sensor.

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?.

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?

With this PRTG version we provide various fixes to improve security and stability.

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.

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.

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.

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.

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.

Various other minor fixes and improvements, updated user manual.

We updated the German, Spanish, French, Portuguese, Russian, Japanese, Chinese and Dutch language files.

We updated the German and Spanish language files for certain selected sensor types

• We updated the versions supported for Veeam sensors (Veeam Backup Job Status sensor, Veeam Backup Job Status Advanced sensor) regarding the Veeam Backup Enterprise Manager.
• We updated the information for Possible Values in the section Sorting and Advanced Filtering in our user manual.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

• sha256_exe 36C0FB110EE870F82CE83CE29E8D88F4AA2936FFBED1B8B35183CDA04771BBBD
• sha256_zip 7A6F81ACD884CAA0AA94A24E2B7804C3970673884E67264982F9E0741D74334B

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).

• You are now able to filter for certain objects in the list endpoints via PRTG API v2. You can filter for ID, Kind, Status, Host, Hostv6, Tags, Interval and Type. Filtering works on the endpoint experimental/devices via GET request.
• The endpoint for experimental/probes/{id}/overview now includes the field probe_status which will show you the status of your local probes and remote probes. The status will be displayed in the response when you execute a GET request on the mentioned endpoint. The following probe states are possible: Connected, Disconnected, Hello, Banned, Initializing, Waiting, Updating, Manual, Restart.
• We added a new endpoint /setting-lookups/{lookup-name} in the Objects section where you can get all possible values for a setting lookup. The name of the lookup and the item ID are valid parameters that you can enter when you execute a GET request for this relevant endpoint.
• We fixed an issue that occurred when you sent an invalid body via request to the device path endpoint for any device. The returned error response code would be 400 with the message BAD GATEWAY in those cases. The response will now be BAD REQUEST for invalid values.
• You are now able to filter for certain objects via GET request in the following endpoints: experimental/sensors, experimental/groups, experimental/probes and experimental/devices. You can filter for ID, Kind, Status, Host, Hostv6, Tags, Interval and Type. Please note that the filter for status = connected in the experimental/probes endpoint currently throws an error with the message The provided filter is invalid. Cause: connected is not a valid enumeration value for the field status.
• /channels/{id} and /experimental/channels are new endpoints for retrieving all channel measurements and settings. In the future we will also provide editing functionality for channels based on these endpoints.
  
  Please note that a certain rise in memory is noticeable and expected due to this new endpoint but should not exceed more than 70kb per channel.

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.

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.

• We fixed an issue where the links on a sensor Settings page directed to the classic PRTG web interface instead of the new UI.
• 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 .

PRTG version 24.2.96.1375 is a maintenance release with several code improvements necessary for upcoming PRTG versions.

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

• sha256_exe 8C2124ADD6BE4CCD2A83E5B85CA2F34C90EAB26436D7D858DD402086FFBF44F0
• sha256_zip 9C3FAB3B68726D51EEB6629DD6EA5532D1AB7C866B2E3EF532C6B0127DEDD448

Stable 24.2.96.1346

• sha256_exe 1B4C10344DC4F7B3D63B6726842A088B448E70E951AF83D5323EF6D16C80B5DC
• sha256_zip 7473A44270D8D4A0595E9C182DEB4DFEC0E18B3BE15D7FD01719F23178A97E63

With this PRTG version we provide various fixes to improve security and stability.

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.

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.

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.

Various other minor fixes and improvements, updated user manual.

We updated the German, Spanish, French, Dutch, Portuguese, Japanese, Chinese and Russian language files.

We updated the German and Spanish language files for certain selected sensor types.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

• sha256_exe D0DA0003C068800D38C5F65DD5EFD57D91B96FE83D12D67BC675C69BF9B1AF29
• sha256_zip CE60F73C75A37CFD44471330B05DA28AB712FFD06452670584234CCC6A9CB82A

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.

We implemented the sections for Windows Compatibility Options, SNMP Compatibility Options and Proxy Settings in the device settings in the new UI.

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.

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.

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.

• You can now send GET requests to the following endpoints api/v2/groups/{id}, api/v2/sensors/{id} and api/v2/probes/{id} to receive relevant information about these objects.
• You are now able to clone objects (group, device, sensor) via PRTG APIv2 POST request and the endpoint object name/id/clone. The settings of the cloned object will have the same settings as the original object. A cloned sensor, for example, has the default name 'Clone of '. After you have cloned an object it is paused by default. Here the same clone rules apply as for the classic PRTG UI, that means you cannot clone fixed objects such as the root group, a probe device, or PRTG system-internal sensors. When you have entered a wrong object ID for cloning, the response will return a 404 not found error message.

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.