Part of RMM. Network monitoring is in RMM → Network (/rmm/network). It used to be a separate app called Pulse, and old /pulse links open RMM. In the Network menu, network locations are labelled Locations. Network settings and credentials are behind the RMM Settings gear.
Overview
RMM Network (formerly Pulse) is the network monitoring and remote access part of RMM. Where RMM's device pages watch the endpoints (the laptops and servers with an agent on them), the Network section watches the network — the routers, switches, firewalls, access points, printers, and any IP-reachable device at a client site — plus the internet circuit itself. It does this with a lightweight collector you deploy at each site, which discovers devices, runs monitors (ping/SNMP/HTTP/TCP), measures circuit speed, draws topology, and brokers secure remote-access tunnels back to those devices.
Use RMM Network to answer "is the site up, is the internet healthy, what's on this network, and can I get to that switch right now."
Key Concepts
- Location (labelled Locations in the menu; older guides call it a site) — a physical location (an office, a branch). A site has one or more CIDR ranges that define which networks it covers, an optional time zone, and an optional link to a CRM/CMDB client so it can appear in that client's portal. Almost everything in RMM Network is organized under a location.
- Collector — a small piece of software you run on a box at the site (or alongside the RMM agent on an existing device). It is the eyes and hands at that location: it scans the network, executes monitors, runs speedtests, and terminates remote-access tunnels. A collector is enrolled to exactly one location using a one-time token.
- Device — anything the collector discovers on the site network: managed (you've claimed/credentialed it) or unmanaged (just seen). Identified by IP, hostname, vendor, MAC, and device class.
- Monitor — a recurring check against a device or endpoint (ping, TCP port, HTTP, SNMP OID). Each monitor reports Healthy, Failing, or Paused.
- Alert rule — turns monitor/state changes into notifications, scoped by severity and target, with optional ticket/on-call escalation.
- Speedtest — a scheduled or on-demand download/upload/latency measurement of the site's internet circuit, trended over 30 days.
- Tunnel — an on-demand, audited remote-access session to a device on the site network, brokered through the collector. Tunnels can require approval and are overseen by THEO.
- Credential — an SNMP community / SSH / API secret, scoped to a site or device, used by monitors and tunnels. Stored encrypted, never shown back in full.
Navigation
Open RMM. The Network section of the RMM sidebar has Overview, Devices, Monitors, Topology, Network Alerts, Network Alert Rules, Speedtests, Collectors, Tunnels, Run CLI, and Locations. Network settings and network credentials are behind the RMM Settings gear.
Typical First-Run Flow
- Create a Location with its CIDR range(s).
- Enroll a Collector for that location (mint a token, install it).
- Wait for discovery — Devices populates as the collector scans.
- Add Monitors on the devices/endpoints you care about.
- Set Network Alert Rules so failures notify you (and optionally open a ticket / page on-call).
- Optionally schedule Speedtests and open Tunnels when you need hands-on access.
Frequently Asked Questions
How is the Network section different from the rest of RMM? RMM's device pages manage devices that run our agent (endpoints). The Network section monitors the network and any IP device — including gear that can never run an agent (switches, firewalls, printers, IoT) — through a site collector. The two complement each other. Network monitoring used to be a separate app called Pulse, and SNMP, discovery, and bandwidth monitoring now live in this section.
Do I need a collector at every location? Yes. Monitoring, discovery, speedtests, and tunnels are all executed by the site's collector, so each monitored location needs at least one online collector.
Can a client see their own location? Yes, if you link the location to that client and mark it visible in the client portal.
Troubleshooting
No devices appear after enrolling a collector. Confirm the collector shows Active (not Pending/Offline) on the Collectors page, and that the location's CIDR ranges actually match the network the collector sits on. Discovery only sweeps the configured ranges.
A monitor flaps between Healthy and Failing. Check the monitor's interval and timeout, and whether the underlying circuit is congested (look at Speedtests). Widen the failure threshold on the monitor or add an alert-rule dampener.
A tunnel is stuck "Awaiting approval." Tunnels that require approval wait for an authorized user to approve them on the Tunnels page. Approve it there, or relax the approval requirement in Network settings (RMM Settings gear) if your policy allows.