Microservices - Monitoring and Observability
In a microservices system using Zipkin, a span shows a duration of zero milliseconds. What is the most probable cause?
In a microservices system using Zipkin, a span shows a duration of zero milliseconds. What is the most probable cause?
medium📝 Analysis Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze zero duration span causes
Zero duration usually means start and end times are the same, often due to instrumentation errors.Step 2: Evaluate other options
Instant processing is unrealistic; network drop or missing trace ID would cause missing spans, not zero duration.Final Answer:
Span start and end timestamps are identical due to incorrect instrumentation -> Option CQuick Check:
Zero duration span = Instrumentation error [OK]
Quick Trick: Check instrumentation if span duration is zero [OK]
Common Mistakes:
MISTAKES- Assuming instant processing is possible
- Blaming network for zero duration
- Confusing missing trace ID with zero duration
Master "Monitoring and Observability" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes