Overview
An alert (specification) defines the conditions under which an alert is triggered and an Alert Escalation is called or a Voting Tag is set. Several of the most common alerts have already been predefined for your convenience and are already included in many of RightScale's ServerTemplates. You can either create a new alert from scratch (see Create a New Alert Specification) or copy an alert (see Copy an Alert Specification). To create your own custom alerts, see Create a Custom Alert Specification.
An alert must be defined at either the ServerTemplate, Server, or Server Array levels.
The ability to add an Alert Specification (new / copy alert) is only supported under the following conditions.
- Current/Next Server (
Alerts
tab) - Enabled Server Array (
Next Alerts
tab only) - Disabled Server Array (
Alerts
tab) - HEAD ServerTemplate (
Alerts
tab)
When you create an Alert Specification you can associate it with either an Alert Escalation or Voting Tag. You can only assign one Alert Escalation or Voting Tag to an Alert Specification. However, you can create multiple alerts that monitor the same metric and then call for a different Alert Escalation. Similarly, you can have multiple alerts that call the same alert escalation. For example, you might have several alerts that point to the 'default' Alert Escalation.
A Server inherits its Alert Specifications from the ServerTemplate and Server Array (if applicable). Alerts can also be added at the Server level. Once a Server is launched, the instance that's configured in the cloud will contain all Alert Specifications and its Voter Tag will be set (if applicable).
In the following diagram, the Server inherits 3 Alert Specifications from the ServerTemplate and Server Array levels. An additional Alert Specification is also defined at the Server level. So when the Server is launched and an instance in the cloud is created, all of the Server's Alert Specifications will be monitored. In this example, the monitored Server is part of a scalable alert-based Server Array. Therefore, it will be allowed to vote for scaling actions based on a 'cpu' metric, so a related Voter Tag will be assigned (rs_vote:MyArray=none).
Alert Specifications can still be added to a Server (Instance) once it's operational under the Current Server's Alerts tab.
