Monitors are individual checks that watch a specific device, service, or metric in your network. A monitor can be as simple as “is this server reachable?” or as detailed as “what is the current CPU load, disk space, or database query result?” The goal is to detect problems early by checking both availability (up/down) and operability/performance (is it responding normally, and are key values within healthy limits?).
Monitors in IPNetwork Monitor. In IPNetwork Monitor, a monitor is the core building block: it polls a target at a defined interval, returns either a value or an error, and then changes state based on configured conditions (for example OK, Performance Warning, or Down). Each monitor has key settings such as its name, monitor definition (what/how to check), polling interval, optional dependencies (only check if another monitor is healthy), and reporting options. When a monitor changes state, IPNetwork Monitor triggers notifications through alerting rules. You can organize monitors into host groups for easier management and choose from many monitor types—like PING, TCP, HTTP/HTTPS, DNS, SNMP, WMI, SSH, database monitors (ODBC/Oracle/MySQL/MS SQL), file and disk checks, syslog, Windows Event Log, and custom scripts (including Nagios plugins and Python). For faster troubleshooting, IPNetwork Monitor can also link monitoring to built-in admin tools like SSH, Telnet, and Remote Desktop directly from the GUI.
