![]() ![]() You can try out the experimental SNMP Custom v2 sensor that we have rewritten to work on the Multi-Platform Probe. For example, the error message will include the HTTP status code of the REST response in case the parsing fails due to invalid JSON. We improved the error handling of the REST Custom v2 sensor that will now display an according error message in case of an error and will run into an error status.Please note that you have to provide the name of the lookup during sensor creation for now when you want to select a lookup file and that the lookup can only be edited in the channel settings after sensor creation. If you select lookup as channel type the sensor will be created using the given lookup file. Currently, all settings are visible when you enable the Channel # Custom Unit with Absolute (integer), Absolute (float) and Delta (counter) as value types. For custom units you can set a unit name now. Input fields for Channel # Lookup ID and Channel # Custom Unit are now available. You can now select unit types and lookups for each channel in the Channel Settings of your REST Custom v2 sensor.The setting resolves any issues on a device or group level where the API url has an extension other than. With this field you can define your API endpoint for the sensor types Cisco Meraki License (BETA) and Cisco Meraki Netwok Health (BETA) after unlocking it. We added a new setting Meraki Dashboard API EndPoint in the section Credentials for Cisco Meraki devices. ![]() We already announced the deprecation of NetApp v1 sensors with PRTG version 23. Note: Your running NetApp v1 sensors will no longer work when you update to ONTAP version 9.13.1. when it was used in cluster configurations. Previously, the sensor displayed an error with the message The queried field "space.available" is empty. Your NetApp Volume v2 sensor now reports volumes correctly in a NetApp MetroCluster configuration setting.We received valuable feedback and in addition to the functionality that the sensor already had in the last PRTG version, we resolved one more issue for this release. since NetApp delivers a new RESTful API for ONTAP based storage systems and former ONTAPI will reach end of availability soon. We first introduced the new NetApp v2 sensors as experimental with PRTG version 22. The new NetApp v2 sensors NetApp Aggregate v2, NetApp I/O v2, NetApp LIF v2, NetApp LUN v2, NetApp NIC v2, NetApp Physical Disk v2, NetApp SnapMirror v2 Sensor, NetApp System Health v2 and NetApp Volume v2 support the new ONTAP REST API as of ONTAP 9.6. We fixed an issue for the Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor In previous PRTG versions, the sensor reported an error when a private key with a length other then 2048 bits was used. The OPC UA Server Status sensor now supports Client Keys with a 4096 bit length for OPC Client Certificates. With this fix the sensor returns the average values. We fixed an issue for the Microsoft Azure Storage Account sensor's channel, Used Capacity, which was previously recording 0 values. The sensor displayed the error message regex_error(error_brace): The expression contained mismatched. We fixed an issue for the DNS v2 sensor where the character escaping for curly brackets } in the Filter Value did not work properly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |