Skip to main content
Alerts: batch ingested documents checked against retriever in parallel, matches trigger webhook, Slack, or email notifications
Alerts let you attach retriever pipelines to collections so that every ingested document is automatically checked against your search criteria. When matches are found, notifications fire to your configured channels (webhook, Slack, or email).

How It Works

  1. Create a retriever that defines your search criteria (e.g., semantic similarity, attribute filters)
  2. Create an alert referencing that retriever, with notification channels configured
  3. Attach the alert to a collection via alert_applications with input mappings
  4. Ingest documents — alerts execute automatically during post-processing (Phase 3)
  5. Receive notifications when matches are found

Architecture

Alerts execute during the post-processing pipeline after document ingestion completes:

Parallel Execution

Within a single alert, document-level retriever calls execute in parallel as independent Ray tasks. If a batch ingests 100 documents, all 100 retriever calls fan out simultaneously rather than running sequentially. Results are aggregated after all calls complete, and a single notification is sent if any document produced matches. Multiple alerts on the same collection execute sequentially to avoid race conditions in notification delivery.

Configuration

Create an Alert

Attach to a Collection

Attach alerts to collections via alert_applications when creating or updating a collection:

Input Mappings

Input mappings connect document fields to retriever input parameters:

Execution Modes

Notification Channels

Webhook

The webhook receives a JSON payload with alert details, matched documents, and scores.

Slack

Email

Monitoring Executions

Track alert execution history to monitor performance and debug issues:

Comparison with Other Enrichment Types