Metrics

Per cluster

• Cluster IOPS (total)
• Cluster IOPS (read)
• Cluster IOPS (write)
• Cluster IOPS (other)
• Cluster latency (total)
• Cluster latency (read)
• Cluster latency (write)
• Cluster latency (other)
• Cluster throughput (total)
• Cluster throughput (read)
• Cluster throughput (write)
• Cluster throughput (other)
• Cluster block storage used
• Cluster block storage size
• Cluster block storage used percentage
• Cluster media storage used (by media type)
• Cluster media storage available (by media type)
• Cluster media storage size (by media type)
• Cluster media storage used percentage (by media type)
• Unassigned disk count

Per node

• Over temperature status
• FRU status counts (by status e.g. OK and error)
• Disk count
• Aggregate count
• Aggregate spare count

Per SVM

• SVM state
• Volume count
• Volume error count

Per disk

• Disk RPM
• Disk rated life used percentage

Per aggregate

• Block storaged used
• Block storage available
• Block storage size
• Block storage used percentage

Per volume

• Volume IOPS (total)
• Volume IOPS (read)
• Volume IOPS (write)
• Volume IOPS (other)
• Volume latency (total)
• Volume latency (read)
• Volume latency (write)
• Volume latency (other)
• Volume throughput (total)
• Volume throughput (read)
• Volume throughput (write)
• Volume throughput (other)

Supported Distributions

Requires an OnTap version with the REST API that was introduced in OnTap 9.6.

Licensing Consumption

Extension consumes DDUs at approximately the following rate per endpoint per year:

(16 + 4 * <number_of_media_types> + 6 * <number_of_nodes> + 3 * <number_of_svms> + 2 * <number_of_disks> + 4 * <number_of_aggregates> + 12 * <number_of_volumes>) * 525.6

Requirements

• NetApp OnTap version 9.6+ with REST API reachable
• OnTap user with 'http' application access that is assigned a rest-role with at least readonly access to the following API paths:
  • /api/cluster
  • /api/svm/svms
  • /api/storage/cluster
  • /api/storage/aggregates
  • /api/storage/disks
  • /api/storage/volumes

1. Environment ActiveGate server - Extract the extension zip file to the plugin_deployment folder of the remote plugin module
   • In a default installation this is done with unzip -o -d /opt/dynatrace/remotepluginmodule/plugin_deployment custom.remote.python.netapp_ontap.zip
   • Adjust the path if the Activegate was installed somewhere other than /opt/dynatrace
2. Browser - Upload the same extension zip file to your tenant
   • Settings > Monitored technologies > Custom extensions > Upload extension

Configuration

Create an endpoint for each cluster you would like to monitor. This is done in Settings > Monitored technologies > Custom extensions > Netapp Ontap.

The parameters are:

• OnTap URL
  • e.g. https://<ontap_cluster_url>/
• Username
  • For authenticating with API
• Password
  • For authenticating with API
• (Optional) Proxy host
• (Optional) Proxy user
• (Optional) Proxy password
• Verify SSL cert
  • Skip SSL cert validation if you have a self-signed certificate on the cluster URL
• Log level
  • Set to DEBUG if you are troubleshooting issues, otherwise keep on INFO

Custom entities

Cluster wide data will be reported to a Custom Device Group with the name of the discovered cluster. Each discovered node and SVM in the cluster will also be reported as individual Custom Devices within that group. These metrics will also be available for use in the Data Explorer and custom events for alerting like all other metrics.

Extension Logs

The logs under %PROGRAMDATA% (windows) or /var/lib (linux) give us more details in case of failures

The full path is /var/lib/dynatrace/remotepluginmodule/log/remoteplugin/custom.remote.python.netapp_ontap/OntapExtension.log

or C:\ProgramData\dynatrace\remotepluginmodule\log\remoteplugin\custom.remote.python.netapp_ontap/OntapExtension.log