Hi, This extension will not work for many cases. You cannot hard code the argument index. The number of arguments is a factor of NUMBER_OF_EVALUATION_ENTITIES and NUMBER_OF_TRIGGERED_CONDITIONS_PER_EVALUATION_ENTITY. Please see this documentation for more details https://docs.appdynamics.com/display/PRO42/Build+a+Custom+Action. Please take a look at pagerduty alerting extension as a sample. https://github.com/Appdynamics/pagerduty-alerting-extension We use a common library to parse these arguments. Once you get an idea from the pagerduty-alerting-extension you can download this common library from here https://github.com/Appdynamics/maven-repo/tree/master/releases/com/appdynamics/appd-exts-commons/1.6.4 and use it in your code. Other option is for you to replicate the code that we have in your own codebase. Thanks, Kunal
... View more
AppDynamics extensions are divided into three broad categories: Monitoring extensions, Alerting extensions, and Cloud Connector extensions.
These extensions run as monitors on AppDynamics Machine Agent and report metrics from an artifact to AppDynamics Controller.
Examples of these are Cassandra Extension and Memcached Extension.
A guide to building monitoring extensions using Java and Shell Scripts can be found in the product documentation here and here respectively.
These extensions are integrations that run as custom actions on the AppDynamics Controller.
Most of these alerting extensions work only for dedicated (single-tenant) SaaS Controller or on-premises Controllers.
Examples of these are PagerDuty Extension and VictorOps Extension.
Cloud Connector Extensions
These extensions enable custom implementations of orchestration functionalities such as creating, destroying, restarting, configuring, and validating machine and image instances directly from the AppDynamics Controller user interface.
Example of this is AWS Cloud Connector Extension.
A guide to building cloud connector extension can be found here.
Find more information in the AppDynamics Exchange.
... View more