Kubernetes and Cloud Native Associate (KCNA)Cloud Native ObservabilityMedium
A company is migrating its monolithic application to a microservices architecture on Kubernetes. They are experiencing increased latency and errors, but it's difficult to pinpoint which specific service or interaction is causing the problem. Which observability strategy would be most effective in identifying the exact path a request takes through the multiple services and the time spent in each?
- AHealth Checks
- BMetric Dashboards
- CDistributed Tracing
- DAggregated Logging
Show answer & explanationAnswer & explanation
Correct answer: C. Distributed Tracing
Distributed tracing is specifically designed to track the full lifecycle of a request as it propagates through multiple services in a distributed system. It provides a visual representation of the request path, latency at each hop, and any errors encountered, making it ideal for diagnosing issues in microservices.
Why the other options are wrong
- A. Health checks indicate if a service is up or down, not its performance during a request.
- B. Metric dashboards show overall service health but not the journey of a single request.
- D. Aggregated logging helps consolidate logs but doesn't show the end-to-end request flow.
Distributed Tracing
An observability technique used to monitor requests as they flow through a distributed system, providing a visual representation of the request path and timing.
- Tracks requests across multiple services and processes.
- Uses 'spans' to represent operations within a trace.
- Helps identify latency bottlenecks and errors in microservices.
Memory trick: Tracing shows the Path, like a map for your request.