Performance Optimization for Real-Time Console & Monitor
  • Dark
    Light
  • PDF

Performance Optimization for Real-Time Console & Monitor

  • Dark
    Light
  • PDF

Introduction

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.

Below is a table describing the optimization and the ControlUp components affected:

Optimization Name

Real-Time Console

ControlUp Monitor

Disable Process Flat Views

 

Increase Data Collection Interval

Dedicated Data Collectors

Optimize Auto Connection Settings

✓ 

Exclude Folders From Monitor

 

Disable Console Incidents Processing

 

Change Search

 

Deploy Agents Automatically

✓ 

1. Disable Process-Level Dependent Views

By default, the console has 9 different views: Folders, Hosts, Machines, Sessions, Processes, Accounts, Applications, Storage and Application Delivery Controllers.

A high number of processes displayed by the Processes view may cause high resource consumption in large environments (summary of all processes running on all monitored resources).

We recommend disabling the Processes tab in such cases. Double-clicking any user session or machine, even when the tab is grayed out, will take you to Processes.

To disable process-level views, go to Settings > Advanced, check the Disable views that depend on process-level information checkbox.

The Processes tab will be grayed out once you disable the "Process-level views".

2. Increase the Data Collection Interval

By default, the console refreshes real-time metrics every three seconds. These metrics are coming from the ControlUp Agents.

There are several ways to configure the data collection interval:

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. Once 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, you can set the data collection interval in the registry on your machine where the ControlUp Agent is installed.

Path: HKEY_LOCAL_MACHINE\Software\Smart-X\ControlUp\Agent
Key: ProcessesCollectionInterval (DWORD)
Possible Values: Any value in seconds

4. Use our GPO templates that apply to all console users. Click here for more details on UI management via the 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.

The console machine is the default data collector when you set up a Hypervisor connection. Imagine 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, refer to this article.

4. Optimize Auto Connection Settings

Connecting to managed machines from the Console can be automated by using the "Show auto-connect state" checkbox. You can define machines that you want to automatically connect to, either when the Console is started or/and after a specific time interval that you need to define in the Agent settings. 

You can find the Show auto-connect state checkbox under the ControlUp organization tree. Once you click this checkbox, you can define folders or machines that you want to automatically connect to:

To configure a reconnect interval, go to Settings > Agent Settings and configure a value (in minutes) under Reconnect to machines automatically every.

In large environments, if all computers are set to auto-connect this may extend the console launch process, mark 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 will not 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, 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 and add the following registry key:

Path: HKEY_CURRENT_USER\SOFTWARE\Smart-X\ControlUp\Console
Key: DisableIncidents (REG_DWORD)
Value to disable incidents: 1

7. Change the Search Options to Name Only

In the search field, all fields will be searched by default. 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, click here.


8. Uncheck "Deploy agents automatically"

By default, the "Deploy agents automatically" checkbox is checked in the Agent Settings.

By unchecking 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.

The Monitor is also affected by this Checkbox, when checked, the monitor will try to connect to all machines in the folder tree (besides those who were excluded), which will cause high resource consumption.

Note
If you added multiple machines to the folder tree that don't have agents installed, the monitor might crash if the "Deploy agents automatically" is checked.

Only enable that option if you fully deployed the agents via MSI or Installed Agent Mode.

We recommend disabling Automatic Agent Deployment for VDI customers with more than 1000 computers.


Was this article helpful?