Cloudmon Probes handle agentless monitoring by polling devices using SNMP, WMI, ICMP, TCP, and NetFlow/IPFIX, then pushing the collected data to the Controller. Each probe monitors the devices in its local network segment.
The Cloudmon Probe is the agentless monitoring engine. It sits in the network, actively polls devices using the enabled protocols, and forwards the collected performance and availability data to the Cloudmon Controller at regular intervals. Separate probes must be installed for each distinct network segment within an organization. In MSP deployments, separate probes are required for each individual customer environment.
Probes are managed from the Controller under Settings → Monitoring → Probes, which lists all registered probes, their status, and the devices each probe is monitoring.
The probe list shows the following details. To add a probe, click Add, and see Probe Installation.
| Column | Description |
| Name | The probe name, with its status. Click it to open the probe's page. |
| IP | The IP address of the probe. |
| Hostname | The hostname of the probe. |
| Platform | The operating system of the probe: Linux or Windows. |
| Version | The installed probe version. |
| Created At | When the probe was added. |
| Entities | The number of monitors on the probe. |
| Tags | The tags on the probe. |
| Actions | Enable or disable the probe, edit it, delete it, Open terminal, and Update Probe. |
Click a probe to open its page. The header shows its status, IP address, hostname, version, when it was last polled, and its last boot. Use the time range control to change the period. The page menu has Edit, View Agent Information, Update Probe, and Export PDF.
| Tab | Description |
| Overview | Availability, system time and whether it is in sync, downtime, CPU, memory, and operating system. A map shows the probe's location. General Information shows the total monitors and whether SFTP, TFTP, SNMP Trap, and Syslog are on. Monitors counts the monitors by type, and Topology View shows the topology. |
| Monitors | Every monitor on the probe, with its name, type, status, when it was last polled, and tags. |
| Topologies | The Layer 2 topology scans on the probe, with their name, seed IP, IP range, and status. |
| Outages | A timeline and list of the probe's outages, with their start time, end time, duration, and reason. |
Click the edit icon of a probe to open Edit Probe Monitor. The Network Device, Host Availability, Service Availability, Website, IPAM, and Plugin tabs list the probe's monitors of that type. The Configuration tab holds the following sections.
| Section | Description |
| Probe Details | The Name and Tags of the probe, and its Hostname or IP. |
| Syslog & SNMP Trap Ports | Select Enable syslog and Enable SNMP Trap to turn on these receivers on the probe, and set the Port for each one. |
| TFTP & SFTP/SCP Servers | Select Enable TFTP to turn on the TFTP server on port 69, and Enable SFTP/SCP to turn on the SFTP/SCP server on port 22. |
| Alert Settings | The probe's "alerts" and who is notified, as described in Probe Alerts. |
You can open a command line on a probe from your browser. Commands run as the user the collector service runs as, with that user's login profile. Who connected, when, and your comment are recorded in the audit log. Your role needs permission to open a collector terminal.
| Field | Description |
| Session length | Required. How long the session lasts. You can extend it while connected, up to 2 hours in total. |
| Comment | Required. Why you are connecting, for example, to check a disk alert. |
The window has two more options, described in the following table.
| Option | Description |
| History icon | Opens Terminal sessions, which lists the sessions opened on the probe, with when each started, the user, the length, the connection, the result, and the comment. |
| Settings icon | Opens Terminal connection settings, used to connect the browser directly to the probe. Enter a STUN server, a TURN server, and the TURN user name and TURN password, which is stored encrypted. Leave the servers empty when the browser and the probe can reach each other. Without a working path, the session falls back to a relay through the controller. Click Use for this session, or select Save as default for every terminal session of this customer first to keep the settings. |
Once connected, the window shows the following controls.
| Control | Description |
| Live status and Direct badge | Show that the session is live. Direct means the browser is connected straight to the probe, not through the controller relay. |
| Time left | A countdown of the time left in the session. |
| Extend | Adds time to the session, up to 2 hours in total. |
| Full screen and minimize icons | Enlarge the window to full screen, or minimize it. |
| Close session | Ends the session. |
Each probe has its own alert settings, so the right people are told when a probe stops working or its clock drifts.
| Field | Description |
| Alert when Probe goes down | Select to raise an alert when the probe goes down. |
| Alert when Probe time is not in sync with controller by | Select to raise an alert when the probe's time differs from the controller's by the number of minutes you enter. |
| User Groups | The user groups notified for the selected probe alerts. |
| Third Party Services | The third-party services notified for the selected probe alerts. |
The following Cloudmon monitoring capabilities require a probe to be deployed in the relevant network segment:
| Feature | Protocol / Method |
| SNMP Network Device Monitoring | SNMP (Linux probe only) |
| WMI Monitoring | WMI (Windows or Linux probe) |
| Network Discovery | ICMP, TCP, SNMP |
| Layer 2 Topology Discovery | LLDP / CDP via SNMP |
| Host and Port Availability Monitoring | ICMP, TCP |
| Website and DNS Monitoring | HTTP/HTTPS, DNS |
| Log Monitoring (Syslog, SNMP Traps) | UDP/514 (Syslog), UDP/162 (SNMP Trap) |
| NetFlow / IPFIX Traffic Analysis | NetFlow / IPFIX via UDP/2055 |
| VMware Monitoring | VMware API via probe |
| Network Configuration Management (NCM) | SSH / Telnet via probe |
| AWS Cloud Monitoring | Cloud provider APIs via probe |
Azure monitoring does not need a probe. In the Azure account form, Monitor From can be set to Controller or Probe.