Check Backend Latency and Response for API Gateway Errors
Question
You work for a large bank where your main application is a payment processing gateway API.
You deployed the application on Oracle Container Engine for Kubernetes (OKE) and used API Gateway with several policies to control the access of the API endpoint.
However, your customers are complaining about the unavailability of the API endpoint.
Upon checking, you noticed that the Gateway URL is throwing Service Unavailable error.
You need to check the backend latency and backend responses when this error started last night.
What should you do to get this data? (Choose the best answer.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D.
https://docs.cloud.oracle.com/en-us/iaas/Content/APIGateway/Reference/apigatewaymetrics.htmThe best answer to this question is D. Go to Monitoring and click on Service Metrics. Choose the Metric Namespace as oci_apigateway. Change the Start and End time accordingly. Add a Dimension and select httpStatusCode: 503. Check the backend latency and backend responses metric.
Explanation: The given scenario mentions that the API endpoint is throwing a Service Unavailable error, and the customers are complaining about the unavailability of the API endpoint. The first step is to identify the root cause of the issue, which in this case is checking the backend latency and backend responses when the error started last night.
To get this data, we can use the monitoring service in Oracle Cloud Infrastructure (OCI). OCI provides a comprehensive set of monitoring services that enable you to monitor the performance, availability, and utilization of resources in your tenancy. In this case, we need to use the Service Metrics feature of OCI to get the required data.
Option A suggests checking the log files for the container to get the metrics. While log files may contain some relevant data, they are not the best source of information for monitoring and troubleshooting purposes.
Option B suggests checking the Audit log for the API Gateway. The Audit log is useful for tracking changes to the configuration of the API Gateway, but it does not provide information about the backend latency and backend responses.
Option C suggests checking the metrics in the API Gateway detail page. While this is a good option to check the overall performance of the API Gateway, it does not provide the required data about backend latency and backend responses.
Option D suggests going to the Monitoring service and selecting the Metric Namespace as oci_apigateway. This namespace contains metrics for the API Gateway, including backend latency and backend responses. We can add a dimension to filter the metrics based on the HTTP status code, which in this case is 503 (Service Unavailable). This will give us the required data to troubleshoot the issue.
Therefore, the best option is D. Go to Monitoring and click on Service Metrics. Choose the Metric Namespace as oci_apigateway. Change the Start and End time accordingly. Add a Dimension and select httpStatusCode: 503. Check the backend latency and backend responses metric.
