Monitoring API Gateway

Monitoring is an important part of maintaining the reliability, availability, and performance of webMethods API Gateway. The webMethods API Gateway monitoring service enables you to

• View the health and performance of the application.
• Discover, 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 webMethods API Gateway monitoring, you can monitor the health and resources of the following webMethods API Gateway components:

• webMethods API Gateway Server. For details about the monitoring specifics, see Monitoring API Gateway.
• Elasticsearch. For details about the monitoring specifics, see Monitoring Elasticsearch.
• Kibana. For details about the monitoring specifics, seeMonitoring Kibana.

You can monitor webMethods 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 webMethods 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 webMethods 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 webMethods 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 webMethods API Gateway component.