Apigee Developer Analytics Test

Developers implement client/consumer apps and must be registered with an organization on Apigee Edge. The developers build the apps using the APIs on the organization. A developer can be registered with multiple organizations to consume APIs from different organizations. Since success of application development depends on how well the developers handle the traffic after they registered with the Apigee Edge. To ensure the traffic to and from the developers is always smooth, adminitrators should continuously track the request processing ability and responsiveness of each developer. The Apigee Developer Analytics test can help administrators achieve this.

For each developer, this test revelas the count of applications registered by him/her on the organization such that the administrators knows the load imposed by the developers. This test reports the count of client requests and average time taken to process them, and also reveals how long he/she waited to receive response from the backend targets. In the process, the test points administrators to slow developers who has suffered the most owing to slow response from the backend targets. Besides, this test reveals the count of errors encountered by each developer and latency during request and response processing. Using these metrics, administrators can timely investigate the problematic issuess and resolve the error and latency conditions.

Target of the test : Apigee Edge Server

Agent deploying the test : An external agent

Outputs of the test : One set of results for each environment and developer pair in the target Apigee Edge server.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	The IP address of the host for which this test is to be configured.
Port	The port at which the target Apigee server listens to.
Username and Password	By default, the eG agent uses the REST API to collect the metrics from the target Apigee Edge server. To be able to connect to the REST API, the eG agent should be configured with the Apigee email and password of a user who is vested with the rights. Specify the Apigee email and password in the Username and password text boxes.
Confirm Password	Confirm the password by retyping it here.
SSL	By default, the SSL flag is set to Yes indicating that the SSL (Secured Socket Layer) is used to connect to the target Apigee Edge server. If not so, set the SSL flag to No .
Organizations	To enable the eG agent to monitor a particular organization of your interest, specify the name of that organization against this parameter. For instance, primaryorg. Doing so will enable the eG agent to monitor each of the components within the specified organization.
Environments	The organization specified in the Organizations field can contain multiple environments such as dev, test, and prod environment. To enable the eG agent to monitor an environment of your interest, specify the name of that environment in the Environments field. For example, test.
Timeout Seconds	Specify the duration (in seconds) within which the REST API command executed by this test should time out in this text box. The default is 120 seconds.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
App count by developers	Indicates the total number of applications registered by this developer during the last measurement period.	Number	Compare the value of this measure across the developers to know which developer has registered more number of applications on an organization in the Apigee Edge.
End user count by developers	Indicates the total number of users associated with this developer during the last measurement period.	Number
Requests by developers	Indicates the total number of client requests serviced by this developer during the last measurement period.	Number	This measure is a good indicator of workload of each developer. Compare the value of this measure across the developers to know which developer handled maximum number of requests.
Average response time by developers	Indicates the average time taken by this developer to respond to the received requests during the last measurement period.	Milliseconds	A very low value is desired for this measure. An increase in the value of this measure indicates that the developer is very slow in processing the requests. Compare the value of this measure across the developers to know which developer took maximum time to respond to the requests.
Average target response time by API	Indicates the average time that this developer waited to receive the response from the backend targets during the last measurement period.	Milliseconds	Ideally, the value of this measure should be very low. This measure helps administrators to figure out how well the backend targets are performing while servicing the requests.
Errors by developers	Indicates the number of errors encountered by this developer during the last measurement period.	Number
Average request size by developers	Indicates the average size of the request payload received by this developer during the last measurement period.	KB
Average response size by developers	Indicates the average size of the response payload of this developer during the last measurement period.	KB
Average response processing latency by developers	Indicates the average amount of time that this developer took to process the responses.	Milliseconds	Typically, the value of this measure denotes the time starting when each developerreceives the target service response and ending when the Apigee Edge server forwards the response to the original caller. A high value is a cause for concern, as it indicates a potentially slow resource. Compare the value of this measure across the applications to know which developeris the most latent in sending out sthe responses.
Average request processing latency by developers	Indicates the average amount of time that this developer took to process the requests.	Milliseconds	Typically, the value of this measure indicates the time in Milliseconds from the time when a call reaches the developerto the time when Apigee Edge server sends the request to the target backend server.