Release notes
for the "stable" release channel

Syslog Receiver sensor

Sensor gauges

Maps

Security

• sha256_exe BB4D22183C3DE6C4FC15E5984765E05DA4273733A9C76DC2008B31619F263BFE
• sha256_zip AB84E8DADA0373F6299D101F9953BB93EC75E98E50997B82E5E924FE272763FA

SNMP Custom String v2

SNMP Printer v2

SNMP RMON v2 sensor

Reports

Webserver

• We performed sanitization on HTTP error responses to prevent information disclosure.
• We performed sanitization on the URL Path in HTTP error responses to prevent information disclosure.
• We enforced input sanitization on object name parameters to defend against possible Cross-Site Scripting.
• We hardened PRTG against possible cross-site scripting attacks through certain parameters on the public login page.

Microsoft 365 Mailbox sensor

Activated PRTG Database (BETA)

Custom sensors

System Status

Geo map

NATS setup

PRTG Core service

NetApp SnapMirror v2

DNS v2 sensor

Ping v2 sensor

• We fixed an issue where having multiple ping sensors targeting the same host caused all raw ICMP sockets to receive all answers, resulting in an error message Received packet had unexpected identifier or sequence number in the Result of Sensor logfile. The sensor also wrongly reported packet loss in case of packets received with a mismatching type or identifier.
• You are now able to use a new setting for the Ping v2 sensor Error Status Handling, to define an evaluation method to display negative results. The sensor immediately shows the Down status based on channel lookups for the setting Enter the down status immediately (default).

Auto-discovery

API Keys

PRTG Database migration (BETA)

PRTG installer

Security

• sha256_exe 62E2681F26E81436A24C2EB0BE26CADEADFD0D529A400FB7DACE806680CCFD83
• sha256_zip A1CE8074AD75B4E06E9567A7EDFC27FDE64D5F83364AB21287FE9AEDA7324236

PRTG Database (BETA)

PRTG Database (BETA)

• We fixed an issue where certificates created by NATS Manager were never deleted from the Windows Certificate Store. The certificates NATS Server for Paessler PRTG and Paessler NATS Manager are now properly removed when PRTG including NATS is fully uninstalled, when an initial installation is canceled or rolled back, or when an update is rolled back to a previous PRTG version without PRTG Database.
• With this PRTG version, the PostgreSQL Database installer will no longer install the pgAdmin tool if you have already installed a PRTG version with the PRTG Database. Your installation will proceed as expected, but the pgAdmin tool will no longer be updated in this case.
• We fixed an issue where setting up the PostgreSQL database with a custom password failed if the password contained certain special characters. The installer now validates both the username and password against the allowed character sets in real time. The PostgreSQL username is restricted to alphanumeric characters only, while the password additionally allows the following special characters: _ ! . + - = ~. An error message is displayed and the user cannot proceed until invalid characters are removed. The setup screen now also clearly displays these constraints to guide users during configuration.
• We fixed an issue when the installation was cancelled in certain cases either manually or due to an error. The PRTG installer will now inform you about the process and the next steps with the message: Roll back of all changes done within this installation finished. Please reboot your system.
• We fixed an issue that occurred if you canceled the installation or rolled back to the previous PRTG version. In that case, the PRTG Administration Tool could no longer be started because the .exe file was no longer present.
• We fixed an issue that occurred in certain cases if you had PRTG installed with a Multi-Platform Probe connected and updated to a PRTG version that includes the PRTG Database. After updating, the NATS service was stopped and could not be started again. Additionally, the NATS server.log file was not created. In the Windows Event Logs you could find the following error: The service did not respond to the start or control request in a timely fashion.
• We have updated our PostgreSQL database from version 18.1 to 18.3.

Data migration

SIMATIC S7-300/400 CPU Restart Overview sensor

SIMATIC S7-300/400 CPU Status sensor, SIMATIC S7-300/400 CPU Restart Overview sensor

• We fixed an issue for the SIMATIC S7-300/400 CPU Status (BETA) and SIMATIC S7-300/400 CPU Restart Overview (BETA) sensor that did not display any data results in certain cases. The issue happened because the sensor did not finish the scan for some monitored PLCs.
• We fixed an issue for the SIMATIC S7-300/400 CPU Status (BETA) and SIMATIC S7-300/400 CPU Restart Overview (BETA) sensor that reported an error message The buffer supplied is too low to accomplish the operation in certain cases. The issue happened for S7-410-5H controllers when the sensor failed to read the diagnostic buffer.

SNMP Custom String v2 sensor

• We added a new setting Numeric Extraction to the Specific Sensor Settings of the SNMP Custom String v2 (BETA) sensor, which allows you to locate numbers inside a string from the SNMP device by using regular expressions. The sensor then displays the result in an additional channel: Extracted Number.
• We have improved the SNMP Custom String v2 sensor by changing the primary channel from Response Time to String Found. The Response Time channel did not display a meaningful error message if you used too many wildcards in the Search String setting. The primary channel String Found will display The search string contains too many wildcards in this case.


Important: To get the new primary channel String Found, you need to create this sensor again.

SNMP Traffic v2

API

• With this PRTG version we introduce parameter support for the metascan endpoint /experimental/{id}/metascan to create a NetApp System Health sensor via POST request on /experimental/devices/{id}/sensor. The metascan endpoint now accepts a request body with parameters as defined in the schema, allowing the NetApp System Health sensor metascan to be triggered successfully via URL parameters.
• We fixed an issue where consecutive calls to /experimental/schemas/{deviceID} returned inconsistent results for the same sensor. Affected sensors, particularly Dell EMC sensors such as paessler.dellemc.storage_filesystem_v2_sensor and paessler.dellemc.storage_capacity_v2_sensor, could alternately appear as creatable with no hints in one call and non-creatable with a MissingCredentials hint in the next. Consecutive calls to the schema endpoint now consistently return the same results.
• We fixed an issue where the PRTG application server responded with a panic.log file including the message panic: runtime error: invalid memory address or nil pointer dereference. The issue occurred when you executed a GET request on endpoint /experimental/schemas/{parent}/post with parent=40 (local probe) and kind=snmpcustomtable.
• We fixed an issue where the api/v2/settings/public endpoint did not return the correct language upon GET request. Previously, only en-US was returned for the language field. The endpoint will now correctly display the language you have configured in the PRTG webinterface settings.
• We have improved the endpoint /experimental/objects/{id}/clone with better documentation in Swagger UI, for example. The deprecated endpoint clone endpoints experimental/devices/{id}/clone was removed.
• We fixed an issue in PRTG API v2 for the endpoint api/v2/channels/{id} where for some channel items the name field was returned with an empty string.
• We fixed an issue for the /experimental/schemas/{id}/get endpoint that did not handle the readonly property correctly for Read Only users that have the right to acknowledge alarms.
• We renamed the PATCH endpoint to /experimental/sensors/{id} to be consistent with other resource endpoints that use the object plural.
• We have updated the endpoints POST /experimental/devices/{id}/sensor and POST /experimental/devices/{id}/metascan in PRTG API v2 to now support all sensor kinds. Previously, only a selected set of fully tested sensors were allowed. With the sensor creation flow working reliably, the whitelist restriction has been removed, making sensor creation available for all supported sensor kinds without limitations.

Channel units

Device tree

• We fixed an issue for the Device Tree in the New UI that displayed an additional Add Sensor button when you entered a search string in the search field.
• You can now move devices into different groups and reorder objects within a parent in the new UI. Active monitoring objects are now highlighted across the full row width for better visibility, and a context menu has been added to streamline navigation and management actions.

Monitoring

Objects

User session

PRTG Home page

• We improved the Home page in wording and display of content to match the user type that is logged in to PRTG.
• You are now able to use our new AI Chatbot Max on the Welcome Page in PRTG New UI. Clicking the Start Chatting button opens a slide-in panel on the right side of the page, where you can interact with the chatbot. MAX AI has in-depth knowledge of PRTG and is ready to assist you with questions and troubleshooting directly from the Welcome Page.

