Collector 0.2.0-dev: what it collects for topology
The exact topology data the in-development 0.2 collector emits, and what is intentionally not collected yet.
Updated Aug 24, 2026Product 0.2.0-dev5 minMSP operator, Internal IT, Developer
What Collector 0.2.0-dev emits
- interfaces — ifIndex, name, description, MAC, type, MTU, speed, admin/operational status, PVID
- vlans — VLAN id and name per device
- ip_addresses — address, prefix length, subnet, associated interface/VLAN
- routes — destination, prefix length, next hop, interface, metric
- neighbors — LLDP/CDP neighbor records with local/remote port and system identifiers, plus confidence
- forwarding — MAC forwarding-table entries with bridge port and VLAN
- subnets — CIDR, gateway, VLAN, internet-exposure flag
- links — the derived topology edges built from the above
What is NOT yet collected
Not live yet
ARP tables, trunk/tagged-VLAN membership, STP topology, LACP/port-channel membership, switch stacking, interface utilization counters, WAN/VPN circuit detail, and vendor-specific APIs (e.g. Meraki, Aruba Central) are not yet collected. Any UI element referencing these is labelled Placeholder — not yet collected.
Error codes covered
Was this helpful?