Extend the platform, empower your team.
2.0 remote extension that collects important NetApp OnTap metrics from the OnTap 9.6+ REST API for use in Dynatrace.
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).
Connects to and collects data from the NetApp OnTap API. This REST API is available in OnTap 9.6+.
A NetApp OnTap Overview dashboard is included with the extension. This includes links to access the various OnTap entities detected.
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:
Metrics are associated with different feature sets that can be enabled or disabled as needed. Metrics will be collected once per minute.
Cannot be disabled.
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).
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:
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).
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.
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:
(16 + (3 x nodes) + (1 x frus) + (1 x svms) + (2 x disks) + (5 x aggregates) + (17 x volumes) + (6 x LUNs) x 60 min x 24 h x 365 days data points/year
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.
This extension will report log events in 2 situations:
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.
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.
In log monitoring classic, license consumption is based on the number of ingested log records.
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.
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual metrics can be activated and deactivated by your administrator during configuration.
No release notes