| Measurement |
Description |
Measurement Unit |
Interpretation |
| Availability |
Indicates the availability of this storage, in percent. |
Percent |
|
| Tot_req |
Indicates the total number of requests made to this storage. |
Number |
|
| Tot_ingress |
Indicates the amount of ingress data in this storage. |
MB |
The value of this measure includes the ingress from an external client to the Azure as well as ingress within Azure. |
| Tot_egress |
Indicates the amount of egress data in this storage. |
MB |
The value of this measure includes the egress from an external client to the Azure as well as egress within Azure. |
| Tot_bill_req |
Indicates the number of billable requests received by this storage. |
Number |
Every request made to an account's storage service is either billable or non-billable. Storage Analytics logs each individual request made to a service, including a status message that indicates how the request was handled. Similarly, Storage Analytics stores metrics for both a service and the API operations of that service, including the percentages and count of certain status messages. Together, these features can help you analyze your billable requests, make improvements on your application, and diagnose issues with requests to your services. |
| Avg_E2E_latency |
Indicates the average end to end latency of successful requests made to this storage. |
msecs |
A low value is desired for this measure. |
| Avg_ser_latency |
Indicates the average latency used by this storage to process a successful request. |
msecs |
A low value is desired for this measure. |
| Success_per |
Indicates the percentage of successful requests made to this storage. |
Percent |
Ideally, the value of this measure should be high. |
| Success |
Indicates the number of successful requests made to this storage. |
Number |
A high value is desired for this measure. |
| Throt_err_per |
Indicates the percentage of requests made to this storage that failed with throttling errors. |
Percent |
Ideally, the value of this measure should be zero. |
| Timeout_err |
Indicates the percentage of requests made to this storage that failed with timeout errors. |
Percent |
Ideally, the value of this measure should be zero. |
| Ser_err_per |
Indicates the percentage of requests made to this storage that failed with status code 500. |
Percent |
Internal Server Error where the storage error code is not Timeout.
Ideally, the value of this measure should be zero. |
| Client_err_per |
Indicates the percentage of requests made to this storage that failed with errors such as NotFound, Precondition Failed etc. |
Percent |
Most 3XX and 4XX failures fall under this category.
Ideally, the value of this measure should be zero. |
| Auth_err_per |
Indicates the percentage of requests made to this storage that failed with authorization errors. |
Percent |
Ideally, the value of this measure should be zero. |
| Net_err_per |
Indicates the percentage of requests made to this storage that failed with network errors. |
Percent |
Ideally, the value of this measure should be zero. |
| Anonym_suc |
Indicates the number of anonymous requests that were successfully made to this storage. |
Number |
These will also include all conditional GET requests that did not return because the condition did not succeed.
These are billable requests and counted for availability. |
| SAS_suc |
Indicates the number of successful shared access signature requests made to this storage. |
Number |
These will also include all conditional GET requests that did not return because the condition did not succeed.
These are billable requests and counted for availability. |
| Throt_err |
Indicates the number of authenticated requests that returned ServerBusy status i.e., that returned status code 503. |
Number |
These are not billable and are not counted for availability.
Ideally, the value of this measure should be zero. |
| Anony_thro_err |
Indicates the number of anonymous requests that returned ServerBusy status i.e., that returned status code 503. |
Number |
These are not billable and are not counted for availability.
Ideally, the value of this measure should be zero. |
| SAS_throt_err |
Indicates the number of Shared Access Signature requests that returned ServerBusy status i.e., that returned status code 503. |
Number |
These are not billable and are not counted for availability.
Ideally, the value of this measure should be zero. |
| Cli_timeout_err |
Indicates the total number of authenticated requests that timed out. |
Number |
These are seen as timeout errors or Http Status code 500 with Storage error code as “Timeout”.
This happens when timeout value provided is not sufficient for the IO over the network. For example, if the read/write/etc. request completes in the expected time on the server but it takes a long time to return to the client due to network latency, this is considered as a client timeout.
Any other timeout will be deemed as ServerTimeout.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Anoms_cli_tout_err |
Indicates the number of anonymous errors that timed out. |
Number |
These are seen as timeout errors or Http Status code 500 with Storage error code as “Timeout”.
This happens when timeout value provided is not sufficient for the IO of the network. For example, if the read/write/etc. request completes in the expected time on the server but it takes a long time to return to the client due to network latency, this is considered as a client timeout.
Any other timeout will be deemed as AnonymousServerTimeout.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| SAS_cli_tout_err |
Indicates the number of Shared Access Signature requests that timed out. |
Number |
These are seen as timeout errors or Http Status code 500 with Storage error code as “Timeout”.
This happens when timeout value provided is not sufficient for the IO of the network. For example, if the read/write/etc. request completes in the expected time on the server but it takes a long time to return to the client due to network latency, this is considered as a client timeout.
Any other timeout will be deemed as SASServerTimeout.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Ser_tout_err |
Indicates the total number of authenticated requests that timed out. |
Number |
The requests may time out due to the storage service taking too long to respond to the request. The time taken by service excludes the time to read/write from/to client over the network.
These are seen as timeout errors or Http Status code 500 with Storage error code as “Timeout”.
These are not billable requests and counted against availability.
Ideally, the value of this measure should be zero. |
| Anoms_ser_tout_err |
Indicates the total number of anonymous requests that timed out. |
Number |
The requests may time out due to the storage service taking too long to respond to the request. The time taken by service excludes the time to read/write from/to client over the network.
These are seen as timeout errors or Http Status code 500 with Storage error code as “Timeout”.
These are not billable requests and counted against availability.
Ideally, the value of this measure should be zero. |
| SAS_ser_tout_err |
Indicates the total number of Shared Access Signature requests that timed out. |
Number |
The requests may time out due to the storage service taking too long to respond to the request. The time taken by service excludes the time to read/write from/to client over the network.
These are seen as timeout errors or Http Status code 500 with Storage error code as “Timeout”.
These are not billable requests and counted against availability.
Ideally, the value of this measure should be zero. |
| Cli_oth_err |
Indicates the number of authenticated requests that failed as expected. |
Number |
The requests may be expected to fail when the resources already exits or when the resources fail.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| SAS_cli_oth_err |
Indicates the number of Shared Access Signature requests that failed as expected. |
Number |
The requests may be expected to fail when the resources already exits or when the resources fail.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Anoms_cli_oth_err |
Indicates the number of anonymous requests that failed precondition checks. |
Number |
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Ser_oth_err |
Indicates the total number of authenticated requests that failed due to unknown server errors. |
Number |
These are typically Http Status code 500 with Storage error code other than Timeout.
These are not billable requests and counted against availability.
Ideally, the value of this measure should be zero. |
| Anoms_ser_oth_err |
Indicates the total number of anonymous requests that failed due to unknown server errors. |
Number |
These are typically Http Status code 500 with Storage error code other than Timeout.
These are not billable requests and counted against availability.
Ideally, the value of this measure should be zero. |
| SAS_ser_oth_err |
Indicates the total number of Shared Access Signature requests that failed due to unknown server errors. |
Number |
These are typically Http Status code 500 with Storage error code other than Timeout.
These are not billable requests and counted against availability. |
| Auth_err |
Indicates the total number of authentication requests that failed due to authorization errors. |
Number |
A good example for such errors is write requests from users to logs under $logs.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Anoms_auth_err |
Indicates the total number of anonymous requests that failed due to authorization errors. |
Number |
A good example of authentication error occurance is when only authenticated write requests are allowed against all write requests in the storage.
These are billable requests and counted for availability. |
| SAS_auth_err |
Indicates the number of Shared Access Signature requests that failed due to authorization errors. |
Number |
Example: write requests using SAS when only read access was provided Authorization error.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Net_err |
Indicates the number of authenticated requests that failed due to network errors. |
Number |
Network errors occur when a user prematurely closes the connection before the timeout expires or if there are problems in any of the intermediate switches.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Anoms_net_err |
Indicates the number of anonymous requests that failed due to network errors. |
Number |
Network errors occur when a user prematurely closes the connection before the timeout expires or if there are problems in any of the intermediate switches.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| SAS_net_err |
Indicates the number of Shared Access Signature requests that failed due to network errors. |
Number |
Network errors occur when a user prematurely closes the connection before the timeout expires or if there are problems in any of the intermediate switches.
These are billable requests and counted for availability.
Ideally, the value of this measure should be zero. |
| Ingress_bw |
Indicates the amount of bandwidth utilized for transferring ingress data requests per second to this storage. |
MBs |
|
| Egress_bw |
Indicates the amount of egress data utilized per second in this storage. |
MBs |
|