Skip to technology filters Skip to main content
Dynatrace Hub

Extend the platform,
empower your team.

Popular searches:
Home hero bg
NetApp OnTap (Remote)NetApp OnTap (Remote)
NetApp OnTap (Remote)

NetApp OnTap (Remote)

Remote extension that collects NetApp OnTap metrics from the OnTap 9.6+ API.

Extension
Free trial
An example monitoring configuration with one clusterThe NetApp OnTap overview dashboardThe cluster entity screenThe volume entity screenThe node entity screenThe SVM entity screenThe aggregate entity screenThe disk entity screen
  • Product information
  • Release notes

Overview

Collect, view, and analyze metrics from your NetApp OnTap clusters in context with your hosts, applications, and services already being monitored by OneAgents. Make use of powerful charting and dashboarding capabilities as well as allow the Davis® AI causation engine to generate baselines and alert you when anomalies are detected in designated metrics. Metrics will be collected OnTap cluster-wide as well as for each of your nodes and storage virtual machines (SVMs).

Compatibility information

Connects to and collects data from the NetApp OnTap API. This REST API is available in OnTap 9.6+.

Details

Assets

A NetApp OnTap Overview dashboard is included with the extension. This includes links to access the various OnTap entities detected.

NetApp OnTap Overview dashboard

Metric events

Three metric event configurations are included with the extension. These must be enabled in the Metric events for alerting settings before they will be active:

  • OnTap Cluster monitoring unavailable
  • OnTap FRU in error state
  • High Temperature on OnTap Node

Metrics

Metrics are associated with different feature sets that can be enabled or disabled as needed. Metrics will be collected once per minute. Review the bottom of the Hub page for a breakdown of metrics.

Volume to VMware datastore linking

Starting with version 2.3.2 rules are included to allow linking of this extension's netapp_ontap:volume entity to the vmware:datastore from the VMware remote monitoring extension. Version 3.5.1 of the VMware extension is required for the necessary attributes to be collected. This linking is done via a "same as" relationship and is based on the volume's name matching the datastore's 'NAS remote path' property.

Installation

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

Dynatrace configuration

Find 'NetApp OnTap' in the in-product Extensions or Hub page and activate (if offline you can download the extension from this Hub page in the 'Versions' section and install as a custom extension).

Monitoring configurations

Once activated in your environment you can create monitoring configurations. Each monitoring configuration can have one or more OnTap clusters configured.

First select the desired ActiveGate group that will run the monitoring configuration.

For each cluster configure a NetApp OnTap Extension Endpoint:

  • OnTap REST API URL: URL (including protocol) to where OnTap API is available (e.g. https://ontap-prod/)
  • Cluster name: Used in naming the cluster entity (default is detected hostname)
  • Username: For API access
  • Password: For API access (check requirements section for needed permissions)
  • Proxy
    • Address: e.g. http://proxy.example.com:8080
    • Proxy username
    • Proxy password
  • Verify SSL certificate

The Frequency can be used to collect metrics less frequently than the default of once per minute. You may need to use this in large clusters where collecting all requested data would take longer than 1 minute.

The Log level will be set at the monitoring configuration level and will apply to all endpoints. INFO by default. DEBUG logging is only needed when investigating issues with support.

Finally, enable the desired feature sets (refer to the Details tab for what metrics are associated with which feature sets).

Monitoring configuration

Licensing

Licensing

There is no charge for obtaining the extension, only for the data (metrics & events) that the extension ingests. The details of license consumption will depend on which licensing model you are using. This will either be Dynatrace classic licensing or the Dynatrace Platform Subscription (DPS) model.

Metrics

License consumption is based on the number of metric data points ingested. The following formula will provide approximate annual data points ingested assuming all feature sets are enabled (formula must be adjusted if a lower frequency than once per minute used):

(16 + (4 x nodes) + (1 x frus) + (1 x svms) + (2 x disks) + (5 x aggregates) + (20 x volumes) +(4 x volume of svm with qos policy) + (3 x snapmirror relationships)) x 60 min x 24 h x 365 days data points/year

Classic licensing

In the classic licensing model, metric ingestion will consume Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point.

Multiply the above formula for annual data points by .001 to estimate annual DDU usage.

Log records

This extension will report log events in 2 situations:

  1. When a cluster node restart is detected
  2. When the extension cannot connect to the configured cluster API endpoint
    • Each minute will have another event reported until the issue is resolved and a successful connection occurs

Log management and analytics (powered by Grail)

License consumption is based on the size (in bytes) of data ingested & processed, retained, and queried so there is not a single formula to estimate the total consumption from this extension. Consult the log management and analytics documentation for details on the other dimensions that will effect license consumption.

Classic licensing

In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of 100 DDUs per Gigabyte of log records ingested.

Log monitoring classic

In log monitoring classic, license consumption is based on the number of ingested log records.

Classic licensing

In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of .0005 DDUs per ingested log record.

Multiply estimated ingested log records by .0005 to estimate DDU usage from log records.

Dynatrace
By Dynatrace
Dynatrace support center
Subscribe to new releases
Copy to clipboard

Extension content

Content typeNumber of items included
alerts
3
screen layout
9
screen logs cards
2
list screen layout
9
screen injections
1
metric metadata
66
screen metric tables
1
generic type
9
screen chart groups
21
dashboards
1
screen properties
10
screen entities lists
17
generic relationship
9

Feature sets

Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.

Feature setsNumber of metrics included
Metric nameMetric keyDescriptionUnit
LUN statenetapp.ontap.lun.stateThe state of the LUN. Normal states for a LUN are online and offline. Other states indicate errorsCount
LUN container statenetapp.ontap.lun.container_stateThe state of the volume and aggregate that contain the LUN. LUNs are only available when their containers are availableCount
LUN enabled statenetapp.ontap.lun.enabledThe enabled state of the LUN. LUNs can be disabled to prevent access to the LUN. 1 = enabled, 0 = disabledCount
LUN space usednetapp.ontap.lun.usedThe amount of space consumed by the main data stream of the LUNByte
LUN sizenetapp.ontap.lun.sizeThe total provisioned size of the LUNByte
LUN space used percentagenetapp.ontap.lun.used_percentageSpace used in the LUN as a percentagePercent
Metric nameMetric keyDescriptionUnit
Node uptimenetapp.ontap.node.uptimeHow long the node reports it has been runningSecond
Over temperaturenetapp.ontap.node.over_temperatureSpecifies whether the hardware is currently operating outside of its recommended temperature range (1 = "normal", 2 = "over").Count
Node membershipnetapp.ontap.node.membershipMembership status of the cluster nodeState
Node processor utilizationnetapp.ontap.node.processor_utilizationAverage CPU Utilization for the nodePercent
Metric nameMetric keyDescriptionUnit
SVM statenetapp.ontap.svm.stateCurrent SVM state: starting, running, stopping, stopped,or deletingCount
Metric nameMetric keyDescriptionUnit
Aggregate statenetapp.ontap.aggregate.stateCurrent aggregate state: online, onlining, offline, offlining, relocating, unmounted, restricted, inconsistent, failed, or unknownCount
Aggregate block storage usednetapp.ontap.aggregate.block_storage_usedSpace used or reserved in bytes. Includes volume guarantees and aggregate metadata.Byte
Aggregate block storage availablenetapp.ontap.aggregate.block_storage_availableSpace available in bytesByte
Aggregate block storage sizenetapp.ontap.aggregate.block_storage_sizeTotal usable space in bytes, not including WAFL reserve and aggregate Snapshot copy reserve.Byte
Aggregate block storage used percentagenetapp.ontap.aggregate.block_storage_used_percentPercentage of block storage usedPercent
Metric nameMetric keyDescriptionUnit
Volume statenetapp.ontap.volume.stateVolume state: error, mixed, offline, or onlineCount
Volume throughput (other)netapp.ontap.volume.throughput.other.countThe volume's rate of throughput bytes observed at the storage object (other)Byte
Volume throughput (read)netapp.ontap.volume.throughput.read.countThe volume's rate of throughput bytes observed at the storage object (read)Byte
Volume throughput (write)netapp.ontap.volume.throughput.write.countThe volume's rate of throughput bytes observed at the storage object (write)Byte
Volume throughput (total)netapp.ontap.volume.throughput.total.countThe volume's rate of throughput bytes observed at the storage object (total)Byte
Volume IOPS (other)netapp.ontap.volume.iops.other.countThe volume's number of I/O operations observed at the storage object (other)Count
Volume IOPS (read)netapp.ontap.volume.iops.read.countThe volume's number of I/O operations observed at the storage object (read)Count
Volume IOPS (write)netapp.ontap.volume.iops.write.countThe volume's number of I/O operations observed at the storage object (write)Count
Volume IOPS (total)netapp.ontap.volume.iops.total.countThe volume's number of I/O operations observed at the storage object (total)Count
Volume latency (total)netapp.ontap.volume.latency.totalThe volume's raw latency in microseconds observed at the storage object (total)MicroSecond
Volume latency (read)netapp.ontap.volume.latency.readThe volume's raw latency in microseconds observed at the storage object (read)MicroSecond
Volume latency (write)netapp.ontap.volume.latency.writeThe volume's raw latency in microseconds observed at the storage object (write)MicroSecond
Volume latency (other)netapp.ontap.volume.latency.otherThe volume's raw latency in microseconds observed at the storage object (other)MicroSecond
Volume sizenetapp.ontap.volume.sizeTotal provisioned sizeByte
Volume space availablenetapp.ontap.volume.availableThe available spaceByte
Volume space usednetapp.ontap.volume.usedVolume space used (including data and metadata)Byte
Volume space used percentagenetapp.ontap.volume.used_percentPercentage of volume space used (including data and metadata)Percent
-netapp.ontap.volume.files.maxiumum--
Files (inodes)netapp.ontap.volume.files.usedNumber of files (inodes) used for user-visible data permitted on the volume.Count
Files (inodes) used percentagenetapp.ontap.volume.files.used_percentagePercentage of the maximum number of files used on the volume.Percent
Metric nameMetric keyDescriptionUnit
Cluster IOPS (other)netapp.ontap.cluster.iops_other.countThe cluster's number of I/O operations observed at the storage object (other)Count
Cluster IOPS (read)netapp.ontap.cluster.iops_read.countThe cluster's number of I/O operations observed at the storage object (read)Count
Cluster IOPS (total)netapp.ontap.cluster.iops_total.countThe cluster's number of I/O operations observed at the storage object (total)Count
Cluster IOPS (write)netapp.ontap.cluster.iops_write.countThe cluster's number of I/O operations observed at the storage object (write)Count
Cluster throughput (other)netapp.ontap.cluster.throughput_other.countThe cluster's rate of throughput bytes observed at the storage object (other)Byte
Cluster throughput (read)netapp.ontap.cluster.throughput_read.countThe cluster's rate of throughput bytes observed at the storage object (read)Byte
Cluster throughput (total)netapp.ontap.cluster.throughput_total.countThe cluster's rate of throughput bytes observed at the storage object (total)Byte
Cluster throughput (write)netapp.ontap.cluster.throughput_write.countThe cluster's rate of throughput bytes observed at the storage object (write)Byte
Cluster latency (other)netapp.ontap.cluster.latency_other.countThe cluster's raw latency in microseconds observed at the storage object (other)MicroSecond
Cluster latency (read)netapp.ontap.cluster.latency_read.countThe cluster's raw latency in microseconds observed at the storage object (read)MicroSecond
Cluster latency (total)netapp.ontap.cluster.latency_total.countThe cluster's raw latency in microseconds observed at the storage object (total)MicroSecond
Cluster latency (write)netapp.ontap.cluster.latency_write.countThe cluster's raw latency in microseconds observed at the storage object (write)MicroSecond
Cluster block storage sizenetapp.ontap.cluster.block_storage_sizeThe size of the cluster's block storageByte
Cluster block storage usednetapp.ontap.cluster.block_storage_usedAmount of block storage on the cluster in useByte
Cluster block storage used percentagenetapp.ontap.cluster.block_storage_used_percentageThe percentage of the cluster's block storage that is currently in usePercent
Metric nameMetric keyDescriptionUnit
Cluster availabilitynetapp.ontap.cluster.availabilityConnectivity to the configured OnTap cluster URL as detected by the extensionPercent
Metric nameMetric keyDescriptionUnit
Rated life usednetapp.ontap.disk.rated_life_used_percentagePercentage of rated life usedPercent
Disk statenetapp.ontap.disk.stateCurrent disk state: broken, copy, maintenance, partner, pending, present, reconstructing, removed, spare, unfail, or zeroingCount
Metric nameMetric keyDescriptionUnit
Lag timenetapp.ontap.snapmirror.relationship.lag_timeThe time since the exported snapshot was createdSecond
Relationship statenetapp.ontap.snapmirror.relationship.stateThe state of the relationshipState
Relationship healthnetapp.ontap.snapmirror.relationship.healthIs the relationship healthy?State
Metric nameMetric keyDescriptionUnit
Volume QOS minimum throughput (IOPS)netapp.ontap.volume.qos.min_throughput_iopsThe minimum throughput in IOPS (volumes)Count
Volume QOS maximum throughput (IOPS)netapp.ontap.volume.qos.max_throughput_iopsThe maximum throughput in IOPS (volumes)Count
Volume QOS maximum throughput (Mbps)netapp.ontap.volume.qos.max_throughput_mbpsThe maximum throughput in Mbps (volumes)MegaBytePerSecond
Volume QOS minimum throughput (Mbps)netapp.ontap.volume.qos.min_throughput_mbpsThe minimum throughput in Mbps (volumes)MegaBytePerSecond
SVM QOS minimum throughput (IOPS)netapp.ontap.svm.qos.min_throughput_iopsThe minimum throughput in IOPS (svms)Count
SVM QOS maximum throughput (IOPS)netapp.ontap.svm.qos.max_throughput_iopsThe maximum throughput in IOPS (svms)Count
-netapp.ontap.svm.qos.max_throughput_mbps--
SVM QOS minimum throughput (Mbps)netapp.ontap.svm.qos.min_throughput_mbpsThe minimum throughput in Mbps (svms)MegaBytePerSecond
Metric nameMetric keyDescriptionUnit
FRU statenetapp.ontap.node.fru.stateState of the field replaceable unit (100% for OK 0% for ERROR))Percent

Full version history

To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate

Full version history

  • Uses detected OnTap version to selectively query for fields/metrics that were added in later OnTap versions
    • The previous extension version used the 'ignore_unknown_fields' parameter on queries however it was found that this parameter was temporarily removed in some versions which would result in query failures if used.

Full version history

  • Sets parameter on calls to not fail if a requested field is not present
    • Fixes issue where collection on older versions of OnTap could fail if a given field were not present
  • Adds credential vault support
  • Handles reporting of 'offline' LUNs
  • Corrects mix-up of metric metadata for 2 keys

Full version history

  • new snapmirror relationship feature set
  • new qos feature set
    • qos metrics collected per applicable svm and volume
  • inode metrics reported for volumes
  • processor utilization metric added to cluster nodes
  • metrics/entities reported for SnapMirror relationships
  • topology rules to allow linking an OnTap volume to a VMware datastore
    • Requires use of the VMware extension (3.5.1+) (not legacy integration)
  • Small fixes including setting a larger resolution for 'currently monitoring' tiles on default dashboard
    • resolves issue where with multiple monitoring configurations at lower frequencies inconsistent values could be displayed

Full version history

  • Topology changes
    • There are some significant changes in topology rules for entities and relationships in this version. These changes are made to ensure consistency in how entities detected and to avoid scenarios where a changed name or moving a volume would have resulted in new entities being detected
    • Due to this change once applied you will see new entities created and relationships being formed for the following entity types:
      • Nodes
      • SVMs
      • Aggregates
      • Volumes
    • It may take upwards of an hour for you to see all of the changes reflected in the UI entities and relationships due to the need for the old entities and relationships to "age out"
    • If you have configurations such as metric alerts that were made for specific entity IDs as opposed to using rules around properties you will need to update these to use the new entities
    • This is a one-off necessary change that was identified and similar changes that may 'break' existing configs are always avoided as much as possible
  • LUN metrics are now collected
    • You must enable the 'luns' feature set for any existing configurations after updating
  • Bug fixes
    • Properly report the configured and detected name of the cluster
    • Updated rule for detecting clusters and nodes to ensure reported log entries for one type do not mistakenly create an entity of the other type

Full version history

  • handle issue that would prevent volume collection caused by volumes reported with very few fields populated
  • improved logging of certain errors

Full version history

No release notes

Dynatrace Hub
Hub HomeGet data into DynatraceBuild your own app
Log Management and AnalyticsKubernetesAI/ML ObservabilityInfrastructure ObservabilitySoftware DeliveryApplication ObservabilityApplication SecurityDigital ExperienceBusiness Analytics
Filter
Type
Built and maintained by
Deployment model
SaaS
  • SaaS
  • Managed
Partner FinderBecome a partnerDynatrace Developer

12 Results

Found in 'All'

Alicloud Extension logo

Alicloud Extension

Automatically discover, baseline, and monitor Alicloud environment components.

Technology by Phenisys
  • alibaba
  • alicloud
  • cloud
  • ECS
Mulesoft Cloudhub (Extension v2) logo

Mulesoft Cloudhub (Extension v2)

Gather metrics and topology from your Anypoint Cloudhub applications

Extension
Cloudflare (extension) logo

Cloudflare (extension)

Collect notification history and various metrics from your Cloudflare accounts.

Extension
  • cloudflare
  • extension
Google Kubernetes Engine (GKE) logo

Google Kubernetes Engine (GKE)

Harness automation and AI to simplify Kubernetes observability at scale.

