Real-time Alerts
Trigger notifications when retriever results match conditions on ingest, schedule, or demand
Why do anything?
Important content changes go unnoticed without proactive monitoring. Manual checking doesn't scale.
Why now?
Real-time applications need instant notifications when relevant content appears.
Why this feature?
Alert system with three execution modes: ON_INGEST (real-time), SCHEDULED (cron), ON_DEMAND (API trigger). Multiple notification channels.
How It Works
Alert system monitors retriever results and triggers notifications based on conditions.
Trigger
ON_INGEST, SCHEDULED, or ON_DEMAND execution
Retriever Execution
Run associated retriever query
Condition Evaluation
Check if results match alert conditions
Notification
Send alerts via EMAIL, SLACK, or WEBHOOK
Why This Approach
Multiple execution modes support different monitoring patterns. Retriever-based alerts leverage existing search logic.
Where This Is Used
Integration
alert = client.alerts.create(retriever_id="...", execution_mode="ON_INGEST", channels=[...])
