Azure API Management Test
Azure API Management is a fully managed Microsoft solution where developers can easily build their APIs to expose internal and external applications without writing a single line of code. Using Azure API Management, you can manage your APIs, define policies for publications and usage restrictions for your applications running on the web and cloud. The Azure API Management allows you to manage multiple APIs under multiple services. Using the Azure API Management test, the administrators can identify the availability of the target Azure API Management, total number of APIs, users and subscriptions attached to the Azure API Management. This test also helps to identify the Azure API Management services that are responding slowly to the API requests and why - is it due to many failed requests? whether it encountered many Gateway errors? is it due to high latency at the Backend of APIs.
Target of the test : Microsoft Azure API Management
Agent deploying the test : An external agent
Outputs of the test : One set of results for the target Microsoft Azure API Management.
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 API Management 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 Microsoft Azure API Management 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 ProxyPort |
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 Azure API Management to be managed in the Resource Group text box. |
APIM Service Name |
The Azure API Management allows you to manage multiple APIs under multiple services and reports the specific metrics for all APIs under each service. Specify the name of such Azure API Management Service in the APIM Service Name 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 | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Status |
Indicates whether/not the target Azure API Management is available. |
|
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 whether/not the target Azure API Management is available. The detailed diagnosis of this measure lists the details like Location,Tags, SKU, Publisher name, Developer portal url, Management api url, Gateway url, scm url and Public IP Addresses. |
||||||||||||||||||||||
Provisioning state |
Indicates the provisioning state of the Azure API Management. |
|
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 the provisioning state of the Azure API Management. |
||||||||||||||||||||||
Total APIs |
Indicates the total number of APIs in the target Azure API Management. |
Number |
The detailed diagnosis of this measure lists the details like Api id, Api name, Api revision, Protocols, Service Url and Path. |
||||||||||||||||||||||
Total users |
Indicates the total number of users attached to the target Azure API Management. |
Number |
|
||||||||||||||||||||||
Total subscriptions |
Indicates the total number of subscriptions subscribed to the target Azure API Management. |
Number |
|
||||||||||||||||||||||
Total requests |
Indicates the total number of requests handled by the target Azure API Management. |
Number |
|
||||||||||||||||||||||
Overall average gateway request duration |
Indicates the average time taken by the gateway requests to be processed in the target Azure API Management. |
Seconds |
Ideally, the value of this measure should be low. |
||||||||||||||||||||||
Total requests failed recently |
Indicates the total number of requests that recently failed in the target Azure API Management. |
Number |
|||||||||||||||||||||||
Failed requests |
Indicates the percentage of requests that failed in the target Azure API Management. |
Percent |
|||||||||||||||||||||||
Gateway errors |
Indicates the number of Gateway errors encountered by the target Azure API Management. |
Number |
Ideally, the value of this measure should be low. |
||||||||||||||||||||||
Capacity |
Indicates the percentage of requests handled by the target Azure API Management. |
Percent |
Ideally, the value of this measure should be high. |
||||||||||||||||||||||
Gateway requests |
Indicates the number of Gateway requests handled by the target Azure API Management. |
Number |
|
||||||||||||||||||||||
Backend requests |
Indicates the number of requests handled at the Backend of APIs in the target Azure API Management. |
Number |
|
||||||||||||||||||||||
Average backend latency |
Indicates the time taken for the requests to be processed at Backend of APIs in the target Azure API Management. |
Seconds |
Ideally, the value of this measure should be low. High latency in this case denotes that the request and response process from the Backend encounter a delay. |