Alerts¶
Alerts are generated when a rule condition is met during evaluation. They provide visibility into data quality issues and track their resolution.
Alert Lifecycle¶
stateDiagram-v2
[*] --> Triggered
Triggered --> Acknowledged: Team member reviews
Triggered --> Resolved: Issue fixed
Acknowledged --> Snoozed: Temporarily hide
Acknowledged --> Resolved: Issue fixed
Snoozed --> Triggered: Snooze expires
Resolved --> [*]
| State | Description |
|---|---|
| Triggered | A rule condition was met. The alert is new and requires attention. |
| Acknowledged | A team member has seen the alert and is investigating. |
| Snoozed | The alert is temporarily hidden until a specified time. |
| Resolved | The underlying issue has been fixed. |
Severity Levels¶
| Level | When to Use |
|---|---|
| Critical | Data loss, broken tracking, revenue-impacting issues |
| Warning | Degraded quality, early indicators of problems |
| Info | Informational, no immediate action needed |
Alert Grouping¶
On the dashboard, alerts are grouped by the rule that generated them. Each group shows:
- The rule name and type
- Number of occurrences
- A sparkline showing alert frequency over time
- Time since last occurrence
- Current severity
This grouping helps you focus on patterns rather than individual events.
Alert Activity¶
The activity chart on the overview dashboard shows alert volume over time. You can filter by time range:
- Last hour
- Last 24 hours
- Last 7 days
- Last 30 days
This helps you spot trends — are data quality issues increasing or decreasing?
Managing Alerts¶
Overview Dashboard¶
The Overview page is your alert command center. It shows:
- Alert Activity Chart — A time-series view of alert volume. Toggle between 1h, 24h, 7d, and 30d views.
- Grouped Alerts — Alerts grouped by the rule that generated them, with sparklines showing frequency over time.
Alert Actions¶
| Action | From | To | When to Use |
|---|---|---|---|
| Acknowledge | Triggered | Acknowledged | You've seen it and are investigating |
| Resolve | Triggered / Acknowledged | Resolved | The underlying issue is fixed |
| Snooze | Acknowledged | Snoozed | Temporarily hide (e.g., known issue, off-hours) |
Filtering Alerts¶
On the Alerts page, you can filter by:
- Rule — Show alerts from a specific rule.
- Severity — Critical, Warning, or Info.
- Status — Triggered, Acknowledged, Resolved.
- Time range — Focus on recent alerts.
Workflow Tips¶
Acknowledge early
Acknowledging an alert signals to your team that someone is looking at it. This reduces duplicate investigation.
Use severity to prioritize
Focus on Critical alerts first — these represent data loss or revenue impact. Warning alerts are early indicators. Info alerts are for awareness.
Resolve with context
When you resolve an alert, note what you fixed. This builds a knowledge base for your team.
Notifications¶
When an alert is triggered, Adwize can notify you via:
- Dashboard — Alerts always appear on the overview page.
- Webhooks — Push alert data to Slack, PagerDuty, or any HTTP endpoint. See the Webhooks API reference for setup details.