Release notes
for the "stable" release channel

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