The Actions tab shows a breakdown of the action(s) that will be taken when an alert is triggered and the escalation is executed. Actions will be executed in sequential order until the triggered alert condition no longer exists. At that point, everything is reset. If the same alert is triggered again, the escalation will start to execute its actions from the beginning of its list. When you add actions, you have the ability to repeat the action every 'n' minutes or wait before the next action is executed (escalate after 'n' minutes). For example, you may want to keep sending your SysAdmin email every 10 min and only escalate to the 'scale up' action after 30 min, which would give him 30 min to investigate the deployment before autoscaling can take place.
If you add multiple actions, you can define whether an action should be "added" to the prior action or "replace" the prior action. You cannot change the order of the listed actions. You must simply delete and create new actions.
The supported actions are:
Design > Alert Escalations > Show > Actions tab
send_email - Send email to one or multiple recipients.
reboot_server - Reboot the server generating the alert.
relaunch_server - Relaunch the server generating the alert (this terminates the current instance and launches a fresh instance).
run_right_script- Run a RightScript on the server generating the alert.
vote_grow_array - The server is voting to grow or 'scale-up' by launching additional servers into the server array that's attached to the deployment. It is only a vote; not a trigger to launch servers. Additional servers will not be launched unless enough servers are voting for the 'vote_grow_array' action. The server array's scaling parameters will ultimately determine when to scale (e.g. >51% are voting) and how to scale (e.g. Launch '2' new servers into the array). Note: The array must be active (enabled) in order for any scaling to take place.
vote_shrink_array - The server is voting to shrink or 'scale-down' by terminating underutilized servers from the array that's attached to the deployment. It is only a vote; not a trigger to terminate servers. Underutilized servers will not be terminated unless enough servers are voting for the 'vote_shrink_array' action. The server array's scaling parameters will ultimately determine when to scale (e.g. >51% are voting) and how to scale (e.g. Terminate '1' server from the array). Note: The array must be active (enabled) in order for any scaling to take place.