The checkout path is visible at the edge and in the backend, but not as one request.
The evaluation needs a fast investigation story while the customer protects its existing edge configuration and request data.
Who you’d be doing this for
“I had a slow order in front of me, and I still had to ask three teams where it went.”
Emil Dahl · Staff Software Engineer
Technical champion for the customer’s checkout services and the person expected to validate the proof of value.
What is at stake
Checkout requests split into separate edge and backend traces, forcing engineers to reconstruct the path by hand. You must weigh a fast, convincing trace path against safe changes to the customer’s live edge configuration.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- end-to-end visibility vs. stable edge configuration
- evaluation speed vs. production safety
- trace continuity vs. request-data boundaries
- narrow scope vs. convincing proof
Why Datadog
Datadog APM has to show the full distributed request path when customer traffic crosses Cloudflare before reaching instrumented services.
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.