Azure Deployments Test
Deployment in Azure represents a collection of Azure infrastructure resources defined in a template. Developers can deploy infrastructure defined in the templates in subscriptions where they have access, and build their applications on the infrastructure. For example, a deployment environment can be defined with web app, database, and storage account and the web developer can begin coding the web app without worrying about the underlying infrastructure.
Using this test, the administrators can ensure that the performance and health of resources in each resource group are stable enough to handle Azure deployments. It also helps the administrators to identify issues specific to a resource, which is crucial for quick troubleshooting and problem resolution.
Target of the Test : A Microsoft Azure Subscription
Agent deploying the test: A remote agent
Output of the test: One set of results for each resource group in the target Microsoft Azure Subscription.
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:
|
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. |
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:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Number of deployments |
Indicates the number of deployments managed by this resource group. |
Number |
|
Deployments with success status |
Indicates the number of successful deployments in this resource group. |
Number |
|
Deployments with failure status |
Indicates the number of failed deployments in this resource group. |
Number |
If the deployment fails, Azure typically rolls back all changes made during that deployment. This means that any resources that were created or modified are deleted, and the resource group returns to its state before the deployment began. Ideally, the value of this measure should be low.
|
Deployments failed recently |
Indicates the number of deployments that failed recently in this resource group. |
Number |
|
Recent successful deployments |
Indicates the number of deployments that succeeded recently in this resource group. |
Number |
|