Release notes
for the "stable" release channel

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

SNMP v3

Security

• sha256_exe 480637BD026D608FF987BAF3273921C7995934653913EBF42DDD0DA939EFE47A
 
• sha256_zip 6B2ED30C8AF36F2355674BE8A1F2724CBEBD969ACC4937EA353A12F01E3E0D20

PRTG intermediate version 25.1.104.1906

All parts of PRTG

Audit Logging

Subscription only

Cisco WLC Access Point Overview sensor

PRTG Data Hub sensors

Port v2 sensor

SSH INodes Free v2 sensor

Lookups

MQTT Subscribe Custom sensor

Sensor credentials settings

PRTG application server

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

Upcoming migration of SSH INodes Free sensor with PRTG version 25.x.106

API calls

Access Rights

Auto Update

Geo Map

Logging

Notifications

Probe service

Remote probes

Reports

Single Sign-on

HPE3 PAR Drive Enclosure sensor

MQTT Round Trip sensor

MQTT Subscribe Custom sensor

Sensor Settings

WMI Event Log Sensor

Historic Data

Sensors

Auto-update

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

Auto-Update/Signature

Graph Settings

Cluster setup

SNMP v3

Security

• sha256_exe 012721D374016A2B472171EE5B1B6657C05744E8A6AA2A05479D5CB004A26D93
 
• sha256_zip 2AC635C1B702628CE7613D3E1236A4CF5063A56466D3AFFA2135E6389F188D6D

Add sensor

Connection Settings

API

• We fixed an issue for the section scheduledependency where maintstart and maintend for Schedules, Dependencies, and Maintenance Window setting where not displayed in UTC (Universal Time). When you executed a GET request on the endpoint api/v2/devices/id you could notice that the maintstart and maintend was displayed in the given timezone of the user set in the PRTG web interface instead of the UTC timestamps used by PRTG core and appserver.
• We fixed an issue for the endpoint devices/id that happened in rare cases when you executed a GET request with the include parameter. The values for id, name and href under _inheritanceSource were empty in these cases. For the value kind type you would receive an error message: unknown_referenced_object_type_for_itemEnumerated.
• We fixed an issue for GET request API call on [Probe/Group/Device] endpoint with the include parameter set where certain settings were missing in the returned response. The issue occurred only when you had a fresh new PRTG installation and with the object IDs [1/50/40] that are automatically created upon installation.
• You can now receive the settings Credentials for PRTG Data Hub when you execute a GET request on the endpoints schemas/kind and devices/id in the PRTG APIv2.
• We improved the handling for receiving and editing access rights via PRTG API v2. When you execute a GET request on an object endpoint, for example /devices/{id} with id=40 (local Probe) and include= accessgroup, inheritance as parameter, you will get the corresponding access rights groups. Previously, if you wanted to change access rights via PATCH request, you would have to use the same number of arguments that were returned with your GET request before. It is now possible to change access rights settings for only a certain number of groups via PATCH request. Executing a PATCH request for access rights will lead to a 403 access denied error in the API when you are logged in with a read-only user.

PRTG Application server

Add object

Acknowledge alarms

Error Page

Home Page

Logs

Monitoring

Page refresh

Remote Probe

Reports

• Your selected sensors will now be displayed fully in the Report settings under Select Sensors Manually when you have added them to your report via drag and drop. In the previous PRTG versions, those selected sensors were cut off in the Objects area under Select Sensors Manually.
• We fixed an issue for the reports URL when you open the settings Select Sensors Manually. The URL would wrongly display /report//channels in this case. We changed it now to /report//select-sensors-manually.

Settings

Sensor Overview

• We fixed an issue that occurred, when you clicked on a sensor in the navigation tree under Monitoring. The sensor overview page would open on the right side. When you closed the split view for the sensor overview page and clicked on the same sensor in the tree again, the overview page would not open.
• We improved the message for new added sensors to a device when there is no data available yet. Previously, when you navigated to the sensor overview page of a new created sensor when no data was available yet, you would see the message No matches could be found. The message now displayed in such cases is No data yet.

Single Sign-on

Tabs

All parts of PRTG

Languages

Sensor languages

Auto-Discovery

Security

• sha256_exe 45BE984AEBCECFD670BDCD3B7228A4190E7656CAEC4BE29A2E43E5BE3EF24E81
• sha256_zip 5659680469A7ECC56FD49D6D6EE0DFE84CCA09819820765911DE2AD4A1319378

Improvements and Fixes

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

Data Buffer

SNMP Disk Free v2

WMI Microsoft SQL Server 2022 sensor

Geo location maps

