AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

A custom action is typically used to integrate third party alerting and ticketing systems with an on-premise controller. Custom action scripts are not supported on SaaS controller. A custom action is different from other actions in that it executes just once on the on-premise controller instance.

The custom action is made up of a custom action script and a custom.xml file, which you must create before you can create an action that uses them. The custom action scripts include parameters for specifying the affected entity, for example the tier, node, business transaction, etc. See Build an Alerting Extension for details on how to create the custom action script and xml file.

Custom actions are commonly used when you want to trigger a human work flow or leverage an existing alerting system that is external to AppDynamics. For example, you could use a custom action to file a JIRA ticket when AppDynamics reports that a connection pool is near saturation.

If you are using a SAAS controller, you may be able to use a remediation action on a local node to accomplish similar results. See Remediation Actions for more information.

To Create a Custom Action

After the custom action script and custom.xml files have been tested manually and installed on the Controller and you have restarted the Controller, you can create the custom action.

1. Follow the instructions in To create an action, selecting Automation->Run any custom action that has been uploaded to the controller in the Create Action window.
2. Enter a name for the action.
3. Select the custom action from the dropdown list.
4. Click OK.

The custom action is now available for assignment to a policy.

Learn More

1 Comment

  1. Unknown User (tdepuy@xmatters.com)

    "Custom action scripts are not supported on SaaS controller"

    But then:

    "If you are using a SAAS controller,..."

    Are custom action scripts supported for SaaS instances at all?

    Can you clarify what this means:

    " A custom action is different from other actions in that it executes just once on the on-premise controller instance"

    Just once per alert? How is that different from otherwise?