PRTG Manual: NetApp I/O v2 Sensor
The NetApp I/O v2 sensor monitors input and output operations of a NetApp storage system via the Representational State Transfer (REST) application programming interface (API) using ONTAP as of version 9.11.
This sensor was converted to a new framework so that it will continue to function after the changes of the ONTAP REST API. This sensor now requires permissions for the ONTAP REST API and credentials for NetApp in settings that are higher in the object hierarchy, for example, in the settings of the parent device.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: NetApp I/O v2
- French: NetApp I/O v2
- German: NetApp I/O v2
- Japanese: NetApp I/O v2
- Portuguese: NetApp I/O v2
- Russian: NetApp I/O v2
- Simplified Chinese: NetApp I/O v2
- Spanish: E/S NetApp v2
- This sensor requires an ONTAP System Manager user account with specific access rights.
- This sensor requires permissions for the ONTAP REST API.
- This sensor requires ONTAP as of version 9.11. If you want to use NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to version 9.10, use the NetApp I/O sensor.
- This sensor requires credentials for NetApp in settings that are higher in the object hierarchy.
- This sensor supports IPv6.
- This sensor has a very low performance impact.
Requirement |
Description |
---|---|
This sensor requires an ONTAP System Manager user account with the role readonly and with access to the HTTP application with Password authentication. |
|
This sensor requires the role readonly with the following permissions for the ONTAP REST API: Access level Read-Only:
Access level Read/Write:
Access level None:
|
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Setting |
Description |
---|---|
Node Name |
The name of the node that this sensor monitors. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
The minimum scanning interval of this sensor is 1 minute.
The recommended scanning interval of this sensor is 1 minute.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Bytes Read |
The number of bytes read |
Bytes Written |
The number of bytes written |
CIFS Read |
The CIFS read speed |
CIFS Total Ops |
The number of CIFS operations
|
CIFS Write |
The CIFS write speed |
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
FCP Read |
The FCP read speed |
FCP Total Ops |
The number of FCP operations |
FCP Write |
The FCP write speed |
iSCSI Read |
The iSCSI read speed |
iSCSI Total Ops |
The number of iSCSI operations |
iSCSI Write |
The iSCSI read speed |
NFS Read |
The NFS read speed |
NFS Total Ops |
The number of NFS operations |
NFS Write |
The NFS write speed |
Total Ops |
The number of operations |
KNOWLEDGE BASE
What security features does PRTG include?