NXLog Agent system requirements
The following are general guidelines for planning an NXLog Agent deployment. Actual system requirements will vary based on the configuration, event rate, and the presence of third-party components. Always thoroughly test a deployment to verify the desired performance with the system resources available.
These requirements are in addition to the operating system’s requirements.
CPU
NXLog Agent uses between one and three CPU threads for each module you load. Performance depends on how often modules are used and how the operating system schedules threads.
You need at least one processor core to run NXLog Agent. If you plan to use several modules, we recommend two or more cores.
RAM
The required memory depends on the number of loaded modules, which is typically under 100 MB, and the NXLog Agent configuration.
Open file handles, network connections, the number of output module instances, and module variables all cosume additional memory.
As a rule of thumb, we recommend dedicating at least 250 MB of RAM to NXLog Agent.
Disk space
The required disk space depends on the operating system, hardware architecture, and the presence of third-party components:
- Windows installer
-
Approximately 340 MB
- macOS, Debian, Ubuntu, and RHEL-based packages
-
Approximately 270 MB
- Solaris and AIX packages (limited module set)
-
Approximately 100 MB
In addition, NXLog Agent’s data caching and buffering configuration also affects disk space usage. You can calculate the approximate disk space required by multiplying the LogQueueSize value by the number of output module instances, plus 10 MB for the configuration cache.