Thema: PRTG Network Monitor ...

[SiLæncer]

Changelog

    SECURITY:
    Server:
    This version includes an important security update for your PRTG core server. We recommend that you update as soon as possible. Please find more details in the email we sent to the email address provided in your license information. (CVE-2020-10374)
    IMPROVED:
    Sensors:
    LDAP:
    The LDAP sensor now supports LDAP over SSL (LDAPS). If you want to monitor your secured Active Directory server, choose the option Use LDAP over SSL for the sensor setting Connection Security in section LDAP Specific. LDAP without encryption is default. You can also define a custom port for the connection to the LDAP server or use the default port.
    VMware Host Hardware Status (SOAP)
    The VMware Host Hardware Status (SOAP) sensor now categorizes unknown states reported by the VMware host server as entity with its own sensor channel and does not show them as warnings anymore. You also have the sensor settings option to not show unknown states in the sensor message. The setting Known Warnings is only purposed for warning states now.
    IMPROVED:
    Server:
    Notifications:
    We added a few more placeholders for notifications. You can use a new placeholder that only resolves to the current sensor status and additional placeholders for elapsed times since status updates.
    %laststatus simply resolves to the current sensor status to ease, for example, automation tasks in comparison to the more complex %status placeholder
    %elapsed_lastcheck resolves to the elapsed time since the last scan of a sensor as shown in its general information section and is a simpler version of %lastcheck because it omits the timestamp
    %elapsed_lastdown resolves to the elapsed time since the last down status of a sensor and is a simpler version of %lastdown because it omits the timestamp
    %elapsed_lastup resolves to the elapsed time since the last up status of a sensor and is a simpler version of %lastup because it omits the timestamp
    IMPROVED:
    WebGUI:
    Reports:
    The column in the list of reports that shows the number of sensors included in the last run of a report now also updates if you run an HTML report. In previous version, only PDF reports were considered. We also renamed the column to # Sensors in last run to make it clearer what the numbers actually show.
    Security
    We updated the bootstrap.js plugin that we ship with PRTG because the previously used version 3.2.0 had an XSS vulnerability. (CVE-2019-8331)
    FIXED:
    Sensors:
    NetApp Volume:
    We fixed an issue with the snapshot time calculation of the NetApp Volume BETA sensor. In certain cases, values of sensor channels like, for example, Latest snapshot and Oldest snapshot did not match the times displayed in the NetApp interface because the sensor mixed up the handling of UTC and local time.
    Sensor channels:
    The sensor channel option Hide from tables immediately takes effect again. In previous versions, channels with this option enabled only disappeared from tables after a PRTG server restart.
    We fixed a display issue of channel gauges that occurred when switching the alerting mode from limit-based to lookup-based and back.
    WMI sensors:
    WMI sensors now show an according error message (PE069) if they do not find any items to monitor on the target device during the meta-scan on sensor creation.
    FIXED:
    Server:
    API:
    When you use an API call that returns PRTG objects sorted by a numerical property like objid, the returned objects are now numerically sorted. In previous versions, the objects were alphabetically sorted.
    For example, as of the current PRTG version, IDs (objid) are sorted like [2419, 2470, 10359, 10360], where in previous versions the sorting was [10359, 10360,2419, 2470] in such a case.
    Cluster
    PRTG now shows a correct error message if you provided a wrong cluster access key and try to log in into the failover node so that you can easier help yourself.
    Licensing
    We fixed an issue with the PRTG PLUS license where, in certain cases, PRTG instances erroneously showed the message your license will expire in

