PRTG Release Notes:
Preview Channel

The REST Custom v2 sensor has left its BETA status and is now fully supported with this PRTG release. We introduced the REST Custom v2 sensor as experimental sensor with PRTG version 21.2.68.1492. The REST Custom v2 sensor queries a JSON or XML REST API endpoint and maps the according result to sensor values.

During sensor creation, the REST Custom v2 sensor will now have a pre-filled value in the field Request URL for the section Specific Sensor Settings. The field displays https://%host/ to make it easier to identify the supported placeholder. The Request URL field was empty before in previous PRTG versions.

We improved the session based authentication method for REST API based sensors to accept more success response codes in the range of 200-299. The Credentials for REST API only accepted the HTTP response code 200 OK for session-based authentication in previous PRTG versions.

Various other minor fixes and improvements, updated user manual.

We updated the German, Spanish and Japanese language files.

We updated the language files in German, French, Portuguese, Russian, Chinese, Japanese and Dutch for certain selected sensor types.

We fixed an issue where a device and sensor with status paused by dependency could not be resumed. The issue occurred, for example, if a sensor was put into simulated error status and this sensor was not set as Master sensor for parent on the according device. In this case, you could not resume the sensor afterwards as it also went into the state paused by dependency. The sensor will now remain in the error status to be able to be resumed again.

We fixed an issue for reports that could not process umlauts correctly when you ran a report that included data files within the setting File Format and Delivery. For example, sensors with channel names that include umlauts were not displayed correctly in the xml file after generating the report with those sensors included. The issue occurred with PRTG version 25.1.104.1961.

We fixed an issue for SMTP notification delivery when you have set your Notification Delivery settings to Use direct delivery with the built-in email server (default). This issue occurred with updating to PRTG version 25.2.106.1114 where email notifications were sent several times instead of only once and was happening only for the PRTG internal SMTP relay server.

We fixed an issue for the REST Custom v2 sensor that ignored Custom HTTP Headers settings for the type Accept header. For example, if you defined an Accept header in the Custom HTTP Headers of the REST Custom v2 sensor, the header value would be overwritten in the previous PRTG version. The header is now transmitted correctly and you can see the value in the response of the Result of Sensor logfile.

We fixed an issue that occurred for certain SSH v2 sensors when you updated to PRTG version 25.2.106.1114. The issue happened only for v2 sensor types, that is why you have been able to observe it in these particular cases after the sensor migration for the SSH INodes Free v1 sensor. The sensor was not able to reconnect to the target device after a broken connection in some circumstances, which we improved now by changing the logic for reconnection.

With this PRTG version we discontinue the Python Script Advanced sensor. We announced the deprecation of this sensor type with PRTG version 25.1.104.1946. Running sensors of this type will stop working and report an error message about the disontinuation and the Python installation will be removed when you update to this PRTG version. To ensure further monitoring, please use the successor Script v2 sensor instead and make sure to adjust your custom scripts in advance.

For more information please see our Knowledge Base article: What do deprecation and discontinuation in the context of sensors mean?

Read here for differences and more information about the two sensors: Why should I use the Script v2 sensor?

We also provide information on how to migrate your scripts with this Knowledge Base article: How can I make my Python scripts work with the Script v2 sensor?

With this PRTG version we display an Activation Token on the License Information page. This token shows the identifier of your activated license. The Activation Token is displayed for Paessler PRTG Enterprise and Subscription licenses and valid also for offline license activations.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.3.110.1297

• sha256_exe AEFAD074EE78A69BD1A252670AD2289662CCCA8A789558B510727056173B347C
 
• sha256_zip 1AE61C2B3CCB9BE728BE84EBBCCC45D4A77FBE07C4A6EC7ACBCEA7A33FEE905B

You can try out the experimental REST JSON Data sensor (BETA) that we introcude with this PRTG version. This sensor queries an HTTP endpoint which returns JSON data in a well defined format. The format is the same as for the Script v2 sensor. Depending also on the JSON response, the sensor will create the channels Status and HTTP Status fix, amongst others. This sensor is also compatible with the Multi-Platform Probe.

• We improved the supported number of ciphers used in the TSL configuration for Default security (TLS 1.3, TLS 1.2) (recommended) that you can edit in the PRTG Web Server settings for Connection Security. The setting for Weakened security will still support older TLS versions and all current cipher suites used in the PRTG application server.
• We fixed an issue that occurred in previous PRTG Preview version 25.3.109.1353 where an HSTS( Strict-Transport-Security) header was not sent correctly by the application server. The PRTG application server will now no longer send an example HSTS header during installation. Please use appserver.config.yml for configuration of an own HSTS header.
• We fixed an issue for the PRTG application server that got stuck in certain cases during shutdown process and where it has hung up during the step unsubscribing from core notifications. As a result, also core and web server processes were not able to shutdown. A possible workaround was to manually stop the process.

We fixed an issue that occurred in certain cases when you have added a PRTG Subscription license and when displaying PRTG in the new UI was not possible. PRTG Subscription license types were enabled in the PRTG core, however, in certain cases the PRTG application server did not recognize them as valid. When you clicked on Open new UI button on the login page, PRTG would show An unknown error occurred in these cases.

The SSH Disk Free v2 sensor has left its BETA state with this PRTG version and is now fully supported. This sensor monitors the available disk space of a Linux/Unix system using Secure Shell (SSH). We released this sensor type as experimental (BETA) sensor with PRTG version 25.1.104.1946.

With this version we introduce the new SNMP Linux Block Device I/O sensor, which is the successor to the SNMP Linux Physical Disk sensor. This sensors monitors the input/output (I/O) on disks of a Linux/Unix system via SNMP.

To offer more details and information on a sensor, we added the following columns to the sensorlist.htm: Premeta (if the sensor requires a pre-meta scan), MinInterval and Momo (if it is a rewritten sensor type or not).

Various other minor fixes and improvements, updated user manual.

We fixed an issue that occurred on addsensor4.htm where large metascan entries during sensor creation could lead to an ajax timeout (PE:PE1113) in certain cases due to our update to Delphi 12.2 which also processes this page. This issue occurred, for example, if you tried to add SNMP Traffic sensors to a device with a large number of interfaces.

We fixed an issue where license activation for PRTG did not work in certain cases when the license activation file contained certain unicode/UTF characters that could not be decrypted. For example, when the license name included such a special character like Á or a long hyphen, you could observe the following error in the CoreActivationLog: No mapping for the Unicode character exists in the target multi-byte code page. The License status would also return Activation message processing has failed. in these cases.

• We fixed an issue for email notifications that were sent immediately after a sensor went from paused state into a resumed state and therefore got the status unknown first before collecting data. The issue occurred when you have set a State trigger to this sensor that applies when the sensor stays in an unknown status for a certain time period. PRTG will now recognize the transition from paused state (by user, by dependency, by schedule, by license and until) and will only trigger the notification when the configured trigger applies.
• You will now receive test notifications properly for MQTT messages within a notification template when you click on the button send test notification. In previous PRTG versions, PRTG would send the test notification with the prefix TEST, what therefore changed the topic you have subscribed to and thus you did not receive the according test notification. We have now added the wording TEST to the body of the notification, so that the topic will not change in this case.

We fixed an issue for Sensors With Alarms where objects were not displayed in the column Probe Group Devices. This issue was also fixed for the new UI and occurred only when you used Firefox as web browser.

We fixed an issue in the PRTG Tickets tab that occurred in the Select a Group, Device or Sensor from the list section when you clicked on Add Ticket. The elements from the device tree would be overlapping in the search field in previous PRTG versions.

We fixed an issue for the NetApp SnapMirror v2 sensor that reported the value 0 for the channel Lag in certain cases. The issue occured only for the NetApp SnapMirror v2 sensors. In course of this, we changed the default name of NetApp SnapMirror v2 sensors to show the destination path instead of the source path in the sensor name to ensure that the NetApp SnapMirror v2 sensor uses the same instance name as its predecessor NetApp SnapMirror v1.

The Ping v2 sensor will now keep the dependency when you create a device template with an according Ping v2 sensor that is set as Master sensor for parent for the device. Previously, when you run an Auto-discovery with specific device templates before, the Ping v2 sensor would be created afterwards, however, it was not set as Master sensor like in the original device.

We fixed an issue for SNMP sensors that reported a timeout -2003 error in certain cases when you updated to the previous PRTG version 25.2.106.1114. The issue occurred in cases when you had SNMP sensors configured with SNMP version v3.

