Confirm access, credentials, and connectivity for every monitoring component before configuring it in Cloudmon.
Before onboarding a device or feature into Cloudmon, certain prerequisites must be in place to ensure successful monitoring. This article lists the required access, credentials, and connectivity for each monitoring component, along with a quick validation step that can be run to confirm readiness before configuring it in Cloudmon.
| Component | Prerequisite | Validation |
| Physical Servers (Agent-based) | Remote access (RDP/SSH) to the server with admin/root credentials. Elevated privileges are required to install the Cloudmon agent. | Confirm RDP/SSH connectivity and verify the ability to execute installation commands. |
| End-User Devices | Remote access to end-user devices with elevated privileges required to install the Cloudmon agent. | Verify remote access and confirm installation permissions. |
| Hyper-V Native Integration | Server access with elevated privileges to install the agent. | Confirm RDP connectivity and verify agent installation capability. |
| Microsoft Applications (WMI) | Windows Server domain credentials. Network connectivity from the Cloudmon Windows Probe to the target systems. | Execute Get-WmiObject from the Cloudmon Windows Probe to query WMI objects on the target and confirm a successful response. |
| VMware Native Integration | VMware vCenter/ESXi read-only credentials. MOB access enabled. Network connectivity from the Cloudmon Probe to vCenter. | From the Cloudmon Probe, run: curl -k -u '<user>:<pass>' https://<vcenter-ip>/sdk. A valid XML response confirms API access. |
| Network Devices (SNMP) | IP/Hostname of each device. SNMP v1/v2c/v3 credentials. Connectivity from the Cloudmon Probe. | Run: snmpwalk -v2c -c <community> <IP> from the Cloudmon Probe. |
| Azure Native Integration | Azure credentials → Tenant ID, Client ID, and Client Secret Key. Connectivity from the Cloudmon Probe. | — |
| AWS Native Integration | AWS credentials → Access Key ID and Secret Access Key. Connectivity from the Cloudmon Probe. | — |
| Oracle Database Monitoring | A dedicated Oracle monitoring user with SELECT_CATALOG_ROLE and CREATE SESSION privileges. Cloudmon agent installed on the DB host or a remote host with DB connectivity. Firewall access on port 1521. | Confirm listener and database reachability from the agent host. |
| MySQL Monitoring | A dedicated MySQL user with REPLICATION CLIENT, REPLICATION SLAVE, PROCESS, SHOW DATABASES, and SELECT on performance_schema privileges. Database reachable from the agent host. | Confirm database connectivity from the agent host. |
| Component | Prerequisite | Validation |
| Node Availability Monitoring | IP/Hostname of the node. ICMP connectivity from the Cloudmon Probe. | Run ping <IP> from the Cloudmon Probe. |
| Service Availability Monitoring | IP/Hostname and port number. TCP connectivity from the Cloudmon Probe. | Run curl http://<IP>:<port> or telnet <IP> <port> from the Probe. |
| Website Availability Monitoring | URL of the website to be monitored. HTTP/HTTPS connectivity from the Cloudmon Probe. | Run curl -I <website-URL> from the Cloudmon Probe and verify the HTTP response code. |
| Component | Prerequisite | Validation |
| NCM | SSH or Telnet credentials for each network device. The device must be onboarded into Cloudmon. Connectivity from the Cloudmon Probe. Note: Config restore via SFTP/TFTP is not included in this implementation scope. | Test SSH/Telnet login from the Probe using ssh <user>@<IP> or telnet <IP>. |
| Component | Prerequisite | Validation |
| Syslog | Network devices must forward Syslog messages to UDP/514 on the Cloudmon Probe. The source IP must match the monitored device's IP in Cloudmon. | On the Cloudmon Probe, run sudo tcpdump -i any port 514 and verify log entries appear in the Cloudmon UI. |
| SNMP Trap | Network devices must forward SNMP Traps to UDP/162 on the Cloudmon Probe. The source IP must match the monitored device. | On the Cloudmon Probe, run sudo tcpdump -i any port 162 or verify traps are received in Cloudmon logs. |
| Component | Prerequisite | Validation |
| Windows Event Logs | Remote access (RDP) to target devices with admin credentials. Elevated privileges are required to install the Cloudmon agent. | Confirm RDP connectivity and verify installation permissions. |
| Component | Prerequisite | Validation |
| DEM (Agent-based) | Remote access to end-user devices with elevated privileges to install the Cloudmon DEM agent. | Confirm end-user system reachability and verify agent installation permissions. |
| Component | Prerequisite | Validation |
| SPM | SNMP credentials (v1/v2c/v3) for target switches. IP/Hostname of each switch. UDP/161 connectivity from the Cloudmon Probe. | Run snmpwalk -v2c -c <community> <switch-IP> from the Cloudmon Probe and verify SNMP OID values in the response. |
| Component | Prerequisite | Validation |
| IPAM | Subnet and IP range details for monitored subnets. ICMP and SNMP access enabled from the Cloudmon Probe. | Run ping <target-IP> from the Cloudmon Probe to confirm basic network connectivity. |
| Component | Prerequisite | Validation |
| NTM | Network devices must forward NetFlow v5/v9 or IPFIX traffic to UDP/2055 on the Cloudmon Probe. The source IP must match the monitored device. | Run sudo tcpdump -i any port 2055 from the Cloudmon Probe to confirm flow data is being received. |