| Methodology |
Deploy the Cloudmon Agent on each server that requires monitoring. |
Cloudmon uses Probes to monitor IP network endpoints and devices in the network such as routers, switches, servers, and hosts supporting SNMP, as well as Windows applications and servers through WMI. |
| How it works |
The Cloudmon Agent executes commands/queries to collect information and key metrics relating to the compute system (hardware/OS/hypervisor) and the processes running on the system, and periodically sends them to the Cloudmon Controller over a secure channel. |
The Cloudmon Probe gathers information by employing SNMP/WMI polling for network devices and Windows servers, and acquires data from network nodes and services through ping and trace route operations. At regular intervals, the collected metrics are sent to the Cloudmon Controller. |
| Installation methods |
The Agent can be installed on Linux, Windows, or macOS servers. |
For unified monitoring of network endpoints from multiple sites, Probes can be installed on a Linux server at the required sites and configured to report to the Cloudmon Controller. |
| Connectivity to the internet |
All Agents require connectivity to the Cloudmon Controller. If the Controller is deployed in the public cloud or externally, Agents can send data to the Cloudmon Controller through a proxy server connected to the internet. |
Satisfactory collection of server metrics by the on-premise Probe does not require internet access, but the Cloudmon Probe must have connectivity to the Cloudmon Controller. |
| Data transfer to Cloudmon |
A one-way HTTPS connection sends data to the Cloudmon Controller using the secure SSL protocol. |
Uses an HTTPS connection to send data to the Cloudmon Controller. |
| Supported devices |
Windows, Linux, and macOS servers. |
For SNMP/WMI polling: any device that supports SNMP/WMI protocol. For IP endpoint monitoring: any device that supports ICMP/TCP protocol. |
| Credentials |
Administrative credentials are required for installation. |
Requires SNMP credential details. Supported versions: SNMP v1/v2 and SNMP v3. For monitoring Windows devices through WMI: requires a Domain User with Admin Rights (if the device is in a domain) or a Local Admin Account (if the device is in a workgroup). |
| License |
Licensing is based on the number of IP addresses. |
Licensing is based on the number of endpoints. |
| High-frequency resource monitoring |
Agents have a poll frequency of up to one second to collect performance metrics, providing detailed insights into the performance of critical devices. |
For SNMP/Ping/WMI polling, performs up to a one-minute polling frequency to collect performance metrics. |
| Automatic remediation |
Yes – incident remediation can be performed through configured scripts that are executed automatically based on alerts. |
No – incident remediation through configured scripts cannot be performed directly on network devices or endpoints. |
| Liveness |
Detects device downtimes and restarts within 25 seconds, ensuring availability data is updated instantly. |
Not supported. |
| Alerting |
Alerts can be triggered for all monitored performance metrics and reported to users. |
Alerts can be triggered for all monitored performance metrics and reported to users. |
| Performance reports |
Reports can be generated based on the available templates. |
Reports can be generated based on the available templates. |
| Monitors supported |
Through Agents – Hyper-V monitoring, Docker monitoring, Database Monitoring, and DEM (Digital Experience Monitoring) can be achieved. |
Through Agentless – Automatic Network Discovery, Automatic Topology Discovery, IP Address Management, Switch Port Mapper, Wireless Device Monitoring, Network Configuration Management, and Windows Application Monitoring can be achieved. |
| Multi-site monitoring |
Agents must be installed on individual servers to monitor each device. |
Probes can be deployed at each site to monitor all network devices and endpoints at that location, and report to the Cloudmon Controller. |