A custom action is typically used to integrate third-party alerting and ticketing systems. A custom action differs from other actions on its singular execution on the controller instance.

The custom action is made up of a custom action script and a custom.xml file (you must create the file before you create an action that uses them). The custom action scripts include parameters for specifying the affected entity, for example, the tier, node, business transaction, and so on. See Build a Custom Action 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 workflow or leverage an existing alerting system that is external to Splunk AppDynamics On-Premises. For example, you could use a custom action to file a JIRA ticket when Splunk AppDynamics On-Premises reports that a connection pool is near saturation.