Azure Infrastructure Status Test

Microsoft Azure offers a wide variety of cloud services such as Azure Apps, Azure Analytics, Azure Storage, Azure Virtual Machines etc., for the benefit of its users.

Administrators often need real-time updates on the health of these services, so they can quickly identify services that are in an abnormal state, and can resolve the issues experienced by those services before they impact user experience with Azure. The Azure Infrastructure Status test helps administrators with this!

This test monitors the health of the services offered by Azure, and reports the count of services in different health states. Alerts are sent out to administrators if any service is in bad health. Administrators can then use the detailed diagnostics provided by the test to identify the precise services that are experiencing health issues presently. Once the problem services are identified, administrators can then proceed to see what is ailing such services and remove it, so that users can continue to use the services without a glitch.

Target of the Test: A Microsoft Azure Subscription

Agent deploying the test: A remote agent

Output of the test: One set of results for the target Azure subscription

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.

Host

The host for which the test is to be configured.

Subscription ID

Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored. To know the ID that maps to the target subscription, do the following:

  1. Login to the Microsoft Azure Portal.

  2. When the portal opens, click on the Subscriptions option (as indicated by Figure 1).

    Figure 1 : Clicking on the Subscriptions option

  3. Figure 2 that appears next will list all the subscriptions that have been configured for the target Azure AD tenant. Locate the subscription that is being monitored in the list, and check the value displayed for that subscription in the Subscription ID column.

    Figure 2 : Determining the Subscription ID

  4. Copy the Subscription ID in Figure 2 to the text box corresponding to the SUBSCRIPTION ID parameter in the test configuration page.

Tenant ID

Specify the Directory ID of the Azure AD tenant to which the target subscription belongs. To know how to determine the Directory ID, refer to Configuring the eG Agent to Monitor a Microsoft Azure Subscription Using Azure ARM REST API.

Client ID, Client Password, and Confirm Password

To connect to the target subscription, the eG agent requires an Access token in the form of an Application ID and the client secret value. For this purpose, you should register a new application with the Azure AD tenant. To know how to create such an application and determine its Application ID and client secret, refer to Configuring the eG Agent to Monitor a Microsoft Azure Subscription Using Azure ARM REST API. Specify the Application ID of the created Application in the Client ID text box and the client secret value in the Client Password text box. Confirm the Client Password by retyping it in the Confirm Password text box.

Proxy Host and Proxy Port

In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the Proxy Host and Proxy Port parameters. By default, these parameters are set to none, indicating that the eG agent is not configured to communicate via a proxy, by default.

Proxy Username, Proxy Password and Confirm Password

If the proxy server requires authentication, then, specify a valid proxy user name and password in the Proxy Username and Proxy Password parameters, respectively. Then, confirm the password by retyping it in the Confirm Password text box.

Show DD for Warning

By default, this test reports detailed diagnostics for the Services in Warning state measure. This is why, this flag is set to Yes by default. If for some reason you want to turn off detailed metrics collection for this measure, then set this flag to No. In this case, the test will not report the list of services that are in the Warning state, as part of the detailed metrics it collects.

Show DD for Information

By default, this test does not report detailed diagnostics for the Services in Information state measure. This is why, this flag is set to No by default. If you want to turn on detailed metrics collection for this measure, then set this flag to Yes.

Regions

By default, this test reports the health of services that are offered across all regions. Accordingly, this parameter is set to ALL by default. However, if you want the test to report metrics for specific regions alone, then specify the names of those regions as a comm-separated list here.

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.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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. 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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measures made by the test:
Measurement Description Measurement Unit Interpretation

Services in Good state

Indicates the number of services in a healthy state currently.

Number

 

Services in Information state

Indicates the number of services in Information state currently.

Number

Use the detailed diagnosis of this measure, if enabled, to know which services are in an Information state.

Services in Warning state

Indicates the number of services in the Warning state currently.

Number

Ideally, the value of this measure should be 0.

If this measure reports a non-zero value, then use the detailed diagnosis of this measure to know which services are in a Warning state.

Services in Critical state

Indicates the number of services in the Critical state currently.

Number

Ideally, the value of this measure should be 0.

If this measure reports a non-zero value, then use the detailed diagnosis of this measure to know which services are in a Critical state.