The configurable properties for Dynatrace Managed are stored in the /opt/dynatrace-managed/server/conf/config.properties file, but don't change them in that file. The file is overwritten during an update.
If you configure properties directly in /opt/dynatrace-managed/server/conf/config.properties, your custom configuration won't be preserved during an update.
Instead of changing /opt/dynatrace-managed/server/conf/config.properties, make all your changes in the custom.settings file located in the /opt/dynatrace-managed/installer directory of each Managed Cluster node. You can create the file if it doesn't already exist. During an upgrade, the installer reads custom.settings and modifies config.properties accordingly.
The custom.settings file specifies:
Suppose you have made two modifications to settings:
connection-timeout property to 3000000proxy-off property to trueTo preserve these settings during upgrade:
Open the custom.settings file.
/opt/dynatrace-managed/installer directory of the node.Add one line to specify the configuration file to modify during the install.
<server/conf/config.properties>
Include the chevrons (< and >).
Add two lines to specify the section, property name, and property value to be modified for connection-timeout, which is in the [settings] section.
[settings]connection-timeout=3000000
Add two lines to specify the section, property name, and property value to be modified for proxy-off, which is in the [http.client.external] section.
[http.client.external]proxy-off = true
The resulting custom.settings file for this example should now look like this:
<server/conf/config.properties>[settings]connection-timeout=3000000[http.client.external]proxy-off = true
Place this custom.settings file on all Managed Cluster nodes in the /opt/dynatrace-managed/installer directory. Every time you upgrade a node, the installer sets connection-timeout to 3000000 and proxy-off to true in config.properties, preserving your custom configuration.
Dynatrace Managed also executes this custom configuration action with each restart of the Dynatrace service.