Azure Database Status (classic) Test

This test enables administrators to determine how many Azure databases were registered with the Azure cloud and how many are currently powered on/powered off. In addition, this test helps administrators to determine how many Azure databases were currently added and how many databases were removed. Using this test, administrators can instantly identify the powered off databases i.e., unavailable databases and start investigating the exact reason behind the powered off status of the databases.

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

Registered databases

Indicates the number of database instances registered on the Azure cloud.

Number

The detailed diagnosis of this measure if enabled, lists the database instances that were recently registered.

Powered on databases

Indicates the number of database instances that are currently powered-on on the Azure cloud.

Number

The detailed diagnosis of this measure if enabled, lists the database instances that were powered on recently.

Powered off databases

Indicates the number of database instances that are currently powered off on the Azure cloud.

Number

The detailed diagnosis of this measure if enabled, lists the database instances that were powered off recently.

Added databases

Indicates the number of database instances that were added during the last measurement period.

Number

The detailed diagnosis of this measure if enabled, lists the database instances that were recently added.

Removed databases

Indicates the number of database instances that were removed from the Azure cloud during the last measurement period.

Number

The detailed diagnosis of this measure if enabled, lists the database instances that were removed recently.

The detailed diagnosis of the Removed databases measure if enabled, lists the databases that were removed from the Azure cloud as shown in Figure 1.

Figure 1 : The detailed diagnosis of the Removed databases measure

The detailed diagnosis of the Added databases measure lists the databases that were added to the Azure cloud as shown in Figure 2.

Figure 2 : The detailed diagnosis of the Added databases measure

The detailed diagnosis of the Powered on databases measure(see Figure 3) lists the databases that were powered on on the Azure cloud.

Figure 3 : The detailed diagnosis of the Powered on databases measure