OneAgent files and disk space requirements on Windows

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.

Full-stack and Infrastructure Monitoring mode

The same disk space requirements apply to both Full-stack and Infrastructure monitoring modes.

OneAgent directories and their sizes

Default directory
Can be modified?
Size of installation (with temporary installation files removed)
~1.1 GB
%PROGRAMFILES%\dynatrace\oneagent
Yes 1
Persistent configuration
~5 MB
%PROGRAMDATA%\dynatrace\oneagent\agent\config
No
Temporary files, runtime configuration
200 MB
%PROGRAMDATA%\dynatrace\oneagent\agent\runtime
No
Logs
1 GB
%PROGRAMDATA%\dynatrace\oneagent\log
Yes 2
Crash reports, memory dumps
3 GB
%PROGRAMDATA%\dynatrace\oneagent\datastorage
Yes 3
EEC logs retransmission persistence file
600 MB
%PROGRAMDATA%\dynatrace\oneagent\agent\runtime\extensions\persistence
Yes 4 5
Additional space required for updates
2.4 GB
Total
9.7 GB
1

Use the INSTALL_PATH installation parameter.

2

Use the LOG_PATH installation parameter.

3

Use the DATA_STORAGE installation parameter.

4

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.

5

The reliability mechanism does not work if the requirement is not met. Extra 1.5 GB required as a buffer. For more information see Persistence details.

For a complete list of files and directories added to your system by OneAgent, see OneAgent security on Windows.

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.

Space required for updates

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).

Size
Description
Removed after
Claimed by
Path
1
~80 MB
EXE installer downloaded by AutoUpdate
OneAgent restart or next version installed 1
AutoUpdate
%PROGRAMDATA%\dynatrace\oneagent
2
~520 MB
Extracted MSI installer
End of the installation
OneAgent Installation
%PROGRAMDATA%\dynatrace\oneagent
3
~520 MB
Extra storage for temporary installation files
End of the installation
OneAgent Installation
%APPDATA%
4
~520 MB
Copy of the MSI installer saved by Windows
Next version installed
Windows installer
%WINDIR%\Installer
5
~520 MB
Installed files
Next version installed
OneAgent Installation
[Installation path]
Σ
~2160 MB
1

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.

Persistence details

The reliabilty mechanism ensures the persitance of Extention Execution Controller (EEC) logs in case ActiveGate or OneAgent is unavailable, there are network problems, or EEC experiences the data ingest overload. Thanks to the reliability mechanism, we're able to minimize the gaps in the log coverage.

General information

  • persistence is working by default if the volume requirement is satisfied - 2136 MB
    • 600 MB of free disk space to be used by the reliability mechanism
    • extra 1.5 GB of free disk space as a buffer (not used by the reliability mechanism)
  • the requirement is checked periodically and if not met, the persistence will be turned off - log ingest will be transmitted without the reliability mechanism
  • the volume is used proportionally to the load of logs ingest
  • if the requirement can't be met on the host, the configuration of logs persistence can by adjusted - for more information see Persistence configuration.

Configuration

Windows configuration file: C:\ProgramData\dynatrace\remotepluginmodule\agent\conf\extensionsuser.conf

Linux configuration file: /var/lib/dynatrace/remotepluginmodule/agent/conf/extensionsuser.conf

Variable

Description

persistence.reliable_mode

true - reliable mode turned on; SFM logs genereted if space requirement not met false - reliable mode turned off; log ingest will be transmitted without the reliability mechanism

persistence.total_limit_kb

Maximum volume limit for Extensions Log Persistence in kilobytes. By default: 600 MB Can be modified manually if the requirement can't be met on the host.