Impact
Dependencies
Upstream and downstream relationships are stored as explicit edges — or evidence-backed edges with a note. Topology is never invented.
Declared edges
Operators can record upstream/downstream services and external dependencies (APIs, databases, queues, workers) on the catalog service. Empty sections stay hidden.
Evidence-backed edges
Observed service relationships from telemetry may appear when correlation evidence exists — they are not guessed from titles or timestamps alone. See also Service Relationships.
Empty state
No edges means none were configured or observed — not that the system invented a flat topology.
Limitations
- Automatic full-mesh discovery from traffic alone is not claimed.
- Configure services first: Services.