Skip to content

Commit 8191239

Browse files
Merge pull request #297250 from b-ahibbard/maxfiles-2-38
new maxfiles metrics
2 parents 527812b + eb6ea31 commit 8191239

File tree

3 files changed

+29
-7
lines changed

3 files changed

+29
-7
lines changed

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

Lines changed: 22 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 03/18/2025
8+
ms.date: 04/16/2025
99
ms.author: anfdocs
1010
---
1111
# Metrics for Azure NetApp Files
@@ -150,21 +150,39 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
150150

151151
Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume I/OPS, and latency. Use these metrics to understand usage and performance.
152152

153-
- *Percentage Volume Consumed Size*
153+
- *Percentage Volume Consumed Size*
154+
154155
The percentage of the volume consumed, including snapshots.
155156
Aggregation metrics (for example, min, max) aren't supported for percentage volume consumed size.
156-
- *Volume Allocated Size*
157+
- *Volume Allocated Size*
158+
157159
The provisioned size of a volume
158160
- *Volume Quota Size*
161+
159162
The quota size (GiB) the volume is provisioned with.
160163
- *Volume Consumed Size*
164+
161165
Logical size of the volume (used bytes).
162166
This size includes logical space used by active file systems and snapshots.
163167
- *Volume Snapshot Size*
168+
164169
The size of all snapshots in a volume.
170+
- *Volume Inodes Quota*
171+
172+
The volume's maximum allowed [inodes (or `maxfiles`)](maxfiles-concept.md) if the limit was increased via support request. If the limit hasn't been increased via support request, this metric's value is 0.
173+
174+
- *Volume Inodes Total*
175+
176+
The volume's maximum allowed [inodes (or `maxfiles`)](maxfiles-concept.md) based on the volume size.
177+
- *Volume Inodes Used*
178+
179+
The volume's used [inodes (or `maxfiles`)](maxfiles-concept.md).
180+
165181
- *Volume Inodes Percentage*
166182

167-
The percentage of the volume's available [inodes (or `maxfiles`)](maxfiles-concept.md) consumed.
183+
The percentage of the volume's available [inodes (or `maxfiles`)](maxfiles-concept.md) consumed.
184+
185+
If the volume inode limit has been increased by a support request, the percentage is calculated based on Volume Inodes Quota metric. If the volume inode limit is the default value based on the volume size, the percentage is calculated based on the Volume Inodes Total metric.
168186

169187
- *Throughput limit reached*
170188

articles/azure-netapp-files/maxfiles-concept.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 03/18/2025
8+
ms.date: 04/16/2025
99
ms.author: anfdocs
1010
---
1111
# Understand `maxfiles` limits in Azure NetApp Files
@@ -41,7 +41,7 @@ The following table shows examples of the relationship `maxfiles` values based o
4141
| 200 TiB (214,748,364,800 KiB) | 6,375,342,024 |
4242
| 500 TiB (536,870,912,000 KiB) | 15,938,355,048 |
4343

44-
To see the `maxfiles` allocation for a specific volume size, check the **Maximum number of files** field in the volume’s overview pane. You can also view the `maxfiles` consumption for a volume as a percentage in [Azure monitor](azure-netapp-files-metrics.md#volumes).
44+
To see the `maxfiles` allocation for a specific volume size, check the **Maximum number of files** field in the volume’s overview pane. You can also view metrics for available and consumed `maxfiles` in [Azure monitor](azure-netapp-files-metrics.md#volumes).
4545

4646
:::image type="content" source="./media/azure-netapp-files-resource-limits/maximum-number-files.png" alt-text="Screenshot of volume overview menu." lightbox="./media/azure-netapp-files-resource-limits/maximum-number-files.png":::
4747

articles/azure-netapp-files/whats-new.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: b-hchen
66
ms.service: azure-netapp-files
77
ms.custom: linux-related-content
88
ms.topic: overview
9-
ms.date: 04/01/2025
9+
ms.date: 04/16/2025
1010
ms.author: anfdocs
1111
---
1212

@@ -16,6 +16,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
1616

1717
## April 2025
1818

19+
* [New volume usage metrics:](azure-netapp-files-metrics.md#volumes) Volume Inodes Quota, Volume Inodes Total, Volume Inodes Used
20+
21+
Azure NetApp Files supports [new metrics](azure-netapp-files-metrics.md#volumes) to monitor consumption of [inodes (also known as maxfiles)](maxfiles-concept.md), which is the maximum number of files a volume can hold. These metrics are especially useful for workloads with high file counts, such as high-performance compute (HPC) or electronic design automation (EDA), where you might have millions of small files. By monitoring these metrics, you can avoid running out of inodes thus keeping your storage running smoothly and making it easier to plan for future needs.
22+
1923
* [File access logs](manage-file-access-logs.md) (preview)
2024

2125
File Access Logs provides detailed logging of file access activities, including user identity, operation type, and timestamps, enhancing security, reliability, and operational insights. It supports SMB, NFSv4.1, and dual-protocol volumes, offering valuable features for monitoring unauthorized access, tracing activity for compliance, resolving incidents, and optimizing data usage patterns. By embedding this capability, you can strengthen your organization's security posture, maintain system reliability, and achieve operational excellence in alignment with the Well-Architected Framework security best practices. Azure NetApp Files file access logs play a critical role in safeguarding sensitive data, detecting anomalies while enabling operational excellence.

0 commit comments

Comments
 (0)