Alert Escalations

Overview

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, ServerTemplate, or Server Array, Alert Escalations can be designated to a specific Deployment or made available for use across all Deployments.

An alert must be enabled on a server in order for the server to monitor for a condition and call an Alert Escalation. Alert conditions are evaluated every minute. When an alert that is tied to an Alert Escalation is triggered, the actions of the associated escalation will be executed until the alert condition no longer exists or it's disabled. You can also override an Alert Escalation by creating one with the same name in order to override the account-wide escalation with one that is deployment-specific.

Action Buttons

• New - Create a new Alert Escalation.

List of supported actions inside an Alert Escalation:

• send_email - Send email to one or multiple recipients.
• reboot_server - Reboot the server instance generating the alert.
• relaunch_server - Relaunch the server generating the alert (this terminates the current instance and launches a fresh instance).
• run_right_script - Run a RightScript on the server instance generating the alert.
• vote_grow_array - Vote to grow a server array attached to the deployment in which the alerting server is running. (This option will soon be deprecated. Use Voting Tags instead.)
• vote_shrink_array - Vote to shrink a server array attached to the deployment in which the alerting server is running. (This option will soon be deprecated. Use Voting Tags instead.)

Note: The "vote to grow/shrink array" options will soon be deprecated. Autoscaling is now performed using voter tags.

Actions

Concepts

Show Tabs

See also

• Alerts, Alert Escalations, and Server Arrays
• Create an Alert Specification
• Create a Custom Alert Specification
• Set up Autoscaling using Voting Tags

Related FAQs