Technology
  • cloud-extension
  • apm
  • autopilot
  • cloud
  • container
  • full-stack
  • gke
  • infrastructure
  • k8s
  • Kubernetes
  • log-analytics
  • microservices
  • platform
  • pods
Azure Kubernetes Service (AKS) logo

Azure Kubernetes Service (AKS)

Harness automation and AI to simplify Kubernetes observability at scale.

Technology
  • cloud-extension
  • aks
  • apm
  • azure
  • cloud
  • container
  • full-stack
  • infrastructure
  • k8s
  • Kubernetes
  • log-analytics
  • microservices
  • platform
  • pods
Azure App Service logo

Azure App Service

Intelligent end-to-end observability for serverless and hybrid environments using Azure App Services.

Technology
  • cloud-extension
  • cloud
  • serverless
NetApp OnTap (Remote) logo

NetApp OnTap (Remote)

Remote extension that collects NetApp OnTap metrics from the OnTap 9.6+ API.

Extension
  • cloud-extension
  • 2.0
  • cloud storage
  • netapp
  • ontap
Azure Virtual Machines logo

Azure Virtual Machines

Intelligent end-to-end observability for cloud environments using Azure Virtual machines.

Technology
  • cloud-extension
  • cloud
Serverless logo

Serverless

Seamless integration with serverless technologies to eliminate blind spots through OOTB integrations with AWS, Azure, and Google Cloud.

Technology
  • cloud-extension
  • cloud
  • container
  • faas
  • serverless
  • serverless function
Azure Service-Fabric logo

Azure Service-Fabric

Intelligent end-to-end observability for serverless and hybrid environments using Azure Service Fabric.

Technology
  • cloud-extension
  • cloud
  • container
AWS Fargate logo

AWS Fargate

Intelligent end-to-end observability for serverless and hybrid environments using AWS Fargate.

Technology
  • cloud-extension
  • cloud
  • container
  • ECS
  • EKS
  • serverless
Amazon Elastic Kubernetes Service (EKS) logo

Amazon Elastic Kubernetes Service (EKS)

Harness automation and AI to simplify Kubernetes observability at scale.

Technology
  • cloud-extension
  • apm
  • aws
  • azure kubernetes service
  • cloud
  • container
  • EKS
  • full-stack
  • infrastructure
  • k8s
  • log-analytics
  • microservices
  • platform
  • pods