Azure Storage (classic) Test

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 up to 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 Azure Storage (classic) 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.

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Microsoft Azure as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the Test: Microsoft Azure

Agent deploying the test: A remote agent

Output of the test: One set of results for each storage account on the target Microsoft Azure being monitored

  1. TEST PERIOD - How often should the test be executed
  2. Host– The host for which the test is being configured
  3. SUBSCRIPTION ID- Specify the GUID which uniquely identifies your subscription to the target Microsoft Azure that is to be monitored.
  4. CERTIFICATE PATH - In order to collect metrics from the target Microsoft Azure, the eG agent communicates via Microsoft Azure Service Management API Requests. By default, a management certificate is required to authenticate Microsoft Azure Service Management API Requests. The Management certificate should be associated with the subscription ID. The management certificate can be created on your own or you can request Microsoft Azure portal to create a certificate on behalf of you. Prior to creating a management certificate, you have to create a keystore. The steps for creating a management certificate and the keystore is discussed elaborately in Section 1.1. The created keystore will reside in the <JAVA_INSTALL_DIR>\jre7\bin folder. Specify the exact path to the keystore file in this text box. If you have requested Microsoft Azure portal to create the management certificate, then, specify the exact path on which you have stored the keystore file. For example, if the keystore file created is WindowsAzureKeyStore.jks and if you have stored it in D:\Azure folder, then specify the CERTIFICATE PATH as D:\Azure\WindowsAzureKeyStore.jks.
  5. CERTIFICATE PASSWORD - Specify the password that is provided while creating the keystore in this text box.
  6. confirm password - Confirm the password by retyping it here.
  7. dd frequency - Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
  8. detailed diagnosis - To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.
    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

Measures reported by the test:

Measurement Description Measurement Unit Interpretation

Current 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:

Measure Value Numeric Value
Creating 1
Created 2
Deleting 3
Deleted 4
Changing 5
Resolving DNS 6
Unknown 0

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 only - 0 to 6.

Primary 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:

Measure Value Numeric Value
Available 1
Created 2
Unknown 0

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.

Secondary 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:

Measure Value Numeric Value
Available 1
Created 2
Unknown 0

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 Current Status measure reports a value Created, Primary Status and Secondary Status values are Available.

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Online 1
Offline 2

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 - 0 to 2.