Runtime map
Which services and instances exist, and who calls whom.
Who a request touches
Topology is generated from real calls; impact paths, service flow and flame graphs use the same call data.
Service topologyDiting
Topology generated from real calls
Services, hosts, containers, databases and queues change as calls change. You can see what differs from yesterday.
Impact paths, service flow, flame graphs
Impact paths
Which upstreams a slow request affects, and where failure spreads.
Service flow
Traffic and latency from entry to exit.
Relationship history
When the graph changed, and which release did it.
How relationships are built
| Nodes | Services, hosts, containers, databases, middleware |
|---|---|
| Edges | Real calls with latency, error rate and volume |
| Updates | Live, with historical snapshots |
| Drill-down | Any node opens traces, logs, metrics or sessions |
Fits
- Microservices, monoliths and mixed estates
- Teams that need to judge blast radius
Doesn't fit
- Estates with no east-west traffic that also forbid network capture
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.