<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Configurable properties of Dynatrace Managed | Dynatrace help</title>
    <description></description>
    <link>https://www.dynatrace.com/support/help/</link>
    <atom:link href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/configuration/configurable-properties-of-dynatrace-managed/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Fri, 18 Oct 2019 07:17:18 +0200</lastBuildDate>
    <pubDate>Mon, 08 Apr 2019 13:05:46 +0200</pubDate>
    <generator>Metalsmith v2.3.0</generator>
    <item>
      <title>Configurable properties of Dynatrace Managed updated on Mon, 08 Apr 2019 13:05:46 +0200</title>
      <description>&lt;p&gt;The configurable Dynatrace Managed properties are described below. While these properties are in the &lt;code&gt;/server/conf/config.properties&lt;/code&gt; file, this file is always overwritten during an update. As a result, if you configure properties in that file, &lt;strong&gt;your custom configuration won&amp;apos;t be preserved&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;To preserve custom configuration settings during an update, make all changes to property settings in the &lt;code&gt;custom.settings&lt;/code&gt; file located in the &lt;code&gt;/opt/dynatrace-managed/installer&lt;/code&gt; directory of all cluster nodes. You can create the file if it doesn&amp;apos;t already exist. During an upgrade, the installer reads the &lt;code&gt;custom.settings&lt;/code&gt; file and, based on your custom configuration, modifies the &lt;code&gt;config.properties&lt;/code&gt; file.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;custom.settings&lt;/code&gt; file must have the following information:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The location of the file to be modified&lt;/li&gt;
&lt;li&gt;The section to modify&lt;/li&gt;
&lt;li&gt;The property and the value to be set&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For example, if you have modified the &lt;code&gt;connection-timeout&lt;/code&gt; property to &lt;code&gt;3000000&lt;/code&gt; and set the &lt;code&gt;proxy-off&lt;/code&gt; property to &lt;code&gt;true&lt;/code&gt;, and you would like to preserve these settings during the upgrade:&lt;/p&gt;
&lt;div class=&quot;step&quot;&gt;
&lt;p&gt;Edit or create the &lt;code&gt;custom.settings&lt;/code&gt; file.&lt;/p&gt;

&lt;/div&gt;
&lt;div class=&quot;step&quot;&gt;
&lt;p&gt;In the &lt;code&gt;custom.settings&lt;/code&gt; file, specify which file should be modified during the install. Add a line with the target configuration file path (including the chevrons).&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-text&quot;&gt;&amp;lt;server/conf/config.properties&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;div class=&quot;step&quot;&gt;
&lt;p&gt;Add a line with the section to be modified for &lt;code&gt;connection-timeout&lt;/code&gt;. The &lt;code&gt;connection-timeout&lt;/code&gt; property is in &lt;code&gt;[settings]&lt;/code&gt; section.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-text&quot;&gt;[settings]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;div class=&quot;step&quot;&gt;
&lt;p&gt;Add a line with the property and the value setting.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-text&quot;&gt;connection-timeout=3000000
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;div class=&quot;step&quot;&gt;
&lt;p&gt;Add a line with the section to be modified for &lt;code&gt;proxy-off&lt;/code&gt;. The &lt;code&gt;proxy-off&lt;/code&gt; property is in &lt;code&gt;[http.client.external]&lt;/code&gt; section.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-text&quot;&gt;[http.client.external]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;div class=&quot;step&quot;&gt;
&lt;p&gt;Add a line with the property and the value setting.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-text&quot;&gt;proxy-off = true
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;The resulting &lt;code&gt;custom.settings&lt;/code&gt; file for this example should look like this:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-text&quot;&gt;&amp;lt;server/conf/config.properties&amp;gt;
[settings]
connection-timeout=3000000
[http.client.external]
proxy-off = true
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;With such a &lt;code&gt;custom.settings&lt;/code&gt; file placed on all of the cluster nodes in the &lt;code&gt;/opt/dynatrace-managed/installer&lt;/code&gt; directory, every time you upgrade the node the installer will set &lt;code&gt;connection-timeout&lt;/code&gt; to &lt;code&gt;3000000&lt;/code&gt; and &lt;code&gt;proxy-off&lt;/code&gt; to &lt;code&gt;true&lt;/code&gt; in the &lt;code&gt;config.properties&lt;/code&gt;, thus preserving your custom configuration.&lt;/p&gt;
&lt;div class=&quot;callout information&quot;&gt;
&lt;span class=&quot;callout__title&quot;&gt;Applies to service restarts&lt;/span&gt;
&lt;p&gt;Dynatrace Managed also executes this custom configuration action with each restart of the Dynatrace service.&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&quot;section-comcompuwareapmwebserver-&quot;&gt;Section: [com.compuware.apm.webserver]
      &lt;span class=&quot;shortlink-copy shortlink-copy-js&quot; data-clipboard-text=&quot;https://www.dynatrace.com/support/help/shortlink/dynatrace-server-configure#section-comcompuwareapmwebserver-&quot;&gt;
      &lt;/span&gt;&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;strong&gt;Property&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Default value&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;port-ssl&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;8021&lt;/td&gt;
