Skip to content

Receiving Logs & Traps

A collector is how your devices’ logs and traps get into GridNMS. Point a device at a collector’s address on the right port, and the collector receives the messages, ships them up GridNMS, and they become searchable and alertable.

A collector can receive the two most common formats, and additional, more capable listeners when you need them. Every one of them is switched off until you turn it on for that collector.

The Collectors page with a collector open. Open a collector under Configure → Collectors to manage how it receives logs.

These two cover almost every device:

What Port Used by
Syslog over UDP 514 (UDP) Switches, routers, firewalls, servers, Linux/Unix hosts — the standard for almost everything.
SNMP traps 162 (UDP) Network gear sending event notifications (link down, fan failure, and so on).

Turn the one you need on first. Like every other collector service, both start switched off, so a collector that has just come online is not listening on either port and a device pointed at it is sending into nothing — with no error to tell you so. Open the collector under Configure → Collectors, select its Settings tab, and switch on Syslog or SNMP Traps under Plugins. The collector picks the change up within a few seconds. See Collector Services for the full list and what each one does.

With the service on, configure each device to send its syslog to the collector’s IP on port 514, and its SNMP traps to the collector’s IP on port 162. Reception is never filtered by which devices you have added — once the listener is on, the collector accepts what arrives.

Plain UDP syslog is simple and lightweight, but it has trade-offs: UDP can silently drop messages under heavy load, and it isn’t encrypted. For environments that need guaranteed delivery, encryption in transit, or HTTP-based sources, a collector can run additional listeners.

Open the collector under Configure → Collectors and look for the log ingestion settings. Each advanced listener has an enable toggle and a port you can set.

Reliable delivery. TCP syslog uses a connection-oriented transport, so messages aren’t silently dropped the way they can be with UDP when a device or the network gets busy. It also handles larger messages cleanly.

  • Enable the TCP syslog listener and set its port (a common choice is 601).
  • Point devices that support TCP syslog at the collector’s address on that port.

Choose this when: you’re seeing dropped messages under load, you have chatty devices, or you simply want delivery you can count on.

Option Delivery Encrypted Best for
UDP syslog (514) Best-effort (can drop under load) No The default — simple, low overhead, works everywhere.
SNMP traps (162) Best-effort No Event notifications from network hardware.
TCP syslog Reliable No High-volume or critical devices where no message should be lost.
TLS syslog Reliable Yes Logs crossing untrusted networks; compliance needs.
HTTP Event Collector Reliable Yes Apps and cloud sources that POST events over HTTPS.

Whichever option you use, the steps are the same shape:

  1. Find the collector’s address: it’s the IP address or hostname of the host (or container) where you installed the collector. If devices reach it through a NAT or load-balanced hostname and you’re using TLS syslog or HEC, add that hostname under Reachable addresses on the collector’s Settings tab so it’s included on the auto-issued certificate — otherwise senders that validate the certificate will reject it.
  2. Pick the port for the transport you’ve enabled (514 for UDP syslog, 162 for traps, or the port you set for TCP/TLS/HEC).
  3. Configure the device’s logging or trap destination to that address and port.
  4. Generate some activity on the device, then confirm the messages show up in Logs & Log Search.

If nothing arrives, confirm in Logs & Log Search — search for the sending device or open the raw feed. The collector’s Health tab also shows a Log ingest history chart so you can confirm events are actually arriving at the collector; see Reading a Collector’s Health Tab.

docs built 2026-11-12 · 945a2dec2