Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureEasy
A team is developing a new cloud-native application using microservices. They want to implement a mechanism that allows them to quickly detect and diagnose issues in their distributed system by tracing requests across multiple services. Which observability practice is most relevant for this requirement?
- ALog aggregation
- BHealth checks
- CDistributed tracing
- DMetric collection
Show answer & explanationAnswer & explanation
Correct answer: C. Distributed tracing
Distributed tracing is specifically designed to track the path of a single request as it propagates through various services in a distributed system, making it ideal for diagnosing issues in microservices.
Why the other options are wrong
- A. Log aggregation collects logs from all services but doesn't provide a direct, end-to-end view of a single request's flow.
- B. Health checks determine if a service is operational but don't trace the path of a request through the system.
- D. Metric collection gathers performance data but doesn't show the sequence of operations for an individual request.
Distributed Tracing
An observability technique used to monitor and profile requests as they traverse multiple services in a distributed system.
- Tracks individual request paths.
- Helps identify latency bottlenecks and errors.
- Uses trace IDs and span IDs.
- Key components: tracing agents, collectors, visualization tools.
Memory trick: Logs, Metrics, Traces: the three wise men of system insight.