Skip to content

Commit f1b600a

Browse files
committed
acrolinx
1 parent fc567ee commit f1b600a

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

articles/azure-netapp-files/azure-netapp-files-metrics.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: anfdocs
1010
---
1111
# Metrics for Azure NetApp Files
1212

13-
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.
13+
Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume I/OPS, and latency. By analyzing these metrics, you can gain a better understanding on the usage pattern and volume performance of your NetApp accounts.
1414

1515
## Definitions
1616

@@ -189,7 +189,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
189189
## Performance metrics for volumes
190190

191191
> [!NOTE]
192-
> Volume latency for *Average Read Latency* and *Average Write Latency* is measured within the storage service and does not include network latency.
192+
> Volume latency for *Average Read Latency* and *Average Write Latency* is measured within the storage service and doesn't include network latency.
193193
194194
- *Average Read Latency*
195195
The average roundtrip time (RTT) for reads from the volume in milliseconds.
@@ -222,7 +222,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
222222
Lag time is the actual amount of time the replication lags behind the source. It indicates the age of the replicated data in the destination volume relative to the source volume.
223223

224224
> [!NOTE]
225-
> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume will not catch up to the source. To resolve this issue, adjust the replication speed or the replication schedule.
225+
> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume won't catch up to the source. To resolve this issue, adjust the replication speed or the replication schedule.
226226
227227
- *Volume replication last transfer duration*
228228
The amount of time in seconds it took for the last transfer to complete.
@@ -248,15 +248,18 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
248248
## Throughput metrics for volumes
249249

250250
* *Read throughput*
251+
251252
Read throughput in bytes per second.
252253

253254
* *Total throughput*
254255
Sum of all throughput in bytes per second.
255256

256257
* *Write throughput*
258+
257259
Write throughput in bytes per second.
258260

259261
* *Other throughput*
262+
260263
Other throughput (that isn't read or write) in bytes per second.
261264

262265
* *Total throughput*
@@ -266,24 +269,31 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
266269
## Volume backup metrics
267270

268271
* *Is Volume Backup Enabled*
272+
269273
Shows whether backup is enabled for the volume. `1` is enabled. `0` is disabled.
270274

271275
* *Is Volume Backup Operation Complete*
276+
272277
Shows whether the last volume backup or restore operation is successfully completed. `1` is successful. `0` is unsuccessful.
273278

274279
* *Is Volume Backup Suspended*
280+
275281
Shows whether the backup policy is suspended for the volume. A value of `1` means it's not suspended. A value of `0` means it's suspended.
276282

277283
* *Volume Backup Bytes*
284+
278285
The total bytes backed up for this volume.
279286

280287
* *Volume Backup Last Transferred Bytes*
288+
281289
The total bytes transferred for the last backup or restore operation.
282290

283291
* *Volume Backup Operation Last Transferred Bytes*
292+
284293
Total bytes transferred for last backup operation.
285294

286295
* *Volume Backup Restore Operation Last Transferred Bytes*
296+
287297
Total bytes transferred for last backup restore operation.
288298

289299
## Cool access metrics

0 commit comments

Comments
 (0)