Hardware Requirements

There are two ways to get the number of events.

Before installing the ESET Inspect Server:

1.Install the ESET Inspect Connector on at least three endpoints (ESET Inspect Connector is operable without ESET Inspect Server).

2.Activate the product with a valid ESET Inspect license. The activation is done via ESET PROTECT by creating a "Product activation" task. To do this, contact your ESET PROTECT Administrator or create a Product Activation task.

3.Wait for at least a day.

4.Navigate to the folder where ESET Inspect Connector is installed (by default C:\Program Files\ESET\Inspect Connector) and run command EIConnector.exe --stats.

5.From the output, use "Average Events Per Day".

After the ESET Inspect Server is already installed and working:

1.Go to Dashboard->Events load tab and check the highest values of events received per 24h in the "Events processed and stored per computer" chart.

To calculate the estimated CPU, RAM, and disk space requirements for ESET Inspect Server and MySQL on the same machine, use the following calculator:

The values in the table below are based on the assumption that the endpoint does not have more than a hundred thousand events generated per day, and the default data retention is 31 days. If the number of events in your environment is higher than a hundred thousand, you should proportionally scale the number from the table.

Disk Space Consumption Reduction

We recommend these steps for disk space consumption reduction.

This can significantly save the disk space used by stored events.

The disk IOPS

To get the information regarding the IOPS that your disk can provide, use the tool described below:

66% of IOPS triggered by ESET Inspect are write-related operations, and the block size is 32KB.

IOPS achieved by the customer’s hardware can be measured using the following command line: diskspd -b32K -d60 -o4 -t8 -h -r -w65 -L -Z1G -c20G C:\iotest.dat > C:\DiskSpeedResults.txt.

diskspd is a Microsoft tool that can be downloaded from: https://docs.microsoft.com/en-us/azure-stack/hci/manage/diskspd-overview

The CPU and RAM impact reduction

To reduce the impact on CPU and RAM, you can use two approaches:

1.Navigate to Dashboard->Server Status->Event Packet Queue Length. If the chart shows most of the time 500, then consider upgrading your hardware or lower the load on the server by using the steps described in the Disk Space Consumption Reduction.

2.You can change the interval of sending the events from connectors to the server. By default, the interval is every 7 minutes. The user can change this in ESET PROTECT by going into Policies > New Policy > Connection > Interval of sending events to the server (minutes). The possible interval is 5-1440 minutes.