Microservices - Monitoring and Observability
In a Zipkin trace, if a child span has a duration longer than its parent span, what is the most likely cause?
In a Zipkin trace, if a child span has a duration longer than its parent span, what is the most likely cause?
medium📝 Analysis Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Understand span timing relationships
Child spans should not exceed parent span duration unless clocks are not synchronized.Step 2: Identify cause of timing mismatch
Clock skew between services causes inconsistent timestamps, making child span appear longer.Final Answer:
Clock skew between services -> Option AQuick Check:
Child span longer than parent = Clock skew [OK]
Quick Trick: Clock skew causes timing inconsistencies in traces [OK]
Common Mistakes:
MISTAKES- Blaming span names for timing issues
- Assuming missing trace ID causes duration errors
- Confusing network latency with span duration
Master "Monitoring and Observability" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes