# Servers: CPU, memory and disk

> Read CPU, memory and disk for each of your servers, know when to look, and hide a laptop or test machine so it doesn't count.

Section: Each part of Relia · Page: https://tryrelia.com/docs/servers · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/v08p3Z7U4Cc

The **Servers** page shows the health of each machine your services run on: CPU, memory and disk. The Node.js and Python SDKs report it every 30 seconds from each server, with no extra setup.

Open **Servers** in the sidebar, under **Your product**.

## What the page shows

- **Three cards on top**: CPU, memory and disk. Each shows the highest number across your servers, so one busy machine is enough to raise it.
- **A chart for each**, with the average and the peak.
- **Pick one server** (for example `api-2`) to see only its own lines.
- Choose the time range and how often the page refreshes at the top.

Serverless functions (Vercel, Firebase, AWS Lambda and similar) have no server of their own, so they send no host numbers.

## When to look

You don't need to watch this page. Relia does:

- On Home, the **Servers** line turns amber (watch) when memory or disk passes 80 %, and red past 90 %.
- Relia raises an incident when CPU, memory or disk is high, and links it to the slow requests on that server when they happen together.
- Relia also looks ahead: memory that keeps growing hour after hour, or a disk that will be full within 7 days, becomes a warning before it breaks anything.

Open Servers when an incident points at a machine, or when the Home line changes colour. A typical pattern: one server's memory climbs from Monday morning, hour after hour, until a restart.

> **Tip:** watch [Server running out of memory or disk? See it before it crashes](https://youtu.be/cn-cF38dUgU) (2 min).

## Hide a laptop or test server

A developer laptop or test machine that sends data can make your numbers look wrong. Relia already leaves out machines whose environment is `dev`, `development`, `local`, `localhost`, `test` or `testing`.

> **Important:** the Node.js SDK reports `development` when `NODE_ENV` is not set, so a real server without `NODE_ENV=production` is left out too. Set it, or switch on **Include development machines** below.

To hide any other machine, hide it by name:

1. On the **Servers** page, click **Hosts**.
2. **Which hosts count** lists every machine Relia has seen, with its environment and services.
3. Click the eye next to the machine: **Hide this host**.

To count development machines after all, switch on **Include development machines** in the same panel.

Only owners and admins can change this. A hidden host keeps sending data, but it is left out of the Servers page, the Map, the Servers line on Home and Relia's host checks. Nothing is deleted; click the eye again to show it.

> **Tip:** set the environment on your test machines so they are left out on their own: `NODE_ENV` for Node.js, `RELIA_ENV` (or `ENVIRONMENT` / `APP_ENV`) for Python. See [Environment variables](https://tryrelia.com/docs/environment-variables.md).

## If something's wrong

- **No data yet**: host numbers come from the Node.js or Python SDK running on the server. Upgrade to the latest `relia-sdk` and restart the app.
- **A real server is missing**: it may report a development environment (on Node.js, `NODE_ENV` not set). Set `NODE_ENV=production` and restart, or switch on **Include development machines** under **Hosts**.
- **"Reporter stopped"**: the server stopped sending. Restart the app on that machine.

## Next

- [Server running out of memory or disk](https://tryrelia.com/docs/server-memory-disk.md)
- [APIs](https://tryrelia.com/docs/apis.md)
- [Home](https://tryrelia.com/docs/home.md)

---
All Relia docs for AI assistants: https://tryrelia.com/llms.txt (index) · https://tryrelia.com/llms-full.txt (everything in one file)
