How Cloudmon Probes Collect Data (SNMP, WMI, ICMP, NetFlow)

Probes

Installation and Deployment

Probes

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.

Overview

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.

Probe List

The probe list shows the following details. To add a probe, click Add, and see Probe Installation.

ColumnDescription
NameThe probe name, with its status. Click it to open the probe's page.
IPThe IP address of the probe.
HostnameThe hostname of the probe.
PlatformThe operating system of the probe: Linux or Windows.
VersionThe installed probe version.
Created AtWhen the probe was added.
EntitiesThe number of monitors on the probe.
TagsThe tags on the probe.
ActionsEnable or disable the probe, edit it, delete it, Open terminal, and Update Probe.

Probe Details

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.

TabDescription
OverviewAvailability, 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.
MonitorsEvery monitor on the probe, with its name, type, status, when it was last polled, and tags.
TopologiesThe Layer 2 topology scans on the probe, with their name, seed IP, IP range, and status.
OutagesA timeline and list of the probe's outages, with their start time, end time, duration, and reason.

Editing a Probe

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.

SectionDescription
Probe DetailsThe Name and Tags of the probe, and its Hostname or IP.
Syslog & SNMP Trap PortsSelect Enable syslog and Enable SNMP Trap to turn on these receivers on the probe, and set the Port for each one.
TFTP & SFTP/SCP ServersSelect 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 SettingsThe probe's "alerts" and who is notified, as described in Probe Alerts.

Opening a Terminal

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.

  1. In the probe list, click the Open terminal icon of the probe.
  2. Fill in the fields as described in the following table.
  3. Click Connect.
FieldDescription
Session lengthRequired. How long the session lasts. You can extend it while connected, up to 2 hours in total.
CommentRequired. Why you are connecting, for example, to check a disk alert.

The window has two more options, described in the following table.

OptionDescription
History iconOpens 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 iconOpens 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.

ControlDescription
Live status and Direct badgeShow that the session is live. Direct means the browser is connected straight to the probe, not through the controller relay.
Time leftA countdown of the time left in the session.
ExtendAdds time to the session, up to 2 hours in total.
Full screen and minimize iconsEnlarge the window to full screen, or minimize it.
Close sessionEnds the session.

Probe Alerts

Each probe has its own alert settings, so the right people are told when a probe stops working or its clock drifts.

  1. Navigate to Settings → Monitoring → Probes and click the edit icon of the probe.
  2. In the Configuration tab, expand Alert Settings.
  3. Fill in the fields as described in the following table.
  4. Click Save.
FieldDescription
Alert when Probe goes downSelect to raise an alert when the probe goes down.
Alert when Probe time is not in sync with controller bySelect to raise an alert when the probe's time differs from the controller's by the number of minutes you enter.
User GroupsThe user groups notified for the selected probe alerts.
Third Party ServicesThe third-party services notified for the selected probe alerts.

Features Requiring a Probe

The following Cloudmon monitoring capabilities require a probe to be deployed in the relevant network segment:

FeatureProtocol / Method
SNMP Network Device MonitoringSNMP (Linux probe only)
WMI MonitoringWMI (Windows or Linux probe)
Network DiscoveryICMP, TCP, SNMP
Layer 2 Topology DiscoveryLLDP / CDP via SNMP
Host and Port Availability MonitoringICMP, TCP
Website and DNS MonitoringHTTP/HTTPS, DNS
Log Monitoring (Syslog, SNMP Traps)UDP/514 (Syslog), UDP/162 (SNMP Trap)
NetFlow / IPFIX Traffic AnalysisNetFlow / IPFIX via UDP/2055
VMware MonitoringVMware API via probe
Network Configuration Management (NCM)SSH / Telnet via probe
AWS Cloud MonitoringCloud 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.