Monitoring
See CPU, RAM and disk usage of your runners in the dashboard, and what monitoring installs on the server.
Resource monitoring shows the CPU, RAM and disk usage of each active runner on its dashboard card. It helps you choose the right server type and concurrency.
Monitoring needs an active plan for the runner’s organization. Any plan qualifies. See Billing and plans.
Turn monitoring on or off
Use the Resource monitoring switch when you create or edit a runner. It is on by default for new runners when your plan is active.
Turning monitoring on or off for an active runner recreates its server, because the collector is installed when the server is created. Running jobs are interrupted. The edit form warns you before you save.
What you see
Under Resource usage, each monitored active runner shows:
- CPU usage in percent,
- RAM used of the total, in GB,
- Disk usage for each disk of the server.
Each value comes with a chart. Choose the time range with the Metrics selector: last hour, 24 hours, 7 days, 30 days or 90 days. Only ranges for which data exists are offered. Manage Runners keeps samples for 90 days.
The first values appear a few minutes after the runner starts. If the newest sample is older than three minutes, the card says how long no data has arrived.
How it works
When monitoring is on, the server runs a small collector as a systemd service under its own user, limited to 64 MB of memory and 5% of one CPU. About once a minute it sends CPU, memory and disk usage to Manage Runners over HTTPS. It collects only these system values.
Each server gets its own credential for sending samples. The credential is revoked when the runner is deleted or becomes Unknown, and when the organization no longer has an active plan.
When the plan ends
If the organization’s plan is no longer active, the dashboard shows Monitoring paused. The owner sees a link to Billing; other members are asked to contact the owner. The servers’ monitoring credentials are revoked, so their collectors stop sending data. After the plan is active again, pause and resume a runner to give its new server a new credential.
With the CLI, read the same data with manage-runners runner metrics.