The APM footprint is cheaper, but the on-call investigation path is broken.
Finance is protecting a fixed telemetry spend while DevOps is protecting the ability to trace failures across services.
Who you’d be doing this for
“We saved money, then spent an hour guessing where the request disappeared.”
Ebuka Traore · DevOps Engineer
Runs on-call for a distributed application and relies on correlated telemetry to investigate production incidents.
What is at stake
APM usage fell after a cost review, and on-call engineers lost request paths across two services. You have to weigh a smaller telemetry footprint against the evidence responders need during incidents.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- telemetry spend versus incident evidence
- fast restoration versus durable adoption
- finance certainty versus DevOps visibility
- narrow service scope versus renewal value
Why Datadog
Datadog APM must remain part of the customer’s incident workflow when observability budgets are under review.
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.