List triggered alerts with filtering by status, type, and date range
| Parameter | Type | Description |
|---|---|---|
status | string | Filter by status: triggered, acknowledged, resolved |
event_type | string | Filter by type: schema_change, freshness_violation, discovery_failed |
asset | string | Filter by asset qualified name |
since | datetime | Only alerts after this timestamp |
until | datetime | Only alerts before this timestamp |
limit | integer | Max results (default: 100, max: 1000) |
offset | integer | Skip first N results |
| Field | Description |
|---|---|
id | Unique alert identifier |
rule_name | Name of the rule that triggered |
event_type | Type of event that triggered the alert |
status | triggered, acknowledged, or resolved |
message | Human-readable alert description |
asset | Affected asset qualified name |
details | Event-specific details (varies by type) |
triggered_at | When the alert fired |
acknowledged_at | When someone acknowledged it (if applicable) |
resolved_at | When the alert was resolved (if applicable) |
destinations | Where the alert was sent |
| Status | Meaning |
|---|---|
triggered | Alert fired, not yet acknowledged |
acknowledged | Someone is looking at it |
resolved | Issue has been addressed |
| Type | Description |
|---|---|
schema_change | Table or column structure changed |
freshness_violation | Data older than SLA threshold |
discovery_failed | Discovery job couldn’t complete |
asset_removed | Table or view no longer exists |
| Status | Meaning |
|---|---|
401 | Invalid or missing API key |
400 | Invalid filter parameters |
429 | Rate limit exceeded |
How to combine tag filters (AND/OR)
Filter by tags
Filter by severity
Filter by status
Filter by asset
Filter by lifecycle state
Filter by scope level
Filter by scope hierarchy
Use saved filter
Maximum number of alerts to return
Number of alerts to skip