Alerts Manager

The Alert Manager shows detailed information about all of your alert specifications. Alert specifications and escalations are used to automatically take actions on a deployment on your behalf if certain user-defined conditions are met that trigger an alert. Alerts are commonly used with Server Arrays in order to set up autoscaling.

Set up your alert specifications and escalations under Design > Alerts. See Alerts.

Tab Views

Overview - Lists the 10 most recent server alerts.
Active - Lists all of the alerts that are currently active and voting for a particular escalation.
All - A list of all servers that have alerts that are being monitored.

Overview

This tab provides a high level overview of the alert conditions of your running servers and displays the most recent alert conditions.

Enabled - The number of running servers that are currently being monitored. (i.e. alerts are enabled)
- In the example below, there are 94 active servers with alerts enabled, which are being monitored for triggered alerts. Currently, there are 4 alerts. Remember, since each server can have multiple alerts, there could be one server with 4 alerts or there could up to 4 servers with alerts.
Quenched - Servers who have had their alert silenced.
Inactive - The number of running servers that have alerts, however the servers are not being monitored for alerts. (i.e. alerts are disabled)

Active

The Active tab shows all of the alerts that are currently active and voting for a particular escalation, as well as how long the alert has been continously triggered. Remember, the configuration settings of your server array will ultimately determine how the alerts will be handled in order to prevent one "problematic" server from accidentally resizing the array. The percent that you define for the "Decision Threshold" will determine how many servers must be voting to resize an array before any action is taken. For instance, in the example below, the alerts have been voting for 22 days, yet no action has been taken because the decision threshold has been set to 51%. Therefore, in this example, 48 servers must be voting for the same alert escalation (ex: "lamark_vote_scale_down") before any action is taken.

See Server Arrays.

All

The All tab lists all servers that have alerts enabled. Each server in the list is currently being monitored, regardless of whether or not the server is operational.