The first tab you open in the morning
The real test of a monitoring tool is not the feature list. It is whether, six months in, it is the first thing you check with the coffee and the last thing you would give up in a budget cut.
Key points
- A thirty-second morning check: KPIs, a site latency and loss heatmap, top talkers, hygiene nudges, and a NOC wall view for any spare screen.
- A device workspace with the tree and the map together, which remembers your view, filters and open tabs.
- Discovery that runs whether or not you are logged in, files new devices into the right group, and keeps up when a host is renamed.
- Incidents you can acknowledge, assign and comment on from any browser, with the graph and the events timeline beside them.
- Maintenance windows, a rule tester, a test-send and a text-size control, so planned work stays quiet and the console fits the screen you have.
On this page: The morning check Finding the device New devices Working an incident Planned work Staying out of your way
That depends on a hundred small decisions about how the console behaves on an ordinary Tuesday: how long the morning check takes, how fast you find the device you are looking for, whether the page remembers where you were, and how much of the housekeeping the tool does for you. This page is about those decisions.
The thirty-second morning check
The dashboard opens on fleet KPIs, a site latency and loss heatmap, hygiene nudges and the widgets you add — top talkers, an hourly heat strip of traffic per flow exporter — with the open incidents one click away. It also says how much of the last 24 hours SysPeep was observing, and if the service is stopped or network-blind the tiles turn grey and hatched with "Not observing since", so nobody mistakes the last known state for the current one. The same dashboard has a NOC wall view that works on any spare screen in the office, so the person walking past the door sees the same red the on-call engineer sees.
Finding the device in seconds
The device workspace shows the tree and the topology map in one place. Groups visibly contain their devices; dependency parents and children are stepped and connected. A Show filter narrows the view — by status, by flow (sending, stopped) or by vantage (seen by this server and a probe, found only by one probe) — search finds the box by name, and each device opens in its own tab, where a Manage sensors page holds everything about what the device collects, why a sensor fails, and a Pause alerts button for the next hour or four.
The page remembers your view, your filters and your open tabs, so every navigation lands you back where you left off rather than at the top of the tree. (Monitoring consoles that reset to the top of the tree on every click have cost the industry more hours than most outages.)
In the workspace
- Tree and topology map together
- Show filter and search, by status, flow or vantage
- Per-device tabs, with Manage sensors on each
- View, filters and tabs remembered
New things take care of themselves
On a new install, discovery waits for you to run the first sweep from the dashboard; after that it runs continuously as a service, whether or not anyone is logged in. A device that appears on the network shows up in the "Discovered" filter with a nudge on the dashboard, so onboarding is a click rather than an audit — and a device that appears where nothing should have appeared is at least noticed.
- Smart groups file the new switch into the branch group by subnet
- Twelve identical switches are twelve devices, each with its own key, not the first of each model
- A renamed host keeps its discovered name current; the names your team chose are kept, with "Discovered as" beside them
- Retired hardware leaves the working views but keeps its history
- Flow exporters that are sending but not yet monitored are listed on the Flows page with an Enable button, and a daily reminder, rather than silently dropped
Working an incident
The alert is the incident. From whatever browser is nearest — including one with scripting disabled on a locked-down jump host — you can acknowledge it, assign it, add a comment on what you found, clear it and archive it, with the full history kept on the incident itself. The incident names the sensor and, when the device is watched from several places, the place that raised it. The device's graph shows the spike or the red no-response band that led up to it, with the exact readings one click away in a table. The events timeline shows every syslog line, trap, Windows event, availability change and flow notice from just before, with what each one became. Unacknowledged incidents re-notify on an interval and escalate to a second channel, so nothing slips because the first page arrived during a meeting.
| Ordinary Tuesday | Where it lives in SysPeep |
|---|---|
| Coffee, overnight check | Dashboard: KPIs, heatmap, hygiene nudges; then the open incidents |
| "Is the new switch in the branch monitored yet?" | "Discovered" filter; smart group membership by subnet |
| "What happened to the file server at 02:14?" | Device tab: graph with red no-response band, events timeline from 02:00 onward |
| Patch window tonight on the database cluster | A maintenance window; the restarts stay quiet |
| "Did anyone pick up the firewall alert?" | The incident shows who acknowledged it, when, and what they wrote |
| "Which router stopped sending NetFlow?" | The Flows page: a status tile per exporter, and a flow-silence event on the device within minutes |
| "Is it the server, or the WAN to the branch?" | "Also monitor from…" a second place; the alert names which place raised it |
| "Add the vendor's temperature counter to the new switch" | Add sensor: search by what it measures, Test, then Add; the MIB set names the counter |
| Monthly report due Friday | Scheduled report delivery (paid editions); CSV export in every edition, PDF export in the paid editions |
| "Is the monitoring server itself okay?" | The SysPeep server device in the Self-Monitor group: collection failures, poll-cycle timing, event rate, disk, and the date it fills |
Planned work without the noise
Before the change
Maintenance windows keep scheduled work quiet without anyone remembering to pause and un-pause devices. The event rule tester shows which rule will win for a given event, which is how you change the rules at four in the afternoon without wondering what will page you at four in the morning.
During and after
Restarting the monitoring service never produces a storm, because failures during the restart are batched, open incidents survive it, and each sensor's stored status is taken as confirmed before the first poll, so nothing is alerted twice. An upgrade stops the old service itself, even one stuck in Stopping, and starts the new one again; if the service ever does stop, the control panel says why. A test-send from the console proves each notification channel works before it is needed.
The monitor stays out of your way
One Windows service, one installer, retention settings that bound disk growth to numbers you chose. Remote probes self-update and pick up configuration without a restart. The built-in SysPeep server device watches its own collection failures and timeouts, poll-cycle timing, event rate, host CPU and memory, database latency and data-volume disk, and gives a projected date for the disk filling, so the monitoring server is the one box you will not be surprised by. The console itself fits the screen you have: a text-size control in the header offers normal, large and extra-large, and the layout reflows to a 320-pixel window without sideways scrolling.
The product is designed to be installed, configured and then mostly left alone, which is the highest compliment an administrator pays to software.
Run it for a week and see where it ends up in your tabs
The free edition monitors up to 5 devices at full depth for as long as you like. If it is the first tab you open by the second Monday, the trial has done its job.
Download Free TrialNext: How the licensing works