What Sergward collects
This list comes from the batch format the agent sends: every point here is a field that actually travels. If something is not on this page, it is not collected.
Machine identity
- Hostname, operating system, platform, kernel version and architecture.
- Agent version and which modules are on.
- How long its last measurement cycle took.
Usage metrics
- CPU, memory, disk and network: the numbers behind the charts.
- Each reading travels as a name, a value and a timestamp. Nothing else.
Processes and services
- Per process: id, name, the user running it, and how much CPU and memory it uses.
- Per watched service: its name and whether it is running.
A process command line is never sent. The executable name is; its arguments — where someone occasionally puts a password — are not.
Inventory
- Hardware: manufacturer, model, serial number, CPU, memory, BIOS and physical disks.
- Installed software: name and version of each package.
It does not travel every cycle: it is heavy and barely changes, so it is taken now and then.
Backups
- Per backup file: where it is, when it was written and how big it is.
- To tell whether it is healthy, the agent does open the file and reads its header.
That content is discarded as it is read and at no point leaves the machine. At most 8 MiB are read, only to check the file is not corrupt. What travels is the verdict: healthy or not.
Network gear
- From the devices the agent probes — switches, UPS, NAS, cameras —: whatever they answer over SNMP or ping.
- From network discovery: which addresses replied and what kind of device they look like.
What is not collected
- The contents of your files. The agent opens backups to check they are not corrupt, and discards what it reads.
- What you type, what is on your screen, what you browse.
- The arguments a process was launched with.
And who looks at it
The agent only talks outbound, over HTTPS. It opens no inbound port. If you would rather nothing left your network, the product can run on your own infrastructure.