Adding a ControlUp Monitor

In this step of the Getting Started tutorial, you will see how to add a monitor to your ControlUp setup. 

A monitor is a Windows service requiring no user interaction, and enables continuous monitoring of your resources. It is recommended to run the ControlUp Real-Time Console and the ControlUp Monitor on two separate servers. By adding a monitor you benefit from the ControlUp Insights historical reporting module. (Learn how to login to ControlUp Insights in the next step.)

If you prefer, you can add an automatic backup for your monitor by adding a second monitor to your organization. If you add a second monitor, the two monitors will automatically operate as an active/passive high-availability (HA) pair, helping to prevent any potential loss of data due to unscheduled reboots or downtime.

Large organizations with more than 5,000 monitored resources or multiple sites require multiple monitors, with at least one monitor deployed at each site. You can add as many monitors to your organization as necessary, and they will automatically be configured to work together as a cluster.

For more information about the ControlUp Monitor, see ControlUp Monitor and Introduction to ControlUp v8.1.

If you encounter a connection issue between the monitor and the ControlUp server, see Missing Data In Insights.

See the following video to learn how to add a monitor or see below for step-by-step instructions:

To add a monitor:

  1. Select a computer or virtual machine that is correctly sized for your needs and your environment, and that can be dedicated exclusively running the ControlUp Monitor service. 
  2. Click Add Monitor in the Home Ribbon, and the Sites and Monitors - Configuration Wizard popup appears.
  3. Select the Computer from the list that you wish to deploy the Monitor Service to. 
  4. The Monitor installation Wizard tests various components of the target machine before deploying the service to ensure that it is running as designed.
  5. Click Next, and  console will push the binaries to the machine, and, once complete, the ControlUp Monitor Installation Wizard confirms that the monitor is installed. Once installed the ControlUp Monitor Configuration Wizard begins to collect the monitor credentials and settings.
  6. From the Domain Identity tab, select Save new credential set, and enter you User, Password, Domain, and Friendly Name, and click OK, and the Login Mode tab appears.
    IMPORTANT: It should be noted that:
    1. The monitor service runs on the monitor server as the 'NETWORK SERVICE' user. 
    2. The domain credential is the account that the monitor uses to connect to and communicate with the active directory resources (i.e. the agents installed in your environment).
    3. The connection credential is the credential that the monitor (and ,if configured as a Shared Credential, your users) use to connect to the console connections, such as a hypervisor, NetScaler, AWS, or XenDesktop Site. 
  7. Once your credentials are defined, the console asks for a login mode. Generally speaking, unless you have a specific reason, you should leave it as default. Click Next, and the Proxy Settings tab appears.
  8. Configure any Proxy settings if required. See this article for more details information about communication to back-end systems used by ControlUp. Click Next, and the Export Schedule tab appears.
  9. Configure the export schedule export schedule (optional) See here for more information. Click Next, and the SMTP Settings tab appears,
  10. Configure SMTP settings for trigger alerts (optional). Click Next, and the Advanced Settings tab appears.
  11. Configure regulating information updates. For environments with less than 1500 licenses, you can leave this default. See the ControlUp Optimization Guide for recommendations on this setting. 
    Click Next, and the Login Tab appears while the wizard configures the monitor.

    Once complete, the wizard closes and the Summary tab of the Monitor Settings page appears.
  12. Check the Resources Connected to make sure that your monitor is properly configured  to communicate with the configured objects in your environment. 
Powered by Zendesk