K
What is Server monitoring? Getting started Install the agent Metrics collected Uninstall MCP Integration

What is Server monitoring?

Updated April 18, 2026

Server monitoring is a Hyperping product that installs a lightweight agent on your Linux and macOS hosts and streams system metrics back to your dashboard. Each install creates one server entry, and you can collect CPU, memory, disk, and network data without managing your own collector.

Platforms
Linux (systemd) · macOS (launchd)
Architectures
amd64 · arm64
Cadence
15 second heartbeat
Transport
OpenTelemetry over HTTPS
Enrollment
Single-use install token
Footprint
~50 MB RSS target
📘Sits alongside your HTTP monitors

HTTP monitors tell you a page stopped loading from the outside. The agent tells you the machine ran out of memory two minutes earlier. Use both together for full coverage.

What it collects

The agent ships metrics every 15 seconds over an embedded OpenTelemetry pipeline.

Metric categories 5 groups

CPUpercent / load
Utilization percentage, 1/5/15-minute load averages, logical core count.
Memorybytes
Used, available, total, and swap.
Diskbytes
Used, available, and total per mount point.
Networkbytes / count
Bytes and packets in and out per interface, plus errors.
Host metadatastring
Hostname, OS, kernel, architecture, and agent version.

For the full list of fields and units, see Metrics collected.

How enrollment works

Step 01
Generate a token
Add a server in the dashboard. Hyperping returns a single-use install token scoped to that server entry.
Step 02
Exchange for an agent token
The installer POSTs to /v1/ingest/enroll with the install token and receives a long-lived agent token and UUID.
Step 03
Rotate by re-running
Running the installer with a new install token re-enrolls the agent and revokes the old credential. Same server UUID, clean rotation.

Next steps