Check it's reporting

With a key in place and the service restarted, the box should move from waiting to receiving within one collection interval.

On the server

$sudo systemctl status monilogix-agent

A healthy agent reports active (running). If it exited instead, the logs will say why:

$sudo journalctl -u monilogix-agent -n 50 --no-pager

In Boxes

Back in Boxes, the box's status badge switches from Waiting for first metrics to Receiving, and CPU, RAM and storage begin filling in. That is the whole setup — every server you repeat it on joins the same list.

If nothing arrives

• Wrong or rotated key. Compare the value in /etc/monilogix/config.yaml against the box's current key. Rotating invalidates the previous one immediately.
• Config never reloaded. The file is read at start-up only — restart the service after editing it.
• Outbound HTTPS blocked. The agent needs to reach the server; it never accepts inbound connections.
• Clock badly out of sync. Large drift can cause submissions to be rejected. Check that NTP is running.