Disk space requirements for OneAgent installation and update on Linux

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)
Size of installation (with temporary installation files removed) 900 MB 300 MB 130 MB
Recommended free space for runtime data (logs, temporary files, crash reports, memory dumps, etc.) 3 GB 3 GB 3 GB
Additional space required for updates 1.5 GB 530 MB 300 MB
Total 5.4 GB 3.8 GB 3.4GB

The space required for logs is about 1 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 110 MB 35 MB 35 MB
Installation process size 1 GB 400 MB 235 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.