Datadog APM & Distributed Tracing Fundamentals free question 1 / 10 · Domain 1: APM Fundamentals
In a microservices system, you want to follow how a single request moved through several services from end to end. Which approach does the use case table in the official documentation list for this?
- Overlay each service's metrics on one graph in the Metrics Explorer
- Query across the distributed services in the Trace Explorer to see end-to-end traces
- Follow the lines between services on a service map to read their dependencies
- Search all logs in the Log Explorer and sort them by timestamp
Show the answer and explanation
Answer: B
Why this is correct
The APM use case table pairs "Understand how requests flow through your system" with the Trace Explorer, which you use to query and visualize end-to-end traces across distributed services. Individual spans are joined into a single trace through trace context propagation, so the path across services can be followed as it happened.
Why the other options are wrong
"Follow the lines between services on a service map to read their dependencies" … A service map shows how services are connected overall, but the use case table does not list it as the way to reconstruct the path of one request.
"Overlay each service's metrics on one graph in the Metrics Explorer" … Metrics show trends, but they cannot trace the route of an individual request.
"Search all logs in the Log Explorer and sort them by timestamp" … Logs can provide clues, but they are not the tool the documentation lists for this use case.
Key point
Even among things that "investigate", the screen you use depends on whether your subject is the path of one request or the trend of a whole population. Paths belong to the Trace Explorer; trends belong to metrics and dashboards.