Automatic Network Topology Mapping in PRTG
As a Network Engineer, I want PRTG to automatically generate and maintain a dynamic visual topology map of my network — including Layer 2 and Layer 3 relationships — directly from auto-discovery data, so that I can instantly understand the physical and logical structure of my environment, quickly identify the impact of failures, and share live network views through dashboards without relying on third-party tools.
What we're looking for:
- A dynamically generated topology map that updates as the network changes
- Integration with the existing Maps/Dashboards editor so topology views can be embedded in dashboards
- The ability to drill down from the topology map directly into device and sensor details
- We would love to see native automatic topology mapping built directly into PRTG, without requiring a third-party integration like UVExplorer.
Why this matter:
Other vendors already offer this capability natively through its Network Topology Mapper, and it is one of the features that customers frequently highlight when evaluating monitoring platforms. We are aware of several customers who are considering switching from other vendors to PRTG, but the absence of native automatic topology mapping is a blocker for them. Having this feature in PRTG would not only retain these potential customers but also make PRTG a truly complete and competitive network monitoring solution.
Carl Chan
shared this idea
-
Nabila
commented
It would be grate also to expand this feature to further improve PRTG in the following:
- when doing subnets discovery to ensure it not adding multiple IPs if same device has different IPs, it shall add as one.
- to show the mapping up to port level
- automatic dependency mapping to avoid alert flood. for example if main device connecting to a branch got impacted, it shall pause all that branch by dependency - this to be as optional or customized feature. -
Marc Prakke
commented
As a Network Engineer, I want PRTG to automatically map network devices and their interconnections on maps using LLDP/CDP neighbor data — including port-level connection details — so that I can maintain an accurate, up-to-date network topology visualization without manual effort, and leverage the same discovery data to automatically configure device dependencies.
Should also be great if this can be used together with autodiscovery. But adding device to a map will auto connect to the devices in this same map with port info.