• days so that you had to manually reactivate the license each time this case occurred.

    Maps
    You can add custom background images to maps again. In the previous PRTG version 20.1.56, PRTG showed an internal server error when you selected a file as Custom Image to use as Background Image and tried to save the map settings.
    Memory Usage
    The PRTG server may consume less memory over time in certain monitoring scenarios. We also improved the memory usage of maps that include many historic graph images.
    Reports
    The default Security Context of a report is again the PRTG user account that creates the report.
    Timezones
    The default timezone for newly created user accounts and reports is the system timezone of the PRTG server again.
    IMPROVED:
    Various:
    All parts of PRTG
    Various other minor fixes and improvements, updated user manual including a style update
    Sensors:
    Npcap:
    We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 0.9987.
    Beta sensors
    The following sensor types are not in beta status anymore and are now fully supported.
    Dell PowerVault MDi Physical Disk
    DICOM Bandwidth
    DICOM C-ECHO
    DICOM Query/Retrieve
    HL7
    HTTP IoT Push Data Advanced
    HTTP Push Data
    SNMP Buffalo TS System Health
    SNMP Custom String Lookup
    Windows Physical Disk I/O
    WMI Battery
    WMI Logical Disk I/O

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    Fixed:
    Various:
    API:
    Filtering by object ID (filter_obj) properly works again. In the previous PRTG version 20.1.57.1745, API calls using filter_obj returned an empty response file, which affected XML, JSON, and CSV.
    Auto-Discovery
    You can add WMI sensors with the PRTG auto-discovery again. In the previous PRTG version 20.1.57.1745, the auto-discovery for WMI sensors did not work and did not create the sensors.

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    Server:
    Active Directory
    The PRTG active directory integration now supports LDAP over SSL (LDAPS). You can define to use SSL encryption as LDAP Transport Security in the Active Directory Integration section of your Core & Probes settings. Default is LDAP transport security without encryption.
    Languages:
    Japanese:
    We completely revised the Japanese language version of PRTG. Thanks to significantly improved texts, the new Japanese version helps you to even better find your way in the PRTG web interface, makes your monitoring tasks easier, and you can enjoy your administrator life even more. If you speak Japanese, we highly recommend this update and trying out the new language file.
    All languages
    We also updated all other language files additionally to the completely revised Japanese version.
    Sensors:
    Business Process (Processus métier):
    You can edit the channel definition settings of the Business Process (Processus métier) sensor again even when using the French language version of PRTG. In previous versions, a malformed link in the French language file made it impossible to add or change the channel definitions.
    HTTP sensors
    HTTP sensors properly support URLs that include a hash sign (#) again. In certain cases, when monitoring URLs that include the character sequence /#/, for example, HTTP sensors encoded the hash sign and showed error 404 (not found).
    HTTP Full Web Page
    The HTTP Full Web Page sensor supports URLs that include an equals sign (=) again. In previous versions, the sensor encoded the equals sign so that the sensor could not monitor the target URL and showed an error. We also increased the sensor message visibility to 255 characters and malformed results now show error PE132.
    Python Script Advanced
    You can install new packages in PRTG Python using pip or easy_install, for example, like normal again. In previous versions, you received an error message in such cases because the PRTG Python post-install script was not working when the base path included whitespaces, which is typically the case in PRTG Network Monitor installation paths. We also updated the Python distribution delivered with PRTG to version 3.7.7.
    SNMP Fujitsu System Health v2
    We added the missing lookup file for the Redundancy Mode channel of SNMP Fujitsu System Health v2 BETA sensors that monitor the power supply redundancy status (default sensor name: iRMC Power Supply Redundancy: Status). The sensor channel shows a warning status if there is no redundancy, and an up status if there is a PSU redundancy, dual AC redundancy, or triple AC redundancy.
    SNMP Trap Receiver and Syslog Receiver
    SNMP Trap Receiver and Syslog Receiver sensors now purge their messages after 180 days if you select this option in the Purge Messages After settings. In previous versions, both sensor types already purged the messages after 120 days even if you had selected 180 days.
    SSH Meminfo
    The SSH Meminfo sensor now queries MemAvailable instead of MemFree from the target device to monitor the channels Available Memory and Percent Available Memory. This approach reflects the actual RAM usage of Linux systems in a better way and is aligned with the values that the SNMP Linux Meminfo sensor monitors.
    Custom advanced sensors
    We fixed an issue with custom advanced sensors that sometimes showed wrong values in tables (differing by 1 from the correct values) while showing correct values in the data graph. The issue was caused by the Decimal Places channel setting (the custom option worked correctly) and affected sensor types that use XML input like EXE/Script Advanced, Python Script Advanced, SSH Script Advanced, HTTP Push Data Advanced, HTTP IoT Push Data Advanced, HTTP Data Advanced, and REST Custom.
    Server:
    Maps:
    You can now use JPEG files as Background Image for maps. In previous versions, maps only supported JPG, PNG, and GIF images for the background.
    Opening monitoring objects like groups and devices from the sunburst in public maps works again. In previous versions, you received the error message Map refresh failed in such cases.
    Probes:
    Sensor requests will now be removed from the original probe when you move sensors (directly or via parent devices and groups) from one probe to another probe. In previous versions, the original probe kept on sending monitoring requests for the moved sensors until the requests were deleted by pausing and resuming the moved sensors or by a server restart. This resulted in unnecessary high CPU load on the probe systems.
    Reports
    Historic data reports for Sensor Factory sensors work more reliable now. Certain combinations of report interval and average interval resulted in empty reports in previous versions.
    Passhash
    The Generate new passhash function for PRTG user accounts on PRTG hosted by Paessler instances works again. In previous version, generating a new passhash resulted in an error and so was not possible.
    Enterprise Console:
    Housekeeping
    We deliver the PRTG Enterprise Console Remover with this PRTG version. With this tool, you can simply uninstall the deprecated Enterprise Console from your server. You find it in your PRTG Network Monitor program folder, as well as there is a shortcut in the Windows Start Menu.
    Sensors:
    MQTT Round Trip:
    The upcoming PRTG version 20.2.59 will include a new, significantly changed MQTT Round Trip sensor. We already inform you now about the change because any previously deployed MQTT Round Trip BETA sensors will immediately stop working upon updating to PRTG 20.2.59 or later and you will have to add them anew.
    All parts of PRTG:
    Various other minor fixes and improvements, updated user manual
    Tree Version:
    Tree Version Update:
    The configuration file of this version is not downwards compatible with previous PRTG versions.

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

Version 20.2.59.1689

New
Sensors

DNS v2
   The new DNS v2 BETA sensor monitors a DNS server, resolves domain name records, and compares the records to a defined filter. It shows the response time of the DNS server and if records were resolved, the number of records, as well as the number of records matching the filter. With the help of this monitoring data, you can check if resolving a domain works, if the number of certain records changes, and if a certain record exists for a domain.

In comparison to the already existing DNS sensor, the new DNS v2 sensor provides more features and works more reliable in certain configurations. For your convenience, the original DNS sensor will still work after the update to PRTG 20.2.59, as well as you can still add sensors of this type, but please note that we may deprecate the DNS sensor at some time in the future. Of course, we will inform you in time before the deprecation.
MQTT Statistics
   The new MQTT Statistics BETA sensor monitors MQTT topics and shows related statistics of the broker, for example, the number of incoming messages from a subscribed topic and the received payload. With this new sensor type you can check if your IoT devices and the broker still send messages. We are looking forward to hearing your feedback about this new beta sensor! Please send your feedback to [email protected].

Changed
Sensors

MQTT Round Trip
   This version comes with a completely rewritten MQTT Round Trip BETA sensor. The new version of this sensor type replaces the original MQTT Round Trip BETA sensor.

Any previously deployed MQTT Round Trip BETA sensors will immediately stop working upon updating to PRTG 20.2.59 or later because of the significant changes in the sensor implementation. You have to add the sensors anew after the update to continue your MQTT round trip monitoring. To keep historic data, you can pause existing instances of deprecated sensors.

Improved
WebGUI

Maps
   We added new map objects for MQTT brokers. This enables you to create maps that visualize the status of your MQTT brokers on your dashboards so that you can identify the status right away. You find the new map objects in the map designer sections Default A and Default B.

Improved
Sensors

Amazon CloudWatch sensors
   This version includes a minor security improvement for Amazon CloudWatch sensors.
AWS Cost
   

    We added the setting sections "Scanning Interval", "Schedules, Dependencies, and Maintenance Window", "Access Rights", as well as "Channel Unit Configuration" to the AWS Cost BETA sensor.
    You can now add the AWS Cost BETA sensor to devices on remote probes and cluster probes as well, which also includes cluster support for this sensor. In previous versions, you could only add the sensor to your local probe.

Windows Updates Status (PowerShell)
   We added an option to the Windows Updates Status (PowerShell) sensor settings that allows you to include the port number in the SPN (Service Principal Name) used for Kerberos authentication. Use Enable for the Include Port in SPN setting to apply the option.

This option might help if your sensor monitors devices where an IIS service or similar is installed and the sensor did not work before. Because the new option is kind of experimental and we cannot say if it works in every case, we really would like to hear about your experience with it! Please send your feedback to [email protected].

Improved
Server

Active Directory
   You can now define how PRTG performs Active Directory queries, either by using the domain name or by using specific domain controllers. If you use Active Directory integration, you can choose the desired Domain Access option in the Core & Probe settings of PRTG. You can configure up to two domain controllers, a Primary Domain Controller and optionally a Backup Domain Controller.

We also fixed some minor issues that affected the PRTG Active Directory integration.
Geo Maps
   We improved the validation of coordinates that you enter into the Location (for Geo Maps) field. PRTG now checks if the geocode (longitude and latitude) is in a valid range and shows an error message if not, as well as PRTG tries to automatically correct invalid numbers. The improved validation will help to avoid issues when displaying geo maps.
Probes
   

    We increased the resilience of the PRTG core server towards reconnecting probes with buffered data. If probes lose the connection to the PRTG server, they keep performing their assigned monitoring requests and buffer the results. Upon re-establishing the connection, the probes send all buffered data to the server at once. This can lead to dropped data when the maximum raw data buffer capacity is reached, which results in numerous sensors in "unknown" status.

    With the improvements in this PRTG version that include an increased buffer size, a slowed down processing of incoming data packets if required, and breaks in sending buffered data, the monitoring of current values will become more reliable in such cases. We call the new mechanism that applies on probe reconnect "burst mode".
    If you delete a connected remote probe from the PRTG device tree, PRTG will now stop the PRTG probe service on the probe system and set the startup type to manual. This prevents the removed remote probe from sending unnecessary connection attempts to the PRTG server. We recommend that you additionally uninstall the remote probe on the remote probe system.

    Note: PRTG cannot automatically stop the services of disconnected or denied remote probes.

Search
   We improved the stability of the PRTG search function and also fine-tuned the search results. For example, you will not receive a bunch of PRTG tickets anymore as search result when you search for more than one keyword.
Toplists
   To improve performance and stability, PRTG now more efficiently handles data transmission to toplists and purging of toplists that are used by flow and packet sniffer sensors.

Fixed
Sensors

SNMP Custom Table
   The SNMP Custom Table sensor correctly replaces OIDs in the sensor name with the value of the referenced column again.
SSH Meminfo
   We fixed an issue with the SSH Meminfo sensor that occurred in the last PRTG version 20.2.58.1629 when target devices returned values in a certain notation. In this case, the sensor showed error PE094.
WMI Disk Health
   The WMI Disk Health BETA sensor now supports blanks in the serial number of the monitored disk and continues monitoring this disk even after a PRTG server restart. In previous versions, PRTG removed the blanks upon restarting, so that the sensor was not able to identify the monitored disk anymore and showed an error message (PE016).

We recommend that you update soon if you use this sensor type. In future PRTG versions, a seamless update of the sensor without having to add it anew might not be possible anymore because of the fix.

Fixed
Server

Installer
   We hide the CLI window again that in the last version appeared during the Python installation step when installing or manually updating the PRTG server or a probe.
PRTG Administration Tool
   We disabled the option to change the Path for probe data storage on the Probe Settings for Monitoring tab when you run the PRTG Administration Tool on the PRTG core server. Please use the option Local Storage of Data Files and Monitoring Database on the Core Server tab to change the path.

In previous versions, having the option on both tabs available could be misleading and could result in unexpected behavior when changing the path on the probe settings tab.
User Accounts
   You can change the settings of user accounts that you added via Add Multiple Users without restarting the PRTG server again. In previous versions, PRTG showed the error message The validation of the data you entered has failed. A user with this login name already exists. Login names have to be unique. in this case.

Improved
Various

All parts of PRTG
   Various other minor fixes and improvements, updated German language file, updated user manual

Note
Sensors

Npcap
   We added a registry key that allows you to individually prevent PRTG from installing Npcap on your PRTG probe machines. This might be necessary in certain scenarios to not interfere with other services. Please note that Packet Sniffer and Packet Sniffer (Custom) sensors need Npcap to monitor your traffic.

For details, see the Knowledge Base article How can I disable the installation of Npcap before updating or installing PRTG?

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    [Sensors] The new sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced monitor the overall and detailed status of all services of a Microsoft 365 subscription.
    [Sensors] The new Zoom Service Status sensor monitors the global status of each Zoom service. It shows the operational states of the services and according error messages if something went wrong.
    [Sensors] The new Dell EMC Unity Storage LUN v2 sensor monitors the health status and several size metrics of a LUN on a Dell EMC Unity storage system. It also supports Unity REST API version 5 and later.
    [Sensors] The new MQTT Subscribe Custom sensor subscribes to an MQTT topic and monitors the returned values.
    Various fixes and improvements for all parts of PRTG

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    Sensors:

    Cloud HTTP v2:

    The new Cloud HTTP v2 BETA sensor monitors a web server and shows the loading times from different locations. It is the successor of the Cloud HTTP sensor introduced with PRTG 14.x.14 that we will deprecate and remove from PRTG in an upcoming version depending on your feedback for the new Cloud

    HTTP v2 sensor:

    The new sensor uses a new technology in the backend and comes with an enhanced feature set. For example, you can now individually define the regions that you want to use for the requests.

    Cloud Ping v2:

    The new Cloud Ping v2 BETA sensor monitors the ping times to a device from different locations. It is the successor of the Cloud Ping sensor introduced with PRTG 14.x.14 that we will deprecate and remove from PRTG in an upcoming version depending on your feedback for the new Cloud Ping v2 sensor.
    The new sensor uses a new technology in the backend and comes with an enhanced feature set. For example, you can now individually define the regions that you want to use for the requests.

    Dell EMC Unity File System v2:

    The new Dell EMC Unity File System v2 BETA sensor monitors a file system on a Dell EMC Unity storage system. It shows free size, allocated size, as well as size and number of snapshots.
    This new Dell EMC Unity storage sensor supports Unity OE API version 5 and later, which the existing REST Dell EMC File System BETA sensor is not capable of.

    Dell EMC Unity Storage Capacity v2:

    The new Dell EMC Unity Storage Capacity v2 BETA sensor monitors a Dell EMC storage system and shows free size, used size, preallocated size, and subscribed size.
    This new Dell EMC Unity storage sensor supports Unity OE API version 5 and later, which the existing REST Dell EMC Capacity BETA sensor is not capable of.

    Dell EMC Unity Storage Pool v2

    The new Dell EMC Unity Storage Pool v2 BETA sensor monitors a storage pool on a Dell EMC Unity storage system. It shows the health status of the storage pool, as wells as several size metrics.

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    NEW:

    Dell EMC Unity Enclosure Health v2
    The new Dell EMC Unity Enclosure Health v2 BETA sensor monitors the health of a disk-array enclosure (DAE) or a physical or virtual disk processor enclosure (DPE) on a Dell EMC storage system. It shows the health status and, depending on the target device, temperatures as well as the status of cooling modules, drives, storage processors, power supplies, and link control cards. This sensor will help you to ensure your Dell EMC Unity enclosure is always working as expected.
    Microsoft Azure Subscription Cost
    The new Microsoft Azure Subscription Cost BETA sensor monitors the cost in a Microsoft Azure subscription so that you can keep track of the overall expenses of your subscription. It shows the current and previous period cost, the cost forecast, user budgets, and the most expensive service by category.
    Veeam Backup Job Status
    The new Veeam Backup Job Status BETA sensor monitors the status of all backup job runs on the Veeam Backup Enterprise Manager in the last 24 hours. It shows the number of successful and failed job runs, running and finished job runs, job runs in warning states, and scheduled backup jobs. This sensor gives you a general overview of the status of your backup jobs so that you see the jobs which need your immediate attention at a glance.

    IMPROVEMENTS:

    Sensors:

    Modbus TCP Custom
    Thanks to your feedback, we implemented several improvements for the Modbus TCP Custom BETA sensor that we introduced in the last PRTG version.
    We improved the usage of the sensor settings.
    We increased the range for register addresses.
    Register numbers can now start from 0.
    You can define a lower scanning interval than 60 seconds.
    The sensor log provides more information.
    We updated help texts and documentation.
    Important: After updating from PRTG 20.4.63 to 20.4.64 or later, you will have to add the sensor anew. Running Modbus TCP Custom sensors will show a down status after you have installed the update due to changes in our underlying Modbus monitoring configuration.
    MQTT sensors
    You can now create device templates that include the sensor types MQTT Round Trip, MQTT Statistics, and MQTT Subscribe Custom. You can use the device templates to add MQTT sensors via auto-discovery.
    MySQL v2
    The MySQL v2 sensor now supports authentication with caching_sha2_password on MySQL 8.0 and later. In previous versions, the sensor showed the error message Authentication method 'caching_sha2_password' not supported by any of the available plugin when you tried to monitor MySQL server version 8.0.
    OPC UA Server Status
    We further improved the OPC UA Server Status BETA sensor that we introduced in the last PRTG version. Thank you for your feedback!
    The sensor can now monitor session related metrics if diagnostics data is activated on the server, so that PRTG can notify you if there are too many ongoing sessions or the amount of timeout sessions increases.
    We added support for authentication with username and password, as well as you can use encryption and provide a certificate to authenticate the sensor against the OPC UA server.
    We improved the general performance of OPC UA sensors in this version by minimizing their network communication.
    We drastically reduced the amount of log entries that OPC UA sensors write into the probe.log file.

    SSL CERTIFICATE:

    The SSL Certificate sensor has a new timeout setting for TCP read requests, which is useful if you monitor a slow server with the sensor.

    FIXED:

    Sensors:

    Cisco IP SLA
    Tag and Owner are now in the correct column when adding the Cisco IP SLA sensor. Furthermore, the sensor will not erroneously add a vendors_cisco tag to a device anymore when you run an auto-discovery and the discovered device is not a Cisco device.
    Google Analytics
    You can add Google Analytics sensors again. The sensor type needed a new OAuth verification by Google to be able to access data.

    HTTP Push Data sensors:

    HTTP Push Data and HTTP Push Data Advanced sensor now keep and display their last value on device overview pages and map objects instead of showing No data after a scanning interval without a new value.
    The HTTP Push Data Advanced sensor now applies the unit to a channel value if provided in the push message and as defined in the Channel Unit Configuration settings.

    HTTP Transaction:

    Smart URL Replacement in the HTTP Transaction sensor now even works if you use the Alternate/Compatibility Mode as Monitoring Engine. In previous versions, the URL replacement only worked with the recommended default monitoring engine. Please note that support for ports in smart URL replacement when using the compatibility mode will only come with a later version.
    SNMP Custom Table
    We fixed an issue with SNMP Custom Table sensors that are created via auto-discovery. In certain cases, the sensors were created with invalid IDs and uncommon sensor names and immediately showed a down status after creation.
    SQL v2 sensors
    We fixed an issue with SQL v2 sensors that caused a down status with the message Error: An item with the same key has already been added because PRTG did not properly reset the parameters after a sensor timeout.
    WMI sensors
    The auto-discovery with template can add certain WMI sensors again. In previous versions, you could not add the sensor types WMI Exchange Server, WMI Sharepoint Process, and WMI Vital System Data v2 sensors, for example, by using an auto-discovery with template.

    FIXED:

    Server:

    Active Directory:

    If you change the Login Name of an Active Directory user account in PRTG, it is not possible anymore to login with the changed login name because this user account does not exist in the Active Directory. The login with the original login name still works and will create a new Active Directory user account in PRTG. In previous version, the behavior in such cases was unreliable.
    API
    We fixed an issue with historic data queries via the PRTG API. In certain scenarios, the queries could take too much time since we improved the memory consumption of historic data queries in PRTG 20.1.57.
    Config
    We fixed a potential deadlock that could happen when PRTG saved the configuration, resulting in a server crash in rare cases.
    Languages
    The Local Probe now keeps its name after a server restart in Japanese, Russian, and Chinese language versions. In previous versions, the name of the probe was overridden by question marks (??) after a restart.
    Login
    We fixed an issue with the login of PRTG user accounts that occurred in rare cases when changing the password of a user who was logged in into PRTG Desktop at the same time. A re-login was not possible for some time in such cases.
    Maps
    We fixed a potential deadlock that could happen in rare cases when using the Map Designer. PRTG became unresponsive in such cases and required a server restart to work again.

    Multi-Edit:

    You can edit the settings of multiple devices, groups, and probes at once again. In previous versions, multi-edit on these objects resulted in an error with the message The validation of the data you entered has failed when you saved your changes.
    Multi-editing limits of sensors now properly works for sensors with channels that display data in percent of the maximum value. In previous versions, the applied limit values were incorrect if two or more multi-edited channels had different maximum values.

    Notification Templates:

    We removed some redundant entries from the History tab of notification templates that still appeared on 64-bit installations of PRTG.
    Reports
    Links to sensors and devices in PDF reports work again. In previous versions, the links included a wrong port and could not be opened.
    Uninstall
    We fixed an issue that prevented a clean uninstall of PRTG on Windows 10 Pro 64-bit instances.

    WebGUI:

    Libraries:

    You can collapse and expand library nodes again.

    System Information:

    Data:

    The System table on System Information tabs shows data for specific SNMP devices again. In previous versions, PRTG could not retrieve system information data from SNMP devices if an interface had multiple IP addresses. You received the message Error: duplicates not allowed in this case.

    PRTG for Android:

    Sorting:

    Sorting by status in the alarms section of PRTG for Android corresponds to the sorting in the web interface again if you connect your app to PRTG version 20.4.64 and later.

    Note:

    Sensors:

    Beta Sensors:

    The following sensor types are not in beta status anymore and are now fully supported.
    AWS Cost
    Cloud HTTP v2
    Cloud Ping v2
    DNS v2
    Microsoft 365 Service Status
    Microsoft 365 Service Status Advanced
    MQTT Round Trip
    MQTT Statistics
    SNMP Nutanix Cluster Health
    SNMP Nutanix Hypervisor
    SNMP Fujitsu System Health v2
    WMI Microsoft SQL Server 2019
    Zoom Service Status

    Experimental Sensors:

    We added two new experimental sensors that you can manually enable.
    Microsoft Azure SQL Database: The experimental Microsoft Azure SQL Database sensor monitors your Microsoft Azure SQL Database instances so that you are notified if there is an issue with your SQL instance. The sensor in the current experimental status has the known issue that the sensor will stop working as expected it if the database type changes or has changed from vCore to DTU or vice-versa. If you try out the sensor and encounter this issue, we would kindly ask you to contact us and provide the sensor logs if possible. This will help us to further develop the sensor.
    Modbus RTU Custom: The experimental Modbus RTU Custom sensor monitors up to 5 values that your Modbus RTU device returns.

    Improved:

    Various:

    All parts of PRTG:

    Various other minor fixes and improvements, updated user manual, updated German language file

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

OPC UA Certificate
   The new OPC UA Certificate sensor monitors the certificate of an OPC UA server and helps you to ensure a secure and consistent communication between the machines in your shop floor. We released this sensor type as experimental sensor in the last PRTG version and received valuable feedback that we now implemented to enhance the sensor based on your needs. The following additional features made it into this version.

    We added the channel Self Signed that shows if the monitored certificate is self-signed or not.
    The sensor shows the certificate thumbprint and the common name in the sensor message.

OPC UA Custom
   The new OPC UA Custom sensor monitors the values returned by multiple nodes of an OPC UA server. We released this sensor type as experimental sensor in PRTG 20.4.63 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we added two more features for this release.

    The sensor now automatically creates a lookup channel if the OPC UA server returns a Boolean value. By default, the channel will show a down status if the server returns the value 0 (false), and an up status if the server returns 1 (true).
    The sensor can now read string nodes from an OPC UA server and display them in the sensor message. You can specify the node ID for the string in the sensor settings and use this feature to display serial numbers of connected modules or the like.


Improved
Sensors

DNS v2
   You can now create device templates that include the DNS v2 sensor. This enables you to add sensors of this sensor type via auto-discovery.
Microsoft 365 Service Status Advanced
   The Microsoft 365 Service Status Advanced sensor now shows in the sensor message whether an issue is an advisory or incident so that you can easily see the impact of an issue.
Packet Sniffer
   We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic to version 1.10. The new version includes several fixes and performance improvements compared to the previously delivered version 0.9987.
Windows Updates Status (PowerShell)
   The Windows Updates Status (PowerShell) sensor can now monitor workgroup machines and target systems that are not in the same domain as the PRTG probe. You can define the required authentication method, Kerberos authentication or negotiation authentication, in the sensor settings.
WMI Battery
   The WMI Battery sensor can now monitor the battery level of USB connected UPS so that you can ensure there is enough load in case of a power outage.

Improved
Server

User Accounts
   PRTG now logs changes to user account passwords and shows which user account changed a password and when. You can view the changes on the History tab of a user account.

Improved
WebGUI

Add Sensor Dialog
   Several more sensor types for which required credentials in the parent device settings are missing are now greyed out in the Add Sensor dialog. You cannot add the sensors without providing the credentials anymore. PRTG lists the credentials that you need to provide in this case for each sensor. This will help you to more flawlessly enhance your monitoring with new sensors. The change affects the recently introduced sensor families Dell EMC v2, Microsoft 365, Microsoft Azure, Veeam Backup, and HPE 3PAR (BETA).
Channel Limits
   PRTG now validates the limits you enter in sensor channel settings. You cannot save invalid limit combinations anymore like, for example, a higher value for the lower error limit than for the lower warning limit. This will help you to avoid unexpected sensor behavior due to mistakenly defined limit configurations.

Lab
Sensors

HPE 3PAR Common Provisioning Group
   We added the channels Logical space free, User space free, and Snapshot space free to the HPE 3PAR Common Provisioning Group (BETA) sensor.
Microsoft Azure SQL Database
   We improved the Add Sensor dialog of the Microsoft Azure SQL Database (BETA) sensor. The table where you select the databases you want to monitor when you add the sensor supports filtering and sorting by DTU and vCore, and you can see if a database belongs to an elastic pool and which one. Additionally, the elastic pool is added to the sensor name upon sensor creation.
Veeam Backup Job Status Advanced
   We added the channels Last Job Run and Job Scheduled to the Veeam Backup Job Status Advanced (BETA) sensor. Because of the new channel, we also removed the setting Warn if the job is not scheduled, as well as we improved the help texts for the sensor and the names of lookup states.

Fixed
Sensors

Auto-Discovery
   

    Auto-discovery on IPv6 devices works again. The sensors in according device templates are automatically created when you run the auto-discovery with a device template for an IPv6 device. In previous versions, it was not possible to add sensors via auto-discovery in this case.
    The standard device template UPS (Generic) now creates sensors with correct unit and scaling for the Current channels.

Dell EMC Unity v2 sensors
   Dell EMC Unity v2 sensors now support multiple descriptions in the API response from the target device. Multiple descriptions can appear if there is an issue with a disk in a Dell EMC Unity storage system, for example. In this case, the sensors showed a down status in previous versions and created the log message The received value is an array instead of a single value. Dell EMC v2 sensors now show the correct value and all received descriptions in the sensor message in this case.
Dell EMC Unity VMware Datastore v2
   You can now add Dell EMC Unity VMware Datastore v2 sensors to Dell storage systems even if there is a Veeam Backup plugin installed. In previous version, you could not add the sensor to such a device because the scan for available monitoring items failed with the error message An error occurred. (The queried field is empty.)
HTTP Transaction
   The HTTP Transaction sensor now supports ports when using smart URL replacement. In previous versions, the sensor did not correctly fill in the parent device's IP address or DNS name if you defined a transaction URL only denoting the port number. The sensor showed a down status with the following message in this case: Failed to establish secure connection [Step 0] Socket Error # 11001 Host not found.
Microsoft 365 Service Status sensors
   We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against some unexpected return values.

    We added a retry setting to avoid sensor errors due to empty responses that the Microsoft 365 API sometimes returns. The error message in such cases is An error occurred. API Response does not contain exactly one result for the workload [...].
    We added support for a status return code that the sensors could not handle so far. The error message when the Microsoft 365 API returned such an unknown code was An error occurred. invalid map key.

Microsoft Azure Subscription Cost
   We improved the handling of empty fields that Microsoft Azure sometimes returns to the Microsoft Azure Subscription Cost sensor. In previous versions, the sensor only showed a down status in such cases.
Modbus TCP Custom
   The Modbus TCP Custom sensor now supports the unit ID 255, which is required for certain target devices. We also implemented the fix for the experimental Modbus RTU Custom (BETA) sensor.
NetFlow and IPFIX sensors
   NetFlow and IPFIX sensors now show an expressive error message if one or more IP addresses that were previously selected for binding in the sensor settings are no longer available. This will help you to faster find the error source. The message in this case is The previously selected Network Adapter (with Address ('[IP]') could not be found, please change the sensor settings to an available IP address.
OPC UA sensors
   We fixed the issue that some valid client certificates caused a BadCertificateUriInvalid error in OPC UA sensors. The OPC UA sensors could not connect to the target device in such cases due to a different application URI in certificate and sensor.
SNMP sensors
   SNMP sensors now support very large values from the numeric SNMP data type Counter64 (unsigned 64-bit integer). In previous versions, SNMP sensors showed the error message [value] is not a valid integer value or wrong values if such a value was returned. The issue was reported by a customer for the SNMP Cisco CBQoS sensor but also affected other SNMP sensor types like SNMP custom sensors, for example.
VMware sensors
   We fixed an issue with the session handling of VMware (SOAP) sensors. In the previous PRTG version 21.1.65, the issue caused the sensors to log in and log out on the target system with each sensor scan, which flooded the VMware logs, for example.

Fixed
Server

Cluster
   

    We fixed a potential deadlock that appeared in very rare cases on cluster failover nodes when moving objects from the local probe to the cluster probe, which could crash the system.
    You can save changes to settings of objects on the cluster probe again. In the previous version 21.1.65, the Save button was always disabled, which made saving changes impossible.

License Activation
   We fixed an issue that could prevent automatic license activation in proxy environments.
Notifications
   We fixed an issue that prevented notifications from being sent out in rare cases.
Notification Templates
   Pausing and resuming notification templates via the notification template list is logged on the History tab of a template again.
Reports
   To avoid memory exhaustion, the maximum report interval is now limited to 500 days per report.

Fixed
Server and Probes

Stability
   We fixed an issue that could cause instability of the PRTG server and probes in varying forms. This could happen in case of failing Execute Program notifications, failing EXE sensors, or failing script sensors, for example.

Fixed
WebGUI

Alarms as Gauges
   We fixed an issue that caused the page Alarms | Shows as Gauges to not show any sensor gauges. The page remained empty in previous PRTG versions if there was at least one sensor in Down (Acknowledged) status with a closing square bracket (]) at the end of the sensor's error message.
Device Tree
   The device tree keeps collapsed and expanded states of all objects again when the page refreshes. In previous versions, all device tree objects were always expanded after a page refresh if you were logged in as read-only user or as read/write user with read access to an object.

Improved
Various

Languages
   We updated the German language file.
All parts of PRTG
   Various other minor fixes and improvements, updated user manual

Note
Known Issues

Channel Limits
   You cannot save Limits in sensor channel settings when using comma as decimal separator. You will get the error message Internal Error: '[value]' is not a valid floating point value in the current PRTG version 21.1.66. Pre-existing limits are not affected and keep working. As a workaround, you can enter the closest integer value like, for example, 1 instead of 0,99 if applicable. The decimal comma is used in several European regions, for example.

Status: We are working on a fix for the next PRTG version 21.x.67.
Microsoft 365 Service Status sensors
   In some cases, the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced may show a down status after updating PRTG with the error message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. (code: PE270).

To resolve the issue, please manually pause and resume affected sensors or restart the PRTG core server service under Setup | System Administration | Administrative Tools | Restart PRTG Core Server Service.
OPC UA Server Status sensor
   We strongly recommend that you add running OPC UA Server Status sensors anew after updating from a previous PRTG version for stability reasons. Although you will not directly encounter issues with the sensors, you may notice errors in the core.log file due to an update issue with the underlying functionality of this sensor type.

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

New

Server

Core Health (Autonomous) sensor

   The new Core Health (Autonomous) sensor monitors your PRTG server and is automatically created on the new PRTG Core Server device when you install PRTG 21.x.67 or later. It shows the status of the PRTG core server and checks various parameters of the PRTG core server that have an impact on the stability of the system.

The sensor has the same functionality as the existing Core Health sensor but runs independently of the local probe. Because of this, the sensor still can monitor the status of the PRTG server if the probe is disconnected. This avoids situations that there is no health data for the PRTG server available when the local probe is disconnected so that efficient troubleshooting in case of server issues is still possible.

Improved

Sensors

MQTT Subscribe Custom

   The MQTT Subscribe Custom sensor can now show text messages from your IoT devices. Define the Sensor Message JSONPath in the sensor settings and always see the latest message from your system in the sensor message.

Zoom Service Status

   We added the channel Webhooks to the Zoom Service Status sensor.

Improved

Security

User accounts

   You can set the Homepage URL of a PRTG user account or user group only to web pages of your PRTG instance as of this version. External domains are not allowed anymore to prevent redirects to potentially malicious pages.

Note: Previously defined homepage URLs that violate this rule will prevent you from saving changes to affected user account or user group settings. Please change the homepage URL to a valid page in this case to be able to save the settings again.

Web server

   Web pages in PRTG that do not require authentication like help and password recovery pages now return the X-Frame Options HTTP header DENY by default. This security improvement helps to prevent potential phishing attempts. Overriding the header value accordingly applies to these pages, see this Knowledge Base article.

Fixed

Sensors

Exchange (PowerShell) sensors

   Exchange (PowerShell) sensors now work with the recent Microsoft Exchange Server security update KB5001779 from April 13, 2021. After applying the Exchange Server update, Exchange (PowerShell) sensors showed a down status with the error message The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details.

This affected all Exchange (PowerShell) sensors.

    Exchange Backup (PowerShell)
    Exchange Database (PowerShell)
    Exchange Database DAG (PowerShell)
    Exchange Mail Queue (PowerShell)
    Exchange Mailbox (PowerShell)
    Exchange Public Folder (PowerShell)

Flow sensors
   

    NetFlow, IPFIX, and jFlow sensors now properly ignore flow timestamps if you define 0 as Active Flow Timeout. Previously, this approach only worked in some cases while in other cases flows were disregarded when using 0 as active flow timeout, resulting in incorrect monitoring data.
    We hardened the flow sensors against unexpected data in received flows that some devices like, for example, Huawei routers may send. In rare cases where this happened, the flow sensors were not able to monitor any flow data and remained in unknown status.

HTTP Transaction

   We fixed a memory leak that occurred when using the HTTP Transaction sensor in Alternate/Compatibility Mode.

OPC UA Custom

   The OPC UA Custom sensor now supports Int64 values. In previous versions, the sensor showed a down status when reading a node with an Int64 data type.

SNMP Library

   The SNMP Library sensor creates sensors and channels for all library OIDs that you select during sensor creation again. In previous versions, some sensor channels were missing after sensor creation if you selected more than one library OID from one category.

SNMP Trap Receiver and Syslog Receiver

   You can now use angle brackets (<>) in the message filter of SNMP Trap Receiver and Syslog Receiver sensors.

Fixed

Server

Auto-Update

   We improved the stability of auto-updates when PRTG updates to a 64-bit version from a 32-bit version. Previously, the auto-update sometimes failed in such cases and required a manual update.

Channel limits

   You can save Limits in sensor channel settings again when using comma as decimal separator. In the previous PRTG version 21.1.66, you received the error message Internal Error: '[value]' is not a valid floating point value when you tried to save the channel settings in this case.

Cluster

    Devices that you clone to a remote probe in a cluster are immediately synchronized to failover nodes again. In the previous PRTG version 21.1.66, failover nodes only showed the cloned device after a restart of the failover.
    Actions on notification contacts like creating, pausing, resuming, deleting are now immediately synchronized to failover nodes.

Gauges

   Device overview tabs show gauges of sensors with a 5-star priority with a proper minimum/maximum value range again. In previous versions, the gauges only showed the value range 0 to 1000.

Search

   The detailed search now properly works even if a search for objects with special characters returns more than 10 results. In previous versions, the More button that appears when more than 10 results are found opened an empty list of search results in such cases.

Startup

   We fixed an issue with the PRTG server that could not start in rare cases due to language files being used by another process.

Toplists

   We fixed the toplists of flow and packet sniffer sensors that only showed data for the most current toplist period in some cases.

User accounts

   You cannot pause the default PRTG System Administrator (user ID 100) account with another administrator account anymore. In previous versions, this was temporarily possible until a server restart and could result in inconsistent behavior of PRTG.

Fixed

Notifications

Execute HTTP Action

   HTTP notifications now use HTTP 1.1 by default to execute HTTP actions. In previous version, the HTTP version always fell back to 1.0, which could lead to issues with several notification targets like Atlassian Opsgenie, for example. If required, you can still switch back to HTTP 1.0 in the notification settings.

Fixed

System Information

Data
   The System table on System Information tabs correctly displays MAC addresses again even if they are returned via SNMP. In previous versions, MAC addresses returned via SNMP were not readable.

Fixed

Reports

PDF reports
   We fixed a layout issue that caused cut off graph legends with certain page format and orientation combinations in PDF reports.

Lab

Sensors

Beckhoff IPC System Health

   We added the experimental Beckhoff IPC System Health (BETA) sensor. The sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. We are looking forward to your feedback!
HPE 3PAR sensors
   You can try out the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA) with this version. Of course, your feedback is highly welcome!

    The HPE 3PAR Drive Enclosure (BETA) sensor monitors a drive enclosure of your HPE 3PAR storage system and shows status and temperature metrics.
    The HPE 3PAR Virtual Volume (BETA) sensor monitors a virtual volume of your HPE 3PAR storage system and shows the status as well as used and free space on the volume.

