Home › MCA Cloud Computing › cloudcomputing › cloudobservability › Which observability practice helps a SRE diagnos…
Which observability practice helps a SRE diagnose a specific slow user request in a microservices system that hops across 8 services?
ARunning `pip freeze` on the developer's laptop
BReading the company's quarterly OKRs
CFollowing the request's trace ID across the spans emitted by each service
DChecking the marketing website's analytics dashboard
Answer & Solution
Correct answer: C. Following the request's trace ID across the spans emitted by each service
Distributed tracing follows a single request's trace ID across spans — the right tool for cross-service latency forensics. The other options have nothing to do with diagnosing a slow request.
Related questions
A canary deployment differs from a blue/green deployment because:What does an SRE typically aim for when setting the WHITE-BOX vs BLACK-BOX monitoring balaWhich managed-observability service maps to its cloud correctly?A hybrid cloud architecture connects on-premises systems to one or more public clouds. WhiA common trade-off when adopting a strict multi-cloud architecture is:A multi-cloud strategy primarily aims to:An error budget is computed from an SLO. If an SLO is 99.9% success over 30 days, the erroService-level objectives (SLOs) are best described as: