Configurable properties of Dynatrace Managed

The configurable Dynatrace Managed properties are stored in the /server/conf/ file, but do not edit them in that file. It is overwritten during an update.


If you configure properties directly in /server/conf/, your custom configuration won't be preserved during an update.

Instead of editing /server/conf/, make all your edits in the custom.settings file located in the /opt/dynatrace-managed/installer directory of each cluster node. You can create the file if it doesn't already exist. During an upgrade, the installer reads custom.settings and modifies accordingly.

The custom.settings file specifies:

  • The location of the file to be modified
  • The section to modify
  • The property and value to be set

Example custom.settings edits

Suppose you have made two modifications to settings:

  • Set the connection-timeout property to 3000000
  • Set the proxy-off property to true

To preserve these settings during upgrade:

Open the custom.settings file for editing.

  • File location: /opt/dynatrace-managed/installer directory of the cluster node.
  • Create the file in that location if it does not already exist.

Add one line to specify the configuration file to modify during the install.


Be sure to 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.


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.

proxy-off = true  

The resulting custom.settings file for this example should now look like this:

proxy-off = true

With this custom.settings file placed on all of the cluster nodes in the /opt/dynatrace-managed/installer directory, every time you upgrade the node the installer will set connection-timeout to 3000000 and proxy-off to true in the, thus preserving your custom configuration.

Applies to service restarts

Dynatrace Managed also executes this custom configuration action with each restart of the Dynatrace service.

Section: [com.compuware.apm.webserver]

Property Default value Description
port‑ssl 8021 The port where Dynatrace Server listens for traffic from OneAgent.
ssl‑protocols TLSv1.2 Supported SSL protocols. Can be one or a list of the following values: TLSv1, TLSv1.1, TLSv1.2
excluded‑ciphers unset List of additionally excluded ciphers (ciphers are defined by a substring matching at least a part of the cipher name, for example _DHE_)

Sections: [http.client.internal] - [http.client.external] - [http.client.opc]

These three sections apply to different HTTP communication types, but include the same content.

  • [http.client.internal] properties apply to internal traffic (server-to-server).

  • [http.client.external] properties apply to external traffic (for example, WebHook calls).

    WebHook integration
    There are cases where the WebHook integration can't use the proxy and therefore the proxy needs to be disabled. See Troubleshoot Dynatrace Managed.

  • [http.client.opc] properties apply to calls made to Mission Control.

Property Default value Description
proxy‑server unset Proxy server URL
proxy‑port unset Proxy port (numeric)
proxy‑user unset Proxy user name (optional)
proxy‑password unset Proxy password (optional). Authentication with user/password is transferred as a basic authentication header to the proxy. The initial plain text password is encrypted and stored in proxy-password-encr by the system.