Qosium Probe is the heart of the Qosium family. It is the software that carries out the actual measurement as instructed by measurement controllers like Qosium Scope, Qosium Scopemon, or even your own developed upon the QMCP API provided by Kaitotek.
Qosium Probe operates the packet capturing process and performs almost all the measurement related calculations. It does not have a user interface, but instead, a measurement controller is required to operate the measurement. The typical deployment is to install Qosium Probe as a system service to the background in a measurement point. The platform, where it is installed, is called a measurement point.
Qosium Probe is a multi-thread server capable of supporting a number of simultaneous controllers. All controller sessions and their measurements are independent. Thus, only a single Probe is required per measurement point.
- Purpose: The core of Qosium, enabling the passive QoS measurements (measurement agent)
- Current main version: 1.4… (Core: 2.26…)
- Delivery type: Binary executable and binary shared libraries
- Tested platforms (Qosium Probe’s availability is not limited to those)
- Windows 7 and newer, including multiple Windows Server versions
- Linux operating systems with kernel version of 2.6 and newer
- FreeBSD v9 and newer
- Android: various versions
- macOS: 10.12 and newer
- Raspbian Buster
- Axis network cameras: various versions
- Teltonika routers: various versions
- NanoPi router: R1S
- Labpano Pilot Era: All-in-One 8K 360 VR Camera
- Other supported platforms
- As long as build environment with GNU C++ version of 4.8 and newer is available, Qosium Probe can typically be provided.
- Installation and Running Requirements
- Administrative rights to install and run
- Packet capture library
Qosium Probe is a light-weight software. When it’s running in an idle state, not instructed to measure, the resources it takes from the host machine are negligible. When measuring, the CPU and memory usage depend almost directly on the packet rate of the measurement target flows. You can measure fairly high throughputs even on a constrained device, like Raspberry Pi. On a modern standard office computer, measuring a traffic stream of 100 000 pkts/s should not be a problem. At this speed, the machine’s 1 Gbit/s LAN link is already filled with traffic.
When there are multiple simultaneous measurements ongoing, they will all their part to a total load of Qosium Probe. The maximum number of simultaneous controllers per Probe is dependent on capture parameterization and heaviness of the simultaneous measurements vs. the resources available in the platform.
By its nature, Qosium Probe is a remotely controlled measurement unit. The control of Qosium Probe can be limited to a certain IP address space or even only to certain IP addresses see the parameterization. However, this is ineffective if the misuse is committed inside the company’s network. Thus, it is the user’s responsibility to set the control limitations to Qosium Probes, and take care of the security of their network in such a way that no third party can break into the network and potentially misuse Probes installed to the devices in the network.