Skip to content

Commit 658766d

Browse files
Update azure-netapp-files-metrics.md
Adding a note informing the user that the Throughput limit reached metrics is collected every 5 minutes.
1 parent 4bdbe7a commit 658766d

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,10 @@ 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 has not yet been reached.
59+
60+
> [!NOTE]
61+
> The Throughput limit reached metrics is collected every 5 minutes.
5962
6063
If the volume is hitting the throughput limit, it's not sized appropriately for the application's demands. To resolve throughput issues:
6164

0 commit comments

Comments
 (0)