DevOps Practitioner · Module 7: Applied observability and SLOs · Lab
Follow a Failure Trace Across Logs with a Shared Request ID
45 min hands-on · Core
A local machine with a two-service fixture emitting structured logs with request IDs; a failing request scenario provided.
Local guide: run the steps below on your own machine in order, then check the validation list.
Objectives
- Propagate one request ID across both fixture services
- Assemble the failure timeline from both logs by ID alone
- Name the failing hop with its evidence quoted
Step 1
Run the failing request
Trigger the provided failure scenario and capture both services' logs. Confirm the same request ID appears at every hop.
Step 2
Assemble by ID
Filter both logs to the single request ID and order the lines by time. Write the timeline: edge received, downstream called, failure returned.
Step 3
Name the hop
Quote the lines that identify the failing hop and its cause class (timeout, wrong status, missing dependency). State what the timeline proves and what needed the next lesson's traces.
How to confirm it worked
- Same request ID quoted at every hop in both logs
- Timeline assembled from ID filtering, ordered by time
- Failing hop named with quoted evidence