Setup

An installed agent is not yet a monitored system. monsys also needs to know how important the system is, who owns it, what must run on it, whether its backup works and whether an alert reaches anyone. The Setup page shows eight steps per server. Only when all eight are done does the system become Monitored. Until then Coverage shows it as “not set up” and never green.

The eight steps

#	Step	Done when
1	Agent and data	The agent checks in, is current, and heartbeat, cpu, disk, services, inventory, updates and certificates deliver fresh data. If something is missing, it says what.
2	Environment, criticality, owner	Production, staging, test or development; critical, normal or low; and a responsible user.
3	What must run here	You confirm the list of services and containers. Everything running now is watched immediately. Exceptions are set to “Not needed” on Coverage.
4	Reachability	At least one active outside check, or the conscious choice “no public service”. Sites monsys found are enabled with one click.
5	Backup	A backup is watched, or the conscious choice “no backup, accepted”.
6	Patch policy	Automatic patching is on, or “we patch ourselves”.
7	Test notification	monsys sends a test notification along the same path as a real alert, and someone confirms it arrived.
8	Learning period	24 hours after first contact, monsys knows normal behaviour.

A conscious choice (“no backup”, “no public service”) counts as done and stays visible as a decision, with who made it and when. Every choice can be undone.

What the profile changes

On a test or development system, or a system with criticality “low”, warnings go to the problem list and the digest, not to the phone. Critical problems always go through. Without a profile nothing changes.

Adding a system

Name the server and copy the install command. The page shows live when the agent checks in and which parts already deliver data.

Refused connections

When the hub refuses an agent or an enrolment token, the reason appears in the install script output and on the Setup page under Refused connections (last 24 hours, with name, IP address and number of attempts):

• the enrolment token does not exist, was revoked, expired or reached its use limit;
• the enrolment token is not valid for the server’s IP address;
• free limit of 5 systems reached without a payment method;
• agent or account suspended;
• the certificate belongs to another agent (remove /var/lib/monsys/mtls and restart the agent).

Account

At the top are three items for your own account: e-mail address confirmed, two-step verification on, and at least one alert channel (a linked phone or a webhook).