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.
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.
0 kommentar(er)