All parts of PRTG

Languages

Authentication

SNMP Windows Service v2

SNMP v3

Kerberos authentication for WMI sensors

License Status

PRTG Administration Tool

Device settings

Folder sensor

Ping v2

Microsoft 365 Mailbox sensor

SNMP Disk Free v2

SSH Disk Free v2

Tree Version Update

PRTG intermediate version 26.1.116.1532

Auto-update

PRTG API v2

PRTG installer

Signature

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

Security

• sha256_exe A8C6E30D0415DC32D67D50887588AED3198F31BCD8258BBB448F7DCB118E2444
• sha256_zip F34DDD69CE8F0CA9FC7149E123092AF611E774FB050B604E9B5DF646190C37CD

26.1.118.1381

PRTG Database (BETA)

• You cannot activate PRTG Database on a PRTG installation that runs a Cluster setup in this first iteration.
• Please note that for the Beta release, you cannot install PRTG core server on a system that already has a database (e.g. PostgreSQL) installed. The installation will fail with an error message in the installer informing you that PRTG requires its own database.
• Please note that you have to start the PRTG services manually in certain cases when you run a Cluster setup with PRTG and update to PRTG version 26.x.117. When you have set your PRTG to Automatically download and install in the Auto-Update settings, the installation will run successfully. However, the services remain stopped and must be started manually.

Database Health (Autonomous)

Proxmox VE Cluster Health sensor

Proxmox VE Node Performance sensor

SIMATIC S7-300/400 CPU Status sensor

SIMATIC S7-300/400 LED Status sensor

SNMP Custom String v2 sensor

SSL/TLS Security Check sensor

API

• We have expanded our endpoint /experimental/devices/[id}sensor in PRTG API v2 with new supported sensors, which are also listed in the endpoint description and which can be created via POST request. For the SNMP Traffic v2 and Windows Network Card sensor you have to perform a Metascan before on the relevant endpoint /experimental/devices/ID/metascan via POST request in order to create the sensor.
• We have improved our endpoints regarding usergroups that only allow certain sensors to be created and when you are logged in to Swagger with a user assigned to such a group. The endpoint /experimental/schemas/{parent} now only returns the selected sensor types from the according group upon GET request. POST request on /experimental/devices/{id}/metascan and /experimental/devices/{id}/sensor with device ID and kind=different sensors will return only the selected sensors in the response.
• We fixed an issue for the endpoint /experimental/devices/{id}/autodiscovery when you executed a POST request for autodiscovery with device ID and a body with wrong or not existing discovery-template. In this case, only a generic error message was returned. You will now receive a correct error message: one or more templates could not be found.
• We have added a new endpoint /objects/{id}/move where you can execute POST requests in order to move the position of any monitoring object within it's siblings or to a new parent. In the Description section you can enter the ID of the object that you want to move. Additionally, you can combine parameters, for example with the position_preset parameter to move objects to a new parent.
• You are now able to create an SSH Disk Free v2 sensor via POST request on the endpoint /experimental/devices/{id}/sensor with the kind ID paessler.ssh.disk_free_sensor. We have also updated the description for supported sensor types for this endpoint in the Open API Specification.
• We have expanded the experimental/schemas endpoint so that the response shows whether a sensor can be created or not due to missing credentials. For example, if you execute a GET request on /experimental/schemas/{parent} with according parent ID and limit, you will see for the according credential group either creatable:true or creatable:false for a sensor. In case of creatable:false the flag CredentialsMissing is returned in the response as well.

Layout

Monitoring

Sensor channels

All parts of PRTG

Languages

Sensors languages

Single Sign-on

Security

• sha256_exe 5A19643A15A9704C7FDD82DD9B4D9AD8BD4D64E19C1CCB09DCBE44ADEE25AAAD
• sha256_zip 34EAC4DF0428B30C92000AAEA0E483C6ECDE500EB43AF6F313AA26200B5E8CBF

26.2.116.1542

Webserver

API tokens

Single Sign-on

User account settings

Logging

