In medium and large environments, the ControlUp Real-Time Console administrator can optimize the performance of the console and the monitor.
Here are a few optimizations that can be applied, according to your needs (displayed in the table and detailed blow)
1. Disable Process-level dependent Views
By default, the console offers 9 different views: Folders, Hosts, Machines, Sessions, Processes, Accounts, Applications, Storage and NetScalers.
In large environments, the Processes view may cause high resource consumption during the operation of the console, mainly due to the high total number of processes the console monitors (summary of all processes running on all monitored resources).
In such cases, it is advised to disable the flat views and still monitor the processes by drilling down:
Machine > Session > Processes or Machines > Processes, as shown in the below screenshots.
In order to disable the "Process-level views" go to Settings > Advanced as displayed in the following screenshot.
Once you disable the “Process-level views” those tabs will be grayed out: Processes, Accounts and Applications.
2. Increase the Data Collection Cycle
By default, all ControlUp Agents push information updates to the console every 3 seconds.
The update interval can be configured by the ControlUp Admin, so the ControlUp Console will pull the information from the agents in set intervals. In addition, you can set the number of computers the console connects to concurrently.
To increase the data collection cycle and change the updates intervals go to Settings > Advanced as shown in the screenshot below.
To update ControlUp Monitor’s intervals go to Monitor Settings.
The first 2 optimizations can be configured via GPO for all console users, click here for more details about UI management via GPO.
3. Setting up a dedicated Data Collector
Note: This configuration is crucial to prevent severe performance implications.
Install agent 4.5 MSI, and assign it as a data collector.
By default, every Console and Monitor connects to the hypervisors or to the XenDekstop brokers.
In large environments where multiple consoles and monitors are running, the best practice is to create a relay or a data collector so you have a single point of hypervisor\XD data collection.
Define a data collector:
- Right-click on the Hypervisor\XD and choose Connection Settings
- Go to Connection Options
- Remove the Console / Monitor and choose one of the agents to be the data collector by clicking "Add..."
- Now CUMONITOR01 will collect the data and all Consoles and Monitors will connect to that agent to retrieve hypervisor performance data (remember to remove the console\monitor as the data collector).
- Here is a screenshot of the XenDesktop connection properties and where to change the data collector.
4. Optimize Auto Connection Settings
You can have the console automatically connect to disconnected computers. Once a computer gets disconnected for any reason, the console will try to contact that endpoint.
To enable this feature: As seen in the below screenshot, under the organization tree, check the "Show Auto-Connect State" and check the computers you would like ControlUp to automatically connect to.
This feature will also enable the console’s automatic connection immediately upon launching the console.
The reconnect interval time can be configured by the ControlUp Admin.
To define the interval go to Settings > Agent Settings as displayed in the following screenshot.
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.
To exclude any resource right click it and choose properties and then "Exclude from ControUp Monitor"=Yes.
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.
In order to disable the incidents collection and free up console resource consumption, open regedit.exe on the machine running the Console and go to - HKCU\Software\Smart-X\ControlUp\Console and create a DWORD with Value name DisableIncidents, with value data = 1
That will disable the incidents collection and optimize the performance.
7. Change the search options to Name Only
By default, the search will be done in the search field, in all fields.
Change the default search option to Name only, which will decrease the resources the console uses because the search is filtered just to the Name column.
These settings can be managed and enforced for all console users via GPO, click here for more details.
8. Uncheck the "Deploy agents automatically"
By default, the "Deploy agents automatically" is checked in the Agent Settings.
By unchecking that option, you take control of 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 added multiple machines to the folder tree that doesn'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.