Correct relationship history is pulling against continuous access to live infrastructure changes.
A full rebuild protects data integrity while a constrained recovery protects customer write continuity.
Who you’d be doing this for
“My incident commander asked which workloads inherit this change, and the graph pointed to two different owners.”
Khamis Ndungu · Platform Engineer
Maintains Kubernetes infrastructure and uses relationship data to assess blast radius during a production change.
What is at stake
A consistency monitor found contradictory Kubernetes ownership links, but affected-tenant estimates range from 19 to 63. You must weigh a hard-to-reverse rebuild against customer write continuity and incomplete evidence.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- historical correctness vs write continuity
- rebuild speed vs proof of impact
- security confidence vs platform capacity
- automated estimates vs verified samples
Why Datadog
REDAPL relationships feed Cloud Security Posture Management, Resource Catalog, Cloud Cost Management, and Service Catalog.
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.