A remediation script is run on the machines that you specify in the remediation script configuration. You can run the script from the machine affected by the violation that triggered the action or from a central management server. It is not necessary for an app agent to be running on the machine on which the script executes, just a machine agent.
Watch the video:
The following remediation action, named increasePool, executes a local script named runbook.sh, which increases the size of the connection pool on the JVM.
When a remediation action is triggered by a backend discovery event, if the backend is not resolved quickly the policy will not start the local script.
Watch the Video