Topology

The topology widget is able to display topologies of networks and other objects. We provide several layout options:

Editing Topology Widget

To configure a topology, select a Layout and specify either a Data Query or Data Source for Nodes and/or Edges.

To display Nodes without Edges, enable the Show nodes without edges option.

Next, configure the necessary fields for nodes and edges in the settings:

Node Configuration

Setting	Description
ID column	Unique identifier
Name column	Display name
State column	Determines the color coding for nodes based on their state. Valid states include: OK (green), Warning (yellow), Minor (orange), Major (red), Maintenance (blue), No Data (grey), or Undefined (white)
Icon column	To display a node icon use: Image names from the Settings/Files section (SVG images must include width, height, and viewBox attributes) Standard SKOOR images (e.g. device_server, device_router, etc.)
Group column	Nodes will be grouped based on this column.

SVG images used for node visualization automatically use the Accent 2 color settings defined in Settings / Theme.

Edge Configuration

Setting	Description
ID column	Unique identifier
Name column	Display name
State column	Determines the color coding for edges based on their state. Valid states include: OK (green), Warning (yellow), Minor (orange), Major (red), Maintenance (blue), No Data (grey), or Undefined (white)
Source column	Specifies where the edge originates. The value in this column must correspond to an existing node ID.
Destination column	Specifies where the edge terminates. The value in this column must correspond to an existing node ID.

Settings

Setting	Description
Layout	Layout for placing items on the view: `fCoSE`: The fCoSE layout is a faster version of the CoSE-Bilkent layout. It supports compound and non-compound graphs, giving top-tier end results and high performance for a force-directed layout. In addition, fCoSE supports user-specified constraints of the following types on nodes: fixed position, alignment, and relative placement. If a force-directed layout is desired, fCoSE should be the first layout to try. `Cola.js`: The Cola.js physics simulation (force-directed) layout. Cola makes beautiful layout results, it animates very smoothly, and it has great options for controlling the layout. It is focussed on giving aesthetically pleasing results for relatively small graphs. `AVSDF`: The AVSDF layout. It organises nodes in a circle and tries to minimise edge crossings as much as possible
Show nodes without links	This setting determines whether to display nodes that do not have links. If disabled and no links are configured, no nodes will be displayed.
Action on node/edge click	Define click action

Setting

Description

Layout

Layout for placing items on the view:

fCoSE: The fCoSE layout is a faster version of the CoSE-Bilkent layout. It supports compound and non-compound graphs, giving top-tier end results and high performance for a force-directed layout. In addition, fCoSE supports user-specified constraints of the following types on nodes: fixed position, alignment, and relative placement. If a force-directed layout is desired, fCoSE should be the first layout to try.
Cola.js: The Cola.js physics simulation (force-directed) layout. Cola makes beautiful layout results, it animates very smoothly, and it has great options for controlling the layout. It is focussed on giving aesthetically pleasing results for relatively small graphs.
AVSDF: The AVSDF layout. It organises nodes in a circle and tries to minimise edge crossings as much as possible

Show nodes without links

This setting determines whether to display nodes that do not have links. If disabled and no links are configured, no nodes will be displayed.

Action on node/edge click

Define click action

Parameters

Node parameters

Database column x of a node configuration can be accessed using the following notation:

${columns.x}

Example: The following Action on node click configuration opens the dashboard Device Details with URL parameter device set to the value of column devicename:

Edge parameters

Parameters like source or destination of links between nodes can have multiple values (e.g. in a connection between two devices, both can act as source and destination). Therefore they come in the form of arrays instead of single values (e.g. <value 1>,<value 2>). Although they are accessed the same way as single value parameters, they must be treated differently when used.

Example: Filter devices using edge configuration parameters:

device=IN(${columns.devicename})