Skip to content →
Log in

Topology

Inspect current relationships among devices, gateways, and services.

Network → Topology draws the devices, gateways and services PulseHA knows about and the links between them. Use it to see which path a device takes to a service and whether traffic was allowed or denied, not to create or edit resources.

Network Topology page in Graph view with devices, gateways and services linked by coloured edges and the Access Insights panel on the right

The Graph view places devices on the left, gateways in the middle and services on the right; the panel opens on the Overview tab.

Before you start#

  • Your role needs gateway read access (gateways:view). Without it the page shows Restricted with the text Your role doesn’t include access to the network topology. Ask a tenant admin for gateway read access.
  • Devices, services, owner details, access activity, alerts and failover events are each gated separately. A section your role cannot read shows a notice rather than an empty list.
  • Traffic counts on links come from the audit log and need audit:view. Without it the toolbar shows Traffic activity: restricted by your role and links show no counts.
  • Dismissing an alert in the Alerts tab needs threats:update.

Read the graph#

  1. Open Network → Topology. The header shows Network Topology, a freshness dot that reads Live or Out of date, the time of the last update, and a refresh button.
  2. Choose Graph or List in the top right. Phones open in List by default; the choice is kept in the URL as ?mode=.
  3. Click a node to focus its connections. Hover an edge to see its access rule and counts. Press F to fit the view and Esc to clear focus. These tips also appear in the legend (the ? button).
  4. Read the details in the insights panel on the right (on small screens, tap Insights to open it as a sheet). The panel has tabs Overview, Live, Alerts, Routing and Insights. Overview shows Gateways online, Devices online, Services and Allowed / denied 24 h.
  5. Select a device to see its owner, Device Details (platform, Online or Offline, location), Posture & Risk (Compliant or Non-Compliant, risk level, score, failing checks), Recent Failovers and Recent Activity. Select a gateway and use Open gateway page to jump to its inventory entry.

Insights tab of the Access Insights panel listing the most denied users and five recommendations

The Insights tab lists the most denied users in the window and the recommendations the control plane has generated.

Topology page with the build-runner-02 device selected and the panel showing its owner, device details, posture score and recent activity

Selecting a device dims the rest of the graph and replaces the panel with its owner, device details, posture and recent decisions.

The page polls the control plane every 10 seconds and backs off to a maximum of 60 seconds after errors. A snapshot that stops being confirmed shows Out of date and the notice Data may be out of date. Retrying.

Network Topology page in List view with sortable tables for gateways, services and devices

The List view shows the same gateways, services and devices as sortable tables; clicking a row opens the same detail panel.

Filter the graph#

The filter bar appears once the tenant has more than five devices.

ControlEffect
Search devices…Matches device name or owner
All, Online, OfflineDevice status
All OS, Windows, macOS, LinuxDevice platform
Grouped / UngroupedCollapse devices into groups or show each one
IssuesOnly devices that are offline or non-compliant
All pathsAlso draw inferred edges to each device’s reported gateway
ClearReset every filter except the grouping mode

The count on the right reads X of Y devices, or N groups · M devices when grouped. Filters are written to the URL so a shared link reproduces the view.

Legend#

Link styleMeaning
Solid greenObserved: allowed in the last 24 h
Red dashedObserved: denied only
GreyConfigured route, no traffic seen
Grey dottedInferred from the device’s reported gateway (needs All paths)

Edge thickness scales with request volume over 24 hours. Node colours mean online or compliant (green), degraded or warning (amber), offline (red) and unknown with no fresh heartbeat (grey). A gateway counts as online when it reported within the last 90 seconds.

Close view of the topology canvas showing green edges with traffic, a red dashed edge to the ERP database and grey configured routes

Green edges carry allowed traffic, the red dashed edge to the ERP database saw denials only, and grey edges are configured routes with no traffic.

Section notices#

Notices appear in the strip above the canvas and name the affected section: Gateways, Devices, Owner details, Services, Device connections, Service routes, Access activity, Alerts or Failover events.

NoticeMeaning
<Section>: restricted by your roleYour permissions exclude it
<Section>: couldn't loadThe control plane failed for that section; it retries on the next poll
<Section>: showing X of YThe section was truncated and the total is known
<Section> incomplete (limit reached) or (took too long to load)Truncated without a known total

Troubleshooting#

  • “Topology unavailable” with “Try again”. The poll failed before any snapshot loaded. Click Try again; the page also keeps retrying in the background.
  • “Build your network” appears. Every readable section returned nothing. Follow the three steps shown: Deploy a gateway, Connect devices, Define services.
  • No counts on edges. Traffic observations need audit:view, or the observations section is incomplete (Traffic activity: incomplete) or failed (Traffic activity: couldn’t load).
  • A device shows Online here but is Offline on the Devices page. The two pages use different freshness rules. Treat the Devices page as the inventory source and use the device’s Connection chip there.
  • “You don’t have permission to dismiss alerts.” Dismissal needs threats:update. “Couldn’t dismiss the alert. Try again.” is a transient failure.
  • A banner reads “Synthetic data: N demo devices”. Someone opened the page with ?demo=N. Those devices are generated in the browser for performance testing. Click Exit demo.

Topology shows relationships PulseHA knows about. It does not prove that an application process is listening or that a given packet passed every control. Use Policy simulation to test a decision and Audit for the event record.