The Collector is a light-weight agent based on patented technology. It captures and reports network connections, program executions, web requests, and many other activities and properties from the devices of the end-users on which it runs. It is implemented as a kernel driver and an accompanying service, offering remote and automated silent installations and negligible impact on the performance of local desktops, while minimizing network traffic.
|CPU usage||Memory usage||Network traffic|
The following figure depicts the role of the Collector within the Nexthink solution.
The capabililty of the Collector for gathering user activity data is shared by the kernel driver and the helper service (or daemon) components. By running close to the operating system, the kernel driver detects some kinds of user activities that are only visible at this level.
The Collector is available for both Windows and macOS operating systems. The present documentation states the platforms to which each feature applies. Likewise, the data model details the individual pieces of information collected for each platform.
Since the Windows Collector driver is a kernel-mode component, any error in its internals or its interaction with a misbehaving third-party driver can lead to system instabilities. Even with Nexthink putting as much attention as possible towards delivering bug-free software, the principle of precaution holds. The CrashGuard feature detects every system crash and, by default, it disables the Collector driver itself if the system crashes more than three times in a row after installation.
Kernel traffic interception
Some applications may send and receive data to and from the network using kernel-mode components, actually hiding their network traffic from user-space monitoring applications. Being a kernel driver itself, the Windows Collector is nevertheless able to detect and report such traffic.
The Collector identifies commonly used paths (e.g. C:\WINDOWS\, C:\Program Files\) and other special mount locations (removable mount points, network drives) with paths aliases. For example, if the DVD-Rom drive is mounted under D:, the Collector reports an application setup.exe being launched from this media as %RemovableDrive%\setup.exe.
Reliable connectivity via TCP
When configured to send data through TCP, the Collector relies on the connection-oriented features of the protocol to ensure that the information reaches the Engine.
In addition, when the connection between the Collector and the Engine is lost or not established yet, the Collector is able to buffer up to 15 minutes of data (a maximum of 2500 packets not older than 15 minutes) to send to the Engine once the connection is (re-)established.
A change of network interface is transparent to the Collector, except when it invalidates the DNS resolution of the Engine. In the latter case, the process of adapting to a different network may take a few minutes and the Collector resends the whole context to the Engine.
Main events and errors are written to either the standard Windows event logs or Mac OS logs.
The Collector driver parameters can be changed through the Collector Control Panel extension or the Collector Configuration tool. There is no need to restart the computer for the changes to become effective.