This section lists the minimum system requirements for installing and working with EventLog Analyzer.
Log management solutions are resource-intensive and selecting the right hardware plays a major role in ensuring optimal performance.
The following table denotes the suggested hardware requirements based on the type of flow.
||3 TB *
||4 TB *
|Network card capacity
- The above-mentioned values are approximate. It is recommended to run a test environment similar to the production environment with the setup details mentioned in the above table. Based on the exact flow and data size, the system requirements can be fine-tuned.
- For higher IOPS, we can use RAID or SSD.
Use the following table to determine the type of flow for your instance.
||Size (in Bytes)
|Low Flow (EPS)
||Normal Flow (EPS)
||High Flow (EPS)
|Linux, HP, pfSense, Juniper
||Type 1 Syslogs
|Cisco. Sonicwall, Huaweii, Netscreen, Meraki, H3C
||Type 2 Syslogs
|Barracuda, Fortinet, Checkpoint
||Type 3 Syslogs
|Palo Alto, Sophos, F5, Firepower, and other syslogs
||Type 4 Syslogs
- A single-installation server can handle either a maximum of 3000 Windows logs or any of the high flow values mentioned for each log type in the above table.
- For log types which are not mentioned in the above table, choose the appropriate category based on the log size. For example, in the case of SQL Server logs when the byte size is 900 bytes, and EPS is 3000, it should be considered as High Flow.
- If the combined flow is higher than what a single node can handle, it is recommended to implement distributed setup.
- It is recommended to choose the next higher band if advanced threat analytics and a large number of correlation rules have been used.
- Allocate 100 percent RAM/CPU to the virtual machine running EventLog Analyzer. Sharing memory/CPU with other virtual machines on the same host may result in RAM/CPU starvation and may negatively impact EventLog Analyzer's performance.
- Employ thick provisioning, as thin provisioning increases I/O latency. In case of VMware, Select Thick provisioned, eagerly zeroed as lazily zeroed is lower in performance.
- Enabling VM snapshots is not recommended as the host duplicates data in multiple blocks by increasing reads and writes, resulting in increased IO latency and degraded performance.
CPU & RAM:
- Server CPU utilization should always be maintained below 85% to ensure optimal performance.
- 50% of server RAM should be kept free for off-heap utilization of Elasticsearch for optimal performance.
- Disk latency greatly affects the performance of EventLog Analyzer. Direct-attached storage (DAS) is recommended on par with the throughout of an SSD with near-zero latency and high throughput. An enterprise storage area network (SAN) can be faster than SSD.
EventLog Analyzer has been tested to support the following browsers and versions with at least a 1024x768 display resolution:
- Microsoft Edge
- Firefox 4 and later
- Chrome 8 and later
EventLog Analyzer can use the following databases as its back-end database.
Bundled with the product
- Microsoft SQL 2012 & above
Please note the hardware requirements needed to configure the MS SQL database for EventLog Analyzer:
EventLog Analyzer can be installed in machines running the following operating systems and versions:
- Windows 7 & above, and Windows Server 2008 & above
- Linux: Red Hat 8.0 and above/all versions of RHEL, Mandrake/Mandriva, SUSE, Fedora, CentOS, Ubuntu, Debian
- SIEM solutions are resource-intensive. It is recommended to provide a dedicated server for their optimal performance.
- Eventlog Analyzer uses Elasticsearch. Elasticsearch process is expected to utilize off-heap memory for better performance. Off-heap memory is maintained by the operating system and will free up when necessary.
Additional Elasticsearch Node Recommendations: