1. Create an agent in the dashboard
From the monitoring dashboard, add an agent. You get a one-time token: copy it now; like all realuptime credentials it is stored hashed and cannot be shown again.
2. Install and configure it on your host
Follow the install command from the docs page for your platform, and give the agent its token. The agent makes outbound connections only: nothing needs to be exposed inbound.
3. Confirm it reports in
The dashboard shows the agent as live once its first poll lands. If it never appears, re-check the token: agent endpoints deliberately answer an opaque 404 for any credential problem (error RU-3005), so the dashboard is where the truth shows.
4. Assign private checks and server health
Point checks at internal hosts through the agent, and enable server health metrics to track CPU, memory, and disk with alert thresholds.
Go deeper
The full reference lives in the docs: Monitor agent documentation. Error codes named above are each explained in the error-code reference.