Monitoring the Apigee Edge Server
Figure 1 shows the dedicated Apigee Edge monitoring model developed by eG Enterprise.
Figure 1 : The layer model of the Apigee Edge
Each layer of the layer model is mapped to a variety of tests that monitor critical performance parameters such as request processing ability, processing latency and response time, of each component of an organization in the Apigee architecture. To pull out such useful performance data from the target server, the eG agent connects to the REST API of the Apigee Edge to collect critical statistics pertaining to its performance. The metrics reported by these tests enable administrators to answer the following questions:
- Which API resource is handling maximum number of client requests?
- Is any API resource slow in responding to requests?
- How many requests are processed by each API?
- How quickly each API is processing the requests?
- Which API has encountered more number of errors?
- Who is a popular developer in terms of receiving more number of requests?
- Is any developer encountering errors frequently?
- What is the processing latency of each API/API resource/developer/API product?
- Which application is overloaded with maximum number of requests?
- Which application is more popular among users?
- Is any application slow in processing the requests?
- Is any API/APP/API resource/API product/developer processing the request that is large in size?
- Is any API/APP/API resource/API product/developer sending out the response that is large in size?
- What is the average time taken by each API/APP/API resource/API product/developer to receive response from the targets to which it has associated with?
- Which environment is handling more number of requests?
- How quickly each environment is receiving the responses from targets and delivering them to the clients?
As the Network layer has been discussed in great in the Cisco Router
