The following table includes information about the disk space requirements for OneAgent full-stack installation and updates. Note that exact values may vary based on OneAgent version.
|Linux (x86)||Linux (ppcle)||Linux (s390)||Default directory|
|Size of installation (with temporary installation files removed)||1.02 GB||410 MB||145 MB||
|Temporary files, runtime configuration||200 MB||200 MB||200 MB||
|Logs||1 GB||1 GB||1 GB||
|Crash reports, memory dumps||3 GB||3 GB||3 GB||
|Additional space required for updates||1.9 GB||728 MB||226 MB|
|Total||7.1 GB||5.3 GB||4.6 GB|
If you have tight disk space constraints, you can limit the log size. If you're interested in saving up the disk space on logs, please contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Dynatrace Managed self-monitoring
OneAgent self-monitoring for Dynatrace Managed requires 4.8 GB of disk space on Linux. For more information, see the directory structure of Dynatrace Managed.
How do 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.
|Linux (x86)||Linux (ppcle)||Linux (s390)|
|Installer file size||175 MB||63 MB||27 MB|
|Installation process size||1.54 GB||600 MB||226 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.