Skip to content

Commit 180a778

Browse files
Update azure-netapp-files-metrics.md
Correcting issues
1 parent 658766d commit 180a778

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
4343

4444
- *Percentage Volume Consumed Size*
4545
The percentage of the volume consumed, including snapshots.
46-
Aggregation metrics (for example, min, max) are not supported for percentage volume consumed size.
46+
Aggregation metrics (for example, min, max) aren't supported for percentage volume consumed size.
4747
- *Volume Allocated Size*
4848
The provisioned size of a volume
4949
- *Volume Quota Size*
@@ -55,7 +55,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
5555
The size of all snapshots in a volume.
5656
- *Throughput limit reached*
5757

58-
Throughput limit reached is a boolean metric that denotes the volume is hitting its QoS limits. The value 1 means that the volume has reached its maximum throughput, and throughput for this volume will be throttled. The value 0 means this limit has not yet been reached.
58+
Throughput limit reached is a boolean metric that denotes the volume is hitting its QoS limits. The value 1 means that the volume has reached its maximum throughput, and throughput for this volume will be throttled. The value 0 means this limit hasn't yet been reached.
5959

6060
> [!NOTE]
6161
> The Throughput limit reached metrics is collected every 5 minutes.

0 commit comments

Comments
 (0)