Monitoring Overview¶
Swarm Hosts reports basic host and Swarm Server CPU and memory readings through the agent. An optional local monitoring stack adds detailed resource charts, collector health, alerts, and supported game-health signals.
To manage the stack, open the Swarm Host's Operations → Maintenance view. Users with host management access can choose Enable monitoring stack, Restart monitoring stack, Repair monitoring stack, or Run monitoring diagnostics. Use Set monitoring retention to change how long detailed history is kept; the default is 30 days.
Open Monitor on a host or Activity & Logs → Monitor on a Swarm Server to view its charts. The stack must be enabled and reachable for detailed charts to load.
What You Can Monitor¶
- swarm host CPU, memory, filesystem, disk I/O, and network usage
- Swarm Server CPU, memory, disk I/O, and network usage
- game health metrics, such as player count or tick rate, when a compatible exporter is configured for that server; these are not available for every game
- monitoring stack health and current alert state
The Swarm Server monitor focuses on the selected game server container. The Swarm Host monitor focuses on the machine running the agent and Docker.
How Monitoring Data Is Handled¶
Detailed history from the optional monitoring stack stays on the Swarm Host. The control plane handles login, permissions, monitor-session setup, and low-rate health and alert summaries; it does not proxy the stack's chart payloads. Separately, normal agent reports send CPU and memory samples to the control plane, which keeps a bounded resource history for the application and customer API.
The browser uses a short-lived monitor session to reach the host-local monitor gateway. When direct access is not available, the browser and swarm host can use WebRTC signaling through the control plane; successful metric payloads still move between the browser and the swarm host.
Requirements¶
Monitoring needs:
- a swarm host agent version with monitoring support
- Docker on the swarm host
- enough local disk for the retention window
- a working browser-to-swarm-host monitor path, either direct or WebRTC-backed
Hosts without the monitoring stack still show normal server status, logs, and agent-reported resource data when available. Disabling the stack does not stop game containers.