Performance Optimization for Real-Time Console & Monitor
For each ControlUp user, a well-performing ControlUp Monitor and ControlUp Real-Time Console are essential. The following article explains how to optimize ControlUp settings to avoid performance issues.
The table below describes the optimization settings and the ControlUp components affected:
1. Disable Process-Level Dependent Views
By default, the console has nine different views: Folders, Hosts, Machines, Sessions, Processes, Accounts, Applications, Storage and Application Delivery Controllers.
A high number of total processes running on all monitored resources displayed by the Processes view may cause high resource consumption in large environments.
If you experience such a case, we recommend disabling the Processes tab. You can double-click any user session or machine, even when the tab is grayed out, to view Processes.
To disable process-level views, go to Settings > Advanced and select the Disable views that depend on process-level information checkbox.
2. Increase the Data Collection Interval
By default, the console refreshes real-time metrics every three seconds with metrics received from the ControlUp Agents.
You can configure the data collection interval in several ways:
1. In the console, go to Settings > Advanced. Here you can modify the data collection interval for windows machines (agent-based collection) or Linux machines (agentless data collection).
2. To update the collection intervals of the monitors, go to Monitor Status > Monitor Settings > Advanced Settings. After you check the Regulate information updates, you can configure the collection intervals of your Agents under Initiate agent based data collection cycle.
3. From version 8.6.5 and later, you can set the data collection interval on your machines with the ControlUp Agent installed by using the following registry setting:
Possible Data Values:
Any integer in seconds
4. Use our GPO templates that apply to all console users. For more details on UI management via the group policy, see Locking UI with Group Policy.
3. Set Up a Dedicated Data Collector
A data collector is a machine that collects data from various components, such as Hypervisors or EUC environments. We recommend using a dedicated data collector to reduce the performance overhead.
When you set up a Hypervisor connection, the console machine is the default data collector. For example, in a large organization with hundreds of consoles connected to hypervisor endpoints, this would greatly impact performance. You can greatly reduce the number of connections to external resources by setting up a dedicated data collector.
To learn more about data collectors, see ControlUp Data Collector.
4. Optimize Auto Connection Settings
You can automate connecting to managed machines from the console by selecting the Show auto-connect state checkbox under the ControlUp organization tree. You can define machines that you want to automatically connect to, either when the console is started and/or after a specific time interval that you need to define in the Agent Settings.
To configure a reconnect interval, go to Settings > Agent Settings and configure a value (in minutes) under Reconnect to machines automatically every.
If all computers are set to automatically connect in large environments, this may extend the console launch process. Select only important servers or folders to automatically connect.
5. Excluding folders from the Monitor
By default, all folders, hypervisors, and computers are monitored. You can reduce the monitored resources in order to optimize monitor performance.
Right-click a resource in the organization tree, such as a machine, folder or a Hypervisor extension and select Properties. In the Properties window, under Exclude from ControlUp Monitor, change the value accordingly:
- Yes. The monitors won't collect data from this resource.
- No. The monitors will collect data from this resource.
- Inherit. Inherits the configuration from the root folder.
From version 8.6.5 and later, you can check which resources are monitored by using the Invoke-CUQuery cmdlet.
6. Disable Console Incidents Processing
Once you add a monitor, it is responsible for all your incident collection and trigger alert notifications. The Console also processes and collects all incidents in parallel to the monitor when running.
To disable the incidents collection and free up console resources, open regedit.exe on the machine running the console by using the following registry setting:
Possible Data Value:
7. Change the Search Options to Name Only
By default, all fields are searched in the search field. By changing the default search option to Name only, the console will use fewer resources since the search is only filtered to the Name column.
You can configure this search behavior in our GPO template. Go to ControlUp > Console > Advanced Settings and configure the Search box behavior settings. To learn more about configuring the console UI with group policies, see here.
8. Uncheck "Deploy agents automatically"
By default, the Deploy agents automatically checkbox is selected in Agent Deployment Settings.
By unselecting that option, you take control of the agent deployment. Otherwise, when the console attempts to connect to a monitored computer or endpoint and fails, it will attempt agent deployment. In large environments that may cause degradation in Console performance, try to deploy the agent in the background to all agents which are not connected.
If the checkbox is selected, the monitor will try to connect to all machines in the folder tree (besides those who were excluded), which will cause high resource consumption.
We recommend disabling Automatic Agent Deployment for VDI customers with more than 1000 computers.