Create Alert Rule

Filter for selecting tables by tags.

Example: { "tag_names": ["revenue", "orders"], "tag_categories": ["business"], "match_mode": "any" }

Filter for selecting tables by lineage relationships.

Example: { "upstream_of": "dbt://models/gold/customer_summary", "downstream_of": null, "max_hops": 5 }

Configuration for alert grouping/digest behavior.

When enabled, alerts are grouped into digest notifications to prevent alert fatigue. The first alert always sends immediately; subsequent alerts within the window are grouped.

Example: { "enabled": true, "window_minutes": 60, "min_alerts_to_group": 2 }

Per-rule trigger configuration for schema_change event-type rules.

Scopes which kinds of detected schema change should fire the rule. Normalization rules enforced by validators:

• trigger_on="any" with no change_types is the default-equivalent state. Callers should normally send null for that case; the API accepts either.
• trigger_on="specific_types" requires a non-empty change_types list whose values all appear in the backend ChangeType enum.
• Any other value of trigger_on must not carry change_types.

The evaluation service reads this alongside the schema alert service's change_types_present context projection (TECH-963).