Topology
Reports
Export and dependency view for this scope, across Org, Network, Site and Gateway levels.
Dependency graph
Every node's config is resolved from its parent's (device rule 8: "the device never computes hierarchy or inheritance -- it receives configuration the cloud has already resolved"). That parent relationship, already carried by every row's own parent_id, is the one real dependency relationship this schema has -- shown below, not a separate invented graph.
Blocker: no non-hierarchical device-to-device dependency data model exists yet.
A genuinely different kind of dependency -- e.g. "Gateway A's uplink depends on Gateway B" -- would need its own concept (something like a depends_on or per-device uplink/neighbor table). Grepped this schema for one before writing this page (any depends_on, parent_device_id, uplink, or neighbor table) -- none exists. Not invented here.
Not built yet.
A topology/health-over-TIME rollup (structure and fault counts trended across a period, per Org/Network/Site/Gateway) is still not built -- no topology-history or topology-snapshot table exists anywhere in this schema to report on. /topology/list only ever returns the CURRENT tree, already shown live in the tree view above this page.