Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Dashboard Users Guide > Design > Alert Escalations > Actions > Create a New Alert Escalation

Create a New Alert Escalation

Objective

Create an example Alert Escalation for scaling down a Server Array.

Table of Contents

Overview

Get a quick synopsis of Alert Escalations (and other types of alerts with respect to the RightScale Dashboard) here.

Steps

Create the new Alert

Go to Design -> Alert Escalations and click New.

screen-NewAlertEscalation-v1.png

Provide the following information for each alert escalation.

  • Name – A short nickname that helps you recognize the alert escalation. 
  • Description – A short description of the alert escalation (for internal use only).
  • Deployment - Select a specific deployment where you will be able to select the alert escalation. By default the escalation will be available to "all deployments."

 

Define Alert Actions

The next step is to define what actions should be taken when an alert escalation is called.  The most common actions are already configured for your convenience.  Under the Actions tab, select which action you would like to add.   See Valid Actions for Alert Escalations for a detailed breakdown of each supported  action.  Add as many actions to an escalation as necessary.  For example, you can create a series of actions to define an escalation process for a persistent problem.

Note: The 'vote_grow_array' and 'vote_shrink_array' actions will soon be deprecated. To set up autoscaling, please use tags instead. See Set up Autoscaling using Voting Tags.

screen-SelectAction-v1.png

In the example below, an email will be sent every 15 minutes to the system administrator.  If the condition continues to persist without change for 60 minutes, the next action will be triggered (Ex: An email to the CEO).

screen-DefineEmailAction-v1.png

  • Prior actions - If there is more than one action for an alert escalation, you can define whether this action should be "added" to the prior action or "replace" the prior action.  Currently, you cannot change the order of the listed actions.  You must simply delete and create new actions.
    • add - This action will be "added" to the prior action.  The previous action will continue to run.
    • replace - This action will "replace" any prior actions.  The previous action(s) will stop running.

 

screen-ListofActions-v1.png
 

Missing Inputs on Relaunch

In the examples above, the alert action was to send an email.  Relaunching a server is among several other possible alert actions.  The following discussion details how the Dashboard has embedded intelligence so that you don't try to relaunch a Server with missing Inputs.

When adding a "Relaunch Server" action to an Alert Escalation, there is a check to see if this escalation is connected to a server with missing Inputs. If so, a warning will be displayed to inform the user that in order to automate the relaunching of a server, its Input parameters must be fully specified.  A warning message will appear when the input's check fails when clicking adding the 'relaunch_server' action.

 

Similarly, when adding an Alert Specification to a Server or ServerTemplate, there is a check to see if the Server (or a Server derived from a ServerTemplate) has missing Inputs. If so, a flash message is displayed to inform the user that in order to automate the relaunching of a server, its Input parameters must be fully specified.  A flash warning message will appear when the Inputs check fails when clicking the "Attach" button from a selected Alert Specification (that includes a relaunch) from Manage -> Servers -> ServerName -> Alerts Tab 

You must to post a comment.
Last modified
09:29, 12 Nov 2013

Tags

Classifications

This page has no classifications.

Announcements

None


© 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.