We fixed an issue for the WMI Event Log sensor where the handling for overflow values did not work properly. For example, when the sensor received and displayed values and you restarted the PRTG probe service, you could observe a high peak in the values afterwards.

There currently is an issue that occurrs in certain rare cases after sensor migration of SSH sensors. The SSH Inodes Free v2 sensor, for example, ran into a timeout under certain circumstances when you updated to PRTG version 25.2.106.1114 in which we introduced the migration process for this sensor type. In the Result of Sensor log, that is created when you enable Store Result for this sensor, you could also observe a connection failure and timeout error. We are investigating the problem with the highest priority.

The configuration file of this version is not downwards compatible with previous PRTG versions.

With this PRTG version we deprecate the Common SaaS sensor. You cannot add this sensor anew when you update to this PRTG version, however, existing sensor types continue to run. This sensor will not have a successor v2 sensor. You will receive an according TO DO ticket from PRTG when you update to this version.

With this PRTG version we discontinue the SSH INodes Free v1 sensor. We announced the deprecation of the SSH INodes Free v1 sensor with PRTG version 25.2.106.1114 where also existing SSH INodes Free sensors were migrated to their successor v2 sensors. Please note that existing SSH INodes Free v1 sensors will stop working when you update to this PRTG versions, however, this does not apply for migrated SSH INodes Free sensors. It is not possible to create an SSH INodes Free v1 sensor anymore. For more information about sensor deprecation and discontinuation, please see our Knowledge Base article: What do deprecation and discontinuation in the context of a sensor mean?

With this PRTG version, the following sensor types are migrated to their successor v2 sensors: SSH Meminfo, SSH Load Average and SSH Remote Ping sensor. PRTG will sent an according TO DO ticket with all relevant information. We announced the deprecation of SSH Meminfo, SSH Load Average and SSH Remote Ping sensor with PRTG version 25.2.108.1358.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.3.109.1353

• sha256_exe 66F1A52A815141F3368E2579BF877F3DE78DF7B214BFE0137840C7600BEA085C
 
• sha256_zip 0DA9A568E3F7EC193F02AA4E3D726F8537020B91EFA9B79AB2C36C8D902D4BAB

We fixed an issue for REST Custom v2 sensors that went into a down or warning state with the message Creation of rest_custom_v2_sensor failed: The setting "authentication_section.authentication_group.login_path" was not available when you updated to PRTG version 25.2.108.1358. A possible workaround for this issue was to pause and resume the sensors to make them run again.

• We improved our internal naming conventions to be more consistent in the format. In course of this, we renamed the property _inheritanceSource to to _inheritancesource.
• We implemented a new endpoint /experimental/devices/templates that returns a list of available device templates upon GET request.
• You are now able to create a Ping sensor with the new endpoint /experimental/devices/{id}/sensor via POST request. The new endpoint is listed under the Sensors section in Swagger UI and gives you information about supported sensors: This endpoint does not yet support all sensor types. Currently only the following sensors are supported: * Ping. The body of the POST request contains the settings of a ping sensor as defined in the schema, for example, required fields and settings sections.
• We fixed an issue where a remote probe returned the status CONNECTED in the PRTG API v2 under yourserver:1615/api/v2/probes/ID although it was not approved yet. You will now receive the correct status for the remote probe PENDING_APPROVAL in this case.
• You can now send a GET request on the endpoints /experimental/objects or experimental/groups/{0} with the include parameter and value all. Previously, the inheritanceSource would return unknown_reference_object_type for the type field. You will now receive correctly REFERENCED_ROOT.

We updated our typography throughout the New UI to match the design system.

With this PRTG version, the SNMP CPU Usage v2 sensor left its BETA status and is now fully supported. This sensor type monitors the system load via the Simple Network Management Protocol (SNMP). We introduced this sensor type as experimental sensor with Preview version 25.2.107.1567.

With this PRTG version we introduce the new SNMP Linux Load Average v2 sensor that is the successor sensor for SNMP Linux Load Average. This sensor type was rewritten to be compatible with the Multi-Platform Probe. The SNMP Linux Load Average sensor monitors the system load average of a Linux/Unix system via the Simple Network Management Protocol (SNMP).

With this PRTG version we introduce the new SNMP Linux Meminfo v2 sensor that is the successor sensor for SNMP Linux Meminfo sensor. This sensor type was rewritten to be compatible with the Multi-Platform Probe.

