The main goal of the application is network monitoring. It involves multiple checks of various types for devices on the network and a response according to the results of these checks.
For this purpose, the user creates sensors. Sensors track certain aspects of the device operation. Each sensor collects and analyzes information about the device, then evaluates the current state based on the user settings and, if necessary, notifies about possible issues.
Each sensor can monitor one node in the network tree. Thus, a sensor can be assigned to a device or a group.
If the sensor is assigned to a group, it will monitor and be displayed for each device in that group. This can be useful when a particular monitoring scenario is viable for multiple devices.
Therefore, to start monitoring a new device, it's enough to place it in a group to which the necessary sensors are already assigned.
If a group contains subgroups, then its sensors will also apply to all devices in the subgroups.
Sensors can be started in three ways
A manual start of a sensor initiates an immediate, single check.
You can start a sensor once from its context menu in various widgets, for example: in the Network tree, in the Sensor list, etc.
- On schedule:
In this case the Scheduler is used. It can be enabled when creating or editing a sensor, on the Configuration step.
- Based on the result of another sensor:
Logic chains can be formed into a monitoring scenario to detect issues more effectively.
With their help, various actions can be performed and notifications sent out depending on sensor results, and additional sensors can be run as well.
Any sensor can be disabled. In such a case, it can't be run until reenabled from its context menu or editor.