Solution · Events in

A syslog server and trap receiver that already knows your devices


A standalone syslog server collects a great deal and understands none of it. The lines land in a file, the file grows, and the one line that mattered is read the morning after. SysPeep receives the same lines inside the monitor that already knows which device sent them and who is on call for it.


Key points

  • Syslog lines, SNMP v1 and v2c traps, v2 informs and Windows event log subscriptions arrive at the same Windows service that polls the devices.
  • Rules turn events into alerts by kind, application and severity; a built-in tester shows which rule wins for a given event and which rules are shadowed.
  • The events that do not matter stay on an events timeline, where they are still there when you need to know what happened right before something broke.
  • Notifications go out by email, webhook or script, with batching and digests so a storm of events does not become a storm of messages.
  • In every edition, including the free one. The firewall rules for the listeners are added by Quick Start.

On this page: Why inside the monitor What it receives Rules and the tester The timeline Setting it up What it is not


Switches, firewalls, UPSes and appliances all speak syslog or send SNMP traps, and most of them say something useful only once every few weeks: a power supply failed, a port went into err-disable, a VPN peer dropped, a fan is spinning down. Polling will find most of those eventually. The trap or the syslog line finds them now. The trick is to receive them somewhere that can tell the one useful message from the thousand routine ones, and then do something about it.


Why the receiver belongs inside the monitor


A standalone syslog server

  • Knows the sending address, not the device, its group, its dependency parent or its on-call route
  • Alerts, if at all, by matching text
  • Keeps a file that someone has to remember to read
  • Is one more service to install, patch and back up

The receiver in SysPeep

  • Files the event under the device that sent it, beside its sensors and its graphs
  • Uses the same rules, notification channels, maintenance windows and escalation as every other alert
  • Rolls an event from a device behind a failed switch under the switch's incident, like everything else
  • Is part of the one service you already run

What it receives


SourceWhat arrives, and where it goes
SyslogLines from network gear, Linux hosts, appliances and anything else that can send syslog, listened for by the service; the port is set in the console and offered to the Windows firewall by Quick Start
SNMP traps and informsv1 and v2c traps and v2 informs, named through the same compiled MIB set that names polled counters, so a trap from a known vendor reads as words rather than a dotted number
Windows event logsEvent log subscriptions over WMI from the Windows servers you monitor; events become alerts through rules with severity mapping, with no agent on the server
SysPeep's own flow noticesA router that stops exporting NetFlow raises a flow-silence event on its device within minutes, handled by the same rules
Pushed readingsNot events, but the same idea: a device or job that cannot be polled POSTs its own reading in and gets a graph and a threshold

Rules, and knowing which rule won


Rules turn events into alerts by kind, application and severity. That is the whole model, and it is enough: the err-disable message becomes a warning on the switch, the power-supply trap becomes a critical on the UPS, and the daily "configuration saved" line becomes nothing. What usually goes wrong with event rules is not writing them; it is not knowing which of fifteen rules actually caught a given line. SysPeep has a built-in tester: paste or pick an event and it shows which rule wins and which rules are shadowed by earlier ones, so the rule that never fires is found before the night it was supposed to.


The event that matters reaches the phone. The thousand that do not stay in the log, where they are still there when you need them.

An alert raised from an event is an incident like any other: it can be acknowledged by a junior administrator who cannot change the configuration, it is batched and digested during a storm, it waits out a maintenance window, and it escalates to a second channel if nobody answers. Notifications name the device and, when a device is watched from several places, the place that raised it.


The timeline: everything else, kept


Events that match no rule are not discarded. They sit on the events timeline, beside the device's sensor history, so that when the graph shows the link dropping at 02:14 you can read what the switch said at 02:13. Metric history and events share one retention horizon, 90 days by default, set in the console. The free edition's console shows the last 30 days; at least 90 are kept.


Setting it up


  • Install SysPeep on a Windows server or desktop you already have. One MSI, one Windows service.
  • Let Quick Start open the ports. Its last step lists every port the service will listen on, reads Windows Defender Firewall for rules that name SysPeep, adds the missing inbound rules and starts the service. A port changed later offers its rule again.
  • Point the devices at it. Set the syslog destination and the trap destination on the switch, firewall or UPS to the SysPeep server, or to the probe nearest the device in the paid editions.
  • Write the handful of rules you need, run them through the tester, and send a test notification from the console to prove the channel works.

What it is not


SysPeep is a monitoring system that receives events, not a log-analytics platform or a SIEM. It does not index terabytes of logs for free-text search, and it does not promise to correlate security events across an enterprise. It does the job most sites actually need from a syslog server: catch the message that means something, alert the right person, and keep the rest beside the graphs for the post-mortem. If you need full-text search over years of logs, run a log platform beside it and send SysPeep the alerts.


Is SysPeep a visual syslog server for Windows, and what is the syslog port no. 514?

Yes in the sense people mean by it: the syslog receiver runs as part of the SysPeep Windows service and the messages arrive in the console as they are received, filtered by device, facility and severity, with the rule tester showing which rule a line would trigger before you save it. The standard syslog port no. is UDP 514; TCP 514 is used where senders want delivery confirmed. Tell the device to send to the SysPeep server's address on that port and the first line appears within the next polling cycle.


Send a trap and watch it become an incident

Install the free edition, point one switch's syslog and trap destination at it, and write one rule. Up to 5 devices stay free at full depth, event rules included; the 30-day trial unlocks probes, scheduled reports and PDF export.

Download Free TrialAgentless and extensible