Network Map is the visual answer to “what depends on what” across your fleet. Three view modes share the same data set:

• Network Map — force-directed topology graph.
• Domain Map — domain-centric view of what each hostname resolves to.
• Heatmap — fleet-wide grid coloured by any metric you pick.

What you see

Network Map

A pannable, zoomable canvas with coloured nodes:

• 🟦 Server
• 🟩 Service (nginx, MySQL, Redis, …)
• 🟪 Domain
• 🟧 Container

Edges connect what actually talks to what — services to their host, domains to the web server serving them, containers to their host — plus every dependency you have declared under Dependencies. Hover any node for a tooltip with name, type, status, and quick facts.

Controls:

• Legend — click a type to hide / show it.
• Server filter — hide entire hosts from the canvas.
• Zoom in / out / fit.

Domain Map

A domain-first layout: every domain, the server it lives on, and the DNS / CDN provider fronting it. Useful for spotting “which of my domains are still on the old load balancer”.

Heatmap

A grid where every tile is a server, coloured by a metric you pick:

• Color by — CPU %, memory %, disk %, load, or health score.
• Size by — equal, total RAM, service count, or container count.

Handy for spotting the outlier host at a glance without scanning the list view.

What you can do

• Toggle node types on and off.
• Filter to a subset of servers.
• Click any node to jump to that server / service / domain / container’s detail page.
• Switch views without losing your filter selection.

How it works

• The graph is stitched together from what the agent already knows — services, containers, domains, and firewall rules — plus any dependencies you declare.
• Declared dependencies (see Dependencies) are treated as first-class edges and show up on this map immediately.
• The heatmap uses the latest metric samples per host, so it refreshes as new agent data arrives.

Tip

Combine the Network Map with declared dependencies and incidents will start showing an impact graph — “these five domains depend on the database that just went down.” The more dependencies you declare, the sharper the picture.

Related

• Dependencies — declare the edges that this map draws.
• Servers and Domains — the nodes you’ll be clicking through to.