Valid Actions for Alert Escalations

Send Email

Action name: send_email

You can send an email to one or multiple recipients.   Email field supports space-, comma- or semicolon-separated list of email addresses.

There are three different types of email formats.

• detailed email message - Standard email format with Subject and Message.
   
• short TXT message - Designed for sending short SMS/MMS text messages to cell phones.  Enter the phone number in a valid SMS string into the Email field.  e.g. 18052224444@vtext.com  (Verizon)  See FAQ 105 - How do I text message an alert?
   
• parsable message - Designed for auto responders.  A server will receive the email message and 'parse' a response.  (See example below)

Example of Parsable Message

subject: alert: 'My cool server' My sweet alert spec

message: Server Name: My super server,
Server Href: http://my.rightscale.com/api/acct/0/servers/0,
Deployment Name : My awesome deployment,
Deployment Href: http://my.rightscale.com/api/acct/0/deployments/0,
Account Name: My account name,
Cloud: 1,
Alert Name: My sweet alert spec,
Alert Time: 2009-11-21 00:00:42,
Alert Spec Input: cpu-0/cpu-idle,
Alert Spec Metric: value,
Alert Spec Condition: >,
Alert Spec Target Value: 60,
Alert Spec Duration: 5

Reboot Server

Action name: reboot_server

Reboot the server generating the alert.  Equivalent to rebooting the same physical machine.  i.e. The Server will maintain its Instance ID.

Relaunch Server

Action name: relaunch_server

Relaunch the server generating the alert (this terminates the current running instance and launches a fresh instance).  i.e. The Server will receive a new Instance ID.

Run RightScript

Action name: run_right_script

Run a RightScript on a server. 

• Repeat every - Enter a positive integer greater than zero (valid range: 1 - 10,000,000) to repeat this action every n minutes. Leave the field blank to run the script once.
• Prior actions - This value is only applicable if a prior action already exists.
  • add - Add the current action to any previously running actions. (i.e. Continue executing any previous actions and run this action too.)
  • replace - Replace any previously running actions with this action. (i.e. Stop performing any previous actions and run this action.)
• Escalate after - Defines how many minutes must pass before executing the next action in the list. Enter a positive integer greater than zero (valid range: 1 - 10,000,000) 
• Execute on server - If the Alert Escalation is available across all deployments in the RightScale account, you can only execute the script on the server that raised the alert. However, if you were explicit when you created the Alert Escalation and only made it available for use inside of a specific deployment, you will also have the option to execute the script on another server in the deployment.
  
  You can only run the script on a single server. To run the script on another server you must create another action. Only servers that currently exist in the deployment will be listed. You cannot execute the script on any instances in an associated array.
• RightScript - Select the RightScript to be executed on the server. All RightScripts available within the RightScale account will be listed. All committed revisions as well as the HEAD version of the script will be listed.

Vote to Grow the Server Array (scale-up)

Action name: vote_grow_array

WARNING: This action will soon be deprecated.  Please see Set up Autoscaling using Voting Tags.

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 to Shrink the Server Array (scale-down)

Action name: vote_shrink_array

WARNING: This action will soon be deprecated.  Please see Set up Autoscaling using Voting Tags.

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.