| title | description | ms.date | ms.custom | ms.topic | author | ms.author | ms.service |
|---|---|---|---|---|---|---|---|
Monitor Azure Blob Storage | Start here to learn how to monitor Azure Blob Storage. | 02/07/2024 | horz-monitor | conceptual | normesta | normesta | azure-blob-storage |
[!INCLUDE horz-monitor-intro]
Important
Metrics and logs in Azure Monitor support only Azure Resource Manager storage accounts. Azure Monitor doesn't support classic storage accounts. If you want to use metrics or logs on a classic storage account, you need to migrate to an Azure Resource Manager storage account. For more information, see Migrate to Azure Resource Manager.
[!INCLUDE horz-monitor-insights]
Azure Storage insights offer a unified view of storage performance, capacity, and availability. See Monitor storage with Azure Monitor Storage insights.
[!INCLUDE horz-monitor-resource-types]
[!INCLUDE horz-monitor-data-storage]
[!INCLUDE horz-monitor-platform-metrics] For a list of available metrics for Azure Blob Storage, see Azure Blob Storage monitoring data reference.
[!INCLUDE horz-monitor-resource-logs] For the available resource log categories, their associated Log Analytics tables, and the logs schemas for Azure Blob Storage, see Azure Blob Storage monitoring data reference.
Note
Data Lake Storage doesn't appear as a storage type because Data Lake Storage is a set of capabilities available to Blob storage.
For general destination limitations, see Destination limitations. The following limitations apply only to monitoring Azure Storage accounts.
You can't send logs to the same storage account that you're monitoring with this setting. This would lead to recursive logs in which a log entry describes the writing of another log entry. You must create an account or use another existing account to store log information.
You can't set a retention policy.
If you archive logs to a storage account, you can manage the retention policy of a log container by defining a lifecycle management policy. To learn how, see Optimize costs by automating Azure Blob Storage access tiers.
If you send logs to Log Analytics, you can manage the data retention period of Log Analytics at the workspace level or even specify different retention settings by data type. To learn how, see Change the data retention period.
[!INCLUDE horz-monitor-activity-log]
[!INCLUDE horz-monitor-analyze-data]
[!INCLUDE horz-monitor-external-tools]
Metrics for Azure Blob Storage are in these namespaces:
- Microsoft.Storage/storageAccounts
- Microsoft.Storage/storageAccounts/blobServices
For a complete list of the dimensions that Azure Storage supports, see Metrics dimensions.
You can analyze metrics for Azure Storage with metrics from other Azure services by using Metrics Explorer. Open Metrics Explorer by choosing Metrics from the Azure Monitor menu. For details on using this tool, see Analyze metrics with Azure Monitor metrics explorer.
This example shows how to view Transactions at the account level.
For metrics that support dimensions, you can filter the metric with the desired dimension value. This example shows how to view Transactions at the account level on a specific operation by selecting values for the API Name dimension.
You can list the metric definition of your storage account or the Blob storage service. Use the Get-AzMetricDefinition cmdlet.
In this example, replace the <resource-ID> placeholder with the resource ID of the entire storage account or the resource ID of the Blob storage service. You can find these resource IDs on the Endpoints pages of your storage account in the Azure portal.
$resourceId="<resource-ID>"Get-AzMetricDefinition-ResourceId $resourceIdYou can read account-level metric values of your storage account or the Blob storage service. Use the Get-AzMetric cmdlet.
$resourceId="<resource-ID>"Get-AzMetric-ResourceId $resourceId-MetricName "UsedCapacity"-TimeGrain 01:00:00When a metric supports dimensions, you can read metric values and filter them by using dimension values. Use the Get-AzMetric cmdlet.
$resourceId="<resource-ID>"$dimFilter= [String](New-AzMetricFilter-Dimension ApiName -Operator eq -Value "GetBlob"3>$null) Get-AzMetric-ResourceId $resourceId-MetricName Transactions -TimeGrain 01:00:00-MetricFilter $dimFilter-AggregationType "Total"You can list the metric definition of your storage account or the Blob storage service. Use the az monitor metrics list-definitions command.
In this example, replace the <resource-ID> placeholder with the resource ID of the entire storage account or the resource ID of the Blob storage service. You can find these resource IDs on the Endpoints pages of your storage account in the Azure portal.
az monitor metrics list-definitions --resource <resource-ID> You can read the metric values of your storage account or the Blob storage service. Use the az monitor metrics list command.
az monitor metrics list --resource <resource-ID> --metric "UsedCapacity" --interval PT1H When a metric supports dimensions, you can read metric values and filter them by using dimension values. Use the az monitor metrics list command.
az monitor metrics list --resource <resource-ID> --metric "Transactions" --interval PT1H --filter "ApiName eq 'GetBlob' " --aggregation "Total" Azure Monitor provides the .NET SDK to read metric definition and values. The sample code shows how to use the SDK with different parameters. You need to use 0.18.0-preview or a later version for storage metrics.
In these examples, replace the <resource-ID> placeholder with the resource ID of the entire storage account or the Blob storage service. You can find these resource IDs on the Endpoints pages of your storage account in the Azure portal.
Replace the <subscription-ID> variable with the ID of your subscription. For guidance on how to obtain values for <tenant-ID>, <application-ID>, and <AccessKey>, see Use the portal to create a Microsoft Entra application and service principal that can access resources.
The following example shows how to list a metric definition at the account level:
publicstaticasyncTaskListStorageMetricDefinition(){varresourceId="<resource-ID>";varsubscriptionId="<subscription-ID>";vartenantId="<tenant-ID>";varapplicationId="<application-ID>";varaccessKey="<AccessKey>";MonitorManagementClientreadOnlyClient=AuthenticateWithReadOnlyClient(tenantId,applicationId,accessKey,subscriptionId).Result;IEnumerable<MetricDefinition>metricDefinitions=awaitreadOnlyClient.MetricDefinitions.ListAsync(resourceUri:resourceId,cancellationToken:newCancellationToken());foreach(varmetricDefinitioninmetricDefinitions){// Enumerate metric definition:// Id// ResourceId// Name// Unit// MetricAvailabilities// PrimaryAggregationType// Dimensions// IsDimensionRequired}}The following example shows how to read UsedCapacity data at the account level:
publicstaticasyncTaskReadStorageMetricValue(){varresourceId="<resource-ID>";varsubscriptionId="<subscription-ID>";vartenantId="<tenant-ID>";varapplicationId="<application-ID>";varaccessKey="<AccessKey>";MonitorClientreadOnlyClient=AuthenticateWithReadOnlyClient(tenantId,applicationId,accessKey,subscriptionId).Result;Microsoft.Azure.Management.Monitor.Models.ResponseResponse;stringstartDate=DateTime.Now.AddHours(-3).ToUniversalTime().ToString("o");stringendDate=DateTime.Now.ToUniversalTime().ToString("o");stringtimeSpan=startDate+"/"+endDate;Response=awaitreadOnlyClient.Metrics.ListAsync(resourceUri:resourceId,timespan:timeSpan,interval:System.TimeSpan.FromHours(1),metricnames:"UsedCapacity",aggregation:"Average",resultType:ResultType.Data,cancellationToken:CancellationToken.None);foreach(varmetricinResponse.Value){// Enumerate metric value// Id// Name// Type// Unit// Timeseries// - Data// - Metadatavalues}}For multidimensional metrics, you need to define metadata filters if you want to read metric data on specific dimension values.
The following example shows how to read metric data on the metric supporting multidimension:
publicstaticasyncTaskReadStorageMetricValueTest(){// Resource ID for blob storagevarresourceId="/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Storage/storageAccounts/{storageAccountName}/blobServices/default";varsubscriptionId="<subscription-ID}";// How to identify Tenant ID, Application ID and Access Key: https://azure.microsoft.com/documentation/articles/resource-group-create-service-principal-portal/vartenantId="<tenant-ID>";varapplicationId="<application-ID>";varaccessKey="<AccessKey>";MonitorManagementClientreadOnlyClient=AuthenticateWithReadOnlyClient(tenantId,applicationId,accessKey,subscriptionId).Result;Microsoft.Azure.Management.Monitor.Models.ResponseResponse;stringstartDate=DateTime.Now.AddHours(-3).ToUniversalTime().ToString("o");stringendDate=DateTime.Now.ToUniversalTime().ToString("o");stringtimeSpan=startDate+"/"+endDate;// It's applicable to define meta data filter when a metric support dimension// More conditions can be added with the 'or' and 'and' operators, example: BlobType eq 'BlockBlob' or BlobType eq 'PageBlob'ODataQuery<MetadataValue>odataFilterMetrics=newODataQuery<MetadataValue>(string.Format("BlobType eq '{0}'","BlockBlob"));Response=readOnlyClient.Metrics.List(resourceUri:resourceId,timespan:timeSpan,interval:System.TimeSpan.FromHours(1),metricnames:"BlobCapacity",odataQuery:odataFilterMetrics,aggregation:"Average",resultType:ResultType.Data);foreach(varmetricinResponse.Value){// Enumerate metric value// Id// Name// Type// Unit// Timeseries// - Data// - Metadatavalues}}You can access resource logs either as a blob in a storage account, as event data, or through Log Analytics queries. For information about how to find those logs, see Azure resource logs.
To get the list of SMB and REST operations that are logged, see Storage logged operations and status messages.
Log entries are created only if there are requests made against the service endpoint. For example, if a storage account has activity in its file endpoint but not in its table or queue endpoints, only logs that pertain to the Azure Blob Storage service are created. Azure Storage logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor individual requests and to diagnose issues with a storage service. Requests are logged on a best-effort basis.
When you view a storage account in the Azure portal, the operations called by the portal are also logged. For this reason, you may see operations logged in a storage account even though you haven't written any data to the account.
The following types of authenticated requests are logged:
- Successful requests
- Failed requests, including time-out, throttling, network, authorization, and other errors
- Requests that use a shared access signature (SAS) or OAuth, including failed and successful requests
- Requests to analytics data (classic log data in the $logs container and class metric data in the $metric tables)
Requests made by the Blob storage service itself, such as log creation or deletion, aren't logged. For a full list of the logged data, see Storage logged operations and status messages and Storage log format.
Note
Azure Monitor currently filters out logs that describe activity in the "insights-logs-" container.
The following types of anonymous requests are logged:
- Successful requests
- Server errors
- Time out errors for both client and server
- Failed GET requests with the error code 304 (Not Modified)
All other failed anonymous requests aren't logged. For a full list of the logged data, see Storage logged operations and status messages and Storage log format.
[!INCLUDE horz-monitor-kusto-queries]
Here are some queries that you can enter in the Log search bar to help you monitor your Blob storage. These queries work with the new language.
To list the 10 most common errors over the last three days.
StorageBlobLogs | where TimeGenerated > ago(3d) and StatusText !contains"Success" | summarizecount() by StatusText | top10by count_ desc
To list the top 10 operations that caused the most errors over the last three days.
StorageBlobLogs | where TimeGenerated > ago(3d) and StatusText !contains"Success" | summarizecount() by OperationName | top10by count_ desc
To list the top 10 operations with the longest end-to-end latency over the last three days.
StorageBlobLogs | where TimeGenerated > ago(3d) | top10by DurationMs desc | project TimeGenerated, OperationName, DurationMs, ServerLatencyMs, ClientLatencyMs = DurationMs - ServerLatencyMs
To list all operations that caused server-side throttling errors over the last three days.
StorageBlobLogs | where TimeGenerated > ago(3d) and StatusText contains"ServerBusy" | project TimeGenerated, OperationName, StatusCode, StatusText
To list all requests with anonymous access over the last three days.
StorageBlobLogs | where TimeGenerated > ago(3d) and AuthenticationType == "Anonymous" | project TimeGenerated, OperationName, AuthenticationType, Uri
To create a pie chart of operations used over the last three days.
StorageBlobLogs | where TimeGenerated > ago(3d) | summarizecount() by OperationName | sortby count_ desc | renderpiechart
[!INCLUDE horz-monitor-alerts]
The following table lists common and recommended alert rules for Azure Blob Storage and the proper metric to use for the alert:
| Alert type | Condition | Description |
|---|---|---|
| Metric | Blob Storage service is throttled. | Transactions Dimension name: Response type |
| Metric | Blob Storage requests are successful 99% of the time. | Availability Dimension names: Geo type, API name, Authentication |
| Metric | Blob Storage egress has exceeded 500 GiB in one day. | Egress Dimension names: Geo type, API name, Authentication |
[!INCLUDE horz-monitor-advisor-recommendations]
Other Blob Storage monitoring content:
- Azure Blob Storage monitoring data reference. A reference of the logs and metrics created by Azure Blob Storage.
- Best practices for monitoring Azure Blob Storage. Guidance for common monitoring and troubleshooting scenarios.
- Metrics and logs FAQ.
Overall Azure Storage monitoring content:
- Monitor storage with Azure Monitor Storage insights. Get a unified view of storage performance, capacity, and availability.
- Transition to metrics in Azure Monitor. Move from Storage Analytics metrics to metrics in Azure Monitor.
- Troubleshoot performance issues. See common performance issues and guidance about how to troubleshoot them.
- Troubleshoot availability issues. See common availability issues and guidance about how to troubleshoot them.
- Troubleshoot client application errors. See common issues with connecting clients and how to troubleshoot them.
Azure Monitor content:
- Monitor Azure resources with Azure Monitor. General details on monitoring Azure resources.
- Azure Monitor Metrics overview. The basics of metrics and metric dimensions.
- Azure Monitor Logs overview. The basics of logs and how to collect and analyze them.
- Analyze metrics with Azure Monitor metrics explorer. A tour of Metrics Explorer.
- Overview of Log Analytics in Azure Monitor. A tour of Log Analytics.
Training modules:
- Gather metrics from your Azure Blob Storage containers. Create charts that show metrics, with step-by-step guidance.
- Monitor, diagnose, and troubleshoot your Azure Storage. Troubleshoot storage account issues, with step-by-step guidance.
