You can configure an HTTP/HTTPS proxy for your Splunk AppDynamics On-Premises Virtual Appliance deployment. 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.
Splunk AppDynamics On-Premises Virtual Appliance has two installation profiles- standard deployment and hybrid deployment.
To configure HTTP/HTTPS proxy on the Splunk AppDynamics On-Premises Virtual Appliance standard deployment:
Locate the /home/appduser/appd-charts/charts/controller/templates/controller-configmap.yml file and take a backup of the file.
Open the controller-configmap.yml file in a suitable editor. Locate the start.ini section and add the following JVM option to enable the HTTP proxy support for alerting actions:
The HTTP proxy support for alerting actions is disabled by default.
You can also enable the HTTP proxy support for alerting actions at,/private/ControllerFlagsServletendpoint. You must have admin credentials to enable this option.
Add the following JVM options to configure the HTTP and HTTPS proxy authentication parameters, namely, host, port, user, and password:
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
Run the following command to restart the Controller:
appdcli start appd <profile>
CODE
The configuration steps for HTTP/HTTPS proxy on Splunk AppDynamics On-Premises Virtual Appliance hybrid deployment are identical to those for Splunk AppDynamics On-Premises deployment. For information, see Configure HTTP/HTTPS Proxy on Splunk AppDynamics On-Premises.