The alarm has been cleared

Take action when the alarm severity returns to Normal.

The alarm has existed for more than…

Take action when the alarm severity has been other than Normal for a specified period of time.

You define the period of time in hours, minutes or days. For example, take action when the alarm severity has been other than normal for 5 days.

The alarm hasn’t been acknowledged within…

Take action when an alarm requiring acknowledgment has not been acknowledged for a specified period of time.

You define the period of time: in hours, minutes or days.

This condition is applicable to alarms requiring acknowledgment. Alarms are configured to require acknowledgment from Configure Alarms.

The alarm is…

Take action when the specified alarm is raised. If an alarm is not specified this rule applies to all alarms.

Note the option to select “is” or “is not”. Where “is not” is selected, take action for any alarm raised except the specified alarm.

When combining with ‘The connection is’ condition the connection types must match.

The alarm severity is…

Take action when the alarm severity changes to one of the following: Information, Low, Medium or High.

The connection is…

Take action when the alarm is raised against the specified connection(s).

Note the option to select “is” or “is not”. Where “is not” is selected, take action when the alarm is raised on any connection except the connection specified.

Refer to the guidelines where ‘the connection is…’ condition is used in a deployment with multiple alarm action rules. The guidelines are designed to support a smooth running system.

The connection type is…

Take action when an alarm is raised against the specified connection type(s): Hyper-V, SQL Server, VMware, Windows.

The connection’s tag is…

Take action when an alarm is raised against a connection with matching connection tag name.

This condition is appropriate if your organization has defined tags for Spotlight connections. Tags are a free form organizational tool that may be optionally applied to Spotlight connections. Tag names represent a project, geographic region or other indicator of interest to you and your organization. Multiple tags can be assigned to one connection. In the Modify Criteria dialog, use the drop down menu to select from tags currently assigned to connections on the Spotlight Cloud Diagnostic Server. For more information on tags, see Connection Tags.

The date is…

Take action when the alarm is raised on the specified date.

Note the option to select “is” or “is not”. Where “is not” is selected, take action when the alarm is raised on any date except the specified date. For example, you may want no action taken on a scheduled public holiday.

Where multiple timezones are involved, the date is as per the date on the Spotlight Cloud Diagnostic Server.

The day of the week is…

Take action when the alarm is raised on the specified day(s) of the week. For example, act on this rule when the alarm is raised on a Monday, take no action on this rule when the alarm is raised on any other day of the week.

Where multiple timezones are involved, the day of the week is as per the day on the Spotlight Cloud Diagnostic Server.

The details contain…

Take action when the Details column of the raised alarm(s) contains (or does not contain) one or more specific phrases.

The Details column is as per the text displayed in the Details column of the Alarm log when the alarm is raised. To customize this text, see Configure Alarms.

The Diagnostic Server is…

Take action when the Spotlight Cloud Diagnostic Server is as selected.

The time of day is between…

Take action during the specified time frame. For example, take the actions associated with this rule when the alarm is raised between 6:00pm and 6:00am. Take no actions associated with this rule outside of that time frame.

Where multiple timezones are involved, the time of day is as per the time on the Spotlight Cloud Diagnostic Server.