Answer-first summary for fast verification
Answer: Instrument your microservices by installing the OpenTelemetry tracing package. Update your application code to send traces to Trace for inspection and analysis. Create an analysis report on Trace to analyze user requests.
The correct approach is to use distributed tracing to identify high-latency HTTP requests. Option C involves instrumenting the application with OpenTelemetry, which captures detailed traces of user requests across microservices. These traces are sent to Cloud Trace (Google's tracing service), allowing analysis of latency spans for specific URLs. This method directly addresses the need to pinpoint which requests have high latency. Other options are less effective: - A focuses on infrastructure metrics, not request-level latency. - B assumes latency data is logged, but the question doesn't indicate this. - D uses network packet analysis, which is too low-level and impractical for tracing HTTP latency in microservices.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
As a developer building an online gaming platform using microservices on Google Kubernetes Engine (GKE), users are reporting slow loading times for specific URL requests. How can you analyze performance bottlenecks in your application to pinpoint which HTTP requests are experiencing unusually high latency in user traffic?
A
Configure GKE workload metrics using kubectl. Select all Pods to send their metrics to Cloud Monitoring. Create a custom dashboard of application metrics in Cloud Monitoring to determine performance bottlenecks of your GKE cluster.
B
Update your microservices to log HTTP request methods and URL paths to STDOUT. Use the logs router to send container logs to Cloud Logging. Create filters in Cloud Logging to evaluate the latency of user requests across different methods and URL paths.
C
Instrument your microservices by installing the OpenTelemetry tracing package. Update your application code to send traces to Trace for inspection and analysis. Create an analysis report on Trace to analyze user requests.
D
Install tcpdump on your GKE nodes. Run tcpdump to capture network traffic over an extended period of time to collect data. Analyze the data files using Wireshark to determine the cause of high latency.