More than one collector
One collector per POP or network segment, which device each one monitors, and why the collector's site matters.
Updated 10 November 2026
One collector is enough for most networks: it handles a thousand devices or more. Add another when:
- part of your network can't be reached from where the first collector runs (a second POP with its own management network, or a separate customer network);
- you want monitoring to carry on from a second place when the first one's site is down.
Add a collector
Add each one in Admin → Collectors with its own name and token, and install it on a machine in that part of the network (how).
Which collector monitors which device
Every device has a Collector setting. A device is monitored by exactly one collector, the one you choose. With a single collector, new devices get it automatically. A device with no collector isn't monitored: the Devices page shows it as not monitored.
When you import devices from a spreadsheet, the collector column takes a collector's name
(import).
The collector's site
Give each collector the site where it runs. WISPMap measures reachability from there: when a link fails, the sites on the far side, as seen from the collector, are the ones cut off. A wrong site means wrong root causes.
Its own intervals
Each collector has its own ping, poll and send intervals on its page (settings).
When a collector goes offline
Its devices show as unknown, not down, and you get one Collector offline alert instead of an outage for everything it monitors.