Secure Shell (SSH) sensors

WebGUI

API Keys

Single Sign-on

Modbus Custom sensors

OPC UA Custom sensor

SNMP HPE ProLiant Physical Disk

Sensor settings

API Keys

Graph Settings

Logging

Notifications

Notification Delivery

Maps

Tags

Oracle Tablespace sensor

SSL Security Check

Maps

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

Multi Edit

HPE ProLiant Physical Disk sensor

Custom Sensor Status

Security

• sha256_exe 8C175D97D0AD6C4C0664336C68DAD4BF8D873720B8215BD3B68CA0DF3CA48D6D
• sha256_zip B0D22BF05641AA138E7E45FD1E915C10E94D3D52ABCEC093460EC92466265421

REST Custom v2

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

SNMP Custom v2

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

SNMP UPS Status sensor

SSH Meminfo v2

SSH Load Average v2

SSH Remote Ping v2

SNMP Traffic v2

API

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

Context Menu

Monitoring

PRTG Ticket system

User Accounts

All parts of PRTG

Languages

Improvements and Fixes

Update to OpenSSL 3.0.14

Notifications

Cisco Meraki Network Health sensor

EXE/Script sensors

FortiGate VPN Overview sensor

HTTP v2

Probe stability

Offline activation

API keys

PRTG probes

DNS v2 sensor

MQTT Round Trip sensor

WMI Event Log sensor

Maps

PRTG Setup

PRTG Status

System information

Security

• sha256_exe B25CCF26E64890D53F26B5FF2F438864D07F6C4C5CA612053F6E709074488AD8
• sha256_zip BC6A5EEE27CEA8D9B30EA903A3E7FC2834F393D77C9FAAA6B86E0FFEB8E8AAEA

Cisco WLC Access Point Overview sensor

PRTG Data Hub Process sensor

PRTG Data Hub Traffic sensor

PRTG Data Hub Rule sensor

REST Custom v2 sensor

SNMP Custom v2 sensor

SSH INodes Free v2 sensor

API

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

Deprecation of endpoints

Swagger UI

Add group

Color Mode

Edit channel settings

Login behavior

Maps

Monitoring

Mobile view

Navigation

PRTG Setup

Settings

System Setup

View settings

All parts of PRTG

Languages

Improvements and Fixes

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

New Features

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

Webserver

Script v2 sensor

API keys

Auto-discovery

NetApp v2 sensors

Microsoft Azure

Sensor message

EXE/Script sensors

API calls

API keys

PRTG Core server

Remote probes

Remote Probe Installer

Auto-discovery

AWS EC2 v2 sensor

HPE 3PAR Drive Enclosure sensor

Microsoft Azure

Microsoft Azure/ Microsoft 365 sensors

OPC UA Custom sensor

POP3 sensor

Probe memory consumption

ProbeWMI.log

Syslog Receiver & SNMP Trap Receiver sensor

WMI Event Log sensor

Security

• sha256_exe 36C0FB110EE870F82CE83CE29E8D88F4AA2936FFBED1B8B35183CDA04771BBBD
• sha256_zip 7A6F81ACD884CAA0AA94A24E2B7804C3970673884E67264982F9E0741D74334B

Cisco WLC Access Point Overview sensor

Template Transfer

API

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

Edit Settings

Login

Web Interface

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

All parts of PRTG

Languages

Sensor languages

User manual

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

Maintenance

Security

• sha256_exe 8C2124ADD6BE4CCD2A83E5B85CA2F34C90EAB26436D7D858DD402086FFBF44F0
• sha256_zip 9C3FAB3B68726D51EEB6629DD6EA5532D1AB7C866B2E3EF532C6B0127DEDD448

• sha256_exe 1B4C10344DC4F7B3D63B6726842A088B448E70E951AF83D5323EF6D16C80B5DC
• sha256_zip 7473A44270D8D4A0595E9C182DEB4DFEC0E18B3BE15D7FD01719F23178A97E63

Webserver

Notifications

Ping v2

Probe Adapter

Contact support

Cluster

Libraries

Maps

PRTG Administration Tool

Search

Single Sign-on

XML tables

Active Directory Replication Errors

HTTP v2

NetFlow sensors

Security

• sha256_exe D0DA0003C068800D38C5F65DD5EFD57D91B96FE83D12D67BC675C69BF9B1AF29
• sha256_zip CE60F73C75A37CFD44471330B05DA28AB712FFD06452670584234CCC6A9CB82A

SNMP Traffic v2

Device settings

Notifications

Notification trigger

Sensor settings

API

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

PRTG application server

All parts of PRTG

Languages

Sensor languages