Disk space requirements for OneAgent installation and update on Windows

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.

Size of installation (with temporary installation files removed) 400 MB
Recommended free space for runtime data (logs, temporary files, crash reports, memory dumps, etc.) 3 GB
Additional space required for updates 465 MB
Total 3.9 GB

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.

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.

Installer file size 65MB
Installation process size 900 MB

Additional space required for updates is calculated as follows:

size of the installation + installer file size

On Windows, we uninstall an earlier version before extracting the new installer.

Size of the installation process

The size of the installation process is calculated as follows:

2 * installer file size + 2 * size of the installation

The installer size must be multiplied by 2 to account for:

  • Downloaded installer file
  • Temporary extraction of the external MSI to %APPDATA%\OneAgent

The installation size must be multiplied by 2 because the installer temporarily extracts all files to %APPDATA%\ruxit\<ID> and copies them to the final destination. At the end of the installation, the %APPDATA%\ruxit\<ID> folder is deleted.

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.