Skip to main content
The Topology Explorer renders your cloud infrastructure and service relationships as an interactive map. Let agents discover the map from live cloud APIs, import it from Infrastructure as Code, or build it by hand.
Topology Explorer

​
Build a topology map

Ask an agent to discover resources and relationships directly from your connected cloud accounts. The map stays synced as your infrastructure changes.
Discovery requires an active connection for each provider you want mapped.

​
Resource types

The Topology Explorer supports all major cloud resource types:

​
Views, filters, and export

​
How agents use topology

Every agent can read the topology map and reason over dependency paths:

​
Topology-driven RCA

Topology speeds up root cause analysis because most incidents originate in a dependency, not in the service that alerted. Here is a worked example. The alert: checkout success rate drops to 60%. Checkout logs show scattered timeouts, but the payment service, database, and cache all report healthy.
  1. Start from the alert, not from logs. Center the map on the alerting service with health overlaid:
    Topology showing service dependencies
  2. Trace upstream. The map shows the dependency chain checkout service → payment gateway → external payment API — and the external API node is marked degraded.
  3. Confirm with metrics and rule out recent changes before acting:
    Alex shows timeouts concentrated on the gateway-to-external-API edge, with no recent deployments on the payment path — confirming the third-party provider as the origin.
  4. Resolve and document. Fail over to the backup payment provider, then export a topology snapshot for the incident record and postmortem.

​
Reading a cascading failure

When several services fail at once, the topology timeline view shows the origin and the propagation order in a single view, instead of each team investigating its own service. In this cascade, every downstream failure traces back to one expired SSL certificate:
Build your topology and connect health data sources before an incident. A pre-built, synced map is what makes the first step take seconds instead of minutes.

​
Other things to ask

  • @alex show downstream dependencies of payment-service — check blast radius before a risky change
  • @oliver map all connections from instance i-0abc123 — scope security exposure during an investigation
  • @tony map every service connecting to the production database — find the source of connection exhaustion
  • @kai show service dependencies and single points of failure in the cluster — harden Kubernetes reliability
  • @alex compare the production topology with the DR region and list missing resources — validate disaster recovery coverage

Resources

View all discovered infrastructure resources

Root cause analysis

Run agent-led RCA on incidents

Assessment

Run infrastructure assessments