Measures reported by AzureStorageTest
Microsoft Azure Storage is developed to enable new scenarios for applications requiring scalable, durable, and highly available storage for their data. Azure Storage is massively scalable, so you can store and process hundreds of terabytes of data to support the big data scenarios required by scientific, financial analysis, and media applications. Azure Storage is currently designed to store tens of trillions of unique customer objects, and handles millions of requests per second on average. Azure Storage is elastic, so you can design applications for a large global audience, and scale those applications as needed - both in terms of the amount of data stored and the number of requests made against it. Azure Storage uses an auto-partitioning system that automatically load-balances your data based on traffic. This means that as the demands on your application grow, Azure Storage automatically allocates the appropriate resources to meet them. Azure Storage is accessible from anywhere in the world, from any type of application, whether it's running in the cloud, on the desktop, on an on-premises server, or on a mobile or tablet device. An Azure storage account is a secure account that gives you access to services in Azure Storage. For a single subscription, you can create upto 100 uniquely named storage accounts.
Azure Storage also supports redundancy so that high read availability of data within the storage can be achieved. There are three different redundancy options available to the users namely:
Locally Redundant Storage (LRS) : All data in the storage account is made durable by replicating transactions synchronously to three different storage nodes within the same region. Geo Redundant Storage (GRS) : This is the default option for redundancy when a storage account is created. Like LRS, transactions are replicated synchronously to three storage nodes within the primary region chosen for creating the storage account. However, the transaction is also queued for asynchronous replication to another secondary region (hundreds of miles away from the primary) where data is again made durable by replicating it to three more storage nodes there. Read Access - Geo Redundant Storage (RA-GRS) : For a GRS storage account, the ability to turn on read only access to a storage account's data in the secondary region has been introduced in limited preview. Since replication to the secondary region is done asynchronously, this provides an eventual consistent version of the data to read from.
If the Azure storage account/Azure Storage is taken offline or is not accessible even for a few minutes, then millions of user requests may not be serviced causing hardship to the users. To avoid such discrepancies, you need to figure out the current state of the storage account and if the storage account supports redundancy, then you may need to figure out the status of the primary as well as the secondary regions. The AzureStorageTest Test helps you exactly in this regard!
For each storage account in the Azure storage, this test helps administrators to figure out the whether the storage account is online or offline. If the storage account is online, then administrators can figure out the current status of the storage account. In addition, if the storage account is redundant across regions, then you can figure out the status of the primary region as well as the secondary region.
Output of the test : One set of results for each storage account on the target Microsoft Azure being monitored
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Cur_status |
Indicates the current state of this storage account. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Numeric Value |
Measure Value |
| 1 |
Creating |
| 2 |
Created |
| 3 |
Deleting |
| 4 |
Deleted |
| 5 |
Changing |
| 6 |
Resolving DNS |
| 0 |
Unknown |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current state of this storage account. The graph of this measure however, represents the status of a server using the numeric equivalents onlyy - 0 to 6.
|
| Pri_status |
Indicates the availability of the primary storage region in this storage account. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Numeric Value |
Measure Value |
| 1 |
Available |
| 2 |
Created |
| 0 |
Unknown |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the primary storage region in this storage account. The graph of this measure however, represents the status of a server using the numeric equivalents only - 0 to 2.
|
| Sec_status |
Indicates the availability of the secondary storage region in this storage account. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Numeric Value |
Measure Value |
| 1 |
Available |
| 2 |
Created |
| 0 |
Unknown |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the secondary storage region in this storage account. The graph of this measure however, represents the status of a server using the numeric equivalents only - 0 to 2.
|
| Status |
Indicates whether this storage account is online or offline. |
|
This measure will report Online if the Cur_status measure reports a value Created, Pri_status and Sec_status values are Available.
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Numeric Value |
Measure Value |
| 1 |
Online |
| 2 |
Offline |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate whether this storage account is online or offline. The graph of this measure however, represents the status of a server using the numeric equivalents only - 1 to 2.
|
|