Response | Description |
200 OK | Readiness check is successful. Readiness probe continues to reply OK if API Gateway remains in an operational state to serve the requests. |
500 Internal server error | Readiness check failed and denotes a problem. |
timeout or no response as the request did not reach the probe | Several factors can contribute to the delay when the Readiness Probe initiates, which may result in the timeout errors. To know the reasons for timeout errors, see
Causes for timeout errors for more information. |
Response | Description |
200 OK | Runtime service health check is successful. |
500 Internal server error | Runtime service health check failed and denotes a problem. The response JSON indicates the problem. |
timeout or no response as the request did not reach the probe | Several factors can contribute to the delay when the Runtime Service Health Probe initiates, which may result in the timeout errors. To know the reasons for timeout errors, see
Causes for timeout errors for more information. |
Status | Description |
green | Indicates that the cluster within the node is in a healthy state. |
yellow | Indicates that API Gateway does not have adequate resources to run. |
red | Indicates the cluster failure in the node and an outage. |
Status | Description |
green | Indicates that API Data Store is in a healthy state. When the status of API Data Store signals green or yellow, the overall status of API Gateway is green. |
red | Indicates that API Data Store is not in a healthy state. When the status of API Data Store signals red, the overall status of API Gateway is red. |
yellow | Indicates a node failure in the cluster. However, the cluster is still functioning and operational. |
Status | Description |
green | Indicates that API Gateway resource types like memory, disk space, and service threads are available to run. |
yellow | Indicates that API Gateway does not have adequate resources to run. When the API Gateway resource status is yellow, the overall status of API Gateway is yellow. |
Status | Description |
green | Indicates that Terracotta server is in a healthy state. When the status of Terracotta server signals green, the overall status of API Gateway is green. |
red | Indicates that Terracotta server is not in a healthy state. When the status of Terracotta server signals red, the overall status of API Gateway is red. |
Response | Description |
200 OK | Administration service health check is successful. |
500 Internal server error | Denotes a problem. The response JSON indicates the problem. |
timeout or no response as the request did not reach the probe | Several factors can contribute to the delay when you initiate the Administration Service Health Probe, which may result in the timeout errors. To know the reasons for timeout errors, see
Causes for timeout errors for more information. |
Status | Description |
green | Indicates that Kibana's port is accessible. When the status signals green, the overall status of Administration Service Health Probe is green. |
red | Indicates that either Kibana's port is inaccessible or Kibana's communication with API Data Store is not established. When the status signals red, the overall status of Administration Service Health Probe is red. |
Status | Description |
green | Indicates that API Gateway administration service is available. When the status signals green, the overall status of Administration Service Health Probe is green. |
red | Indicates that API Gateway administration service is not available. When the status signals red, the overall status of Administration Service Health Probe is red. |