Please note that the channel Available Memory (%) has been renamed to Free Phyiscal (%) and vice versa to better match its purpose, for example, Available Memory (%) should be the memory that is available for applications if the operating system was also reclaiming buffers/cache space, whereas Free Phyical (%) is the value which is not in use currently.

With this PRTG version, the SNMP Memory v2 sensor left its BETA status and is now fully supported. This sensor type monitors the memory usage of a system via the Simple Network Management Protocol (SNMP). We introduced this sensor type as experimental sensor with Preview version 25.2.107.1567.

We improved the behavior of PRTG when you have activated a PRTG Subscription or Paessler PRTG Enterprise Monitor license that has expired or is going to expire. You will now receive a growl message that displays when your PRTG Subscription license has expired or will expire. In case of license expiration, the License Status will show the activation data is no longer valid. Additionally, PRTG requests the value from validuntil in the activation data as well when you activated it with a Paessler PRTG Enterprise Monitor license first on an online system and later switch to an offline environment.

We replaced our old PRTG gauge logo with a new one that was updated in colour and style throughout PRTG. The logo has also changed in the new UI in various locations, for example, in the tab as the favicon display or as the Monitoring icon.

Various other minor fixes and improvements, updated user manual.

We fixed an issue for the HPE 3PAR Drive Enclosure sensor that reported the error message N/A could not be converted to integer in certain cases. The issue occurred when the drive controller reported an invalid temperature or no temperature at all.

We fixed an issue for the SNMP Disk Free v2 sensor that displayed the settings Type and Size for the monitored disks in the sensor Settings. Those columns should only be available during sensor creation. The SNMP Disk Free v2 sensor will now only display the columns Type and Size during sensor creation in the result columns.

The HPE ProLiant Memory Controller sensor now supports additional lookups for systems using Adaptive Double Device Data Correction (ADDDC). Previously, the sensor reported an error undefined lookup value (16) in such cases.

We currently face an issue with SMTP notification delivery when you have set your Notification Delivery settings to Use direct delivery with the built-in email server (default). This issue occurrs with updating to PRTG version 25.2.106.1114 where email notifications are sent several times instead of only once. Additionally, you will notice an error growl message: Your PRTG core server is currently unable to send email notifications. Check your configuration..

With this PRTG version we discontinue the SSH INodes Free sensor. We already announced the deprecation of this sensor type with PRTG version 25.2.106.1114. Running SSH INodes Free sensors on your PRTG installation will stop working when you update to this PRTG version. Migrated sensor types from SSH INodes Free to the successor v2 sensor version are not affected. You cannot add the SSH INodes Free sensor anymore when you update to this PRTG version. Please use the successor sensor SSH INodes Free v2 in this case which left its BETA status with PRTG version 25.1.104.1946.

With this PRTG version we announce the deprecation of the following sensor types: SSH Meminfo, SSH Load Average and SSH Remote Ping sensor. Existing sensor types will continue to run when you update to this PRTG version, however, you cannot add those sensors anymore as new. PRTG will also create an according To Do ticket. For more information on sensor deprecation, please see our Knowledge Base articles: What sensors are deprecated and what are their successors or alternatives? and What do deprecation and discontinuation in the context of sensors mean?

With this PRTG version we announce the sensor migration that will happen with PRTG 25.x.110 for the following sensor types: SSH Meminfo, SSH Load Average and SSH Remote Ping sensor. PRTG will sent an according TO DO ticket with all relevant information. The sensors will be migrated to their successor types SSH Meminfo v2, SSH Load Average v2 and SSH Remote Ping v2 sensor. Those successor sensors left their BETA status with this PRTG release.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.2.108.1279

• sha256_exe 2A9E7C6E6C33D19002B6842FA9D14C821723C80104E2575B428383A889864CDA
 
• sha256_zip 8FA170B12BE441FFA1B9F4AD2614F22F45A917950C5CD335FDBCECA144C956EE

• We implemented a new GET endpoint under api/v2/experimental/license in the Systems section of Swagger UI. This endpoint is only accessible if you are logged in as a PRTG administrator. You can receive information about the current PRTG license with the fields start_date, end_date, maintenance_end_date via GET request.
• We fixed an issue for GET endpoints in PRTG API v2 that returned a 200 OK response with a default set of fields when you, for example, had a typing error in the inheritance parameter. The API will now return a 400 Bad Request in this case with the message the request could not be processed.
• We added a new filter operator Ancestor ID for experimental list endpoints in PRTG API v2. The filter returns all objects that have the specified ID as an ancestor in their object hierarchy. Affected experimental endpoints are, for example, /experimental/channels and /experimental/sensors.