PowerShell Security Enhancement

   We fixed an issue with the parameter handling of custom EXE/Script sensors that occurred when the experimental feature PowerShell Security Enhancement was enabled. The issue could lead to non-functional EXE/Script sensors in some cases.

Veeam Backup Job Status Advanced
   
    The experimental Veeam Backup Job Status Advanced (BETA) sensor can now monitor backup jobs on Hyper-V platforms. Previously, the sensor creation failed with the error message An error occurred. invalid map in such cases.
    We fixed an issue with the Status channel that incorrectly showed the status Not Run Yet for a backup job in certain cases.

Improved

Various

Languages
   We updated the German language file.
All parts of PRTG
   Various other minor fixes and improvements, updated user manual

Changed

Sensors and API

HTTP Push Data Advanced and HTTP IoT Push Data Advanced sensors
   We fixed a typo in the Time Threshold (Minutes) property of HTTP Push Data Advanced and HTTP IoT Push Data Advanced sensors. The property is now correctly spelled timethreshold. If you modify or read out this property via the API (setobjectproperty.htm, getobjectproperty.htm), please change the misspelled timethreshhold to timethreshold if necessary.

Changed

Tree version

Tree version update

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

Changed

Sensors

REST Dell EMC sensors

   The REST Dell EMC sensors are now deprecated as we previously announced. REST Dell EMC sensors that you added in previous versions will continue to monitor after updating to PRTG 21.x.67, but you cannot add them anew. This affects the following sensor types.

    REST Dell EMC Capacity
    REST Dell EMC File System
    REST Dell EMC LUN
    REST Dell EMC Pool
    REST Dell EMC System Health

