Cloudmon Setup Reference Guide

Cloudmon Unified IT Observability. Installation, onboarding and configuration: a working reference for Cloudmon deployments.

Introduction

This guide is published by the Cloudmon team to support the deployment, configuration and handover of Cloudmon solutions in a consistent and successful manner. It provides a structured implementation workflow that covers the complete deployment lifecycle starting from pre-deployment planning and prerequisite validation through platform installation, device onboarding, monitoring configuration, cloud integration, and post-deployment verification.

For new deployments, Cloudmon recommends completing the implementation activities in the order presented to ensure all prerequisites and dependencies are addressed before proceeding to subsequent stages. For existing or partially completed deployments, navigate directly to the relevant section based on the implementation phase or operational requirement.

This guide is intended to complement the Cloudmon Knowledge Base and other official product documentation, providing a practical deployment reference while ensuring that version-specific technical information remains centrally maintained and up to date.

Support Portal: support.cloudmon.ai  |  Support: support@cloudmon.ai  |  Pre-Sales: presales@cloudmon.ai

Solution Capabilities

Workflow Overview

Step 1: Before You Begin, Prerequisites

Confirm the following before opening a terminal window:

• Sizing and OS support. Verify the currently supported operating systems and hardware sizing for the Controller, Database, and Probe components in the target environment.
• Network access. Confirm firewall rules between the Controller, Database, Probe, and every device or agent to be monitored. The complete port-by-port list is maintained centrally and always reflects the current release.
• Credentials in hand. Gather administrative access to the servers being installed on, along with read-only service accounts for the devices to be monitored (SNMP community or v3 credentials, hypervisor API account, database account, Windows remoting access, and similar, depending on device type).

Learn more: Cloudmon System Requirements  |  Cloudmon Communication Matrix (full port list)  |  Deployment Models

Step 2: Install the Platform

2.1 Controller and Database

Provision the Controller and Database on a supported Linux host and run the guided installer. The installation guide walks through each prompt end to end and is updated in step with every release, so follow it rather than improvising.

Learn more: Cloudmon Installation Guide  |  Installation script: Cloudmon Installation Script and How to use it

Verify the Controller and Database. Run these on the Controller host before moving on to the Probe.

Expected: mongod reports Active: active (running). cloudmon-controller@* shows every sub-service running: controller, poller, agent manager, data engine and data aggregator.

If a service is not running:

Logs: Controller logs are written to /var/log/cloudmon/server/. Connection failures and port errors land there. Controller settings live in /usr/local/cloudmon/server/.env.

Note: a mismatch between the database credentials passed to the installer and those configured in .env causes the web UI to return 502. Confirm the UI loads before continuing. See also What steps can be taken to debug frequent server crashes with a 502 bad gateway error in Cloudmon?

2.2 Probe

Install a Probe on each network segment that holds devices to be monitored. The Probe performs local polling and reports back to the Controller; register it to the Controller as the final step of installation.

Learn more: Installation Guide for Cloudmon Probe

Verify the Probe. Run these on the Probe host, then confirm the Probe has registered in the portal.

Expected: each listed unit reports Active: active (running).

Confirm registration in the portal. Log in to the Controller web interface and navigate to Settings > Monitoring > Probes. The Probe should appear in the list with its current version. This is also where the Probe is upgraded.

Logs: Probe logs are written to /var/log/cloudmon/probe/ and collector logs to /var/log/cloudmon/collector/.

2.3 Agent

Where endpoint monitoring is required, install the Cloudmon Agent on the target Windows or Linux systems. The Agent enables operating system and application monitoring, process and service monitoring, log collection, event monitoring, and other agent-based capabilities that are not available through agentless monitoring.

Before deploying the Agent at scale, validate connectivity between the Agent and the Controller, confirm the required communication ports are accessible, and verify that the Agent is successfully reporting to the Controller.

Learn more: Installation Guide for Cloudmon Agent  |  Agent vs Agentless Monitoring, decision guide

Verify the Agent (Linux):

Expected: Active: active (running). The agent log at /var/log/cloudmon/agent/agent.log should show no connection errors.

Verify the Agent (Windows). Open Task Manager and select the Services tab, or run the command below in an elevated PowerShell prompt. The service is named cloudmon-agent.

Expected: Status reports Running. Windows agent logs are written to C:\Program Files (x86)\Cloudmon\logs.

Confirm registration in the portal. Navigate to Settings > Monitoring > Agents in the Controller web interface. The agent should appear with its current version within a few minutes of installation. If it does not, check the agent log, confirm the Controller URL is correct, and verify the required outbound port is open.

2.4 Verify the Install

Once installation completes, confirm that services are running and check the Agent and Probe logs to ensure data is flowing before moving on. If anything fails during installation, the installation log location is the first place to check.

End-to-end service check. Run this on each host after all components are installed. It enumerates whatever Cloudmon units are actually present, so it is safe to run on the Controller, a Probe or an Agent host alike.

Expected: every unit reports active (running); no unit is in failed or activating state. NGINX reports 1.25 or above. The Cloudmon login page loads in a browser at http://<controller-ip>. If you see the default "Welcome to nginx" page instead, see the troubleshooting table in Step 6.

Where the logs are:

Note: the installation log path is also printed on screen during installation. Collect the log matching the component that failed before raising a support ticket.

Learn more: Where to Find Installation Logs

Step 3: Onboard Your First Devices

Run device discovery (or add devices manually) and decide, per device type, whether to monitor agent-based or agentless:

• Network devices (routers, switches, APs, WLCs). Agentless via SNMP polling; add SNMP traps for event-driven alerts in addition to polling.
• Virtualization (VMware / Hyper-V, Nutanix). A read-only API account against the hypervisor management interface provides host, VM, and datastore visibility.
• Databases (Oracle / MySQL). A dedicated read-only database account for query, connection, and replication metrics.
• End-user experience (DEM). A lightweight agent on end-user devices for real experience metrics.

Work through the full onboarding checklist for anything you do not want to miss. It covers availability monitoring end to end and is the single best reference during a rollout.

Learn more: Device Onboarding Checklist

Step 4: Configure Alerting and Access

• Alarm rules. Set thresholds and event triggers so the right people are notified when something breaks.
• Notifiers. Connect email, SMS, Slack, or Teams so alerts reach the right team where they already work.
• Log rules. Filter, tag, and alert on syslog data flowing into the log analyser.
• Users and access. Set up role-based access so each team sees only what they should.

Learn more: Third-party Integration with Cloudmon  |  Alarms User Guide

Step 5: Extend Coverage, Cloud and Integrations

Once core infrastructure is onboarded, connect cloud accounts (AWS, Azure, GCP, OCI) using a read-only integration for visibility across hybrid and multi-cloud environments.

Learn more: Cloud Monitoring User Guide

Step 6: Validate and Troubleshoot

Most first-deployment issues fall into a handful of buckets. Check these before opening a support ticket:

Full troubleshooting index: support.cloudmon.ai knowledge base

Getting Help

• Knowledge base and support tickets: support.cloudmon.ai
• General support: support@cloudmon.ai
• Pre-sales / POC validation sign-off: presales@cloudmon.ai
• License allocation: sales@cloudmon.ai