See and validate engineering network topology in Elastic

This package helps network engineering and observability teams turn inventory and adjacency evidence into a usable topology view in Kibana. It combines a stable engineering topology dashboard with Vega visualizations for zone layout and CDP/LLDP adjacency drill-down, plus an Agent Builder agent that audits whether discovered devices are ready to place on the map.

Use it when devices are being discovered but topology placement still fails because identity, role, site, zone, coordinates, or adjacency evidence is incomplete. The dashboard shows what is already known; the readiness agent makes missing or stale data explicit before you trust the picture.

When to use it

Use this download for network operations reviews, topology onboarding, inventory quality checks, and demos of engineering topology built on network_observability data. It is especially useful when you already collect SNMP, LLDP/CDP, FDB/MAC correlation, CMDB/NetBox, or cloud attachment evidence and need a Kibana starting point that separates observed facts from inferred placement.

What is included

[Network Engineering] Topology v2: Kibana dashboard for stable engineering topology with clickable devices and links.
Zone Topology: Vega visualization for zone-aware device layout with interface and discovery detail.
Adjacency Inspector: Vega visualization for clickable CDP/LLDP adjacency review and link drill-down.
Navigation and Source Contract: markdown panels that explain how to use the dashboard and what source data it expects.
Network Topology Mapping Readiness: Agent Builder agent that audits identity, classification, adjacency, and layout evidence and reports mapping readiness gaps.
ZIP package with one Kibana NDJSON export and one Agent Builder JSON definition for import into a compatible Kibana environment.

Expected inputs and review steps

The Vega views expect network inventory and topology indices such as logs-network.inventory_v2-* and logs-network.topology_v2-* with network_observability.* fields for device identity, layout, zone, and link adjacency. After import, review data views, field mappings, time range, and filter behavior before using the dashboard in production.

The readiness agent relies on tools such as network.topology_layout_readiness, network.topology_adjacency_readiness, inventory, topology links, and interface or sensor health. Treat SNMP reachability as reachability only, not as proof of physical adjacency, and review the agent instructions before enabling it for operators.

Compatibility and source

Source files were checked for an explicit Elastic/Kibana tested version. No Stack version was stated in the package. The NDJSON saved objects report a Kibana core migration version of 8.8.0. Leave compatibility unset until the package is validated against a target cluster, and review Agent Builder artifact formats after import because they can change quickly.

Source: creator-submitted Kibana saved-object and Agent Builder export. Dashboard ID: network-engineering-topology-v2. Agent ID: network-topology-mapping-readiness.

Tested versions
ECS compliant	Ready for publishing review

You must log in to submit a review.