What to consider before deploying Cloudmon, and where to find the detailed hardware and network specifications for your environment.
Cloudmon can be deployed on physical or virtual servers, whether on-premises or in the cloud. Before deploying, it is important to ensure that the servers hosting each component meet or exceed the recommended specifications for your environment size. Deploying on underpowered hardware is one of the most common causes of performance issues and can affect data collection reliability, dashboard responsiveness, and alarm delivery.
The detailed hardware, OS, and network specifications for each component and deployment size are maintained on the official system requirements page. Always refer to that page before beginning a new deployment, as requirements are updated when new versions of Cloudmon are released. For deployments larger than 5,000 nodes or for high availability configurations, contact sales@cloudmon.ai before proceeding.
The published specifications reflect a default configuration. Significantly increasing the number of monitors or the frequency of data collection adds extra load on both the Controller and Database servers. Storage needs also grow with longer data retention periods, higher debug logging verbosity, and larger overall data volumes. When in doubt, size up.
The Controller and Database are the core of every Cloudmon deployment. The Controller handles all data processing, the web interface, and communication with Probes and Agents. The Database stores all collected metrics, events, and configuration data and runs on MongoDB 7.0. Both components require Ubuntu 24.04 LTS and must be NTP synchronised. The Database can be installed on the same server as the Controller for smaller deployments if needed, though separating them is recommended as the environment grows.
The Controller requires specific inbound and outbound port access, as well as internet connectivity to Cloudmon's software repository and geolocation service. Ensuring these network paths are open before installation avoids the most common setup failures. Full port and URL requirements are listed on the official system requirements page.
Probes are distributed collection points deployed at each monitored network location. Because they handle SNMP polling, NetFlow ingestion, Syslog collection, and SNMP Trap reception simultaneously, they need adequate CPU and storage to process data at the collection intervals configured in your monitoring profiles. Probes require Ubuntu 24.04 LTS. Note that a Windows-based probe supports WMI monitoring only and cannot perform the full range of probe functions.
Agents are designed to be lightweight and run on a wide range of endpoints. They have minimal hardware requirements and are supported on Windows, Windows Server, and major Linux distributions including Ubuntu, Fedora, CentOS, Red Hat, and SUSE, as well as macOS and Android. Time synchronisation between each agent and the Controller server is required for accurate data collection and alarm timestamps.
