ControlUp Real-Time Console
ControlUp's main executable file can be downloaded as ControlupConsole.exe. For Hybrid Cloud versions, this component does not require any installation as it is a portable executable.
For on-premises environments, the Real-Time Console must be installed separately.
The ControlUp Real-Time Console is typically used by system administrators or support technicians. When using our Hybrid Cloud solution, it is mandatory for every ControlUp user to create an online account. This account is used for logging in to ControlUp's configuration servers.
In on-premises environments, you don't need to create an online account as it takes the AD accounts.
A Windows or Linux machine that a ControlUp user wants to manage or monitor. When you first install the ControlUp Agent on a Windows machine that machine will be assigned to your ControlUp organization.
The Real-Time Console and the ControlUp Monitor must be able to resolve the fully qualified domain name (FQDN). If you want to monitor a Windows-based machine, .NET Framework 4.5 or 4.7.2 (for ControlUp version 8.6) must be installed. For Linux machines, refer to the following article.
A lightweight executable named cuAgent.exe that runs as a system service on every managed machine. This component provides performance information and handles the execution of management actions.
A logical group of managed computers handled by the same organization. A ControlUp user selects an organization during login and is restricted to managing computers that belong to the selected ControlUp organization only.
A Windows service that operates in a way similar to the ControlUp Real-Time Console but without the graphical user interface. The ControlUp Monitor connects to all of the computers in your organization and performs continuous monitoring and reporting of incidents as well as automatic exporting of data tables for historical reporting. If you require 24/7 monitoring and alerting about incidents in your environment, it is recommended that you install at least one instance of the ControlUp Monitor. Two Monitor services can be installed and will operate as an active-passive high-availability cluster in case of failover.
A reporting and analytics platform that displays historical reports using data gathered by ControlUp. In order to start using ControlUp Insights, at least one instance of ControlUp Monitor should be installed in an organization.
In ControlUp, an incident is an occurrence on one of your managed computers that falls under the scope of one of the configured incident triggers. For example, you might configure a “Process Ended” incident trigger with a filter of “Process name=svchost.exe”. Every subsequent crash or error exit of a process with this name will generate an incident. Incidents are recorded in the ControlUp Hybrid Cloud services database and are available for display in the Incidents Pane of ControlUp.
A definition of an occurrence that should be recorded as an incident. Triggers of two types are supported in ControlUp: community triggers are created by ControlUp based on vendor recommendations and industry best practices, and user-defined triggers which can be configured according to your needs. Each trigger includes a set of conditions: trigger type (Stress Level, Process Started, etc.), filter (specific conditions like computer name or operating system), scope (folders and schedule – when and where the trigger applies). In addition, every trigger may include a set of follow-up actions, for example an email alert.
Script-Based Action (SBA) or Script Actions
A PowerShell, VBScript, or batch script, which was imported to ControlUp as a management action. Script-based actions (SBAs) can be assigned to any of ControlUp’s managed resources (folders, computers, sessions, etc.). You can download SBAs from the community repository or you can create your own SBAs and manually add and shared them within your ControlUp organization.
The connection parameters needed for a Real-Time Console or data collection agent to connect with a supported hypervisor management platform (vCenter, Nutanix, Hyper-V, or XenServer pool master). After the connection to the hypervisor management platform, host and VM information is automatically retrieved and populates the ControlUp database. (If the connection is to vCenter, datacenter and cluster information is also gathered, for better organization of virtualization resources.)
Citrix Virtual Apps and Desktops (CVAD) Connection
An object in the ControlUp Organization tree that contains the details necessary for ControlUp to collect data from a single CVAD site. Once configured and connected, it enables for populating the Sessions and Computers views with information retrieved from CVAD brokers.
With ControlUp, you can monitor and manage your AWS or Azure cloud environment easily from the Real-Time Console or Solve. Performance metrics and cost metrics are displayed with a great level of granularity, all live and in real time.
An object in the organization tree that contains the details necessary for ControlUp to collect data from a single NetScaler appliance. Once configured and connected, it populates the Load Balancers, Services, Service Groups, Gateways, HDX sessions and NICs views with data retrieved from the NetScaler API.
Similar to a regular folder, but intended to organize hypervisor connections.
The term ControlUp uses to refer to the connection points to the virtualization world, namely vCenter and the Xen pool master. Although the vCenter server is technically not a hypervisor, ControlUp refers to it as one for consistency's sake.
A computer running VMware ESX/ESXi, Hyper-V, Nutanix AHV, or Citrix Hypervisor (XenServer) that ControlUp accesses via the Hypervisor connection. The virtualization hosts are the computers that run multiple virtual machines on them.
Virtual Machines that run as guests on ESXi/Citrix Hypervisor hosts. If the guest VM is running a supported version of Windows, then the ControlUp Agent can be installed on it and it will become a fully managed computer by ControlUp. There are some performance statistics that can be gathered about all VMs, managed or not, because ControlUp queries the hypervisor about all of them. However, full data retrieval is only possible if there is a ControlUp Agent installed on the guest OS.