New Relic's integrations include an integration for reporting your Microsoft Azure NetApp Files metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported.
New Relic gathers metrics data from Azure Monitor for the Azure NetApp Files service. Azure NetApp Files is designed to provide high-performance file storage for enterprise workloads, provide high availability for your file storage needs and provides built-in data protection to help ensure the safe storage, availability and recoverability of your data.
Using New Relic, you can:
- View Azure NetApp Files data in pre-built dashboards.
- Run custom queries and visualize the data.
- Create alert conditions to notify you of changes in data.
Follow standard Azure Monitor integration procedure to activate your Azure service in New Relic infrastructure monitoring.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
New Relic queries your Azure NetApp Files service through Azure Monitor integration according to a default polling interval.
Find and use data
To explore your integration data, go to one.newrelic.com/infra > Azure > (select an integration).
This integration collects the following metric data.
Azure NetApp Files metrics
Average read latency in milliseconds per operation.
Average write latency in milliseconds per operation.
Is the backup policy suspended for the volume? 0 if yes, 1 if no.
Total bytes backed up for this Volume.
Total bytes transferred for last backup operation.
Did the last volume backup or restore operation complete successfully? 1 if yes, 0 if no.
Total bytes transferred for last backup restore operation.
Total bytes transferred for last backup or restore operation.
Is backup enabled for the volume? 1 if yes, 0 if no.
Other throughput (that is not read or write) in bytes per second.
Read in/out operations per second.
Read throughput in bytes per second
Sum of all throughput in bytes per second.
The provisioned size of a volume.
The percentage of the volume consumed including snapshots.
Data read in using GET per volume.
Data tiered out using PUT per volume.
Volume footprint for Cool Tier.
Logical size of the volume (used bytes).
Size of all snapshots in volume
Write in/out operations per second.
Write throughput in bytes per second.
Condition of the relationship, 1 or 0.
The amount of time in seconds by which the data on the mirror lags behind the source.
The amount of time in seconds it took for the last transfer to complete.
The total number of bytes transferred as part of the last transfer.
Total amount of data transferred for the current transfer operation.
Whether the status of the Volume Replication is 'transferring'.
Cumulative bytes transferred for the relationship.