Transition to metrics in Azure Monitor
On January 9, 2024 Storage Analytics metrics, also referred to as classic metrics retired. If you used classic metrics, this article helps you transition to metrics in Azure Monitor.
Steps to complete the transition
To transition to metrics in Azure Monitor, we recommend the following approach.
Learn about some of the key differences between classic metrics and metrics in Azure Monitor.
Compile a list of classic metrics that you currently use.
Identify which metrics in Azure Monitor provide the same data as the metrics you currently use.
Create charts or dashboards to view metric data.
Note
Metrics in Azure Monitor are enabled by default, so there is nothing you need to do to begin capturing metrics. You must however, create charts or dashboards to view those metrics.
If you've created alert rules that are based on classic storage metrics, then create alert rules that are based on metrics in Azure Monitor.
After you're able to see all of your metrics in Azure Monitor, you can turn off classic logging.
Classic metrics vs. metrics in Azure Monitor
This section describes a few key differences between these two metrics platforms.
The main difference is in how metrics are managed. Classic metrics are managed by Azure Storage whereas metrics in Azure Monitor are managed by Azure Monitor. With classic metrics, Azure Storage collects metric values, aggregates them, and then stores them in tables that are located in the storage account. With metrics in Azure Monitor, Azure Storage sends metric data to the Azure Monitor back end. Azure Monitor provides a unified monitoring experience that includes data from the Azure portal as well as data that is ingested.
Classic metrics are sent and stored in an Azure storage account. Azure Monitor metrics can be sent to multiple locations. A storage account can be one of those locations, but it's not required.
As far as metrics support, classic metrics provide capacity metrics only for Azure Blob storage. Metrics in Azure Monitor provide capacity metrics for Blob, Table, File, Queue, and premium storage. Classic metrics provide transaction metrics on Blob, Table, Azure File, and Queue storage. Metrics in Azure Monitor add premium storage to that list.
If the activity in your account does not trigger a metric, classic metrics will show a value of zero (0) for that metric. Metrics in Azure Monitor will omit the data entirely, which leads to cleaner reports. For example, with classic metrics, if no server timeout errors are reported, then the ServerTimeoutError value in the metrics table is set to 0. Azure Monitor doesn't return any data when you query the value of metric Transactions with dimension ResponseType equal to ServerTimeoutError.
To learn more about metrics in Azure Monitor, see Metrics in Azure Monitor.
Map classic metrics to metrics in Azure Monitor
Use these tables to identify which metrics in Azure Monitor provide the same data as the metrics you currently use.
Capacity metrics
| Classic metric | Metric in Azure Monitor |
|---|---|
Capacity |
BlobCapacity with the dimension BlobType equal to BlockBlob or PageBlob |
ObjectCount |
BlobCount with the dimension BlobType equal to BlockBlob or PageBlob |
ContainerCount |
ContainerCount |
Note
There are also several new capacity metrics that weren't available as classic metrics. To view the complete list, see Metrics.
Transaction metrics
| Classic metric | Metric in Azure Monitor |
|---|---|
AnonymousAuthorizationError |
Transactions with the dimension ResponseType equal to AuthorizationError and dimension Authentication equal to Anonymous |
AnonymousClientOtherError |
Transactions with the dimension ResponseType equal to ClientOtherError and dimension Authentication equal to Anonymous |
AnonymousClientTimeoutError |
Transactions with the dimension ResponseType equal to ClientTimeoutError and dimension Authentication equal to Anonymous |
AnonymousNetworkError |
Transactions with the dimension ResponseType equal to NetworkError and dimension Authentication equal to Anonymous |
AnonymousServerOtherError |
Transactions with the dimension ResponseType equal to ServerOtherError and dimension Authentication equal to Anonymous |
AnonymousServerTimeoutError |
Transactions with the dimension ResponseType equal to ServerTimeoutError and dimension Authentication equal to Anonymous |
AnonymousSuccess |
Transactions with the dimension ResponseType equal to Success and dimension Authentication equal to Anonymous |
AnonymousThrottlingError |
Transactions with the dimension ResponseType equal to ClientThrottlingError or ServerBusyError and dimension Authentication equal to Anonymous |
AuthorizationError |
Transactions with the dimension ResponseType equal to AuthorizationError |
Availability |
Availability |
AverageE2ELatency |
SuccessE2ELatency |
AverageServerLatency |
SuccessServerLatency |
ClientOtherError |
Transactions with the dimension ResponseType equal to ClientOtherError |
ClientTimeoutError |
Transactions with the dimension ResponseType equal to ClientTimeoutError |
NetworkError |
Transactions with the dimension ResponseType equal to NetworkError |
PercentAuthorizationError |
Transactions with the dimension ResponseType equal to AuthorizationError |
PercentClientOtherError |
Transactions with the dimension ResponseType equal to ClientOtherError |
PercentNetworkError |
Transactions with the dimension ResponseType equal to NetworkError |
PercentServerOtherError |
Transactions with the dimension ResponseType equal to ServerOtherError |
PercentSuccess |
Transactions with the dimension ResponseType equal to Success |
PercentThrottlingError |
Transactions with the dimension ResponseType equal to ClientThrottlingError or ServerBusyError |
PercentTimeoutError |
Transactions with the dimension ResponseType equal to ServerTimeoutError or ResponseType equal to ClientTimeoutError |
SASAuthorizationError |
Transactions with the dimension ResponseType equal to AuthorizationError and dimension Authentication equal to SAS |
SASClientOtherError |
Transactions with the dimension ResponseType equal to ClientOtherError and dimension Authentication equal to SAS |
SASClientTimeoutError |
Transactions with the dimension ResponseType equal to ClientTimeoutError and dimension Authentication equal to SAS |
SASNetworkError |
Transactions with the dimension ResponseType equal to NetworkError and dimension Authentication equal to SAS |
SASServerOtherError |
Transactions with the dimension ResponseType equal to ServerOtherError and dimension Authentication equal to SAS |
SASServerTimeoutError |
Transactions with the dimension ResponseType equal to ServerTimeoutError and dimension Authentication equal to SAS |
SASSuccess |
Transactions with the dimension ResponseType equal to Success and dimension Authentication equal to SAS |
SASThrottlingError |
Transactions with the dimension ResponseType equal to ClientThrottlingError or ServerBusyError and dimension Authentication equal to SAS |
ServerOtherError |
Transactions with the dimension ResponseType equal to ServerOtherError |
ServerTimeoutError |
Transactions with the dimension ResponseType equal to ServerTimeoutError |
Success |
Transactions with the dimension ResponseType equal to Success |
ThrottlingError |
Transactions with the dimension ResponseType equal to ClientThrottlingError or ServerBusyError |
TotalBillableRequests |
Transactions |
TotalEgress |
Egress |
TotalIngress |
Ingress |
TotalRequests |
Transactions |
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for