Optimize performance and robustness from the textual UI
In Cortex XSOAR 8.10 On-prem, optimize system performance from the textual UI.
Once Cortex XSOAR is installed, you can perform system performance optimization tasks from the textual UI, for example:
Set up an external load balancer.
Add or remove nodes from a cluster.
Scale up hardware resources.
How to access the textual UI menu
To access the textual UI menu, log in from the VM web console or from an external terminal using the ssh admin@<server ip address> command to SSH log in.
Important
If you lose the SSH password, you cannot recover or change it. To use SSH you will need to redeploy the VM.
For example:

The textual UI menu opens with all the configuration and maintenance options.
Tip
To start using the textual UI, click anywhere on the screen.
To navigate between the menu items, use the up and down arrow keys. To select a menu item, press the Enter key.
To navigate between fields within a menu item, use the Tab key. To save settings, tab to the Save button and press the Enter key.
To go back to the menu from a specific menu item field, press the esc key.
Scale up hardware resources
The Scale Settings textual UI menu item enables scaling up resources for CPU, memory, and disk size. Before modifying your environment, it is critical to distinguish between scaling up deployment size and extending storage, as the procedures and downtime expectations differ.
Scaling up deployment size
Scaling up deployment size (CPU & RAM) refers to increasing the CPU cores and RAM to move between scale tiers (for example, Extra-Small → Small → Medium). While Cortex XSOAR allows for scaling, the necessary changes at the hypervisor level (for example, ESXi) often require the VM to be shut down to increase CPU and RAM. Downtime depends entirely on your hypervisor configuration.
To scale up the deployment size, first increase the resources on the hypervisor, and then use the Scan scale options in the textual UI.
Extending storage (disk capacity)
Extending storage refers to increasing the data disk capacity of existing nodes to accommodate data growth. For most hypervisors (such as VMware), storage can be expanded on a running VM. This operation typically does not require a restart or service interruption.
If you extend storage, all nodes in the cluster must be extended equally to keep the cluster healthy. Do not extend disks on only one node.
Important
The System Diagnostics page displays storage usage as a percentage. To view the exact available capacity in GB, you may need to open a support session to run backend command-line tools (such as ceph df), as these metrics are not currently exposed in the UI.
How to scale up hardware resources
Choose the scale you want and make sure your hardware resources meet the system requirements. For more information, see System requirements.
For CPU/RAM scaling: Shut down the VM (if required by your hypervisor), increase the CPU and RAM allocation, and restart the VM.
For storage extension: Expand the disk size in your hypervisor. This can usually be done while the VM is running.
From the textual UI menu, select Scale Settings.
The supported scale sizes are:
Small: 16 CPU, 64 GB memory, 1 TB hard disk (1TB = 1024 GB)
Medium: 32 CPU, 128 GB memory, 1.5 TB hard disk
Large: 48 CPU, 192 GB memory, 2 TB hard disk

opp-tui-scale-settings.png Select Scan Scale Options to run a scan to evaluate the cluster recommended scale.
Based on the results, the system indicates the current scale size and gives you the option to increase the scale size.
The following is the type of system message you may see if you need to add resources to scale up.

opp-tui-scale-up-message.png The following is the type of system message you may see if you have sufficient resources to scale up.

opp-tui-scale-up-message2.png
Last updated
Was this helpful?