Please use the new Dell EMC Unity sensors instead to monitor your Dell EMC Unity storage system.

    Dell EMC Unity Enclosure Health v2
    Dell EMC Unity File System v2
    Dell EMC Unity Storage Capacity v2
    Dell EMC Unity Storage LUN v2
    Dell EMC Unity Storage Pool v2
    Dell EMC Unity VMware Datastore v2
 

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    New:

    Login:

    You can now login to PRTG via single single-on (SSO). As of PRTG 21.2.68, you can use Azure Active Directory (Azure AD) as SSO provider in PRTG. After configuring Azure AD for PRTG, enable single sign-on in the PRTG system administration and create a user group that uses single sign-on integration. The members of this user group will then use SSO via Azure AD to login to PRTG.

    Paessler PRTG Hosted Monitor:

    We added the cloud region US East for the hosting option of Paessler PRTG Hosted Monitor. Region transfers of instances between Europe and United States (and vice versa) are now possible. Please contact our support for according inquiries.

    Improved:

    Sensors:

    We improved the stability of Cloud HTTP v2 and Cloud Ping v2 sensors, which will result in less sensor timeouts than in previous versions. The sensors now also continue monitoring and show data for available regions even if one or more region is not working, and we added a PRTG Cloud Response channel for each region that shows the current status of a region.
    We implemented session sharing for the Dell EMC Unity v2 sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the Dell EMC system with every scan. Modbus TCP Custom: You can now create device templates that include the Modbus TCP Custom sensor. This enables you to add sensors of this sensor type via auto-discovery.
    You can now create device templates that include the Modbus TCP Custom sensor. This enables you to add sensors of this sensor type via auto-discovery.
    The MySQL v2 sensor now provides a dedicated setting for the SSL mode. The options you can choose are the same as the values of the MySQL sslmode parameter. Depending on your monitoring setup, for example with offline installations, you may have to change the setting for successful monitoring.

    Server:

    We upgraded the HTTP protocol that PRTG uses in HTTP POST requests to HTTP 1.1. PRTG uses POST requests at several places to call external endpoints. For example, this change affects the notification types email, push, and SMS. If required, you can still switch back to HTTP 1.0 in the according notification template settings.

    Notifications:

    We improved the usability of the SMS service provider setup, which will help you to more easily configure SMS notification delivery. All necessary fields now require you to fill them in before saving the settings to ensure you provide all necessary information. By default, the SMS configuration mode is now disabled if you have not had configured SMS delivery before.

    Fixed:

    Sensors:

    EXE/Script and EXE/Script Advanced sensors now escape round brackets in the Parameters field to prevent potential code injection.
    We fixed an issue with the MQTT Statistics sensor that showed wrong data after some time of monitoring in certain cases.
    We corrected the traffic calculation of NetFlow v9 and IPFIX sensors. The sensors reported too much traffic with certain combinations of flow fields.
    The VMware Host Hardware Status (SOAP) sensor properly reports errors again. In previous versions, the sensor did not show an alert state if a warning state was already present.
    The Windows Updates Status (PowerShell) sensor now properly applies the Port in SPN setting. In previous versions, the port was not correctly included in the SPN even if you enabled the setting.

    Server:

    We fixed an issue with API calls that returned no data in certain cases, for example, when querying System Information via /api/table.json.
    You can define the same values for upper and lower sensor channel limits again.
    We fixed an issue in the map designer that triggered an error dialog window with the message Error (Bad Request). Sorry, the selected object cannot be used here. This happened in the last PRTG version 21.2.67 when you tried to load the preview of an incompatible object type in the properties section of the map.
    We implemented stability improvements for probe connections after a PRTG server restart, which will be especially helpful if you have many remote probes.

    Lab:

    Sensors:

    You can try out the experimental REST Custom v2 (BETA) sensor as of this version. The sensor monitors the results of a JSON REST API call and will be the successor of the existing REST Custom sensor. We are looking forward to your feedback!
    The experimental Microsoft Azure SQL Database (BETA) now shows correct channel names.

    Improved:

    Various

    We updated the German language file.

    Various other minor fixes and improvements, updated user manual.
    Note:

    Sensors:

    We will discontinue the DNS sensor (v1) with the upcoming PRTG version 21.x.69. Running sensors of this type will still work for some more versions, but you will not be able to deploy them as of PRTG 21.x.69. If you use the sensor, we strongly recommend that you replace it with the superseding sensor type DNS v2 soon. If you encounter any remaining issues with the new DNS v2 sensor, please immediately contact us so that we can address them.

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    new Sensors:

    Veeam Backup Job Status Advanced:

    The new Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs on the Veeam Backup Enterprise Manager. The sensor monitors the status of the backup job, the duration, the time since the last run, and if the backup job is scheduled.
    We released this sensor type as experimental sensor in PRTG 21.1.65 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we resolved two more issue for this release.
    Adding a new Veeam Backup Job Status Advanced sensor works more reliably now. In certain scenarios, you could not add the sensor and received the error message An error occurred. The queried field is empty.
    We added the new lookup value None so that the sensor can now handle the combination job status idle and job result none. Previously, the sensor showed a down status with the error message An error occurred: Bad optional access in such cases.

    Dell EMC Unity Enclosure Health:

    The Dell EMC Unity Enclosure Health v2 sensor now can also monitor Power Consumption in a dedicated channel.

    MQTT Subscribe Custom:

    The MQTT Subscribe Custom sensor now supports up to 10 channels so that you can monitor up to 10 values from a subscribed MQTT topic with one sensor of this type.

    SNMP sensors:

    PRTG can now perform more SNMP v3 requests at the same time, so that monitoring with SNMP v3 sensors is more stable compared to previous versions.

    Security:

    Active Directory:

    PRTG now validates all fields that are imported from Active Directory when creating a new user account to close a potential XSS vulnerability. (CVE-2021-29643)

    Fixed Sensors:

    Microsoft Azure sensors:

    We improved the stability of the Microsoft Azure sensors. In previous versions, the sensors had connection issues in some cases, which resulted in wrong down and warning states.

    DNS v2:

    The Records Resolved channel of the DNS v2 sensor correctly uses a lookup with the states yes and no again.

    Microsoft 365 Service Status sensors:

    We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against unknown service states that Microsoft 365 may return. In such cases, the sensors previously showed a down status with the message error.generic[invalid map key].

    SNMP Printer:

    We improved the stability of the SNMP Printer sensor. In rare cases, the sensor showed a down status with the message No such instance (SNMP error # 223) after some time when monitoring certain types of printers.

    Fixed Server:

    API:

    API calls for tables with content=probenodes return all probes again.

    Auto-Discovery:

    Devices now keep their settings even after running an auto-discovery on this device. Previously, the first auto-discovery on a device occasionally overwrote your manually configured settings like names, icons, or tags.

    Graphs:

    The graph on the 2 days tabs of sensors shows the correct downtime again. In previous versions, the 2 days tab showed a wrong downtime in various cases, for example, always 0% even if there was a downtime reported and correctly shown in the data table. The percentage values on the y-axis of 2 day graphs are also back again.

    Single sign-on:

    Logging in with single sign-on now also works if you use an Azure AD group name (sAMAccountName) with upper-case letters as SSO Group Access Claim. We also fixed the misbehavior that PRTG logged out SSO user accounts after some time.

    Fixed WebGUI:

    Maps:

    We fixed a display issue on maps that affected channel gauges on View Map tabs. Sometimes, the gauge values of previously opened sensor pages erroneously appeared in gauge map objects instead of the real values until the page was refreshed.

    Lab Sensors:

    AWS EC2 v2:

    You can try out the experimental AWS EC2 v2 (BETA) sensor as of this version. The sensor monitors the performance of an Amazon EC2 and will be the successor of the existing Amazon CloudWatch EC2 sensor.

    AWS ELB v2:

    You can try out the experimental AWS ELB v2 (BETA) sensor as of this version. The sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor.

    HPE 3PAR sensors:

    We implemented session sharing for the HPE 3PAR sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the HPE 3PAR system with every scan.

    REST Custom v2:

    we fixed the Custom Headers of the REST Custom v2 sensor. In the last PRTG version, sending custom HTTP headers did not work correctly.

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

    HPE 3PAR Common Provisioning Group

    The new HPE 3PAR Common Provisioning Group sensor monitors the capacity of a common provisioning group (CPG) on an HPE 3PAR storage system. It shows the overall state of the CPG, as well as free, allocated, and used logical space, snapshot space, and user space.
    We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions.

    Microsoft Azure SQL Database

    The new Microsoft Azure SQL Database monitors metrics of an Azure SQL Database (single database or elastic pool) in a Microsoft Azure subscription. It can show, for example, CPU and disk usage, number of deadlocks, DTU and eDTU usage and limits, and sessions in percent.
    We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions.

    Microsoft Azure Storage Account

    The new Microsoft Azure Storage Account sensor monitors the storage account in a Microsoft Azure subscription and shows latency, traffic, and capacity metrics, as well as the number of request breakdowns.
    We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions.

    Improved:

    Sensors:

    Microsoft 365 sensors

    You can now create device templates that include the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced. This enables you to add these sensors via auto-discovery.

    Modbus TCP Custom

    We implemented session sharing for the Modbus TCP Custom sensor and the experimental Modbus RTU Custom sensor. Session sharing reduces the load on the monitored system compared to previous PRTG versions where each sensor created its own connection to the Modbus gateway.

    OPC UA Custom

    The OPC UA Custom sensor now supports up to 10 channels so that you can monitor up to 10 values returned by specific OPC UA node IDs with one sensor of this type.

    WMI Event Log

    The WMI Event Log sensor now supports filtering by multiple event IDs.

    Zoom Service Status

    You can now create device templates that include the Zoom Service Status sensor. This enables you to add sensors of this type via auto-discovery.

    Fixed:

    Sensors:

    MySQL (v1)

    Still existing instances of the deprecated sensor type MySQL (v1) work again and continue monitoring upon updating to PRTG 21.3.70 or later. In PRTG versions 21.2.68 and 21.3.69, they showed a down status with the error message parameter -sslmode is missing. Please note that we strongly recommend that you replace all sensors of the deprecated type MySQL (v1) with the MySQL v2 sensor.

    SNMP Custom Table

    Adding SNMP Custom Table sensors with an identification column other than table_index or ifindex properly works again. In previous versions, the sensors showed a down status after creation with error code PE247 in such cases.

    Fixed:

    Server:

    Active Directory:

    We fixed an issue with the login of Active Directory user accounts. If the display name or full name of a user in the Active Directory contained certain special characters like, for example, ampersand (&), a newly introduced security mechanism blocked the login in the last PRTG version 21.3.69. This also affected PRTG user accounts with two or more consecutive whitespaces in login or display name.

    Cluster

    Failover nodes in a PRTG cluster now keep the password of the PRTG System Administrator user account when you have changed it. In previous versions, the administrator password on failover nodes always reverted to default upon updating the PRTG server.
    Important: The PRTG default login with password prtgadmin will not work on failover nodes anymore upon updating to PRTG 21.3.70 or later. Please use the PRTG Administration Tool on the failover node to generate a new password.

    Device templates

    We fixed an issue with certain sensor types like the SNMP HPE ProLiant Memory Controller sensor that, if included, prevented a successful creation of device templates. The created template did not appear in the list of device templates in such cases.

    Single sign-on

    We fixed an issue with external callback URLs for the endpoint handling that included uppercase letters. In such cases, you could not login into PRTG via single sign-on and received the error message The URL you are using to connect to PRTG is not enabled for single sign-on.

    Time zones

    Status messages of down (acknowledged) and paused sensors now show the time zone of the user account instead of the server time. In the logs, the messages are displayed in server time.

    Fixed:

    WebGUI:

    Home page URL:

    Home page URLs with URL parameters that you define for PRTG user groups work again. In previous versions, parameters were removed from the URL so that the you did not land on the defined home page when you logged in into the PRTG web interface.
    Internet Explorer
    Adding new notification triggers and displaying existing triggers in Internet Explorer 11 works again.

    Lab:

    Sensors:

    AWS EC2 v2 and AWS ELB v2:

    We added comprehensible region names to the channels of the experimental AWS EC2 v2 and AWS ELB v2 sensors.

    Local Folder

    We introduce the experimental Local Folder (BETA) sensor with this version. The sensor monitors the number of files and folders in a local folder on the probe device, as well as its size and the age of oldest and newest files.

    Redfish System Health

    You can try out the experimental Redfish System Health (BETA) sensor as of this version. With this sensor, you can monitor the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac.

    Improved:

    Various:

    Languages:

    We updated and improved all language files.
    All parts of PRTG
    Various other minor fixes and improvements, updated user manual

[close]

http://www.paessler.com/prtg/download

[SiLæncer]

Changelog

Version 21.3.71.1416

New

Sensors

Beckhoff IPC System Health

   The new Beckhoff IPC System Health sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. It shows available memory, CPU load, the temperature of CPU and mainboard, as well as the status of the RAID controller.

We initially released this sensor type as experimental sensor in PRTG 21.2.67.

Modbus RTU Custom

   The new Modbus RTU Custom sensor connects to a Modbus RTU server and monitors up to five values returned by the device. With this sensor type, you can monitor, for example, temperature, humidity, and more inside a rack in your datacenter so that you can ensure your equipment operates within the defined ranges.

We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions.

Improved

Sensors

MQTT Subscribe Custom

   You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value with the MQTT Subscribe Custom sensor. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently.

Improved

Server

API
   The API call api/health.json now additionally returns the number of State objects, which corresponds to the number of currently logged in PRTG user accounts. We also added api/health.json to the public API documentation in the PRTG user manual.

Reports

   PRTG now generates your PDF and HTML reports much faster compared to previous versions. You will especially notice this performance improvement when running reports with a lot of sensors and historic data on large installations.

Fixed

Sensors

Common SaaS

   The Twitter channel of the Common SaaS sensor now supports response code 426. In previous versions, the sensor occasionally showed a warning status with the message Twitter API not available - HTTP/1.1 426 Upgrade Required if Twitter returned this code.

DNS v2

   You can add the DNS v2 sensor via auto-discovery again.

EXE/Script sensors

   We updated the sample PowerShell scripts that we deliver for EXE/Script sensors to work with the enabled PowerShell Security Enhancement setting. The scripts now use write-output instead of write-host. We also encourage you again to accordingly adapt your own scripts to write-output to successfully run your custom PowerShell sensors with enabled security enhancement.

Flow and Packet Sniffer sensors

   PRTG now properly handles whitespaces in group names and captions when you change the default groups and channels for Flow and Packet Sniffer sensors (via CustomFlowRules.osr, for example). In previous version, whitespaces led to a disabled Save button on the Settings tab of Flow and Packet Sniffer sensors.

HPE 3PAR sensors

   We fixed an issue with HPE 3PAR sensors that could cause the probe to stop monitoring if you had a certain number of running HPE 3PAR sensors on this probe. All sensors on the affected probe showed the unknown status in such cases. We also improved the stability of HPE 3PAR sensors in case of reconnects where the sensors previously were not able to recover from the down status in some cases.

The issues affected the HPE 3PAR Common Provisioning Group sensor, as well as the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA).

