The renewal depends on a trace path that is useful before the production change becomes hard to reverse.
Payment engineers need trustworthy end-to-end evidence, while the release window protects a service that cannot absorb a speculative instrumentation change.
Who you’d be doing this for
“I had three people asking where the request disappeared, and all I had was two disconnected traces.”
Victoria Walker · Staff Software Engineer
Technical champion for the customer’s payment platform and the engineer asked to explain incident paths to leadership.
What is at stake
Payment requests split into separate traces at the Rust service, blocking a trusted incident path. You have to weigh a fast proof-of-value against a production change the customer may not be able to unwind.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- renewal urgency vs production-change safety
- customer-specific proof vs reusable product learning
- fast remediation vs trace-level verification
- payment reliability vs instrumentation coverage
Why Datadog
Datadog APM must show that distributed traces remain actionable across the customer’s mixed OpenTelemetry and Rust service boundary.
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.