Skip to content

Network Weathermaps

Network Weathermaps, shortened to Netmaps, are saved, editable diagrams of an Observium network. A Netmap combines a deliberately arranged topology with live device state, port traffic and utilisation. It is Observium's modern replacement for the PHP Weathermap (Legacy) system.

The name Netmap is always written as one word. This distinguishes it from Observium's separate Network Map feature.

Which Map Should I Use?

Observium has several related map views:

Feature Use it for
Network Map An automatically generated network topology view.
Network Traffic Map An automatically generated neighbour topology focused on current traffic. See Network Traffic Map.
Network Weathermaps Saved Netmaps whose nodes, links and layout can be edited and shown on dashboards.
PHP Weathermaps (Legacy) Existing maps made with the older PHP Weathermap editor and configuration format.

Netmaps do not use PHP Weathermap configuration files. The two systems are independent, and existing PHP Weathermaps are not automatically converted.

Access and Ownership

Netmaps are global Observium objects rather than personal or owner-scoped objects.

Viewing Netmap pages and data requires global read access (user level 5 or higher). Creating, changing and deleting a Netmap requires administrator access (user level 9 or higher) and is protected by the normal request token checks. The Network Weathermaps navigation entry is shown to administrators.

The device and port selectors use the current user's Observium permissions. A saved Netmap is loaded as a complete object rather than partially hiding individual nodes or links.

Creating a Netmap

Open Network Weathermaps → Create Netmap from the Observium menu.

A new Netmap starts with a topology generated from supported network devices and their active neighbour information. Observium creates device nodes, direct links and recognised link aggregates where the discovered data is sufficient. This is a starting point: the saved Netmap does not continually add or remove topology elements when discovery later changes.

After the initial Netmap loads:

  1. Select Edit.
  2. Drag nodes into the required layout.
  3. Add, remove or configure nodes and links as needed.
  4. Open Settings, give the Netmap a useful name, and choose its display defaults.
  5. Select Save or Save Netmap.

Saving a new Netmap adds it to the Network Weathermaps menu. Later changes are also saved explicitly; leaving edit mode does not save them. Observium warns when navigating away with unsaved changes.

Viewing and Editing

In normal view mode, use pointer pan and zoom gestures to inspect the Netmap. Device-backed nodes show current device state, while links update their traffic and utilisation at the Netmap's configured refresh interval. Link popups provide the associated Observium entity information.

Select Edit to enable node dragging and the editing controls. In edit mode:

  • select a node to open its configuration panel;
  • select a link to configure its endpoints, ports and display;
  • use Add Device to add a monitored device or a custom node;
  • use Add Link, then select two nodes, to create a connection;
  • use Settings for Netmap-wide defaults;
  • select Exit Edit to return to the normal interactive view.

Link popups are disabled while editing so that links can be selected reliably.

Nodes

An Observium-backed node refers to a monitored device. A custom node has no device reference and can represent an external network, provider, label or other conceptual endpoint.

The node configuration panel provides:

  • name and comment;
  • background and border colours;
  • font size and padding;
  • an optional device icon;
  • exact X and Y position;
  • node deletion.

For an Observium-backed node, Expand from this node uses current neighbour data to find additional connected devices and links. It can add missing remote nodes before adding the suggested links. Expansion does not remove existing elements and still requires an explicit save.

Device state is resolved when the Netmap loads. Down and disabled devices are indicated on the node; a node referring to a device that has been deleted is shown as stale rather than silently removed.

To add a link, select Add Link and then select its two endpoint nodes. For two Observium-backed devices, the link chooser offers:

  • Direct Port Link — choose one port at each endpoint;
  • Bundle / Aggregate — configure aggregate endpoints and their member connections;
  • Discovery Suggested — inspect direct or aggregate candidates inferred from Observium neighbour and port-stack data.

Connections involving a custom node can leave that side open or associate it with a selected device and port. A connection between two custom nodes can be used as a purely visual link.

The link configuration panel can switch between direct and bundle modes, select endpoint ports, manage bundle members, and choose how live speed is displayed. The available formats include automatically scaled rates, rates with percentage, fixed Kbps/Mbps/Gbps units and percentage only.

Link endpoints can be repositioned for clearer routing. Use Straighten Link for the selected link or Reset All Link Anchors in Netmap settings to restore automatic connection points.

Netmap Settings

The Settings panel controls:

  • the saved Netmap name;
  • grid size;
  • live-data refresh interval;
  • utilisation-label visibility, font size and padding;
  • default node appearance;
  • default link width, colour and connection distance;
  • resetting all link anchors;
  • saving or deleting the Netmap.

Defaults apply to newly created elements. Existing nodes and links retain their individual settings until edited.

Dashboard Widget

Add the Netmap widget to display a saved Netmap on a dashboard. The dashboard copy is view-only; editing remains on the Network Weathermaps page.

The widget has several deliberate constraints:

  • only one Netmap can be active on a dashboard;
  • dashboard time and device-scope context do not alter it;
  • it uses the Netmap's own live-data refresh cycle;
  • the viewer must have access to the Netmap and its data.

Troubleshooting

A new Netmap is empty or incomplete: The initial topology depends on monitored network devices and active neighbour data. Check that neighbour discovery is enabled and has run for the expected devices.

A link has no traffic or utilisation: Confirm that both endpoints reference the intended Observium ports and that those ports have current rate and speed data. A deleted port is reported as stale; an unknown speed prevents a reliable utilisation percentage.

Topology changes are missing from an existing Netmap: Saved Netmaps are curated diagrams, not continuously regenerated topology. Use node expansion or edit the nodes and links manually, then save.

Changes disappeared after leaving the page: Editing and leaving edit mode do not save automatically. Select Save before navigating away.

The dashboard widget does not render: Confirm that the selected Netmap still exists, the viewer has global Netmap access, and the dashboard does not already contain another active Netmap widget.