Modbus sensors

   We fixed connection issues of Modbus TCP Custom and Modbus RTU Custom sensors that appeared in the previous PRTG stable version 21.3.70. Modbus sensors were not able to connect to the target server if the initial attempt failed and showed a permanent down status with the error message The sensor could not retrieve data from the server or similar.

NetApp LUN

   The NetApp LUN sensor now shows 0% bytes free if the used size exceeds the allocated size, just like the NetApp in its own interface. In previous versions, the sensor showed a completely incorrect value in such cases.

VMware Virtual Machine (SOAP)

   Newly created VMware Virtual Machine (SOAP) sensors now have the Alarm when VM is powered off setting enabled by default.

Sensor creation

   The progress bar in the Working... dialog window that appears when you start adding certain sensor types now also properly visualizes the progress for various sensor types that we implemented over the last couple of PRTG versions.

Fixed

Security

User accounts

   Paused PRTG user accounts cannot resume other paused user accounts via the API anymore.

Version number

   PRTG no longer displays the current version number in the footer of the startup screen in the web interface. This improves security by not providing attackers potentially relevant information on a page that does not require a login.

Fixed

Server

Cluster
   Sensors on failover nodes in status Down (Acknowledged) show timestamps and names of the acknowledging user accounts in the sensor message again.

