The Stats panel shows one node in detail.
What you see
- Total sessions: every session the node has served.
- Active: sessions active or being set up now (a user with several routes counts more than once).
- Links: working links to or from the node.
- Traffic: upload and download across its sessions.
- Live metrics: memory, load, connections, bandwidth, free disk, latency and jitter, while the agent is connected.
- System: CPU cores, RAM, the kernel's connection-tracking limit and link speed.
- Active sessions: each with its route, upload and download, the upload/download ratio, age and any kill reason, and a Kill button that ends the session at once.
The node's own page charts its users, traffic, RAM, load and connections over up to 90 days, and how full its connection table is and the connections it dropped (agent 0.4.20 and newer count these), with its events (agent connections and updates, overloads, tunnels going up or down) marked on every chart (Metrics tab). An overload in the event list says what was passed, in figures, as the notice you got did. The latency and jitter tiles open that tab.