The following operating systems are supported for standalone installation:
Linux Kernel versions 2.6.x and later (x86 (32-bit), x86 (64-bit))
Windows Server 2008 R2, Windows Server 2012, Server 2012 R2, and Server 2016, Windows 8, 8.1 and 10 (x86 (32-bit), x86 (64-bit))
Mac OS X 10.11 and Mac OS 10.12 and 10.13
Solaris 10 and 11 (x86 (32-bit), x86 (64-bit), SPARC)
The following are supported Application Servers for deployment of XpoLog as an application (requires JAVA 1.6+):
Note: XpoLog is known to run on additional application servers. However, it was tested only on the above servers.
JAVA 1.7 or later is required. JAVA 1.8 is recommended.
The following browsers are supported:
Google Chrome (Version 50+) - recommended
Mozilla Firefox (Version 50+)
MS Internet Explorer (Version 11+)
The following are the default ports which should be opened:
30303 - HTTP client access to XpoLog web interface and communication between different XpoLog instances (can be modified if needed)
22 - In order to enable XpoLog to establish connections to remote machines over SSH (can be modified if needed)
The following is hardware recommendation for up to 3 concurrent users, and < 10 GB of daily logs volume:
The following is hardware recommendation for up to 5 concurrent users, and < 10 GB of daily logs volume:
The following is hardware recommendation for up to 25 concurrent users, and higher daily logs volume:
(contact email@example.com to determine if a cluster is needed. More information about clustering can be found here. See installations details at XpoLog Cluster Installation)
XpoLog collection, index and search operations benefit from a disk subsystem that is designed to the system's needs.
Capacity: Generally, the total required storage is calculated based on [DAILY AVERAGE LOG] x [RETENTION POLICY] x 1/2
The required storage for standard application logs may be closer to 35%. It is possible to tune the indexing density to reduce the required storage down to 15%.
Architecture: RAID 0, 10, 01, 0+1 will give the best performance, while RAID 5 will offer the worst performance.
Performance: XpoLog does many bulk reads/writes and many disk seeks. We recommend storage that provides high number (1000+) of random input/output operations per second (IOPS).
As faster the storage is, XpoLog will present better performance. XpoLog processing engines mostly perform write operations but not only, while XpoLog UI engines mostly perform read operations but not only.
It is mandatory to perform tests on your set of data and configuration deployment to determine optimized performance since it may vary between different types of data and searches XpoLog performs.
Note: In Linux/Solaris standalone installations, it is recommended to allocate a high number of open files and processes to the user that runs XpoLog.
For more information please see Post Installation Recommendations or contact firstname.lastname@example.org for more details