Alert Rules

Alert Rules define exceptions to standard alert behavior. Each rule targets a specific alert type and applies to one or more Profiles or Resources. Rules can suppress an alert entirely, or override individual settings — such as severity, tolerance, or notification channels — without changing the underlying alert configuration.

Alert Rules Table

The Alert Rules screen displays all configured rules in a sortable table.

Note: Click any column heading to sort the table in ascending or descending order. Use the magnifying glass icon at the top-right corner of the card to search existing rules.

Click the action icon (three dots) at the end of any row to View, Edit, Enable, or Delete the rule.

Creating or Editing an Alert Rule

Click [+Rule] to create a new rule, or click the action icon on an existing rule and select Edit Rule. Either action opens the New/Edit Rule flyout.

Name and Alert Type

Scope

Scope defines where the rule applies — either across one or more Profiles or against specific Resources. You may select one or many under either option, but not both in the same rule.

Tip: When you need both broad and targeted coverage, create two separate rules — one scoped to a Profile using a wildcard pattern, and one scoped to specific Resources with individual selections.

Level

The Level field appears for alerts that support escalation levels. It controls which level or levels the rule applies to.

Alerts configured in Advanced Mode in a Profile can have up to three escalation levels, each with its own severity and tolerance. Level 1 is the most relaxed setting; each subsequent level must be configured with a stricter threshold. For example, a Low Disk Space alert might be configured as:

Use the Level field to target the rule at a specific level, a selection of levels, or all levels.

Note: If an alert has not been configured with multiple levels in the Profile, only Level 1 will be available. See Profiles for more information on configuring escalation levels.

Objects

The Objects field appears only after a scope has been selected, and only for alert types that support object-level targeting — such as SQL Server Agent Job Failed (Jobs) and Low Disk Space (Disk/Mount Point). It does not appear for alerts that apply at the instance or host level with no finer granularity.

The Objects dropdown is populated based on the instances in your selected scope. You can select individual objects, use wildcard patterns, or combine both in the same rule.

Using wildcards

Type a pattern into the search field using the percent sign (%) as a wildcard character, then click Add Object to add it to the rule.

You can add multiple wildcard patterns and individual selections to the same rule. The badge on the Objects dropdown reflects the total number of objects currently added. All wildcard patterns apply across every instance in the selected scope.

Tip: Select All current and future objects to automatically apply the rule to any matching object — including newly created ones — within the selected scope.

Rule Behavior

The Ignore Alert toggle controls what the rule does when its conditions are met.

When Ignore Alert is off, the following override fields are available:

Saving the Rule

Click [Save] to create the rule or commit edits and return to the Alert Rules screen.

Related Topics

• Alerts
• Notification Channels
• Profiles
• Silencing Windows