Skip to content

Topology Map#

The Unryo Topology Map lets you visualize your infrastructure across multiple topology layers. Additionally, with the Topology Data API and the list of Supported Data Sources, you can retrieve your own topology data into a consolidated view.


The Unryo Topology Map enables you to:

Map Concepts#

The Topology Map has two objectives:

  • Accelerate issue resolution with visual assistance.
  • Act as a data source for the Correlation Engine to identify root-causes and calculate impacts.

Nodes, Edges and Layers#

  • A node - displayed as a circular icon - represents a physical or logical entity such as a network device, an IP network, a VLAN, a VM or a business service.

  • An edge (relation) - displayed as a line - connects two nodes. If multiple relations exists between two nodes, the map will draw one line per relation.

  • An edge is associated to a layer, such as Layer 2, IP Network, VLAN, Application, Business Services or a custom one. The map can display topology for a specific layer or combine multiple layers in a single view.

How Unryo learns the Topology#

Dynamic Mapping from Live Data#

As live monitoring data points come in, Unryo learns the relationships to model the topology, keeping it continuously up-to-date. The result is a real-time, always trustable representation of the infrastructure, which is updated dynamically as the network evolves.

Teams visualize maps that are rendered on the fly, showing the exact real-time topology of the entire environment, both on-premise and in the cloud, and of business-critical applications.

Network L2/L3 Topology#


With the Unryo Discovery Engine, you can run a network discovery and find additional multilayer dependencies in your infrastructure. The Discovery Engine uses a variety of protocols such as SNMP, LLDP, CDP, Forwarding Tables and other methods.

External Topology Sources#

Unryo provides mechanisms to enable users to import their own data as the source for the topology. Unryo's topology model and map representation are open and extensible, capable of receiving and combining topology data from multiple sources.

Importing topology from external sources is optional. By default, when Unryo starts polling metrics from your infrastructure, the topology is instantly learned as the data comes in, and topology maps are automatically rendered. You will also get the physical and logical connectivity between network devices if you have activated the Unryo network discovery.

Use the Search Bar Field to locate a node.

  • once the node is selected, the map shows the node in question and its immediate neighbors.
  • both nodes and edges are colored to reflect their most severe active alarm.
  • grey icons are used for non-monitored nodes.

Use the Layer Dropdown to switch the view from one layer to another.

  • If the node has relations from multiple layers, you can display a multi-layer map using the Expand option from the node tooltip.

Hover over a node or an edge, or click to bring a contextual tooltip:

  • Metadata information: different data - tags and metrics - can be shown in a way that is contextual to the node or edge type.
  • Monitored: YES means the node is monitored by Unryo (metrics are collected). NO means the node has been discovered - for example as a neighbor - or imported by the Topology API, but is not monitored by Unryo.
  • Discovery (Method): Indicates from which data the node or the edge is modelized. UNRYO METRICS if from the monitoring metrics. LLDP/CDP, VLAN or IP if from a network discovery. Other values possible (i.e. 3rd-Party)
  • Last Processed At: Time of the last processing update. If two or more discovery methods are used (ie. UNRYO METRICS + LLDP) then the most recent processing time is shown.
  • Reachability: ONLINE means metrics are received for this node. OFFLINE means metrics are no longer being received for this node.
  • Status: Shows the most severe currently active alarm.
  • Recenter: To make this resource the new center of the map.
  • Expand: Show node neighbors for that node on the given layer.
  • Inspect Resource: Link to the Performance Dashboard, the Explore View or the Alert Console.

Launch a Network Discovery#


A network discovery of your network can be launched from the Configuration Management section. It uses SNMP to collect information from various tables, including CDP, LLDP and IP.

Querying Topology Data using the API#

The topology API abstracts differences/complexity of the underlying sources, and provides a simple way to:

  • search for map nodes
  • get map node properties
  • list neighbors
  • get map edge properties

Integration with external systems#

There are several ways of integrating the topology map with external systems.

Import your data#

The first is to import your data into Unryo, either by pulling it from your external system or pushing it to Unryo.

Unryo accepts data from multiple sources (e.g. TCP and HTTP) and in multiple formats, including:

  • Binary
  • Collectd
  • CSV
  • Graphite
  • Grok
  • InfluxDB Line Protocol
  • JSON
  • Nagios
  • Prometheus
  • XPath

Following Unryo data model#

Timeseries data that is gathered or received continuously and which follows a clear parent-child hierarchy is amenable to being integrated with Unryo's hierarchical data. Such data can simply be pushed to InfluxDB in Unryo with the following mandatory tags: resource, resource_type, resource_parent, resource_parent_type; and a single mandatory field: resource_availability, whose value is typically 0 (the resource in question is unavailable) or 1 (the resource is available).

Using your own data model#

The Unryo topology backend can also be configured to accommodate other arbitrary data models. You can push your data to InfluxDB. Each InfluxDB Line Protocol line must encode one or more relationships between neighbours. The topology backend can then be configured such that it is able to properly retrieve the data.

Handling log/event data#

In Unryo, log data is typically pulled or received by fluentd, and then written in Opensearch. For the purposes of the topology map, the data is then aggregated and written in InfluxDB by using the Unryo Opensearch Query Telegraf plugin to select a subset of log fields.

Expose your data#

You may also expose your data via a REST API with four endpoints that mirror our APIs endpoints:

  • An endpoint that allows searching for nodes
  • An endpoint that allows retrieving the details about a specific node
  • An endpoint that allows retrieving the details about a specific edge
  • An endpoint that returns the neighbours of a given node on a given layer

This option allows the topology backend to forward requests it receives to external systems and to include data from those external systems in the topology map.