Monitoring software, reviewed for the person who ends up on call.
Independent reviews of self-hosted and open-source monitoring — and the commercial tools worth paying for — built from vendor documentation and what admins report about disk growth, poller load and pages per week.
Independent — 7 of 11 products we cover are open source or open core We host no files; links go to vendors’ own sites No affiliate links — product links go straight to official sites
The license is free. The hours are not. This table compares the open-source monitors we see most in small and mid-size shops, plus one commercial yardstick.
Interfaces, errors, CPU on the core switch, the firewall that fills its session table every Friday. Here is how the main tools handle the gear that is not a server.
Disk full, service stopped, certificate expiring in nine days. This table compares tools on how well they catch the ordinary failures that make up most on-call nights.
Icinga vs Nagios Core: stay, fork or rebuild?Icinga 2 vs Nagios Core compared on configuration, APIs, distributed monitoring, web UI and plugin compatibility, with guidance on when staying on Nagios is fine.
How big should your monitoring server be?Sizing a Zabbix (or similar) monitoring server from first principles: items, NVPS, history vs trends, housekeeping, partitioning and proxies, with a worked example.
Scannethub is not a vendor, a reseller or a mirror. We do not host installation packages or archives, and every product link points at the maker’s own website. When you need the software itself, ourwhere-to-get page explains how to use signed package repositories and verify checksums.
Our reviews include what goes wrong. Every product page carries a section on where it falls short and who should skip it, because a monitoring system you outgrow in a year costs more than the license ever did. Questions or corrections go to editor@scannethub.biz.