Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
03-10-2017 08:01 AM
Hi,
I'm trying to set up custom action - https://docs.appdynamics.com/display/PRO42/Build+a+Custom+Action
In the "Definitions of Parameters Sent by a Health Rule Violation" i see
NUMBER_OF_TRIGGERED_CONDITIONS_PER_EVALUATION_ENTITY |
number of times to loop through the triggered condition parameters for each evaluation entity; if more than one condition is triggered, the parameters repeat for each triggered condition, where "x" is the position of the condition |
What exactly is the "position of the condition" here refers to? How do we use parameters like THRESHOLD_VALUE_x, OBSERVED_VALUE_x etc.,
Could you please give some examples? I basically need to handle this parameter in a custom script.
Regards,
Sundar
03-13-2017 10:22 AM
03-13-2017 03:08 PM
Hi Sundar, I'm still working on getting an example for you, but in the meanwhile, you may find it helpful to review sample script that processes an event. See https://github.com/bnagallo/ExportParams-AppD
The way that the doc puts it, "where "x" is the position of the condition", isn't quite clear.... As I read https://github.com/bnagallo/ExportParams-AppD/blob/master/appd_alert.sh, those values (i.e., $CONDITION_NAME_x, etc) are accessed by parameter position in the list of parameters passed by the Controller when calling the scipt.
The sample script checks the number of triggered conditions, and cycles through the parameters by incrementing position reference (CURP). So with two conditions, the first THRESHOLD_VALUE_x would be accessed at parameter position 28, roughly and the next one at around 40 or so.
As I say, I'll try and get confirmation on this for you, along with a sample.
User | Count |
---|---|
4 | |
4 | |
3 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form