&lt;td&gt;The port where Dynatrace Server listens for traffic from OneAgent.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;ssl-protocols&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;TLSv1.2&lt;/td&gt;
&lt;td&gt;Supported SSL protocols. Can be one or a list of the following values: &lt;code&gt;TLSv1&lt;/code&gt;, &lt;code&gt;TLSv1.1&lt;/code&gt;, &lt;code&gt;TLSv1.2&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;excluded-ciphers&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;unset&lt;/td&gt;
&lt;td&gt;List of additionally excluded ciphers (ciphers are defined by a substring matching at least a part of the cipher name, for example &lt;code&gt;_DHE_&lt;/code&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id=&quot;sections-httpclientinternal-httpclientexternal-httpclientopc-&quot;&gt;Sections: [http.client.internal] - [http.client.external] - [http.client.opc]
      &lt;span class=&quot;shortlink-copy shortlink-copy-js&quot; data-clipboard-text=&quot;https://www.dynatrace.com/support/help/shortlink/dynatrace-server-configure#sections-httpclientinternal-httpclientexternal-httpclientopc-&quot;&gt;
      &lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;These three sections regard different HTTP communication types but include the same content. The properties of &lt;code&gt;[http.client.internal]&lt;/code&gt; relate to internal traffic (server-to-server) while those of &lt;code&gt;[http.client.external]&lt;/code&gt; relate to external traffic (for example, WebHook calls).&lt;/p&gt;
&lt;div class=&quot;callout information&quot;&gt;
&lt;span class=&quot;callout__title&quot;&gt;WebHook integration&lt;/span&gt;
&lt;p&gt;There are cases where the WebHook integration can&amp;apos;t use the proxy and therefore the proxy needs to be disabled. See &lt;a href=&quot;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/operation/troubleshoot-dynatrace-managed/#application-can-t-connect-to-cluster-via-webhook&quot;&gt;Troubleshoot Dynatrace Managed&lt;/a&gt;.&lt;/p&gt;

&lt;/div&gt;

&lt;p&gt;The properties of &lt;code&gt;[http.client.opc]&lt;/code&gt; concern the calls to &lt;a href=&quot;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/operation/how-does-mission-control-pro-active-support-work/&quot;&gt;Mission Control&lt;/a&gt;.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;strong&gt;Property&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Default value&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;proxy-server&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;unset&lt;/td&gt;
&lt;td&gt;Proxy server URL&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;proxy-port&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;unset&lt;/td&gt;
&lt;td&gt;Proxy port (numeric)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;proxy-user&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;unset&lt;/td&gt;
&lt;td&gt;Proxy user name (optional)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;proxy-password&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;unset&lt;/td&gt;
&lt;td&gt;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 &lt;code&gt;proxy-password-encr&lt;/code&gt; by the system.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
</description>
      <pubDate>Mon, 08 Apr 2019 13:05:46 +0200</pubDate>
      <link>https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/configuration/configurable-properties-of-dynatrace-managed/?updated=mon-08-apr-2019-13-05-46-0200</link>
      <guid isPermaLink="true">https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/configuration/configurable-properties-of-dynatrace-managed/</guid>
    </item>
  </channel>
</rss>