SERVICE MAP
- Checkout
- Payment
- Stripe
KNOWN
- Dependency
- Traffic
- Latency
- Errors
SYSTEM INTELLIGENCE & TOPOLOGY
AutoObserve builds a living model of your production environment—runtime entities, dependencies, infrastructure, changes and ownership—giving AIDDE and Investigation the context required to reason about failures.
One system graph. Different operational questions.
SYSTEM INTELLIGENCE
KNOWN
Service
Checkout
v2.14.7 · Changed 83s ago
Service
Payment
▲ Impacted
External
Stripe
◐ Unknown
UNDERSTOOD
Topology isn't the visualization. The system model behind the visualization is the product.
01 / DISCOVER
AutoObserve discovers runtime relationships from production evidence, then resolves heterogeneous entities into one System Graph.
OBSERVED TRACE
DISCOVERED RELATIONSHIP
Runtime relationship
Discovery sources
SYSTEM GRAPH
Heterogeneous entities
team
Commerce
Healthy
service
Checkout
Healthy
v2.14.7
service
Payment
Healthy
pod
Pod-7f3
Healthy
database
orders-db
Healthy
external
Stripe
Unknown
Traffic shifts, canaries, and ephemeral infrastructure change the graph without a static CMDB rewrite.
10:00
Checkout ─────▶ Payment-v1
10:30
Checkout ── 90% ▶ Payment-v1 · 10% ▶ Payment-v2
11:00
Checkout ─────▶ Payment-v2
02 / UNDERSTAND CHANGE
Topology without change history tells you what exists. Temporal topology helps explain what happened.
Incident timeline
14:30:00
DEPLOYMENT
checkout-api v2.14.2 → v2.14.7
14:31:23
CHECKOUT LATENCY
Checkout latency ↑
14:31:26
CHECKOUT ERRORS
Checkout errors ↑
14:31:29
PAYMENT FAILURES
Payment failures
14:31:34
ORDERS FAILURES
Orders failures
INCIDENT
14:31:34
Checkout v2.14.7 likely origin — Payment and Orders impacted
service
Checkout
Degraded
v2.14.7
LIKELY ORIGIN
service
Payment
Impacted
IMPACTED
service
Orders
Impacted
IMPACTED
Each state updates the same graph geometry—before, during, and after the incident—so change history stays visible without leaving the system model.
03 / REASON
A dependency tells AutoObserve who talks to whom. It does not by itself tell AutoObserve who caused whom to fail.
Dependency
Checkout ───────▶ Payment
This tells AutoObserve: Checkout calls Payment.
Not a cause
Checkout caused Payment to fail
It does NOT tell AutoObserve: Checkout caused Payment to fail.
Build causality progressively
DEPENDENCY
Checkout ─────────▶ Payment
TEMPORAL ORDER
Checkout degraded 6 seconds earlier
TELEMETRY EVIDENCE
Failures propagate along dependency
CHANGE
Checkout deployed 83 seconds earlier
CAUSAL HYPOTHESIS
Checkout likely contributed to Payment degradation.
Causal edges are hypotheses—labeled likely, never declared fact.
Edge epistemology
Observed relationship
Thin solid edge
Checkout ─── calls ───▶ Payment
Inferred causal relationship
Heavier/double edge + label
Checkout ══ likely propagation ══▶ Payment
Unknown / unverified relationship
Dashed edge
Checkout ┄┄ possible ┄┄▶ Inventory
Structural timeline
14:30:00
DEPLOYMENT
checkout-api v2.14.2 → v2.14.7
14:31:23
CHECKOUT LATENCY
Checkout latency ↑
14:31:26
CHECKOUT ERRORS
Checkout errors ↑
14:31:29
PAYMENT FAILURES
Payment failures
14:31:34
ORDERS FAILURES
Orders failures
Causal path
service
Checkout
Degraded
v2.14.7
LIKELY ORIGIN
service
Payment
Impacted
IMPACTED
service
Orders
Impacted
IMPACTED
04 / UNDERSTAND IMPACT
Blast radius turns topology into operational scope — what is affected, what depends on it, and who owns the response.
Blast radius
Checkout is selected—toggle to clear blast radius focus.
service
Payment
Impacted
IMPACTED
service
Orders
Impacted
IMPACTED
external
Stripe
Unknown
INDIRECT
UPSTREAM
Who depends on Checkout?
DOWNSTREAM
What does Checkout depend on?
EXPLORE SYSTEM INTELLIGENCE
The same System Graph answers different operational questions through lenses — without rebuilding the diagram.
PRODUCTION SYSTEM
14:31:34
QUESTION
Who talks to whom?
Observed runtime relationships
Selected
Checkout
service · Healthy · v2.14.7
Emphasised
Upstream
Downstream
Phase: DEPENDENCIES. Who talks to whom? Observed runtime relationships Selected entity: Checkout. Upstream dependents: Web. Direct dependencies: Inventory, Payment, Orders. Incident state: Stripe: Unknown.
SYSTEM INTELLIGENCE
AIDDE and Investigation consume the System Graph for situation formation, causal testing, and impact — Topology is the structural dimension of the same incident.
PLATFORM CONTEXT
Production signals
System Graph
Reasoning consumers
WITHOUT SYSTEM INTELLIGENCE
3 SIGNALS
WITH SYSTEM INTELLIGENCE
1 INCIDENT CANDIDATE
WEAKENED
Payment provider caused checkout failures
Dependency exists, but temporal order and traces contradict origin.
STRENGTHENED
Checkout deploy likely contributed
Graph path + change window + expected indicators align.
Topology supplies structural questions; Multi-DSL supplies telemetry evidence for Investigation context.
SYSTEM INTELLIGENCE
MULTI-DSL
TECHNICAL FOUNDATION
Discovery sources feed entity resolution and relationship discovery into a System Graph consumed by AIDDE, Investigation, and product UX.
01
Discovery Sources
02
Entity Resolution
03
Relationship Discovery
04
System Graph
05
AIDDE · Investigation · Product UX
DISCOVERY SOURCES
Core definitions
Entity
Something that exists in the runtime environment.
Service · Pod · Deployment · Database · Queue · Cloud Resource
Relationship
A typed connection between entities.
calls · runs_on · reads_from · owns · depends_on
Observation
Runtime evidence associated with an entity or relationship.
Request rate · Error rate · Latency · Trace spans
Change
An event that modifies system state.
Deployment · Config change · Scaling event
Snapshot semantics live in product docs — not on this page.