Supported metrics for Microsoft.ClassicStorage/storageAccounts/fileServices

The following table lists the metrics available for the Microsoft.ClassicStorage/storageAccounts/fileServices resource type.

Table headings

Metric - The metric display name as it appears in the Azure portal.
Name in Rest API - Metric name as referred to in the REST API.
Unit - Unit of measure.
Aggregation - The default aggregation type. Valid values: Average, Minimum, Maximum, Total, Count.
Dimensions - Dimensions available for the metric.
Time Grains - Intervals at which the metric is sampled. For example, PT1M indicates that the metric is sampled every minute, PT30M every 30 minutes, PT1H every hour, and so on.
DS Export- Whether the metric is exportable to Azure Monitor Logs via Diagnostic Settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.

For information on metric retention, see Azure Monitor Metrics overview.

Category	Metric	Name in REST API	Unit	Aggregation	Dimensions	Time Grains	DS Export
Transaction	Availability The percentage of availability for the storage service or the specified API operation. Availability is calculated by taking the TotalBillableRequests value and dividing it by the number of applicable requests, including those that produced unexpected errors. All unexpected errors result in reduced availability for the storage service or the specified API operation.	Availability	Percent	Average, Minimum, Maximum	GeoType, ApiName, Authentication, FileShare	PT1M	Yes
Transaction	Egress The amount of egress data, in bytes. This number includes egress from an external client into Azure Storage as well as egress within Azure. As a result, this number does not reflect billable egress.	Egress	Bytes	Total, Average, Minimum, Maximum	GeoType, ApiName, Authentication, FileShare	PT1M	Yes
Capacity	File Capacity The amount of storage used by the storage account's File service in bytes.	FileCapacity	Bytes	Average	FileShare	PT1H	No
Capacity	File Count The number of file in the storage account's File service.	FileCount	Count	Average	FileShare	PT1H	No
Capacity	File Share Count The number of file shares in the storage account's File service.	FileShareCount	Count	Average	<none>	PT1H	No
Capacity	File share quota size The upper limit on the amount of storage that can be used by Azure Files Service in bytes.	FileShareQuota	Bytes	Average	FileShare	PT1H	No
Capacity	File Share Snapshot Count The number of snapshots present on the share in storage account's Files Service.	FileShareSnapshotCount	Count	Average	FileShare	PT1H	No
Capacity	File Share Snapshot Size The amount of storage used by the snapshots in storage account's File service in bytes.	FileShareSnapshotSize	Bytes	Average	FileShare	PT1H	No
Transaction	Ingress The amount of ingress data, in bytes. This number includes ingress from an external client into Azure Storage as well as ingress within Azure.	Ingress	Bytes	Total, Average, Minimum, Maximum	GeoType, ApiName, Authentication, FileShare	PT1M	Yes
Transaction	Success E2E Latency The end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds. This value includes the required processing time within Azure Storage to read the request, send the response, and receive acknowledgment of the response.	SuccessE2ELatency	Milliseconds	Average, Minimum, Maximum	GeoType, ApiName, Authentication, FileShare	PT1M	Yes
Transaction	Success Server Latency The latency used by Azure Storage to process a successful request, in milliseconds. This value does not include the network latency specified in SuccessE2ELatency.	SuccessServerLatency	Milliseconds	Average, Minimum, Maximum	GeoType, ApiName, Authentication, FileShare	PT1M	Yes
Transaction	Transactions The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests which produced errors. Use ResponseType dimension for the number of different type of response.	Transactions	Count	Total	ResponseType, GeoType, ApiName, Authentication, FileShare	PT1M	Yes