Bird
0
0

You notice that your distributed tracing data in Jaeger shows many missing spans for some services. What is the most likely cause?

medium📝 Analysis Q14 of 15
Microservices - Monitoring and Observability
You notice that your distributed tracing data in Jaeger shows many missing spans for some services. What is the most likely cause?
AThe network latency is too low
BThe services have too many CPU cores
CThe database is down
DThe services are not propagating the trace context headers correctly
Step-by-Step Solution
Solution:
  1. Step 1: Identify cause of missing spans

    If spans are missing, it usually means trace context was not passed properly between services.
  2. Step 2: Eliminate unrelated causes

    CPU cores, database status, or low network latency do not cause missing trace spans.
  3. Final Answer:

    The services are not propagating the trace context headers correctly -> Option D
  4. Quick Check:

    Missing spans = trace context not propagated [OK]
Quick Trick: Missing spans? Check trace context propagation [OK]
Common Mistakes:
MISTAKES
  • Blaming unrelated system resources
  • Ignoring header propagation
  • Assuming network latency causes missing spans

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes