Distributed Tracing — Vocabulary and Communication
Learn to read, describe, and discuss distributed traces in English.
0 / 10 completed
1 / 10
What is a 'trace' in distributed tracing?
A trace is the complete record of a single request's journey — from the entry point through all downstream services and back — represented as a tree of spans.
2 / 10
What is a 'span' in distributed tracing?
A span represents a single unit of work (e.g., one HTTP call, one database query) within a trace. Spans have a start time, duration, and metadata (attributes).
3 / 10
What is a 'latency waterfall' in tracing?
A latency waterfall (or flame graph/Gantt chart view) shows spans arranged by time, making it easy to see which service is the bottleneck in a distributed trace.
4 / 10
What does 'tail-based sampling' mean in tracing?
Tail-based sampling makes the sampling decision after seeing the full trace — allowing you to always capture traces that contain errors or high latency, regardless of sampling rate.
5 / 10
What does 'root span' refer to in distributed tracing?
The root span is the first span in a trace — typically representing the entry point (e.g., an HTTP request to the API gateway). All other spans are children of the root span.
6 / 10
During a code review for the new payment service, Sarah notices a long latency spike in the logs associated with a specific API call. The tracing system labels this span as 'high_risk'. What does it likely mean that this span is labelled 'high_risk'?
In distributed tracing, 'high-risk' typically indicates that the span has a significant latency or is associated with components known to be prone to errors. This doesn't necessarily mean it *is* an error, but rather that it requires closer scrutiny due to its potential impact. The label serves as a prioritization signal for developers.
7 / 10
You're collaborating with Alex on debugging an issue where requests to the order processing service are intermittently failing. He suggests using 'sampled traces'. What is the primary purpose of employing sampled traces?
Sampled traces are used to manage the immense volume of data generated by distributed tracing. By examining only a portion (or 'sample') of requests, we can gain insights into overall system behavior without overwhelming storage and processing resources. This allows for efficient analysis of common patterns and potential issues.
8 / 10
During a standup meeting, David mentions he's been using the tracing system to investigate slow database queries. He describes the data as being presented in a 'latency waterfall'. What does this visualization typically show?
A 'latency waterfall' is a visualization that displays the sequential breakdown of latency across multiple services involved in a request. It shows how time is spent within each component – from the initial invocation to the final response – highlighting potential bottlenecks and areas for optimization. Think of it like tracing the flow of water down a waterfall.
9 / 10
As part of a new feature release, you're configuring your distributed tracing system. You need to decide which span should be considered the 'root span'. What is the fundamental role of the root span?
The root span is the starting point of any distributed trace. It contains initial context such as correlation IDs that are propagated down through subsequent spans. All other spans are derived from this root span, forming the complete trace and allowing you to follow a request's journey across multiple services.
10 / 10
You receive an email from the operations team detailing increased latency during peak hours. The subject line mentions 'tail-based sampling'. What is the significance of this technique in relation to tracing?
Tail-based sampling is a strategy for optimizing tracing by focusing on collecting traces that have the longest durations. These 'tails' of longer traces are frequently indicative of performance bottlenecks or errors. By concentrating efforts on these longer traces, you can maximize the value gained from your tracing data and reduce unnecessary storage costs.
What will I practise in "Distributed Tracing — Vocabulary and Communication"?
This module focuses on Observability Engineering — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Observability Engineering exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around observability engineering — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Observability Engineering exercises?
See the Observability Engineering hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.