Alert states
Prizm uses three alert states:Suppressed is not an alert state. When an alert is inside a suppression window, it remains Active but notifications are paused. A note is added to the alert history. See Suppression below.
Marking an alert as Normal
Use Mark as Normal when the alert has been reviewed and no remediation is needed — for example, a known data pattern or an accepted deviation that does not warrant a tracked issue.- Open the alert detail page.
- Click Mark as Normal.
- Enter a note explaining the decision (required).
- Save. The alert closes with your note recorded in the audit trail.
Mark as Normal is not available for metrics using a manual (Limit) threshold. For those alerts, the only states are Active and Resolved.
Resolving an alert
Automatic resolution — When the metric that fired the alert runs again and the result is back within the configured threshold, Prizm automatically resolves the alert and records the resolution timestamp. Auto-resolution fires within one evaluation cycle of the metric recovering. Manual resolution — Open the alert and click Resolve. A resolution note is required (minimum 10 characters). The note is stored in the audit trail and visible to other users. All state transitions are recorded in the audit trail with the acting user, timestamp, and reason.Issue linkage
An alert can be linked to a Prizm issue to track remediation formally:
Once linked:
- The alert and issue link back to each other.
- If Jira or Azure DevOps integration is configured, Prizm issue creation cascades to a Jira ticket or ADO Work Item automatically.
- When the alert resolves (auto or manual), the linked Prizm issue is updated to Resolved if not already closed.
- When the linked issue is resolved, the associated alert is updated to Resolved — propagation works in both directions.
An alert cannot be in Resolved and Active states simultaneously. The state machine prevents invalid transitions.
Alert suppression
Alert suppression pauses notifications for a defined window or scope. Metric checks continue to run as normal — threshold breaches are still detected and recorded in the audit log. Only the notifications are paused.Suppression modes
Maintenance windows
A maintenance window suppresses notifications for a specific asset, schema, or source during a scheduled period.- Scope: asset, schema, or entire source connection
- Schedule: one-time (specific start/end) or recurring (e.g., every Saturday 02:00–06:00)
- Overlapping windows on the same scope are merged — the effective suppression covers the union of all configured windows
- All breaches during the window are still written to the audit log with a suppression note
- When the window ends, alerts re-fire normally if the metric is still breaching
1
Navigate to the asset or source
Open the asset, schema, or source connection you want to configure suppression for.
2
Open Suppression settings
Go to Settings → Alert Suppression for the asset or source.
3
Add a maintenance window
Click Add Maintenance Window and configure scope, schedule type (one-time or recurring), start/end times, and a reason note.
4
Save
Click Save. The window is active immediately for the configured schedule.
Global suppress
Global suppress pauses notifications across the entire organization for a manually defined window. Use during active incidents where suppressing all noise helps the team focus.What suppression does and does not do
Suppression is a noise-reduction tool, not a remediation action. Use Issues to track and manage the underlying data quality fix.