A: 


1) RDP to the VM

2) Look into Windows Services and ensure that a CloudMonix Agent service is running.  If it is not present you will want to install it.  Latest agent can always be downloaded from CloudMonix dashboard screens.  If it is not running, you will want to start the service and figure out who stopped the service, it should be turned on 24/7

3) If the service is running, next step for debugging is looking into Application Event logs that relate to CloudMonix agent.  Here are the possibilities are numerous. It is best to email CloudMonix support @ support@cloudmonix.com with latest event log entries, if the error messages do not make sense.


 The most popular issues we've seen so far are:

    a) Time clock on the VM is not accurate.  There are issues with SSL connectivity as well as with the agent, if VM's time is off even by a few minutes.

    b) Your VM is blocking agent's requests send data home via some sort of outbound firewall.  Please configure your outbound firewall to allow Agents to connect outside to CloudMonix's static IP addresses: https://support.cloudmonix.com/support/solutions/articles/5000598221  (look for bottom section IP addresses)

    c) There is an issue with your DNs servers that VM is using and it is not able to resolve CloudMonix's or Azure domain names

    d) You've installed the pre-configured agent from a different CloudMonix account.  Validate that the correct agent is installed, by looking at the configuration files for installed agent and compare them to your Account Information screen in CloudMonix.  Do the Account ID and Agent Key match?

    e) It is possible in very rare circumanses that CloudMonix agent crashed by itself.  Try restarting the CloudMonix windows service on the impacted VM.  Is the data coming through within a few minutes on CloudMonix dashboards?  If so, please send the Application Event logs with CloudMonix-relevant entries to support@paraleap.com for further investigation