Copyright (c) 2006-2014 MindTouch Inc.
This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).
At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.
A complete copy of the MSA is available at http://www.mindtouch.com/msa
To create a new Alert Specification from scratch.
Table of Contents
An Alert Specification defines the conditions under which an alert is triggered and an automated action or set of actions take effect. Alert Specifications can either be tied to an Alert Escalation or a Voting Tag (for autoscaling purposes). To learn more about how Alert Specifications can be used, see RightScale Alert System.
Alert Specifications can be defined at either the ServerTemplate, Server Array, or Server levels. It's important to understand where a Server can inherit its Alert Specifications from so that you can define them in the proper location and manage them appropriately. See Alert Specifications for details.
An Alert Specification is defined the same way, regardless of where it's defined.
Depending on where an Alert Specification is defined (ServerTemplate, Server Array, Server), go to its Alerts tab. At this point you have two options:
Note: An Alerts tab also exists at the Dashboard level (Manage -> View Dashboard) or at the Deployment level (Manage -> Deployments -> YourDeployment), but those tabs show an overview status page of all active and triggered alerts across all Deployments or a single Deployment, respectively.
Click the New button, then provide the following information to create a new Alert Specification.
Note: The "warning" Alert Escalation dictates which action(s) are taken once the alert is triggered. Example: If "cpu-0/cpu-idle" falls below 25% available (< 25) for 30 minutes, then execute the "warning" Alert Escalation.
The df and swap alert specification metrics offer the ability to specify the following human readable options when defining the alert specification:
Megabytes (MB) - Defined as 10242 Bytes
Gigabytes (GB) - Defined as 10243 Bytes
An example screenshot showing these options shown here:
Note: After saving an alert specification, the human readable specification will be convert and will always show its value in Bytes.
After an alert is triggered (and the first email is sent), any changes made to the Alert Specification will be ignored. You must disable the alert, make any necessary changes, and then re-enable it in order for the new settings to take effect. For example, you set an alert stating that "if cpu-0/cpu-idle.value is > 10 for 10 minutes" in order to send an escalation. You receive the escalation email and decide the threshold is too low. You change it to "if cpu-0/cpu-idle.value is > 10 for 20 minutes" but you do not disable it. The threshold will remain at 10 minutes until you disable the alert and then re-enable it with the new threshold setting.
|Glossary | 用語 | 용어||Site Map | Site Help||Community||Corporate Site||Get Support||Dashboard Login|
|Doc Feedback||Product Feedback||Resources||MultiCloud Marketplace||Forums|
© 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.