HTTP Request Actions and Templates

An HTTP request action sends an HTTP request in response to an event. These types of actions allow you to integrate policies of Splunk AppDynamics with third-party HTTP APIs.

Note: HTTP Request Actions that use an authentication password configured before FIPS mode was enabled require password migration. Open the HTTP Request Template, re-enter the authentication password, and save the template. See Basic Authentication for details.

You can configure an HTTP/HTTPS proxy for an on-premise Controller to filter access to the web server. When you configure a proxy, the HTTP request actions are routed through the HTTP proxy or HTTPS proxy, depending on the endpoint. See Configure HTTP/HTTPS Proxy.

You create an HTTP request action using an HTTP request template. The template describes the HTTP request and is reusable by different HTTP request actions within an Splunk AppDynamicsaccount.

After you create a template, users in the Controller UI can create actions that use it. The template displays as an option after the user selects the Make an HTTP Request option in the Create Action pane and accesses the Configure Action pane.