We introduce the new NATS Server Overview sensor with this PRTG release that monitors a NATS Server by connecting as a NATS Client in order to retrieve monitoring data. In case of Jetstream enabled NATS servers, the NATS Overview sensor will display the additional channels Jetstream Memory Used (%), Jetstream Storage Used (%), Jetstream Memory Reserved (%) and Jetstream Storage Reserved (%).

With this PRTG version, the SNMP UPS Status sensor left its BETA status and is now fully supported. This sensor type monitors the status of an uninterruptible power supply (UPS) via Simple Network Management Protocol (SNMP). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version, the SSH Load Average v2 sensor left its BETA status and is now fully supported. This sensor monitors the load average of a Linux/Unix system using Secure Shell (SSH). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version, the SSH Meminfo v2 sensor left its BETA status and is now fully supported. This sensor monitors the memory usage of a Linux/Unix system using Secure Shell (SSH). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version, the SSH Remote Ping v2 sensor left its BETA status and is now fully supported. This sensor remotely monitors the connectivity between a system running Linux/macOS and another device using Internet Control Message Protocol (ICMP) echo requests ("ping") and Secure Shell (SSH). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

We hardened PRTG in relation to CVE-2024-12833 by applying further sanitization to names objects.

We hardened PRTG against a possible XSS (Cross-Site Scripting) vulnerability. We considered this vulnerability as medium with a CVSS score of 6.5 and the vectors as follows: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.

We improved our handling for licenses to accept more formats when you have to use the Activation Data file in order to activate PRTG on an offline system. This file will be sent as .dat or .txt file and it is needed during the manual activation process.

We added support for flash memory classification in the SNMP Disk Free v2 sensor. Previously, disks reported as flash memory in the SNMP Disk Free v2 sensor were not listed during sensor creation.

Various other minor fixes and improvements, updated user manual.

We fixed an issue that occurred when your active directory server was not accessible and you wanted to add a user group to your PRTG. You would receive a Bad Request pop-up instead of a proper error message. PRTG will now display Active Directory Domain not found under Active Directory Group in the User Group Settings in these cases.

We fixed an issue for the endpoint getdesktoptoken.htm, that returned the message unauthorized when you had Single Sign-on configured and created an API key for PRTG Multiboard. The issue occurred when you were logged in with the relevant Single Sign-on user to whom the API key was assigned. PRTG will now return the according API token and only display the error message when the user has no assigned token.

We fixed an issue for returned errors on certain not accessible pages in PRTG that previously reported a not found error. PRTG will now return a HTTP 403 forbidden path error in those cases.

We fixed an issue where log messages with the text Wrong period in cache where wrongly logged as exceptions when you changed a graph period under Graph Settings in the User Interface setup.

We fixed an issue for notification templates where settings for Microsoft Teams and Slack notifications were cleared in certain cases. The issue occurred when you selected notification templates via multi-edit menu to add tags. After you have added tags for your notification templates and saved the changes, the set checkboxes under Custom Content in the Microsoft Teams and Slack notification templates were cleared.

PRTG will now list the actual System ID in the Core.log and in the PRTG Administration Tool to help solve license activation issues in case of incorrect returned System IDs. When you wanted to perform an offline activation of PRTG with a Paessler PRTG Enterprise license, for example, and the System ID was incorrect, you would get the error message The local system ID does not match the system ID returned by the activation service. This information is not available on PRTG remote probe systems.

We fixed an issue in the sFlow sensor to support 32bit numbers in the SourceID field. In previous PRTG versions, this packet format was not accepted by PRTG. This change allows you to monitor now specific devices, for example Neptune (NPT) routers.

We fixed an issue for SNMP v3 error messages that did not reflect that the error was due to a timeout. In case of an SNMP timeout, the error message will now display Timeout Error: The sensor failed to communicate with the target system.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.2.107.1567

• sha256_exe CFB289C48E9C0BF32A77D08F53BF47F702D9DFFFB37DB9BABB6B94F99CB9FD65
 
• sha256_zip 12C831CEA32868AD745446B682963AAD55D14D9FC585999EAE8F22DA64B374C4

