Returning Customers — Login
Call 1.866.720.0208 or contact us
Table of Contents
An alert escalation defines the action or set of actions to be taken when specified alert conditions are met. Unlike alerts which are specific to a Server or ServerTemplate, Alert Escalations can be designated to a specific Deployment or made available to all Deployments. By default, you must associate an Alert Escalation when you define the monitored alert condition.
An alert must be enabled on a server in order for the server to monitor for a condition and vote for an Alert Escalation. Alert conditions are evaluated every minute. When enough servers are voting for the same alert, the associated alert escalation will be executed until the alert has been satisfied.
An alert is triggered whenever its conditions are met, as well as the associated array's scaling parameters, when applicable. For example, if more than 51% of the servers that are monitoring for the same alert are experiencing 'Condition A' for longer than 15 minutes (alert threshold), then call Alert Escalation B, which will execute its defined action(s) such as sending an email to the SysAdmin or voting to "scale up" by adding servers to the array. Once an alert condition no longer exists, the Alert Escalation will stop and no more actions will be taken. At that point, everything is reset. If the same alert is triggered again, the Alert Escalation will start to execute its actions from the beginning of its list. Note: An array must be active in order to enable scaling.
Action Buttons
List of supported actions inside an Alert Escalation:
Note: The "vote to grow/shrink array" options will soon be deprecated. Autoscaling is now performed using voter tags.
Design > Alert Escalations > Index