When your application experiences memory leaks or high object churn, it’s important that you get memory dumps so you can analyze these issues. In production environments, this is often a challenge when you can’t log into the environment and you have no other means of triggering memory dumps. Dynatrace enables you to both trigger and securely download memory dumps to your analysis tool of choice. To enable memory dumps, you need to configure an ActiveGate as described below.
If you don’t already have an ActiveGate set up, you need to install an ActiveGate.
Upon each upgrade,
config.properties is updated and the existing settings are overwritten (with some exceptions—see below). To avoid losing your settings with each update, use
custom.properties to preserve them. Whenever you need to configure an ActiveGate setting (for example, proxy, port, or memory dump), do this in the
custom.properties file and then restart the ActiveGate.
custom.properties file is preserved during ActiveGate upgrade (copied from your existing installation to the new one).
custom.properties file of your ActiveGate.
This file is located in the
config directory of your ActiveGate installation:
- Linux systems:
- Windows systems:
Note: On Windows, the
programdata directory is usually hidden by default. Paste the file path above into Windows Explorer to access the file.
[collector] section, uncomment the
DumpSupported line and set the property to
DumpSupported = true
[dump] section, uncomment the
dumpDir = dump
The directory provided in the
dumpDir property setting will be created in the same directory where the
dynatracegateway is run. For example, with the
dumpDir = dump configuration and the
dynatracegateway run in
/opt/dynatrace/gateway/launcher/ directory, the dump will be created in:
Make sure that a user and group running the ActiveGate,
dtuserag user and
dtuserag group by default, have the following permissions to the
Example of dump directory permissions in Windows
[dump] section, uncomment the following properties:
maxSizeGb = 100
maxAgeDays = 7
maxConcurrentUploads = 5
[collector] # collector supports collecting of memory dumps from OneAgents (default: false) # Add this to the [collector] section DumpSupported = true # Add this section to the end of the file [dump] # relative to ActiveGate installation directory or absolute path # ActiveGate runs with reduced permissions to the file system. # Ensure that the user running the ActiveGate has write permissions to this directory dumpDir = dump # maximum size in gb for stored memory dump maxSizeGb = 100 # maximum age in days for keeping stored memory dumps maxAgeDays = 7 # maximum number of concurrent file uploads supported maxConcurrentUploads = 5
Restart the ActiveGate.
All instances of OneAgent will automatically reconnect and recognize that the ActiveGate can now store memory dumps. Now, whenever a memory dump is successfully triggered, the dump will be uploaded automatically to the correct ActiveGate. Once safely stored on the ActiveGate, the OneAgent deletes the local file from its storage.
- This feature requires OneAgent version 1.127 or higher and ActiveGate version 1.127 or higher.
- Memory dumps for IBM Java require OneAgent version 1.135 or higher.
- Memory dump download for "PaaS application only integration" requires OneAgent version 1.139 or higher.
- Your application server must have adequate space to store the heap dump.