Create HTTP Request Action

To create an HTTP Action: 

1. Click Configure > HTTP Request Actions. 
2. Click Create HTTP Request Action in the right panel to access the wizard.
3. In the General Information section: 
   1. Select an Action Template for your endpoint where you want to send the HTTP request:
      
      • New Action: Indicates an action template for an endpoint of your choice. This is a blank template that you can configure to send alerts to a custom endpoint.
      • OpsGenie: Indicates the action template for OpsGenie.
      • PagerDuty: Indicates the action template for PagerDuty.
      • ServiceNow: Indicates the action template for ServiceNow.
      • Slack: Indicates the action template for Slack.
      • Webex: Indicates the action template for Webex.
   2. Define an Action Name.
   3. Select a request method type from the Method dropdown list:
      • GET
      • POST
      • PUT

      • DELETE

        

        The default method type is POST.

   4. Enter a URL for the request in the Raw URL field. This field is pre-filled if you select the action template for these endpoints- OpsGenie, PagerDuty, and ServiceNow. For Slack and Webex, enter the incoming webhook URL.
   5. Select the URL encoding scheme from the dropdown menu. Only UTF-8 and ISO_8859-1 are supported.
4. If the intended communication is encrypted, configure the authentication settings as follows:
   1. Select Basic authentication for your HTTP request from the Type dropdown list.
   2. Specify the authentication username.

   3. Specify a password and confirm the password.

      

      If the communication is not encrypted, we recommend that you do not use any authentication. Select None in step a.

5. (Optional) To use custom variables that replace values in the URL path and payload when the HTTP request is sent, in the Custom Variable and Headers (Optional) section:

   1. Enter a variable name and its default value. The variable names are pre-filled and embedded in the template for a specific endpoint that you select from the action template list.
   2. Click + Add variable to add multiple variables.
   3. Enter a header name and its default value. Custom request headers can contain custom variables encoded as $(VARIABLE_NAME).

   4. Click + Add header to add multiple headers.

      

      You can review a set of Predefined Variables. Check this list before you create any custom variables. It is possible that the variable that you want to define already exists.

      You can optionally configure custom variables if the predefined variables do not meet your needs. When a predefined variable and a custom variable are both configured with the same variable name, the predefined variable is used.

6. (Optional)To include a payload in your HTTP POST, PUT, or DELETE request, in the Payload (Optional) section:
   1. Select a MIME Type from the dropdown list.
   2. Select an encoding scheme for the payload from the dropdown menu. Only UTF-8 and ISO_8859-1 are supported.
   3. If you have configured custom variables, enter the payload details. The payload body is pre-filled if you have selected a specific endpoint in the action template.
7. (Optional)To configure how HTTP responses are handled, in the Response Handling Criteria (Optional) section:
   1. To configure a failure criteria, in the Failure Criteria section, click + Add Failure Criteria. 
      1. Select a status code from the dropdown list.
      2. If you expect a payload for your request, select the Expect payload checkbox.
      3. Select the content type for the payload from the dropdown list.
   2. To configure a success criteria, in the Success Criteria section, click + Add Success Criteria. 
      1. Select a status code from the dropdown list.
      2. If you expect a payload for your request, select the Expect payload checkbox.

      3. Select the content type for the payload from the dropdown list.

         

         If you do not specify any response-handling criteria for either success or failure, the HTTP response is always success. 

8. (Optional)To configure timeouts and redirects for your HTTP request, in the Settings (Optional) section:
   1. Enter the maximum number of milliseconds to wait for the request to reach the server in Connect Timeout.
   2. Enter the maximum number of milliseconds to wait to receive the response in Socket timeout.
   3. Enter the maximum number of times that a single request can redirect in Max Redirects.
9. Click Test to simulate the action or click Save to save the action.

Test an HTTP Action

Before you save an HTTP action, we suggest making sure your endpoint settings are correctly configured and the HTTP action is working instead of waiting for an actual violation to occur.

To test an HTTP action to a configured endpoint:

1. Follow the preceding steps to create an HTTP Action.
2. Click Test.

You get a success or failure message along with the status code that helps you to debug any issue.

Custom Variables 

When you select an action template, you need to enter the values for the following custom variables:

This document contains references to third-party documentation. Cisco AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Edit an HTTP Action

1. Click Configure > HTTP Request Actions. 
2. Click the name of the desired action to access the wizard.
3. Edit the configuration.
4. Click Save.