This page provides information about the OneAgent directory structure and disk space requirements for OneAgent full-stack installation and updates. Note that exact values may vary based on OneAgent version.
|Default directory||Can be modified?|
|Size of installation (with temporary installation files removed)||360 MB||
|Persistent configuration||~5 MB||
|Temporary files, runtime configuration||200 MB||
|Crash reports, memory dumps||3 GB||
|Additional space required for updates||550 MB|
Use the INSTALL_PATH installation parameter.
For OneAgent version 1.201 and earlier, the default location for log files is
Use the LOG_PATH installation parameter.
Use the DATA_STORAGE installation parameter.
For a complete list of files and directories added to your system by OneAgent, see OneAgent security on AIX.
OneAgent files aging mechanism
OneAgent in Full-Stack Monitoring mode uses a built-in aging mechanism to ensure that the OneAgent files, including log files and runtime data, are kept within a reasonable size. For more information, see OneAgent file aging mechanism.
How we calculate space required for updates
When calculating the space required for updates, we take into account the installer file size and the size of the installation process, that is the space required to deploy OneAgent files.
|Installer file size||35 MB|
|Installation process size||465 MB|
Additional space required for updates is calculated using the 10% safety margin:
(installer file size + size of the installation process) * 1.1
Size of the installation process
The size of the installation process is calculated as follows:
3 * installer file size + size of the installation
The installer size must be multiplied by 3 to account for:
- Downloaded installer file (
- Archive, which is separated from the installer script (
- Unpacked external TAR (
In terms of space requirements, there's no real difference between manual installation of the new version (when an older version is already installed), automatic update, and updates that are triggered by restarting the OneAgent container. In all these cases, the installation process is performed exactly the same way. What differs is the method through which the update is triggered.