Skip to content

4.2 Structure

General Information

This section explains how to configure the physical and logical structure of a MultiProbe deployment. For an introduction to the MultiProbe architecture, see Section 1.3.

MultiProbe consists of nodes (servers running the MultiProbe software) placed in locations. Locations represent geographically or structurally distinct sites, connected to each other in a hierarchy. This hierarchy can reflect geographic distribution, network topology, or any organizational structure that makes sense for your deployment.

All nodes belong to the root location called System, which is the top of the hierarchy and contains all other locations.

Access to locations can be restricted by user group — see Section 4.1.5.

Structure configuration is done in Administration → Structure, which contains three screens: Location types, Hierarchy, and Nodes.

Figure 41. Structure menu Figure 41. Structure menu

Recommended configuration order:

  1. Define location types and build the location hierarchy — Section 4.2.2
  2. Assign each node to a location — Section 4.2.3

Info

Nodes cannot be created manually from the UI — they are registered automatically during MultiProbe installation. If a node is not visible in the list, verify its network availability from the Central Server (see Section 2.7).

Locations

Location Types

Before building the hierarchy, define the types of locations your structure will use (e.g., Country, City, Facility, Room).

To manage location types, go to Administration → Structure → Location types. Click New location type and enter a name and description.

Figure 42. Location types list Figure 42. List of Location types

Location Hierarchy

Once location types are defined, build the hierarchy tree in Administration → Structure → Hierarchy. The System location is always the root — all user-defined locations are nested within it.

To add a new location:

  1. In the left panel, select the parent location under which to create the new entry.
  2. Click New child hierarchy.

  3. In the window that opens, fill in:

    • Name — the location name.
    • Location type ID — the type defined in the previous step.
    • Groups — user groups that work at or have access to this location.
    • Description — optional free-form description.

Figure 43. New location window Figure 43. Window for adding a new location

An example of a completed hierarchy is shown below.

Figure 44. Example hierarchy Figure 44. Example of Hierarchy screen

Nodes

Nodes are the servers running MultiProbe software. Every node must be assigned to a location from the pre-configured hierarchy.

To open the node list, go to Administration → Structure → Nodes.

Figure 45. Node management screen Figure 45. Screen for working with nodes

The node list contains the following columns:

  • Node ID — assigned automatically during installation, cannot be edited.
  • Name — user-defined name.
  • Description — free-form description.
  • IP Address — management interface IP address.
  • Location — the location where this node is placed.
  • Type — System (Central Server) or Probe (monitoring node).

Local menu actions:

Icon Action Description
Delete Remove the node from the list
Edit Edit node parameters
Dashboard Open the node summary screen

Editing Node Parameters

To edit a node, open the Edit window from the context menu. The edit window has two tabs.

Main tab — core parameters:

  • Name — user-defined node name.
  • Description — free-form description.
  • IP Address — management interface IP address.
  • Location — select from the location hierarchy.

Figure 46. Node edit window — Main tab Figure 46. Node edit window with Main tab

Thumbnails tab — parameters for thumbnail and mosaic image generation:

  • Thumbnail folder — storage folder for thumbnails. Default: C:\ProgramData\Stream Labs\MultiProbe\Stream Labs MP Probe Manager Service
  • Mosaic folder — storage folder for Video Thumbnails widget images (see Section 12.5.2). Default: same as above.
  • Period — thumbnail capture interval. Default: 15 seconds.
  • Codec — file format for static thumbnails. Default: .png.
  • Height — thumbnail height in pixels. Default: 80 px.
  • File storage depth — retention period for thumbnail files. Default: 2 days.
  • Burn timestamp — embeds a timestamp into each thumbnail image indicating the exact moment the frame was captured.

Figure 47. Node edit window — Thumbnails tab Figure 47. Node edit window with Thumbnails tab

To assign a node to a location:

  1. Go to Administration → Structure → Nodes.
  2. Open the desired node in edit mode.
  3. In the Location field, select the appropriate entry from the hierarchy.

Node Dashboard

The node dashboard provides a quick overview of server resource usage and component status. To open it, click in the node's local menu.

The dashboard has four tabs:

Statistics — displays:

  • IP addresses of all node interfaces with current throughput.
  • Object counts: monitoring objects by type, mosaics, etc.
  • CPU load, memory usage, and disk space for all drives.

Hardware — lists installed hardware (interface cards, etc.).

Services — lists installed MultiProbe services with version numbers.

Figure 48. Node dashboard — Hardware tab Figure 48. Nodes screen with Hardware tab

Service control buttons:

Icon Action
Download service log (uploaded as an archive to the current AWS — useful for support requests)
Restart the service (brief monitoring interruption may occur)
Stop the service
Start the service

To download OS-level logs for the node, click download OS logs in the top-left area of the browser window.

Logs — the system event log, showing time, content, and procedure name for each entry. Covers significant events such as component installation, service startup, and faults.

Figure 49. Services tab Figure 49. Services tab

Figure 50. Logs tab Figure 50. Logs tab