Monitoring data reference for Azure Files

Here’s a concise summary of the "Azure Files monitoring data reference" article.

Overview

This page documents monitoring reference data for Azure Files and links to the main guide: Monitor Azure Files (https://docs.azure.cn/en-us/storage/files/storage-files-monitoring).
Last updated: 01/02/2025.

Applies to

Metrics (platform metrics available in Azure Monitor)

Metrics are grouped by resource type and category. They are also part of Azure Monitor’s global metrics set and follow the platform metric retention rules (see Azure Monitor Metrics overview link).
Each metric entry includes: display name, REST API name, unit, default aggregation, available dimensions, sampling time grains (e.g., PT1M, PT1H), and whether it can be exported via Diagnostic Settings.

Supported metrics for Microsoft.Storage/storageAccounts

Category: Capacity
- Used capacity (UsedCapacity) — Bytes, Average, sampled PT1H, not exportable.
Category: Transaction
- Availability, Egress, Ingress, Success E2E Latency, Success Server Latency, Transactions — various units and aggregations, PT1M sampling, exportable via Diagnostic Settings. Dimensions include GeoType, ApiName, Authentication and other dimensions where noted.

Supported metrics for Microsoft.Storage/storageAccounts/fileServices (file-service-specific)

Category: Capacity
- FileCapacity, FileCount, FileShareCapacityQuota, FileShareCount, FileShareProvisionedBandwidthMiBps, FileShareProvisionedIOPS, FileShareSnapshotCount, FileShareSnapshotSize — Bytes/Count/CountPerSecond, sampled PT1H, per-file-share and/or tier dimensions where applicable; not exportable.
Category: Transaction
- Similar transaction metrics as storageAccounts plus file-share specific metrics:
  - FileShareAvailableBurstCredits, FileShareMaxUsedBandwidthMiBps, FileShareMaxUsedIOPS, FileSharePaidBurstingBandwidth, FileSharePaidBurstingIOS — mostly sampled at PT1M; many are not exportable.
- Standard transaction metrics (Availability, Egress, Ingress, Latencies, Transactions) are available and exportable. FileShare dimension applies only to premium file shares.

Metric dimensions (explanations of metric dimensions)

Important dimensions and notes:
- GeoType — Primary or Secondary (applies to RA-GRS reads).
- ResponseType — Many detailed response/error categories (Success, various server/client errors, throttling categories including share-specific throttling, success-with-throttling variants, metadata warnings/throttling, etc.).
- ApiName — Operation name (or "Unknown" if not identified).
- Authentication — AccountKey, SAS, DelegationSas, OAuth, Anonymous, AnonymousPreflight.
- TransactionType — User or System.
Note: FileShare dimension is only available for premium file shares. For per-share metrics on standard shares, create one share per storage account.

Resource logs (resource-level logging)

Lists resource log categories you can collect (StorageRead, StorageWrite, StorageDelete) for fileServices.
When routed to Azure Monitor Logs, these use the StorageFileLogs table (Storage File Service Logs Schema).
Basic log plan and ingestion-time transformations are supported; exporting has associated costs.

Azure Monitor Logs tables (relevant tables)

Fields for resource logs (main properties and descriptions)

Fields that describe the operation: time, resourceId, category, operationName, operationVersion, schemaVersion, statusCode, statusText, durationMs, callerIpAddress, correlationId, location, protocol, uri, etc.
Fields that describe authentication: identity/type, identity/tokenHash (formats depend on auth type), authorization details (action, denyAssignmentId, reason, result, roleAssignmentId, type), principals info, properties/metricResponseType, properties/objectKey, requester fields, delegatedResource fields, etc.
Fields that describe the service: accountName, requestUrl, userAgentHeader, referrerHeader, clientRequestId, etag, serverLatencyMs, serviceType, operationCount, sizes of headers/bodies, MD5 fields, lastModifiedTime, conditionsUsed, contentLengthHeader, tlsVersion, multiple SMB-specific fields (treeConnectID, persistent/volatile handle IDs, messageID, creditsConsumed, command details, FileId, SessionID, command major/minor), accessTier, sourceAccessTier, rehydrationPriority, downloadRange, etc.

Activity log

The article references the Microsoft.Storage resource provider operations list for operations that may appear in the activity log and links to activity log schema information.