The Grand Fleet’s delivery is running, but the navigation log has stopped telling the truth. Every commission is supposed to leave one clean line, from the moment a captain fills in the papers to the harbor master bringing the finished vessel into formation, all recorded as a single voyage you can read end to end. Lately the log goes dark the instant a vessel leaves the office for the yards, and at the far end captains keep signing for the wrong cargo, salt-pork where citrus was ordered, though every yard along the route reported a clean, successful run. No single tool shows anything wrong. Repair the log so a commission reads as one unbroken voyage again, then use that complete picture to find where the cargo goes astray, and set it right.
Play This Challenge to Learn
- How trace context crosses an asynchronous boundary with no call chain: a commission carries its W3C traceparent to a push-triggered pipeline, so its spans continue the same trace instead of starting a new one
- Why a distributed trace reveals what per-tool logs cannot: the value that flowed through each step, so a fault surfaces where the data diverges
- How to read that trace in Jaeger to localise a fault to a single service by following one attribute across the whole voyage
Awards & Deadline
Complete the challenge and post your solution in the community before the deadline to be eligible.
1st place: 50% voucher for a Linux Foundation certification
Top 3: Credly badge to showcase the achievement
Deadline: 28 July 2026 at 23:59 CET
Play Now
Share your solutions, your questions, and the moment it clicked in this thread. We’re looking forward to seeing how you repaired the log and traced the cargo back to its source.
