The investigation surface exposes many valid signals but offers no ranked next move.
Broad access to telemetry protects exploration, while focused guidance protects engineers from losing time across disconnected evidence.
Who you’d be doing this for
“I had the trace, profile, and logs open, then spent ten minutes deciding what to check next.”
Chiamaka Appiah · Backend Engineer
Investigates latency regressions across services, dependencies, and database calls.
What is at stake
Engineers are switching among traces, profiles, logs, and metrics before finding a useful next step. You have to decide what guidance deserves ranking and how to prove it helps without taking control away.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- guided next steps vs. engineer control
- ranking quality vs. serving latency
- broad telemetry context vs. measurable first version
- offline relevance vs. live investigation behavior
Why Datadog
Datadog APM already brings traces, profiling, and troubleshooting data into the investigation path engineers use during performance incidents.
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.