Partial traces need explanation without pretending absent context is known.
A clear investigation path protects engineer confidence while cautious evidence handling protects trace accuracy.
Who you’d be doing this for
“I spent an hour comparing headers and spans just to find where this trace stopped being connected.”
Almaz Mutua · Senior Platform Engineer
Maintains ingress and service instrumentation for a distributed application team using multiple request boundaries.
What is at stake
Partial traces leave engineers manually comparing proxy headers and service spans to locate lost context. You have to weigh a simple guided view against the risk of overstating incomplete evidence.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- guidance clarity vs evidence certainty
- new investigation surface vs SDK-first investment
- fast diagnosis vs unsupported promises
- customer usability vs cross-language consistency
Why Datadog
APM SDKs and distributed tracing are the connection between external request boundaries and the services customers need to diagnose.
Written with these in mind
Not your kind of problem? 40 more at Datadog, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.