• We fixed an issue where in certain cases activating an incorrect license key for PRTG Subscription licenses led to access violations in the Core.log file.
• We fixed an issue in the Core.log and CoreActivationLog which created incorrect log entries when you changed the license key in your PRTG. This issue only occurred if you had previously changed the log level to DEBUG. After you have changed the license key, you could see a warning message in the Core.log processing of activation data failed. Furthermore, the license activation success message, for example Startup: Error during activation of license PPEM: Activation successful was logged as error.

License activation

• We fixed an issue where the License Name was cut off in certain cases on the License Status page when you did use special characters, in this case quotation marks ", in the license name.
• We fixed an issue for licenses that could happen when you clicked on the Down sensors on the home page to open the sensors list and tried to delete them via multi edit selection. In this case, you would receive an error object not found for those sensors afterwards. Additionally, you could find errors logged in the Core.log as exceptions. The issue also occurred in PRTG when you have activated it on an offline system.

Cloud HTTP v2

DNS v2 sensor

HPE 3PAR Drive Enclosure

HTTP sensors

File System

OPC UA settings

Sensor channels

SNMP Windows Service sensor

Veem Backup Job Status & Veeam Backup Job Status Advanced

Maps

Single Sign-on

Security

• sha256_exe 79DC26307D0888581E570C74A55532E1EF0713C7D126DD38EBEE516C379473A4
• sha256_zip D7CFAC0F043330460CA7102EF6D9A830817387DE486AFA27BDF96A2CA1166192

Proxmox VE Virtual Machine Status sensor

Proxmox VE Container Status sensor

SNMP Custom String v2

SNMP Custom v2

SSL/TLS Certificate Sensor

SIMATIC S7-300/400 Restart Overview

SIMATIC S7-300/400 CPU Status

API

• We fixed an issue for the endpoints api/v2/experimental/devices and api/v2/devices/{id} where the GET and PATCH results for Access Rights were not updated in PRTG API v2. The Access Rights settings are now updated immediately in PRTG APIv2 after you have created a new user group, for example. Previously, you had to execute another GET or PATCH request to receive the updated results.
• You will now receive a list of creatable sensor types via endpoint /experimental/schemas/{parent} when you have created a group or device before. You will see if a sensor is creatable with the flag creatable=true and the result will contain a list of preconditions that have to be met in order to create the sensor.
• We fixed an issue for the endpoint api/v2/experimental/schemas that did not check if it was valid to add a node to a certain partent ID, in this case the probe ID. For example, when you executed a POST request on this endpoint with parentid=1 and kind=ping, the schema would be returned without an error. Now you will receive an according error code in API v2 in this case asking you to check the ID of the object and that the schema ping does not match parent ID 1.
• We improved the display of settings in the response code so that they correspond to user rights. For example, device settings that are returned via endpoint api/v2/devices and which have a notforreadonlyuser flag are now masked with asterics. This change also affects the api/v2/experimental/schemas endpoint.
• We fixed an issue where an internal (500) server error occurred instead of a proper error message when you sent an empty group name with the request body to the endpoint api/v2/experimental/groups/{id}/device or api/v2/experimental/probes/{id}/device via POST request.

Dialogues

Device settings

Mobile view

• We fixed an issue for the Device Settings page on mobile view where long texts where not displayed within the frame of the page but going out of bounds.
• We improved the display of pages where no data was found in the new UI for mobile view. For example, if you previously wanted to open a device or sensor list for a group without objects, the page would simply display a blank page with no content. You will now receive a proper error page with a message in this case that displays no matching results.

Object lists

Sensor status

All parts of PRTG

Languages

Sensor languages

Webserver

• We fixed a reflected Cross-Site Scripting (XSS) vulnerability in the tag parameter. An attacker could inject and execute arbitrary JavaScript code in the user's browser context. To perform a reflective XSS attack, an attacker has to induce the victim to issue a malicious request, for example, by providing a prepared link. This vulnerability can be tracked under CVE-2025-67833, with severity 8.1 - High (CVSS v3.1).
• We fixed a reflected Cross-Site Scripting (XSS) vulnerability in the filter parameter. An attacker could inject and execute arbitrary JavaScript code in the user's browser context. To perform a reflective XSS attack, an attacker has to induce the victim to issue a malicious request, for example, by providing a prepared link. This vulnerability can be tracked under CVE-2025-67834, with severity 8.1 - High (CVSS v.3.1).

Application

VMware Datastore (SOAP) sensor

Windows Update Status (PowerShell) sensor

PRTG intermediate version 25.4.112.1189

Auto-update

Auto-Update/Signature

Signature

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

Veeam Backup Job Status & Veeam Backup Job Status Advanced

Security

• sha256_exe 7AE43FB27631364502DB8C5E635329E15B6542F9FE930B4A955C8A5B2CFA9BBF
• sha256_zip C339DAF3FA37BCDD601CE8F5B620A926C7B2D3F313F810690F2DFC03DAAFFE59

API

• You are now able to create the following sensor types with the new endpoint /experimental/devices/{id}/sensor via POST request: EXE/Script sensor. The new endpoint is listed under the Sensors section in Swagger UI and gives you information about supported sensors.
• The schemas endpoint /api/v2/schemas now returns the lookupkey value correctly, for example lookupkey = intervalid or usergroupid.
• We removed the field kind_variant from all endpoints. This field returned, for example, the value device when you executed a GET request on the api/v2/devices endpoint.
• We changed the Schemas endpoint experimental/schemas/{kind} in PRTG API v2 so that it is replaced with the following endpoints: experimental/schemas/{parent}/post (for creating objects), experimental/schemas/{id}/patch (for updating objects) and experimental/schemas/{id}/get (for reading objects). You can use the include parameter as a filter for these endpoints in your requests.
• The Web.log will now create log entries when you execute an API request in PRTG API v2 Swagger UI with an invalid or deleted API key. Requests via API v2 with invalid API keys were not logged before.

Mobile view

All parts of PRTG

Languages

Sensors languages

SNMP Linux Disk Free v2

HTTP Client

Sensors

Channel limits

Activation Token

License activation

Paessler PRTG Hosted Monitor

Webserver

REST Custom v2

Windows Updates Status (PowerShell) sensor

Security

• sha256_exe A1C764BAA3D02040E35B5E938AE85B31DC25EDB277FF635A3BBD29E1724E0931
 
• sha256_zip 35FAA3B7B3F773C2D35150A7C59DB79BD05D140AD08E51828572714A429EDE2D

API

• We fixed an issue where it was possible to move the ProbeDevice via endpoint /experimental/devices/{id}/move to another Group/Device/Probe. The issue occurred also for the actions clone and delete via APIv2. The ProbeDevice is fixed in PRTG and cannot be deleted, cloned or moved anymore via APIv2.
• The IP address is now logged in the core logfiles, furthermore the Audit Log, in case of a failed login via ApiToken-Provider. The issue occurred in the PRTG application server where the IP address was not set in previous PRTG versions and thus could not be logged in those cases.
• You are now able to create the following sensor types with the new endpoint /experimental/devices/{id}/sensor via POST request: AWS Cost sensor, Cloud Ping sensor. The new endpoint is listed under the Sensors section in Swagger UI and gives you information about supported sensors. All setting sections, including lookups, are supported for this sensor type.
• We have added the field primary that is included in the response code when you execute a GET request on the endpoint /experimental/channels. When you filter for the primary field (true or false) you will receive a list of primary or non-primary channels accordingly.
• We fixed an issue for the experimental endpoint /experimental/devices that returned the status PAUSED_UNTIL for paused objects by user when you executed a GET request. This status did not match our Schema and will now return PAUSED_BY_USER_UNTIL for objects that were paused by user until a certain date or time.
• We added two experimental endpoints /experimental/usergroups/{id} and /experimental/usergroups to PRTG API v2 that return a list of created user groups or by ID when you set the include parameter first upon a GET request.
• We improved the experimental endpoint /experimental/devices/{id}/sensor to accept certain sensor types via POST request when those sensor types have a version number in their name. The endpoint will now accept those sensor types with or without the version number. This change affects the AWS Cost sensor and Ping v2 sensor for now. You will also find an additional note under this endpoint listing the supported sensors.
• We improved the handling for endpoints in PRTG API v2 that are not available for Paessler PRTG Hosted Monitor instances. For the endpoint /users/reset-password, for example, we now display a note that the endpoint is not available on Paessler PRTG Hosted Monitor. When you execute a POST request on this endpoint for password reset, you will receive a HTTP 501 error response that this method was not implemented yet.
• We updated our Open API Specification available on API v2 Overview? regarding the endpoints in the sections Experimental and Deprecated.

PRTG application server

• We fixed an issue for the PRTG application server that ignored parsing errors of the appserver.config.yaml and started with a default configuration. The PRTG application server will no longer start in this case and exit immediately, leaving a panic logfile with a message that explains the issue. This happened, for example, if lines for accesskey and clientuuid existed in the appserver.config.yaml.
• We fixed an issue for the PRTG application server that occurred when you updated to PRTG version 25.2.108.1358. The PRTG application server would crash sporadically in certain cases and create a panic logfile with the message: panic: runtime error: invalid memory address or nil pointer dereference.

Dependencies

Device settings

Device templates

Graphs

Monitoring

Mobile view

Sensor overview

All parts of PRTG

Languages

Improvements and Fixes

• Upgrades failed if the user performing the upgrade had insufficient SQL server permissions. The installer now uses the Application Pool identity for the database upgrade.
• The times of outages recorded in the SLA report are not displayed consistently for all regional settings. For some regional settings, the SLA report displays the times of outages but does not indicate am or pm.
• If a child board is pinned to two or more parent boards, users in non-administrator roles are unable to view the child boards.
• The application displays an SQL timeout error and becomes unresponsive.
• SLA data is not calculated for business services and shows an error state.
• Alerts related to a child board are not visible on the parent board.

New supported sensors

REST Custom v2 sensor

SNMP Linux Block Device I/O sensor

SSH Disk Free v2 sensor

REST API

Sensorlist.htm

Add sensor

Dependency

License activation

Subscription only

Notification delivery

Notifications

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

Reports

NetApp SnapMirror v2 sensor

Ping v2 sensor

REST Custom v2 sensor

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

SNMP v3

SSH Remote Ping v2 sensor

SSH sensors

WMI Event Log sensor

Alarms

PRTG Tickets

Tree Version Update

Common SaaS sensor

SSH INodes Free sensor

Sensor migration

Discontinuation of Python Script Advanced sensor with PRTG 25.x.110

License information

Subscription only

Security

• sha256_exe 16649C98C3EBF43D982E4798448661140704D6209751298AEA4B26A4A3C9D674
 
• sha256_zip 82BF773F808FFEE8ED9AB05F1520E296C2499A1D3430F4170CE7ED64472B4913

REST JSON Data sensor

API

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

PRTG application server

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

Licenses

Subscription only

Interface

All parts of PRTG

Languages

Sensor Languages

Auto-discovery

Webserver

New Architecture

NATS Server Overview sensor

SNMP CPU Usage sensor

SNMP UPS Status sensor

SSH Load Average v2 sensor

SSH Meminfo v2 sensor

SSH Remote Ping v2 sensor

SNMP Linux Load Average v2

SNMP Linux Meminfo v2

SNMP Memory v2

Licenses

License activation

Subscription only

SNMP Disk Free v2 sensor

PRTG logo

SMTP authentication

Active Directory

API keys

HTTP errors

Logging

Notifications

PRTG activation

HPE 3PAR Drive Enclosure

HPE ProLiant Memory Controller sensor

SNMP Disk Free v2

SNMP v3

sFlow sensors

Notification delivery

SNMP v3

SSH sensor migration

Security

• sha256_exe 5DD6D0FEC1071FC5F90CF05E81965BB01CC47726CF63FCA37421DE60E927405C
 
• sha256_zip 144D4E61D3E095550C22542919F0C5859CFDF27683351F03FA1429C53ABC1AD5

