Atlas
IN DEVELOPMENTInfrastructure topology and incident correlation platform - mapping dependencies from OTel traces, Kubernetes state, and alerting into a graph database
The Problem
Infrastructure dependencies are scattered across multiple systems. When something breaks, engineers manually piece together which services depend on what, check multiple dashboards, and dig through past incidents. There's no single place that shows the full picture.
The Approach
Building a platform that automatically maps infrastructure dependencies from real data - OpenTelemetry traces show service-to-service calls, Kubernetes API shows cluster topology, AlertManager shows what's firing. All stored in Neo4j as a graph so you can trace impact paths deterministically, not through ML guesswork.
What's Built
Topology builder that polls OTel traces and maps dependency edges into Neo4j. Kubernetes agent that watches cluster state via informers. REST API serving the topology to a Next.js frontend. The foundation for incident correlation is in place.
Where It's Going
Deterministic incident resolution - when an alert fires, trace the dependency graph to identify the root cause from actual infrastructure topology. Connect to historical incidents and runbooks for context. The goal is what tools like Dynatrace do with ML, but built on real dependency data.