Skip to content

Connection Matrix

The Connection Matrix (also called Topology View) is an interactive graph that visualizes your active SSH session tree — jump hosts, target servers, and the tunnel chains between them — in real time.

It is not just a decorative graph. The topology reflects the same route model OxideTerm uses for ProxyJump, auto-route, and reconnect orchestration.

Click Connection Matrix in the sidebar, or open a new tab and select the topology tab type.

Each active SSH node appears as a labeled card on the canvas. Lines between nodes represent SSH tunnels (ProxyJump hops):

[ Local Machine ]
[ bastion.example.com ] ←── Active (2 terminals, 1 SFTP)
[ prod-db-1 ] ←── Active (1 terminal)
[ internal-cache ] ←── Idle

The graph is built from your active sessions and saved jump relationships:

  • Direct connections appear as root-level nodes
  • Imported ProxyJump chains from ~/.ssh/config preserve their parent/child structure
  • Reusable bastion hosts can serve both as standalone sessions and as parents for downstream routes
  • Link state (active, idle, link_down, reconnecting) comes from the connection pool, not from a static diagram
ColorStateMeaning
GreenActiveConnected with consumers attached
BlueIdleConnected but no active consumers
RedLink DownConnection lost, awaiting reconnect
OrangeReconnectingReconnect attempt in progress
GrayDisconnectedNot in connection pool
InteractionAction
ScrollZoom in/out
Drag canvasPan the view
Click nodeSelect and view details
Right-click nodeOpen context menu
Fullscreen buttonToggle fullscreen view

Right-clicking a node opens actions:

  • Open Terminal — open a new terminal tab for this node
  • Open SFTP — open SFTP browser for this node
  • Port Forwarding — add forwarding rules for this node
  • Disconnect — disconnect this node
  • View Details — show connection statistics panel

When a jump host loses connectivity, the topology immediately reflects the cascade:

  1. The bastion node turns red (link_down)
  2. All downstream nodes (servers behind the bastion) simultaneously turn red
  3. The reconnect orchestrator starts — nodes that can recover show a pulsing reconnect indicator
  4. On recovery, nodes return to green in sequence as each reconnect phase completes

This makes it immediately clear which servers are affected by a bastion outage.

When multiple paths to a target exist, OxideTerm can pick an appropriate route automatically from the saved connection graph.

  • ProxyJump routes are modeled as edges in the topology
  • Auto-Route chooses from the currently reachable path set
  • Parent jump nodes are reused instead of re-dialing duplicate SSH tunnels
  • The canvas helps you see why a target is reachable, degraded, or blocked behind a failed hop

This is especially useful when your SSH config and saved connections describe several bastion layers.

Topology status also mirrors OxideTerm’s reconnect behavior:

  • A parent node going down marks downstream children as link_down
  • During the 30-second Grace Period, OxideTerm probes the old transport before tearing it down
  • If the old path recovers, the graph returns without rebuilding the entire chain
  • If recovery fails, reconnect proceeds parent-first so child routes can reattach in order

The bottom status bar shows:

  • SYSTEM_STATUS: ONLINE
  • Number of active connections and maximum chain depth (e.g., “3 active connections, max depth: 2”)
  • Multi-datacenter overview — see all your bastion → server chains at a glance
  • Incident response — immediately identify which servers are affected by a jump-host failure
  • Onboarding — visually explain your infrastructure topology to new team members
  • Debugging — verify that connection chains are set up correctly before starting work