Frequently Asked Questions
Short answers, in the order people tend to ask, with the catches included. Click a question to open it; the long answers are one link away. If your question is not here, ask us.
Getting started
What it runs on, whether it needs agents, how long the first useful alert takes, and what the trial does when it ends.
What does SysPeep run on?
A Windows server or desktop you already have. It installs from one MSI as a single Windows service that contains the console, the collectors, the event receivers and an embedded time-series store. There is nothing else to license or patch. Everything it monitors — Linux hosts, hypervisors, network gear, cloud accounts, plant-floor controllers — is reached from that one service.
Do I need to install agents on my servers?
No. Windows is monitored over WMI, Linux over SSH, network devices over SNMP, and server hardware over IPMI and Redfish. Remote probes are optional components for branches, DMZs and segmented networks, not agents on every host. Agentless and extensible ›
How long until it is doing something useful?
Quick Start adds the firewall rules and starts the service; you run the first discovery from the dashboard and watch it progress, and from then on discovery runs continuously whether or not anyone is logged in. The first devices are on the map while you are still reading the release notes, and the first 5 are free at full depth, so an evaluation costs an afternoon.
Is there a trial, and what happens when it ends?
The 30-day trial unlocks every feature except clustering, for any number of devices. When it ends, monitoring, discovery and flow intake pause and the configuration is kept intact — devices, groups, thresholds, rules, dashboards and at least 90 days of history. Install a license or continue on the free edition with up to 5 devices, restart the service, and it resumes where it stopped.
Do I have to open the Windows firewall myself?
No. The last step of Quick Start 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 in the settings offers its rule again, so probes and flow exporters are not silently shut out.
Licensing and editions
What the license counts, what the free edition includes, what you own, and what happens when an update period runs out.
What does the license count?
Monitored devices. Sensors are unlimited, so adding the fortieth check to a server costs nothing, and flow analysis is included rather than priced per interface. A device counts once however many places monitor it, and the SysPeep server's own device and the probes' health devices never count. Count the devices you intend to monitor; that is the license. How the licensing works ›
What is in the free edition?
The real product: every sensor type, unlimited sensors, every collection method, flow analysis from the devices you monitor, the full alerting engine, the reports, more than one console account, directory sign-in, and a license that never expires; free for personal and business use. It is not a crippled trial. The Free edition monitors up to 5 devices. It does not include remote probes, scheduled reports or PDF export, and the console shows the last 30 days of history. Professional adds all three, and the full history, from 10 devices; the High Availability edition adds clustering on Windows Failover Cluster. Compare editions ›
Is it a subscription?
Professional and the High Availability edition are sold as perpetual licenses with optional maintenance. You buy it once and own it; a key covers every version released within its update period, and the version you own keeps monitoring whether or not you ever renew.
What happens if I install a version released after my update period?
Monitoring pauses, the devices and configuration are kept with at least 90 days of history, and the failure is written to the Windows Application event log as one of events 1101 to 1105, so the event-log monitoring you already have will notice. Update the license or go back to a covered version, restart the service, and it resumes. What a license turns off is marked, never deleted, so no edition change costs you a configuration.
Are there add-on packs for flows, reports or integrations?
No. Flow analysis and directory sign-in are in every edition including the free one. Scheduled reports are part of the paid editions rather than a separate purchase. Notifications by webhook and script connect to chat, ticketing and paging tools with no per-integration licensing.
What it monitors
The collection methods and sensors, MIBs, custom checks, syslog and traps, NetFlow, and how the poller behaves.
What can SysPeep monitor?
Thirty-eight collection methods and 280 catalog sensors: SNMP, ICMP, TCP, DNS, NTP and SIP for the network; NetFlow, sFlow and IPFIX for traffic; WMI, SSH, Windows event logs, IPMI and Redfish for servers; vCenter, Proxmox, Kubernetes and Prometheus for virtual and container estates; HTTP, multi-step web journeys, databases, mail round trips, LDAP and RADIUS for applications; CloudWatch, Google Cloud Monitoring and Azure Monitor for cloud; Modbus, MQTT and OPC UA for the plant floor; Certificate Transparency, SPF, DMARC and DNSSEC for hygiene; and LLM endpoints. Everything it monitors ›
What if the thing I need to watch is not in the catalog?
On a Windows host, the WMI explorer lets you browse the classes property by property, with sample values, and turn any numeric property into a sensor with no script. Elsewhere, the output of a command, script or program becomes a sensor, as does any SQL result, a file or folder check, a pushed reading from a device or job that cannot be polled, and a calculated expression over other sensors. Custom sensors are graphed, thresholded and alerted on like built-in ones, and they do not add to the license count.
Does it know my switch vendor's MIBs?
A compiled MIB set installed beside the service names walked OIDs, types and enumerations for the standard IETF and IEEE modules and for vendors such as Cisco, Juniper, Arista, Fortinet, Palo Alto, HPE, Dell, APC, MikroTik and Synology — about 2.2 million objects in 14,400 modules. For a device the set does not know, upload its own MIB files: uploads take precedence, missing dependencies and duplicates are reported, and the uploads are kept and compiled again at every start.
Does it receive syslog and SNMP traps?
Yes. Syslog, SNMP traps and informs, and Windows event log subscriptions arrive at the same service, and rules turn them into alerts by kind, application and severity. A built-in rule tester shows which rule wins for a given event.
Does it do NetFlow?
NetFlow v5 and v9, IPFIX and sFlow v5, with listeners on the server and collection at remote probes, and it is included in every edition. A Flows page in the main navigation shows the status of each exporter, the top talkers, conversations, interfaces and QoS classes, interface use as a percent of link speed with the interfaces named as SNMP names them, the traffic pattern by hour of the week, and the countries the busiest senders are placed in — and every total says how much of the window the collector observed. A router that stops exporting raises a flow-silence event on its device within minutes. Exporters that send flows but are not yet monitored are listed with an Enable button and a daily reminder rather than silently dropped. Flow analysis ›
What happens when a poll takes longer than its interval?
The chart, the device row and the sensors table say so in plain words — "Collection took 75 s, longer than the 60 s interval" — with the advice to lengthen it, and one warning event a day. Collection runs on a fixed 30-second clock grid with parallel workers and a bounded cycle, so a hung device delays only its own sensors, and a failed WMI or script check says why it failed. How collection runs ›
Alerting
Alert storms, down versus degraded, notifications, thresholds, and who may acknowledge what.
How does it avoid alert storms?
Devices behind a failed upstream are marked unreachable under the upstream's incident, so a dead core switch raises one incident rather than one per host. If the monitoring host loses its own network link, judgement freezes, exactly one incident is raised, and no device is falsely marked down. Thresholds carry duration and repeat-count damping, so a momentary spike pages nobody. How alerting is designed ›
What is the difference between down and degraded?
You choose which sensor proves a device is reachable (or let SysPeep choose). Only that sensor can mark the device down. Everything else — a full disk, a stopped service, a slow query — marks it degraded, with its own alert, and leaves the availability record alone.
How do notifications reach us?
Email, webhooks and scripts, with batched device-down notifications, repeat reminders for unacknowledged incidents, escalation to a second channel, digests of up to 24 hours, maintenance windows for planned work, and a test-send from the console to prove each channel before it is needed. Every notification names the sensor and, when a device is watched from several places, the place that raised it.
Do I have to type a threshold for every sensor?
No. Besides warning and critical levels with a direction and a debounce, an "Unusual values" threshold sets the level in sigma against the sensor's own recent readings, learned over eight polls, on gauge and counter sensors. Interface utilisation sensors come seeded with a warning at 80% of the link speed.
Can the helpdesk acknowledge alerts without being able to change the configuration?
Yes, in every edition. Three administrator tiers — junior, mid and senior — are enforced at every endpoint that changes anything, so a junior account can acknowledge and investigate but not reconfigure, delete or clear. Every change is written to an audit log with the administrator's identity.
Reports and numbers
Whether the uptime figure can be trusted, which reports it produces, and who monitors the monitoring server.
Can I trust the uptime figure?
Every availability figure is bounded by the coverage that was actually measured. A month with no monitoring data shows as no data, never as 100%; partial months are labelled with how much was measured; a single missed poll is a red gap on the graph. Reports you can stand behind ›
What reports does it produce?
An executive scorecard, and health, SLA, alerts, capacity, inventory and traffic reports, exportable as CSV, and in the paid editions as PDF. In the paid editions they can be scheduled and delivered by email. Countdown metrics such as certificate days and disk space are shown as projected dates.
Who monitors the monitoring server?
SysPeep does. A built-in device for the SysPeep server itself, in the Self-Monitor group, tracks its own collection failures and timeouts, poll-cycle timing, event rate, host CPU and memory, database latency and disk, and projects the date its disk will fill. A run history records when it was running and polling, so a stopped monitor is a hole in the availability record rather than uptime. Every remote probe is a monitored device as well, so a dead probe is an incident rather than a mystery of missing data.
Deployment, scale and security
Where the data and the passwords live, databases, probes, high availability, directory sign-in, certificates, upgrades and the API.
Where does my monitoring data live?
On your server. SysPeep is on-premises software: one Windows service with the console compiled into the service executable, time-series data in its own embedded store, and configuration and history in your choice of SQLite, MySQL or SQL Server, with retention you set. There is no hosted platform holding your data. Deployment and security details ›
Where are the device passwords stored?
Device credentials, and the passwords in the configuration file, are encrypted with AES-256-GCM under a key kept in the installation's own data folder, restricted to SYSTEM, Administrators and the service account, never compiled into the programs and never in the configuration file. A copied configuration file or a database backup without that key does not hand over the network's passwords. Secrets such as API tokens are shown exactly once.
Which databases does it support?
SQLite, MySQL and SQL Server, with the schema kept in verified parity across all three and Unicode text in every one. Start on SQLite with no database administration; move to the corporate standard when policy requires it. Time-series data lives in SysPeep's own embedded store. Metric history and events share one retention horizon, 90 days by default; flow history has its own setting and a storage ceiling that removes the oldest whole days first. A lost database connection is handled without writing a row twice or leaving a change half done.
How does it handle multiple sites and segmented networks?
Remote probes (paid editions) poll a branch, DMZ or OT segment from the inside and report back over mutual TLS, so no inbound firewall rule is needed on the branch. They run 21 of the 38 collection methods at the branch, collect flows locally, self-update, and come as one console download with the configuration inside. Each probe is itself a monitored device, and the console says which place saw and reached each device, so the probe that polls it is chosen on evidence. A sensor can also be checked from up to four places — this server or any probe — with the device still counted once, and every alert names the place that raised it.
Is there high availability?
The High Availability edition runs as a native resource on Windows Failover Cluster, so the monitor survives its own host failing on cluster infrastructure you already operate.
How big an estate will it handle?
We do not print a device-count ceiling, because a number without a reference deployment behind it would be marketing. What is true: remote probes distribute collection, the data tier moves to MySQL or SQL Server when needed, and the High Availability edition clusters the service. Size it on your own network during the trial.
Does it integrate with Active Directory?
Yes, in every edition. Sign-in can be local or through Active Directory and LDAP, including LDAPS, configured in the control panel and applied to the next sign-in without a restart. The local password is checked first, then the directory, so a domain-controller outage never locks the administrator out of the monitoring console; directory groups map to the three permission tiers.
Can I use our own HTTPS certificate?
Yes: a PEM, DER, PKCS#7, PKCS#12/PFX or PVK file, or a certificate from the Windows certificate store by thumbprint. A Check certificate button reports expiry, key strength and missing intermediates before anything is saved, and a certificate that is present but cannot be used stops the service with the reason rather than being replaced by a self-signed one.
What happens during an upgrade?
The installer stops the old service itself, even one stuck in Stopping, installs the new one and starts it again if it was running before. Alert status survives the restart, so nothing is alerted twice and no recovery is reported that did not happen. If the service ever does stop, the control panel says why, with a pointer to the log.
Is there an API?
Scripts and integrations authenticate with API tokens that carry a read or write scope, are shown once at creation and can be revoked individually. Outbound, webhooks and scripts carry incidents to whatever system expects them.
The console
Browsers, accessibility, text size and the documentation.
Which browsers work?
Any browser you have. The console is rendered on the server, so status, filters, search and alert acknowledgement work without JavaScript from a locked-down jump host, a kiosk browser or an old crash-cart laptop. Modern browsers get the modern experience layered on top, and older engines are supported through feature-detected polyfills and WOFF fonts, all served by the console itself.
Is it accessible?
Its keyboard operation, screen-reader announcements, named controls, focus management and contrast were reviewed against WCAG 2.2 AA in an internal review, and the fixes are pinned by automated tests. The layout reflows to a 320-pixel window without sideways scrolling, and Windows high-contrast and reduced-motion settings are honoured.
Can I make the text bigger?
A text-size control in the page header offers normal, large and extra large (100, 112.5 and 125%), remembered per browser. Every size is relative, so browser zoom and font settings scale the console too.
Where is the documentation?
A full manual is provided in PDF and HTML. See the help manual, and contact support for anything it does not answer.
The quickest answer is the trial
Install it on a Windows server you already have, run the first discovery, and monitor up to 5 devices at full depth for free. The 30-day trial unlocks every feature except clustering, so most of these questions can be answered on your own network.
Download Free TrialCompare EditionsAsk Us a Question