CompTIA Cloud+ (CV0-004)OperationsMedium
A cloud operations team is investigating an intermittent issue where their containerized microservices randomly experience high latency and connection timeouts, but CPU and memory metrics show normal utilization. The team suspects an issue with inter-service communication. Which monitoring tool or technique would be most effective for diagnosing this problem?
- ABasic host-level CPU and memory utilization graphs.
- BApplication log aggregation with keyword alerts.
- CNetwork flow logs and distributed tracing.
- DStorage I/O performance metrics.
Show answer & explanationAnswer & explanation
Correct answer: C. Network flow logs and distributed tracing.
Since CPU and memory are normal and the issue is intermittent high latency and connection timeouts in a microservices environment, the problem likely lies in the network communication paths between services. Network flow logs can reveal traffic patterns and potential bottlenecks, while distributed tracing provides end-to-end visibility of requests across multiple services, highlighting where delays occur.
Why the other options are wrong
- A. Host-level CPU/memory are already stated as normal, so this would not identify the root cause.
- B. While useful, log aggregation alone might not pinpoint the exact communication path or latency source without the context provided by tracing.
- D. Storage I/O metrics are relevant for disk-bound applications, but not typically for inter-service communication latency in microservices unless data access is the bottleneck, which isn't indicated.
Distributed Tracing
A technique used to monitor and observe requests as they flow through a distributed system, providing visibility into the performance of individual services and the overall request path.
- Tracks requests across multiple services.
- Helps identify latency bottlenecks and failures.
- Essential for microservices architectures.
Memory trick: Trace the Network Flow to Find the Slow.