Predicates

This page lists all predicates defined for the selected Policy.

Predicates list

• Each row represents a single predicate with concise metadata:
  • Name: predicate identifier (click to open predicate detail).
  • Enabled: toggle to enable or disable the predicate evaluation.
  • Notify: toggle to enable or disable notifications for this predicate.

Behavior

• Disabling a predicate prevents the evaluation engine from running that predicate and stops new issues from being created by it.
• Disabling notifications suppresses alerting for failures; issues are still created and tracked, but no notifications are sent for those events.

Controls and actions

• Click the predicate name to go to the predicate details page
• Use the inline toggles to quickly enable/disable predicates or notifications.

Usage tips

• Use the Notifications toggle to mute noisy predicates while retaining the audit trail of issues.
• Disable a predicate only when you are certain the check is irrelevant or will cause false positives; prefer tuning thresholds where possible.

Overrides and defaults

• Predicates use shared default values for thresholds, enabled state, and other properties. All organizations inherit the same defaults but may override them as needed.
• Overrides can be applied at two scopes:
  • Global: applies everywhere the predicate is used.
  • Scoped: applies to a specific combination of instance, database, object, group, or tag. For example, an override on a tag affects all instances that have that tag; an override on a specific SQL instance affects only that instance.
• Changing any predicate property (including disabling it) counts as an override because the predicate’s effective configuration differs from the shared default.
• Predicates that have overrides are shown beneath the original unmodified predicate. Overrides are highlighted (orange text) to distinguish them from the default predicate rows (green).
• When an override is scoped to instance/database/object/group/tag, the override row displays the scope information so you can see exactly where the change applies.
• To remove an override and revert to the default behavior, use the delete icon on the right of the override row. Deleting the override restores the predicate to the shared default values.

Exclude from evaluation via an issue

• The “Exclude” action available on an Issue creates the same kind of override described above. When you open the Exclude dialog from an Issue you are setting the predicate’s enabled state to off for the scope you select.
• The dialog presents checkboxes for scope selection: instance, database, object, group, and tag. Selecting one or more scopes creates a scoped override (enabled = off) that prevents the predicate from running for that specific combination.
• Excluding from an Issue can optionally close all matching open issues for the selected scope; the override itself is recorded and shown under the predicate (highlighted in orange).
• Exclusions are reversible: delete the override row to restore the default behavior, or edit the override to change its scope or enabled state.