An alert escalation defines the action or set of actions to be taken when specified alert conditions are met. Each alert escalation can have a series of actions that are executed in sequential order until the alert condition no longer exists. By default, you must associate an alert escalation when you create an alert. Because of this requirement, you must create an alert escalation before you create an alert (unless you use one of our predefined alert escalations). See Create an Alert Escalation.
Alert Escalations are either assigned to a specific deployment or they are made available to all deployments. (As shown by the labels "Deployment - A" and "All Deployments" in the following illustration.) Once an Alert Escalation is assigned to a deployment, all servers within that deployment can use that alert escalation when creating an alert specification.
Each alert escalation is comprised of a series of one or more actions. An alert escalation defines which actions are performed in response to a triggered alert condition. Actions are executed in sequence as long as the alert exists. If the alert goes away and then returns again, the actions are processed again in sequence from the beginning of the list.
The following actions are supported:
* The vote to grow/shrink actions will soon be deprecated. Please use Voting Tags instead for configuring a scalable Server Array. See Set up Autoscaling using Voting Tags.
For detailed descriptions about each action, see Valid Actions for Alert Escalations.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.