Collector Services
Every service on a newly enrolled collector starts switched off. A collector that’s just come online won’t check reachability, poll a single device, or receive a log line until you turn on the services you want it to run. This is deliberate, not a bug — it’s how a collector never starts pulling credentials or listening on a port you didn’t ask for.
The six services
Section titled “The six services”| Service | What it does |
|---|---|
| Monitor | ICMP reachability checks — is each device up or down? |
| Poller | SNMP and SSH metric collection from your devices. |
| Syslog | Receives syslog messages sent to the collector, over UDP port 514. |
| SNMP Traps | Listens for SNMP traps sent to the collector, over UDP port 162. |
| Service Monitoring | Runs synthetic HTTP, DNS, SMTP, and SMB checks you define. |
| Discovery | Active network discovery scans — both scans you run on demand and, on networks you’ve set to scan automatically, scheduled ones. |
Turn on only what you need. A collector watching devices that never send syslog doesn’t need the Syslog service running; a collector with no synthetic checks defined doesn’t need Service Monitoring.
Turning a service on
Section titled “Turning a service on”- Go to Configure → Collectors and open the collector.
- Select the Settings tab.
- Under Plugins, toggle on each service you want it to run.
A toggle saves immediately and takes effect on the collector’s next check-in — usually within a few seconds. You can turn any service on or off again at any time; nothing about the change is permanent.
Related pages
Section titled “Related pages”- Installing a Collector — the install itself, and the ports a collector needs open.
- Reading a Collector’s Health Tab — what each service’s status chip means once it’s running.
- Networks & Sites — assigning the networks a collector actually watches.
docs built 2026-09-26 · 195c6d00