You can configure an HTTP/HTTPS proxy for an on-premise Controller. When you configure a proxy, the HTTP request actions or JIRA actions are routed through the HTTP proxy or the HTTPS proxy, depending on the endpoint. 

 To configure an HTTP/HTTPS proxy:

  1. Login to your Enterprise Console.
  2. Select Platform.
  3. Click the Configuration tab.
  4. Click Controller Settings > Appserver Configurations > JVM Options.
  5. Go to the JVM Config section and add the following JVM option to enable the HTTP proxy support for alerting actions:
    -Dappdynamics.alerting.actions.http.enable.proxy=true
    XML

    The HTTP proxy support for alerting actions is disabled by default.

    You can also enable the HTTP proxy support for alerting actions at, /private/ControllerFlagsServlet endpoint. You must have admin credentials to enable this option.

  6. Add the following JVM options to configure the HTTP and HTTPS proxy authentication parameters, namely, host, port, user, and password.

    -Dhttp.proxyHost=$HOST 
-Dhttp.proxyPort=$PORT 
-Dhttp.proxyUser=$USER 
-Dhttp.proxyPassword=$PASSWORD 
-Dhttps.proxyHost=$HOST 
-Dhttps.proxyPort=$PORT 
-Dhttps.proxyUser=$USER 
-Dhttps.proxyPassword=$PASSWORD
    CODE

    Ensure that you provide a plain text password only.
    Proxy parameter changes are not hot-swappable. This means that you need to restart the Controller to ensure that the changes are reflected.

    If you want to exclude some domains from being accessed via the proxy, add them as follows:

    -Dhttp.nonProxyHosts=localhost|*.abcd.com|xyz.com
    CODE


  7. Click Save for the changes to take effect and to restart the Controller.