SecurityFirewall, Fail2Ban, SSH hardening, kernel, AppArmor or SELinux, the WAF, automatic updates, password rules, integrity, audit, certificates and accounts — the server's own Security reading, on every server.
HealthLoad against the CPUs, memory, swap, failed services, processes the kernel killed for memory in the last day, whether the clock is in sync, uptime, zombies.
DiskThe fullest filesystem, the root one, inodes, a filesystem the kernel turned read-only, disk errors in the kernel log, what the drives say through SMART, the size of the journal.
BackupsVigia's backup plans on each server: the last run, how old the newest good copy is against the plan's own schedule, whether the copy leaves the server, encrypted, and the room for the next one.
DatabasesMongoDB, MariaDB or MySQL, PostgreSQL: running or not, the role in the set, replication and its lag, connections against the limit, listening to the world, authentication, TLS between members.
UpdatesSecurity updates first, then everything pending, a reboot owed, how fresh the package lists are, whether updates install themselves, and whether the release still gets security fixes.
AccessRoot over SSH, SSH with passwords, who becomes root and which of them with no password, accounts with an empty password, weak keys.
KnockingFail2Ban, its jails and its bans, and the SSH logins that failed in the last 24 hours — each connection counted once — where they came from, the names they tried, and who got in.
ExposureNot what the firewall's rules say but what is actually reachable from anywhere: the database and admin ports among it, SSH taking passwords, the firewall itself, Docker past it.
CertificatesThe certificate that runs out first, any already expired, Let's Encrypt with nothing renewing it, a self-signed one handed to visitors.
DriftThe release, the kernel, OpenSSL, OpenSSH, database and web server versions, sshd's settings and the time zone — each server against the rest of its own group.