Site Collectors
Run checks inside a private network through an outbound connection.
A site collector runs Sysavia checks from inside a private network and returns their results over an outbound HTTP(S) connection. It does not need inbound firewall ports and does not give the panel a general-purpose network tunnel.
Enroll a collector in the panel and download its configuration once. Each collector has its own randomly generated credential; only its hash is stored in the registry. Revoking that collector prevents subsequent heartbeats and job delivery. Keep the downloaded profile private. Use HTTPS when the collector crosses an untrusted network.
Install the Sysavia package on the collector host, run npm ci, and launch node agent.mjs /path/to/downloaded-profile.json (or set AGENT_CONFIG). The collector profile does not require the legacy shared AGENT_TOKEN. A combined endpoint/collector installation can additionally provide its endpoint AGENT_TOKEN and locally configured services.
Choose the collector when configuring a supported HTTP, TCP, ICMP, UDP, SNMP or API read check. The panel sends only checks assigned to that collector. SNMP and legacy API credential environment references are resolved on the collector host. Network checks execute concurrently (four at a time); their latest results are buffered in memory while the panel is unavailable. The panel rejects expired results and results from a previous check configuration. The buffer does not survive a collector restart.
Hardware and API connection discovery/read requests can also execute through a collector. Each request is dispatched once, has a 45-second panel deadline, and is never silently retried as a management action. A timed-out action may have completed on the remote equipment; check its actual state before retrying. Management actions additionally require allowCollectorActions: true in the collector profile, as well as controls enabled on the panel connection. This limits what a compromised panel can ask a collector to do; the adapter permits defined operations rather than arbitrary shell commands. IPMI needs ipmitool on the selected execution host.
Private VNC relay
A collector profile with allowCollectorRelay: true opens an outbound WebSocket control connection. A VNC media source assigned to that collector can display a private-network VNC server through it without inbound firewall openings. Each viewer uses a short-lived, single-use ticket bound to the collector identity. Closing a viewer releases the upstream TCP connection. Revocation closes existing sessions. Connections are limited to 16 per collector and 128 per panel process, with bounded buffers.
An optional collectorRelayHosts array in the collector profile restricts allowed destination hostnames/IPs. Without it, the collector accepts destinations from configured VNC media sources in the panel. The reverse proxy must pass WebSocket upgrades for /api/collector/socket and /api/collector/relay, in addition to the browser media endpoint.
This relay transports VNC TCP, with verified TLS for Dell VNC sessions where the controller enables encryption. Vendor HTML5 KVM protocols, browser equipment dashboards and video capture streams are not transported by this relay. The relay does not bypass vendor console licensing or turn an IPMI power-control interface into a VNC server.
Network Tool Execution
Enrollment offers Allow managed VPN connections and Allow SNMP trap listeners. These opt-ins become allowVpn and allowTraps in the downloaded profile. Configure the actual connection/listener from the panel and select this collector under Run On. VPNs establish private routes on that execution host; they do not turn the collector WebSocket into a general tunnel. Checks and consoles using those routes must select the same collector.
Network runtime reconciliation runs outside the heartbeat path. A 35-second lease stops managed listeners and VPNs after panel contact is lost; revoked authentication stops them promptly. Current runtime status and a bounded event buffer return over authenticated heartbeats. A reconnect applies the panel's desired enabled state again. Event/status buffers are not durable offline history. See Network Tools.