User accounts

   User accounts that are member of an Active Directory or single sign-on user group now open the defined homepage of their primary user group when they log in for the first time. In previous versions, they always started on the default welcome page.

Lab

Sensors

AWS ELB v2
   We added several new sensor channels for various metrics of application and network load balancers to the AWS ELB v2 (BETA) sensor.

AWS RDS v2

   You can try out the experimental AWS RDS v2 (BETA) sensor as of this version. The sensor monitors various metrics of your RDS instances and will be the successor of the existing Amazon CloudWatch RDS sensor.

Local Folder
   

    We added the option to define whether the Local Folder (BETA) sensor monitors only the specified folder (default) or all subfolders as well. You can define this behavior with the Recurse Subfolders setting.
    You can filter for specific files that you want to monitor. Enable the Filter by File Name setting, define if you want to include or exclude specific file names and file types, and so keep an eye on your most important files.
    You can now filter files by age. With this option you can monitor, for example, the success of certain automatic processes that create or modify files.
    We added a timeout setting, which is useful for larger filesystems to avoid a potential probe overload, and prevent defining UNC paths, which are not supported by the sensor.

Redfish Virtual Disk

   You can try out the experimental Redfish Virtual Disk (BETA) sensor as of this version. The sensor monitors the virtual disks of your Redfish capable servers and shows capacity and status.
REST Custom v2
   The REST Custom v2 (BETA) sensor now supports XML in addition to JSON and you can use XPath to define the sensor channels.

Improved

Various

Languages
   We updated the German language file and implemented some minor improvements for French and Russian.
All parts of PRTG
   Various other minor fixes and improvements, updated user manual

[close]

http://www.paessler.com/prtg/download