Azure Traffic Managers Test
Azure Traffic Manager is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions. Traffic Manager also provides your public endpoints with high availability and quick responsiveness.
This test reports the health status of the endpoints in each profile of a Resource group and it is most required for a stable traffic load balancing. Using this test, administrators would be able to identify the number of endpoints in the target Azure Traffic Manager, the number of queries that Azure Traffic Manager profile processes over a specified period and to identify whether/not the profile of the target Azure traffic manager is enabled. Any abnormal condition of the endpoint and profile status will alert the administrators to take remedial measures.
Target of the test : A Microsoft Azure Traffic Manager
Agent deploying the test : An external agent
Outputs of the test : One set of results for eachResource group:profile in the target Microsoft Azure Traffic Managers.
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 Microsoft Azure section in Monitoring Microsoft Azure Subscription document. |
Client ID, Client Password and Confirm Password |
The eG agent communicates with the target Microsoft Load Balancers using Java API calls. To collect the required metrics, the eG agent requires an Access token in the form of an Application ID and the client secret value. To know how to determine the Application ID and the key, refer to Configuring the eG Agent to Monitor Microsoft Azure section in Monitoring Microsoft Azure Subscription document. 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. Then, confirm the password by retyping it in the Confirm Password text box. |
Proxy Host |
In some environments, all communication with the Azure cloud could 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. |
Resource Group |
A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. Specify the name of the particular Resource Group which is a part of the Traffic Load Balancer to be managed in the Resource Group text box. |
Traffic Manager Profile |
You can create a Traffic Manager profile in a Resource group by using the Azure portal. After creating your profile, you can configure endpoints, monitoring, and other settings in the Azure portal. Traffic Manager supports up to 200 endpoints per profile. However, most usage scenarios require only a few of endpoints. Specify the name of the respective profile in the traffic manager profile 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 endpoints |
Indicates the number of endpoints in each profile. |
Number |
In general, Traffic Manager supports up to 200 endpoints per profile. However, most usage scenarios require only a few of endpoints. Use the detailed diagnosis of this measure to know the Name, Status, Monitor status, type, priority and tags related to the endpoint. |
||||||
Endpoints health status |
Indicates the health status of the endpoints in each profile. |
Percent |
An endpoint is any Internet-facing service hosted inside or outside of Azure. Traffic Manager provides the continuous monitoring of endpoint health and automatic failover when endpoints fail. To serve this benefit, the endpoint should be healthy enough to handle the traffic load balancing. |
||||||
Queries by endpoint returned |
Indicates the number of queries that each profile processes over a specified period. |
Number |
|
||||||
Profile status |
Indicates the profile status of each Resource group in the Azure traffic manager. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate status of the profile in the target Azure traffic manager. |