AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    The information on this page is intended for On-Premise deployments only. SaaS deployments are managed by AppDynamics.

    Related Pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    28 rates

    This page provides an overview of custom actions in AppDynamics.

    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 AppDynamics. For example, you could use a custom action to file a JIRA ticket when AppDynamics reports that a connection pool is near saturation.

    Create a Custom Action

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

    To create a custom action:
    1. Access the Create Action window. See Create and Modify Actions in Actions.
    2. Select Run a Custom Action that has been uploaded to the Controller.
    3. Click OK.
    4. Enter a name for the action.
    5. Select the custom action from the dropdown list. All the custom actions you have created are listed here.
    6. Click Save.

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

    Disabling Custom Actions on a Multi-Tenant Controller

    Because a custom action script has access to the Controller file system, you may decide to disable this functionality in a multi-tenant environment for security reasons.

    To disable custom actions:
    1. Open the Controller admin console.
    2. Go to Controller Settings.
    3. Search for the aas.multitenant.custom.action.local.execution.enabled property.
    4. Set to false.
    5. Click Save.

    • No labels