API Gateway 10.15 | Administering API Gateway | Operating API Gateway | Monitoring API Gateway
 
Monitoring API Gateway
 
Cluster-level Monitoring
Troubleshooting: Cluster-level Monitoring
Node-level Monitoring
Monitoring is an important part of maintaining the reliability, availability, and performance of API Gateway. The API Gateway monitoring service enables you to
*View the health and performance of the application.
*Ddiscover, analyze, and debug the application issues before they adversely impact the system. This improves business continuity and reduce application downtime.
*Understand the behavior of the application, scale for business volumes, and benefit from the cost optimization.
Through API Gateway monitoring, you can monitor the health and resources of the following API Gateway components:
*API Gateway Server. For details about the monitoring specifics, see Monitoring API Gateway.
*API Data Store. For details about the monitoring specifics, see Monitoring API Data Store.
*Terracotta Server Array. For details about the monitoring specifics, see Monitoring Terracotta .
*Kibana. For details about the monitoring specifics, see Monitoring Kibana.
You can monitor API Gateway at:
*Cluster-level. For details about the monitoring specifics, see Cluster-level Monitoring.
*Node-level. For details about the monitoring specifics, see Node-level Monitoring.
In a Highly Available (HA) set up, multiple API Gateway instances operate as a cluster. The HA set up ensures that there is no single point of failure in a multiple node deployment such as multiple virtual machines or Kubernetes pods.
*The cluster-level monitoring ensures service availability, that is, availability of access and functionality (serving API requests) of API Gateway. Service availability must be measured only at the cluster-level, for example, one node down in the cluster does not mean a service outage.
*The node-level monitoring ensures the ability of a particular instance of API Gateway components to serve the functionality ( API requests) in the node. Node-health must be dealt within isolation by setting up probes per instance of each API Gateway component.