The fastest investigation path may point at the loudest symptom rather than the originating failure.
Engineers need less manual evidence gathering, while every ranked cause still needs enough proof to guide a production fix.
Who you’d be doing this for
“I spent half the incident proving the database was downstream, then someone asked why we never looked at the caller.”
Rami Khoury · Senior Software Engineer
Operates a distributed service whose failures must be diagnosed from traces and profiles during production incidents.
What is at stake
Recurring failures send engineers through traces, profiles, and changes without agreement on where the chain began. You must decide what AI can assemble and rank, and what evidence still requires an engineer's judgment.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster triage vs. causal confidence
- runtime evidence vs. code context
- AI ranking vs. engineer accountability
- pilot speed vs. sustainable ownership
Why Datadog
Datadog APM and Datadog Profiling hold the trace and runtime evidence that must connect a distributed failure to an engineer's next decision.
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.