Purpose
The landing page after sign-in: a two-second answer to “is my Relayer healthy and
what network is it standing on?” — provider map, capacity, and live host/system
telemetry.
When you use it
- First thing after login, to confirm the box and the network look normal.
- To see how many storage providers are reachable and where they are.
- To sanity-check hardware load before blaming the Relayer for slow transfers.
Controls
Summary cards (top row)
- Virtual Private Datacenter — your curated provider selection. Shows
“No VPD configured” with a setup button until you create one. - Active Hosts — providers currently reachable, with passive and offline counts
beneath. - Network Capacity — total network capacity and how much is in use.
- Countries — unique provider locations.
- Redundancy — network redundancy indicator.
Provider map
- World map of every provider; search by IP or public key; Ctrl+scroll to zoom.
- Provider Health legend — four colored dots for Critical, Degraded, Healthy, and
Offline — and a Show VPD only filter that appears once a VPD exists.
Info strips
- Hardware — processor, RAM, architecture of the host machine.
- Performance — host CPU/memory and container CPU/memory percentages.
- Network — download/upload throughput and ping.
- HostIO — matched data hosts, parity hosts, cache size, pending bytes.
Charts
- System: Host CPU & Memory · Container CPU & Memory · Network Bandwidth ·
Internet Speed. - Services: Services CPU · Services Memory (one line per running service) ·
Database (connections, active queries, size). - Storage: Relayer Cache percentage · Matched Providers over time.
VPD setup and conditional panels
- The Virtual Private Datacenter card’s button switches the page into setup mode, where
you build a provider selection three ways — Weighted Builder, Country Selector, or CEL
Editor — optionally pin specific providers, and push it live with Apply to Relayer. - With a VPD configured, the monitor view also shows a Top Providers table and an IP
Zones summary. A Disk Usage table appears when the box reports local disks.
Common tasks
- Morning health glance: Active Hosts in the hundreds, Network card showing
sane throughput, HostIO showing matched hosts ≈ the number you normally see. - Find a specific provider: type its IP or public key into the map search.
Gotchas
- Container CPU/Memory is the Relayer’s own usage; Host CPU/Memory is the whole
machine. High host numbers with low container numbers means something else on
the machine is busy. - Matched data/parity host counts fluctuate a little as the network changes; a
sudden drop toward zero is what matters (see Troubleshooting).
Screenshots
