Setting up proxy for ActiveGate

Typically, to set up the proxy for ActiveGate you have to update or add the authentication parameters to the custom.properties file. These proxy parameters affect ActiveGate communication and communication between ActiveGate and a monitored cloud like AWS or VMware. Depending on your ActiveGate version and deployment setup, you'll find this file in either the /var/lib/dynatrace/gateway/config folder or the /var/lib/dynatrace/gateway/gateway/config folder.

If you want to set up the proxy only for Activegate to monitored environment communication, define the proxy settings in the launcheruserconfig.conf file using a set of Java system properties with -D option after -vmargs.

For example:

  -vmargs
  -Dhttps.proxyHost=127.0.0.1
  -Dhttps.proxyPort=8080

Additional proxy settings that can be set in the launcheruserconfig.conf file:

  -Dhttps.proxyHost
  -Dhttps.proxyPort
  -Dhttps.proxyUser
  -Dhttps.proxyPassword

If you want to exclude hosts in proxy communication, you have to update or add the nonProxyHosts parameter to the launcheruserconfig.conf file. See Configure ActiveGate launcher.

Configuration override

Any proxy parameters defined in the custom.properties file override the same parameters (if defined) in the launcheruserconfig.conf file.

Proxy authentication

Private browser monitors

Private browser monitors do not support proxy authentication.

To set up proxy authentication for an ActiveGate:

Stop the ActiveGate and edit the custom.properties file. See Where can I find ActiveGate files?

Specify the proxy-related parameters in the [http.client] section of the custom.properties file—in particular, those parameters related to authentication, such as:

[http.client]
proxy-server=127.0.0.1
proxy-port=8080
# http or https
proxy-scheme=http
# basic authentication credentials
proxy-user=username
proxy-password=password

Command line parameters

proxy-server and proxy-port are the only proxy authentication parameters that can be used in the command line: PROXY=<proxy server>:<proxy port>.

Restart the ActiveGate.

Excluding hosts from proxy communication

The nonProxyHosts parameter configured in the launcheruserconfig.conf file affects only the communication between the ActiveGate and the monitored environment. For example, it may be a cloud technology like AWS or VMware or a resource monitored by your private monitors executed on a synthetic-enabled ActiveGate.

Stop the ActiveGate and edit the launcheruserconfig.conf file. See Configure ActiveGate launcher.

The hosts that should be accessed without going through the proxy. Typically this defines internal hosts. The value of this property is a list of hosts, separated by the '|' character. In addition, you can use the wild card character '*' for pattern matching. There can be only one wild card character, either at the beginning or the end of the hostname. For examplenonProxyHosts=*.foo.com|localhost will indicate that every hosts in the foo.com domain and the localhost should be accessed directly even if a proxy server is specified.

Make sure that the proxy parameters are preceded by the -vmargs flag.

For example:

-vmargs
-Dhttp.nonProxyHosts=hostname0*|10.1.*

JVM version

The syntax for specifying the host variable may vary depending on your JVM version. Single quotation marks or double quotation marks may be required for your version of JVM.

For example:

-vmargs
-Dhttp.nonProxyHosts='hostname0*|10.1.*'

-vmargs
-Dhttp.nonProxyHosts="hostname0*|10.1.*"

Restart the ActiveGate.