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.
The same disk space requirements apply to both Full-stack and Infrastructure monitoring modes.
%PROGRAMFILES%\dynatrace\oneagent
%PROGRAMDATA%\dynatrace\oneagent\agent\config
%PROGRAMDATA%\dynatrace\oneagent\agent\runtime
Use the INSTALL_PATH installation parameter.
Use the LOG_PATH installation parameter.
Use the DATA_STORAGE installation parameter.
Applicable only if you use Dynatrace Extensions that define the log metrics, events, or add their own log processing rules. Can be changed via support request.
For a complete list of files and directories added to your system by OneAgent, see OneAgent security on Windows.
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.
When calculating the space required for updates, we take into account the compressed EXE installer file size, the extracted MSI package, and the size of the installation process (the space required to deploy OneAgent files).
%PROGRAMDATA%\dynatrace\oneagent
%PROGRAMDATA%\dynatrace\oneagent
%APPDATA%
%WINDIR%\Installer
[Installation path]
If you download the EXE installer manually, the installation process won't remove it.
Additional space required for installation and updates is calculated using the 10% safety margin:
(size of the installation process [2+3+4+5] + installer files size [1]) * 1.1
Required disk space for OneAgent installation and update on a single drive is ~2 380 MB calculated using this formula.
Note that the EXE installer is compressed, which explains the difference in size in comparison to the MSI installer.
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.