Putting servers and routers in one dashboard makes life easier, but monitoring is only half finished if you still have to open the page every day to discover a problem. Alerts are the obvious next step: high CPU, a nearly full disk, a missing machine.

Writing a threshold rule is easy. Making the notification useful is harder. If every brief spike produces mail and every continuing fault repeats every few seconds, important messages become easy to ignore. Conversely, no email does not necessarily mean everything is healthy.

This fifth Fleetd article describes v0.3.0. After deploying the agent on Linux and OpenWrt , we now follow reports into alert records, notifications and resolution.

What does an alert actually mean?

Fleetd checks offline reporting, CPU, memory, disk space, inodes, failed services, abnormal containers and WireGuard handshake age. Connection-address changes are separate, one-off events.

These signals have different meanings.…