One representative request path has to prove value without becoming the customer’s entire observability programme.
The evaluation needs enough cross-account coverage to make an investigation credible, while the customer protects its architecture review and limited change window.
Who you’d be doing this for
“I’ve got three service owners asking where the request went, and I’m still stitching account logs together.”
Chandni Kumar · Platform Engineer
Maintains the shared AWS environment used by application teams in the evaluation.
What is at stake
Engineers are rebuilding cross-account request trails by hand, so the evaluation cannot show a credible investigation. You have to weigh a representative proof against the customer’s limited change window and architecture review.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- representative coverage vs limited change scope
- time to first value vs reusable setup
- guided onboarding vs customer-operated pattern
- customer architecture review vs evaluation momentum
Why Datadog
Datadog APM must show distributed application teams how traces connect across the AWS boundaries where their incidents actually unfold.
Written with these in mind
Not your kind of problem? 53 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.