Customers need evidence of telemetry recovery before a regional failure turns into an investigation gap.
A useful resilience check must reveal real recovery behavior while protecting production Kubernetes workloads from unsafe experiments.
Who you’d be doing this for
“After the last regional wobble, I spent two days proving which traces we never received.”
Azmera Fekadu · Platform Engineering Lead
Owns reliability practices for a multi-region Kubernetes estate and prepares on-call teams for regional dependency failures.
What is at stake
Customers lack a safe way to test whether telemetry survives a regional dependency failure. You have to weigh useful recovery evidence against the risk of customer-operated disruption.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer self-service vs experiment safety
- broad coverage vs narrow launch scope
- fast learning vs platform consistency
- recovery evidence vs operational complexity
Why Datadog
Kubernetes, Datadog APM, and Datadog Logs already expose the signals a customer needs to judge telemetry recovery across distributed services.
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.