Network monitoring

Network monitoring software discovers and watches the infrastructure devices an RMM agent cannot, since switches, firewalls, access points and other network hardware do not run an agent the way a workstation or server does. It maps network topology, alerts on outages and configuration changes, and can back up device configurations so a failed switch is restored from a known-good config rather than rebuilt by hand. Bandwidth monitoring and wireless-specific monitoring for access points round out the picture of network health beyond simple uptime. It does not manage the endpoints connected to that network; that is the RMM's job, and the two are usually run together.

Pricing is per network device or per site per month, depending on the vendor. A hardware probe, where required for on-site monitoring, is typically an additional cost separate from the software subscription.

Automatic network discovery and topology mapping matter most for onboarding a new client quickly, since manually documenting every switch and its connections is slow. Device configuration backup and configuration change detection matter for recovery speed after a failure and for spotting an unauthorised change before it causes a problem. Uptime and outage alerting, SNMP support and wireless monitoring cover day-to-day operational visibility, and a multi-site dashboard matters if you manage many client locations from one console. A hardware probe option is relevant for sites without an always-on device already capable of running the monitoring software.

Documentation integration lets discovered network topology and device details flow into your documentation platform automatically, saving a technician from manually re-entering what the monitoring tool already found. Remote access to devices from within the monitoring console reduces how many separate tools a technician needs open during a network incident.

Ask about the contract term, whether pricing is per device or per site, and what a hardware probe costs if one is required. Ask what happens to historical topology maps and configuration backups if you switch vendors, since rebuilding that documentation from scratch is time-consuming.

A small MSP with simple, single-site client networks can often use a lighter product focused on discovery and basic alerting without needing a dedicated hardware probe at every location. A larger MSP managing multi-site networks with more complex switching and wireless infrastructure typically needs topology mapping, configuration backup and a multi-site dashboard to keep visibility manageable across many locations.