Hardware and Software Requirements

Important:

Please note that this is a change from our HW/SW specs from Insights 2021.10. Insights 2021.10 requires a single Windows machine, while Insights 2022.10 requires a Windows machine and a Linux machine with RHEL.

In 2021.10, the Insights Windows machine ran Docker which hosted the Looker Linux container. Starting with Windows 2022, the driver used to nest the Linux containers in Windows OS (called lcow) is not supported anymore by Microsoft for enterprise applications. As a result, we had to change our deployment architecture to require two machines - one Windows machine to run the UiPath Insights components, and a Linux machine to run the Looker container. With this change, enterprise support is available from OS vendors for the components needed to run UiPath products. The supported versions of Linux OS are the same that Automation Suite supports.

Note: Insights isn't supported on FIPS 140-2 enabled host machines.

Hardware Requirements

These requirements are only applicable to the machine where Insights is installed.

Insights Windows Machine

Important: Insights must be installed on its own machine; it cannot be co-hosted with Orchestrator.

	CPU (cores)	System Memory (GB)	Available Storage (GB)	Examples
Required Hardware	4	16	32	AWS t2.xlarge or Azure D4s_v3

Insights Linux Machine

The following table lists the hardware requirements for hosting the Insights Linux Machine.

Important: For air-gapped environments, make sure that the following volumes have enough available space:

/home: over 4Gb.
/var: over 10GB.

CPU (cores) System Memory (GB) Storage (GB) Example
Required Hardware 4 16 32 AWS t2.xlarge or Azure D4s_v3

Note:

An SSL certificate is needed for HTTPS.
Make sure that ip_forward is enabled.
The user.max_user_namespaces OS setting shouldn't be set to 0.

Ports

Make sure the following ports are externally accessible and no other service uses these ports:

Inbound Ports	Machine
`443` Note: This is the default port, and you can change it to any available port	Insights Windows Machine
`9999` Note: This is the Looker port.	Insights Linux Machine
`19999` Note: This is the Looker API port.	Insights Linux Machine
`29999` Note: This is the LookML update port.	Insights Linux Machine

For instructions on how to open an inbound port in AWS, see Authorizing access to an instance. For instructions on how to open an inbound port in Azure, see NSG Quickstart Portal.

Insights architecture.

Note: Make sure that the hostnames for both the Insights Windows Machine and the Insights Linux Machine are resolvable within your DNS.

SQL Requirements

Note: For best performance, consider hosting the Insights database on a dedicated machine. If you currently have a Small-Scale deployment or are evaluating Insights, you might have both Orchestrator and Insights databases on the same machine. If you start noticing performance issues, you can move the Insights database to a dedicated machine.

The following compute resources were used during our tests:

Intel® E5-2673 v4 (Broadwell) 2.3 GHz
Intel® SP-8160 (Skylake)
Intel® 8272CL (Cascade Lake) 2.5 GHz
Intel® Xeon Platinum 8307C (Ice Lake)
AMD EPYC 7763v (Milan)

	Small Scale Up to 1M Rows	Medium Scale Up to 20M Rows	Large Scale Up to 200M Rows	Extra-Large Scale > 200 M Rows
CPU	4 Cores	8 Cores	16 Cores	Please see Performance and scalability
System Memory	16 GB	32 GB	64 GB	See Performance and scalability.
Data Disk	40 GB	100 GB	1 TB	See Performance and scalability.

Note: If you require over 200 million rows, contact your UiPath representative.

Software Requirements

Important: Your Orchestrator and Insights products must be of the same version (e.g., v2022.10.0).

Operating System

Software	Compatible Version
Windows Machine	2019
Red Hat Enterprise Linux	8.2, 8.4, and 8.6 are supported with any version. 8.8, 9.1, 9.2 versions are supported starting with update 2022.10.5. 8.9 version is supported starting with update 2022.10.8.

Database

Software	Compatible Version
SQL Machine	2019

Note:

Insights requires the SQL Server to have support for columnstore index and .json functions.
For Azure SQL, ensure the database is S3 tier or above.
Make sure the compatibility level for Insights database is set to 150 or higher ("SELECT compatibility_level from sys.databases WHERE name = '{dbName}'). In most cases, the default settings meet this requirement. For more information, refer to View or Change the Compatibility level of a Database - SQL Server.