Metrics for Azure NetApp Files

Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume IOPS, and latency. By analyzing these metrics, you can gain a better understanding on the usage pattern and volume performance of your NetApp accounts.

You can find metrics for a capacity pool or volume by selecting the capacity pool or volume. Then click Metric to view the available metrics:

Snapshot that shows how to navigate to the Metric pull-down.

Usage metrics for capacity pools

  • Pool Allocated Size
    The provisioned size of the pool.

  • Pool Allocated to Volume Size
    The total of volume quota (GiB) in a given capacity pool (that is, the total of the volumes' provisioned sizes in the capacity pool).
    This size is the size you selected during volume creation.

  • Pool Consumed Size
    The total of logical space (GiB) used across volumes in a capacity pool.

  • Total Snapshot Size for the Pool
    The sum of snapshot size from all volumes in the pool.

Usage metrics for volumes

  • Percentage Volume Consumed Size
    The percentage of the volume consumed, including snapshots.
  • Volume Allocated Size
    The provisioned size of a volume
  • Volume Quota Size
    The quota size (GiB) the volume is provisioned with.
  • Volume Consumed Size
    Logical size of the volume (used bytes).
    This size includes logical space used by active file systems and snapshots.
  • Volume Snapshot Size
    The size of all snapshots in a volume.

Performance metrics for volumes

Note

Volume latency for Average Read Latency and Average Write Latency is measured within the storage service and does not include network latency.

  • Average Read Latency
    The average time for reads from the volume in milliseconds.
  • Average Write Latency
    The average time for writes from the volume in milliseconds.
  • Read IOPS
    The number of reads to the volume per second.
  • Write IOPS
    The number of writes to the volume per second.

Volume replication metrics

Note

  • Network transfer size (for example, the Volume replication total transfer metrics) might differ from the source or destination volumes of a cross-region replication. This behavior is a result of efficient replication engine being used to minimize the network transfer cost.
  • Volume replication metrics are currently populated for replication destination volumes and not the source of the replication relationship.
  • Is volume replication status healthy
    The condition of the replication relationship. A healthy state is denoted by 1. An unhealthy state is denoted by 0.

  • Is volume replication transferring
    Whether the status of the volume replication is ‘transferring’.

  • Volume replication lag time
    The amount of time in seconds by which the data on the mirror lags behind the source.

  • Volume replication last transfer duration
    The amount of time in seconds it took for the last transfer to complete.

  • Volume replication last transfer size
    The total number of bytes transferred as part of the last transfer.

  • Volume replication progress
    The total amount of data transferred for the current transfer operation.

  • Volume replication total transfer
    The cumulative bytes transferred for the relationship.

Throughput metrics for capacity pools

  • Pool allocated throughput
    Sum of the throughput of all the volumes belonging to the pool.

  • Provisioned throughput for the pool
    Provisioned throughput of this pool.

Throughput metrics for volumes

  • Read throughput
    Read throughput in bytes per second.

  • Total throughput
    Sum of all throughput in bytes per second.

  • Write throughput
    Write throughput in bytes per second.

  • Other throughput
    Other throughput (that is not read or write) in bytes per second.

Next steps