Deprecation of SFTP Secure File Transfer Protocol sensor with PRTG 25.x.108

Discontinuation of SSH INodes Free sensor

Deprecation of certain sensor types with PRTG 25.x.108

Upcoming sensor migration with PRTG version 25.x.110

REST Custom v2

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

SNMP CPU Usage sensor

API

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

PRTG application server

Home page

Notification trigger

Monitoring

Tabs

All parts of PRTG

Languages

Improvements and Fixes

• Dialog boxes that allow users to edit table columns do not work well with screen readers. These tables have been updated for improved accessibility.
• When you attempt to open the Alerts tab on a board, the tab does not load.
• When the alert count for a board changes, the interface does not automatically refresh and show an updated alert count.

Webserver

Device templates

VMware Datastore (SOAP) sensor

Script v2 sensor

Sensor status

License

SSH INodes Free sensor migration

Geo location

PRTG application server

SMTP settings

HTTP Transaction sensor

• We fixed an issue for the HTTP Transaction sensor that occurred in previous PRTG versions where the sensors went into Down state after updating to PRTG 22.2.77.2204 in certain cases. A possible workaround was to set the Monitoring Engine to use the Compatibility engine mode in order to monitor the URL what helped in certain cases. The issue happened because the HTTP request cookie was not transferred for all following requests in a non compatibility mode. In some cases the HTTP Advanced sensor was also affected by reporting that the connection was refused and it would work again with the Compatibility engine mode.
• We fixed an issue for the HTTP Transaction sensor that occurred when you chose the option Compatibility engine under the option Monitoring Engine section and you set a text value for example ccc in the option Response must not include field in the sensor settings. The sensor then would have displayed a down status with the message URL #1 Warning: RegEx does not match [ccc].

LDAP sensor

NetApp SnapMirror v2

OPC UA sensors

SNMP v3

Sensor count

WMI Vital System Data v2 sensor

Single Sign-on

Subscription only

Sensor overview

Tree version update

Deprecation of SSH INodes Free sensor with PRTG 25.x.106

Deprecation of Python Script Advanced Sensor with PRTG 25.x.106

Security

• sha256_exe CBEB1C5ECD86060B2866E1E6C56844FDA63CECB3EB29A7551DA94DB7066F95A0
 
• sha256_zip ED2E78563E54F187F3E6078DE85D0671B246E393AB154A4B0EBEA59A15659C38

API

• You can now receive and edit location information with the include parameter set to locationgroup via GET and PATCH request on the devices and group endpoints. To see the location of an object, use the /{id} or list endpoint for a certain object type and make sure to include locationgroup via the include parameter.
• We added the sections /experimental/users/{id} and /experimental/users for GET requests in the api/v2/oas.
• You are now able to create a group via PRTG API v2 and an according POST request on the endpoint /api/v2/experimental/groups/{id}/group and /api/v2/experimental/probes/{id}/group .
• You are now able to edit group settings via PRTG API v2 and an according PATCH request on the endpoint /api/v2/experimental/groups/{id}.
• You can now delete a group or a sensor with a DELETE request in the experimental section /experimental/groups/{id} or /experimental/sensors/{id}. If the request is successful, you will receive a 204 response code.
• We updated the /devices/{id} and /groups/{id} to receive and display information about the status of auto-discoveries. When you execute a GET request on the mentioned endpoints, you will see the additional section about auto-discovery with the fields active, progress and last_autodiscovery, which display whether an auto-discovery is currently running, the progress and when the last auto-discovery ran respectively. Please make sure to set the include parameter first for the section autodiscovery.
• We fixed an issue that occurred when you sent a PATCH request to the /devices/{id} endpoint for the settings group discoverytypegroup and the devicetemplate value was not set. The returned error response code was 400 with the message BAD REQUEST in those cases.
• We fixed an issue for the dbport field in the dbcredentials used for Credentials for Database Management Systems in the device settings. When the default value of that according field was set to 1, for example, the request would fail in the PRTG API v2.

Auto-discovery

All parts of PRTG

Languages