Hosts & status
Understanding host statuses, the hosts list, and per-host detail pages.
The Hosts page is the main dashboard. It lists all registered hosts with their current status, last seen time, key metrics, and agent version.
Host statuses
| Status | Meaning |
|---|---|
pending | Host created in the dashboard, registration token not yet used by an agent |
online | A heartbeat was received within the last 15 seconds |
offline | No heartbeat received for more than 15 seconds |
paused | Monitoring suspended manually — heartbeats are ignored, no offline alerts fire |
expired | Registration token expired (24-hour window) before the agent registered |
Status is updated in real time via Server-Sent Events — no page refresh needed. An online host transitions to offline within 15–25 seconds after its agent stops sending heartbeats (15-second timeout, checked every 10 seconds).
Adding a host
- Click Add host in the top right of the Hosts page.
- Enter a display name.
- Optionally set the expected IP address — the Hub will flag mismatches if the agent connects from a different IP.
- Copy the registration token and use it when installing the agent.
The token is valid for 24 hours. After expiry, the host status changes to expired and a new token must be generated from the host’s detail page.
Host detail page
Click any host to open its detail page. It shows:
- Header — hostname, IP addresses, OS, architecture, CPU model, total RAM, uptime, agent version
- Live stats — real-time CPU, memory, and disk gauges updated every 30 seconds
- Charts — historical metric graphs for the selected time range
- Packages — installed packages and change history
- Containers — per-container metrics (if enabled)
- Alerts — active incidents and per-host alert rules
- Incidents — history of past alert incidents
Host actions
From a host’s detail page (⋯ menu or dedicated buttons):
| Action | Description |
|---|---|
| Rename | Change the display name |
| Pause | Suspend monitoring — no offline alerts will fire |
| Resume | Re-enable monitoring after a pause |
| Update IP | Update the expected IP address when a host’s IP has changed |
| Dismiss IP mismatch | Ignore the IP mismatch warning without updating the configured IP |
| Dismiss reactivation | Clear the reactivation badge (see below) |
| Regenerate token | Generate a new registration token (e.g. to re-register the agent) |
| Delete | Remove the host and all its data (metrics, packages, alerts) |
IP mismatch
When you create a host and set an expected IP address, the Hub checks that the agent connects from that IP. If the agent’s IP differs — for example after a network change or server migration — the host detail page shows an IP mismatch warning.
From the ⋯ menu you can either:
- Update IP — save the new IP as the expected address and clear the warning.
- Dismiss IP mismatch — keep the old configured IP but suppress the warning.
Reactivation
If an agent re-registers on a host that already has credentials on the Hub (same UUID on disk), the Hub reuses the existing host record instead of creating a duplicate. This is called reactivation and happens when you reinstall the agent on a machine without deleting the host first.
A Reactivated badge appears on the host detail page to signal that the agent reconnected to an existing record. Click Dismiss reactivation (⋯ menu) to clear the badge once you’ve confirmed it is the expected host.
Clock desync warning
If an agent’s system clock differs from the Hub’s clock by more than 5 minutes, the Hub rejects its gRPC requests and a Clock desync banner appears on the host detail page.
Fix: ensure NTP is running on the monitored host (timedatectl status on Linux). The banner clears automatically once a valid heartbeat is received.
Pausing a host
Pausing a host is useful during planned maintenance. While paused:
- Heartbeats are ignored
- The host does not appear as offline
- No alerts fire
- Metrics are not recorded
Resume the host when maintenance is complete.