With this PRTG version we deprecate the SFTP Secure File Transfer Protocol sensor. Existing sensors will continue to run but you will not be able to add this sensor anew when you update to this PRTG version. Currently there is no successor sensor planned for this sensor type. You will receive an according To Do ticket in PRTG about this sensor deprecation.

• We added the option to use session-based authentication with the REST Custom v2 (BETA) sensor in order to monitor devices that cannot be integrated into PRTG yet. You will find additional settings Session Based Authentication in the device settings under Credentials for REST API where you can define an Authentication Method.
  
  Important:: Please note that existing REST Custom v2 sensors will go into down or warning state with the error message Creation of rest_custom_v2_sensor failed: The setting "authentication_section.authentication_group.login_path" was not available when you update to this PRTG version. To solve this issue, please pause and resume the affected sensors to make them work again. We will provide a fix for this issue with the upcoming PRTG versions.
• We improved the logging for the REST Custom v2 sensor concerning passwords, placeholders and API keys that you can configure under Credentials for REST API in the device settings. For example, if you run an auto-discovery with device template for this sensor type, no sensitive data will be logged in the CoreAutoDiscovery logfile or the data is masked and therefore unreadable.

You can try out the experimental SSH Script v2 sensor (BETA) that we introduce with this PRTG version which connects to a Linux/Unix system via Secure Shell (SSH) and executes a script file that is located on the target system. This sensor type is the successor sensor of the SSH Script sensor. Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setupfirst in order to use this sensor.

You can try out the experimental SNMP CPU Usage sensor (BETA) which is the successor of the SNMP CPU Load sensor. This sensor type monitors the system load via the Simple Network Management Protocol (SNMP). Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setupfirst in order to use this sensor.

You can try out the experimental SNMP Memory v2 sensor (BETA) which is the successor of the former SNMP Memory sensor. This sensor type monitors the memory usage of a system via the Simple Network Management Protocol (SNMP). 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 implemented a new endpoint /experimental/devices/{id}/move in our PRTG APIv2 that allows you to relocate objects within the monitoring structure via POST request. In this new endpoint, you can enter the ID of the device that you want to move in an additional field. In the request body, you need to add the parent and the position where the device should be placed.
• We fixed an issue where the pagination headers for all experimental endpoints related to the wrong endpoint. In most of the cases, the headers pointed to endpoints that were not set as experimental. For example, /api/v2/experimental/devices related to /api/v2/devices instead. The pagination headers will now point to the same endpoint as the requested URL.
• We implemented a new GET endpoint /experimental/objects that allows you to receive probes, groups, devices, sensors and channels from a single endpoint.

We improved the performance of the PRTG application server used on larger installations and reduced memory consumption on all installations.

We added an extra card that displays the current version of PRTG that you have installed. The card shows the title Your version of PRTG. You can also see previous and additional versions with the link View version history / release notes of previous versions.

To make the Notification Triggers more visible, we moved the Notification Triggers section from access via button to an extra tab. You will also have the possibility to access the Notification Triggers via context menu.

We fixed an issue that occurred when you clicked the split view buttons on the Monitoring page from left to right or vice versa and when the developer tools were opened in the browser at the same time. You would receive an unknown error growl message in these cases and when you used Chrome as browser for PRTG.

We fixed an issue where the link back from the new UI to classic web interface resulted in an error page when you navigated to the History or Logs tab of the local probe. PRTG would return an error page There was a problem... when you clicked on Open Classic UI in the relevant tabs.

We fixed an issue that occurred with PRTG version 25.1.104.1946 where the application server service stopped running or did not run at all in rare cases, depending on the number of sensors and system resources, for example. As a result, you could not use the new PRTG user interface. You could also observe that the application server was consuming much more memory in these cases.

We fixed an issue for SNMP sensors that reported the error message SNMP error -2011 and Could not create SNMP session (-1)-2011 in certain cases when you updated to the latest PRTG version 25.1.104.1961. The issue occurred for sensors using SNMP v3 for monitoring as set version.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.2.106.1111

• sha256_exe 688099C15E3B3DAE6C1A17C495E99529AA19D13A0F97407D6A64F8A9003FD499
• sha256_zip B2C27298F9B6A924ECD031C451E8510FEF7CDB260D6AA2B2B5D26437308A92E1