Fast dependency lookups are pulling against stable ingestion throughput.
Resource Catalog needs bounded traversal work while REDAPL continues absorbing infrastructure updates.
Who you’d be doing this for
“I had the alert open, but the dependency view spun long enough that I started mapping it by hand.”
Githinji Nsabimana · DevOps Engineer
Uses Resource Catalog during production incidents to identify downstream infrastructure dependencies.
What is at stake
p95 traversal latency reached 3.4 seconds for a known high-fan-out request pattern. You must weigh faster graph reads against the ingestion headroom shared by every tenant.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast traversals vs ingestion headroom
- narrow optimization vs durable coverage
- release speed vs production evidence
Why Datadog
REDAPL powers Resource Catalog and other products that depend on current infrastructure relationships.
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.