The Scale Settings textual UI menu item enables scaling up resources for CPU, memory, and disk size.
The Scale Settings textual UI menu item enable 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 manually, as the procedures and downtime expectations differ.
Scale 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.
Note
You can only scale up, you cannot scale down.
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.
Note
If you are working with more than one node, all the nodes in the cluster must meet the same hardware requirements.
When extending storage, every node's disk must be increased to the exact same size to ensure replication stability.
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
In the Scale up menu, choose either Scale up (default) or Adjust storage.
Select Scan Scale Options to run a scan to evaluate the cluster recommended scale.
If you selected Scale up: Based on the results, the system indicates the current scale size and gives you the option to increase the scale size. The recommended scale is determined by the node with the least hardware resources.
If you selected Adjust storage:
If the existing storage is larger, a message indicates "Previous Storage size:XX TB New Storage size: YY TB. Do you want to continue?"
If the storage is the same, a message indicates "No new storage was detected."
If less storage is detected, an error message indicates "Reducing storage from your XSOAR tenant is not supported."
Note
It is recommended to back up your tenant before proceeding since this is an irreversible action.
You can only increase storage, you cannot decrease.
Example 6.The following is the type of system message you may see if you need to add resources to scale up.
The following is the type of system message you may see if you have sufficient resources to scale up.
Extend 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.