Hi,
Hi,
Thanks for posting back, Yes, your understanding is right if you are using saas controller then you cannot configure custom-actions as you might not have access to the saas controller physical machine,
However you can run local scripts using local machine agent as suggested in docs http://docs.appdynamics.com/display/PRO13S/Remediation+Actions#RemediationActions-PrerequisitesforLo...
Let us know if that helps
Please find the updated links:
http://docs.appdynamics.com/display/PRO13S/Custom+Actions
http://docs.appdynamics.com/display/PRO13S/Remediation+Actions
Thanks,
Arun
Hi,
Thanks for writing in. We would like to clarify that the custom actions are executed by controller and should be integrated under <controller_install_dir>/custom/actions as stated in docs
http://docs.appdynamics.com/display/PRO13S/Build+an+Alerting+Extension
Custom actions are not supoorted and will not be executed by appserver and machine agent and integration custom actions under appserver agent and machine agent install directories will not help.
Also we understood that you have followed the docs listed above and we see doc bug in the same custom.xml syntax:
Can you please configur custom actions as per docs with the custom.xml updated as follows:
make sure that you have executable permissions to test.sh and have configured custom notifications as per docs, you need to configure alert(health rule, or automation task) so that on violation/execution of the corresponding alert your custom action will get executed.
We do have feature to execute a local script using machine agent by configuring remediation actions as stated in docs:
http://docs.appdynamics.com/display/PRO13S/Custom+Actions
http://docs.appdynamics.com/display/PRO13S/Remediation+Actions, let us know if that helps
Let us know how it goes after making above changes, Do write back to us for further assistance
Thanks,
Arun
Hi Arun,
Thanks for the response. So as I understand, if I want to use Saas tool I will not be able to create custom actions?
Also the last couple links don't work, can you repost them?
Hi,
Thanks for posting back, Yes, your understanding is right if you are using saas controller then you cannot configure custom-actions as you might not have access to the saas controller physical machine,
However you can run local scripts using local machine agent as suggested in docs http://docs.appdynamics.com/display/PRO13S/Remediation+Actions#RemediationActions-PrerequisitesforLo...
Let us know if that helps
Please find the updated links:
http://docs.appdynamics.com/display/PRO13S/Custom+Actions
http://docs.appdynamics.com/display/PRO13S/Remediation+Actions
Thanks,
Arun
Configuring remediation actions worked for me, thanks 🙂