Skip to main content

​
Data Observability Alerts

Monitor the health of your data systems by setting up alerts for pipeline failures, data quality issues, and schema changes.

​
Open the Alerts Page

Navigate to the lateral menu Observability > Alerts. Navigate to Observability Alerts Click the Add Alert button. Add Alert Button

​
Name the Alert and Add Context

Provide a unique, descriptive Name for your alert. You can also add an optional Description to provide further context and clarity regarding the alert’s intent. Input fields for Alert Name and Description

​
Select Sources

Choose one or more operational entities to monitor:
  • Container - Monitors schema changes for the container asset
  • Data Contract - Triggers an alert when a data contract status changes
  • Ingestion Pipeline - Monitors status changes to your Collate ingestion pipelines
  • Pipeline - Monitors updates to pipeline assets that you have ingested
  • Table - Monitors schema changes and table metrics changes
  • Test Case - Triggers an alert for the specific test case selected
  • Test Suite - Triggers an alert once for each completed run of the test suite, based on the summary of its test case results. This is a great way to group alerts and reduce notification fatigue
  • Topic - Monitors schema changes for the topic asset
Select the Source Resource for Data Observability To watch several sources with one alert, select each one from the list. After the first source, the field reads Add another…. Changing the sources clears the filters and triggers you chose, and removing a source also clears the destinations.

​
Configure Filters (Optional)

Filters allow you to refine the scope of the alert to focus only on relevant changes, significantly improving the signal-to-noise ratio. With several sources, the list offers only the filters that every chosen source supports. You can narrow down events based on a variety of criteria, including:
  • Entity Specific Name: Filter by the defined specific name of the entity.
  • Owner Name: Filter events based on the designated owner of the asset.
  • Domain: Filter events based on the Data Domain the entity belongs to.
  • Filter By Updater Is Bot: Filter to include or exclude changes made by automated ingestion or system processes.
Use the Include toggle to define the logic for the filter condition:
  • Include (Toggle ON): If the event meets the filter condition, the alert is sent.
  • Exclude (Toggle OFF): If the event meets the filter condition, the alert is silenced (not sent).
If you do not set any filter, the alert will apply to all relevant events over the selected source entity type, which may lead to excessive notifications.
Define Filters Filter Options

​
Select Trigger Conditions (Optional)

Define the specific conditions that will trigger the alert:
  • Schema Changes - Alert on added, deleted, or updated columns
  • Test Case Status - Trigger when a test result has a status you select: Success, Failed, Aborted, or Queued. The alert fires on every matching result, not only when the status changes
  • Pipeline Status - Alert when pipeline execution has a status you select: Successful, Failed, Pending, or Skipped
  • Metric Updates - Notify when table metrics are updated
You can select multiple trigger conditions to create comprehensive monitoring coverage.
With several sources, each trigger applies only to the sources named in brackets after it, for example Get Pipeline Status Updates (Pipeline). Add a trigger for each source you want to hear about. If none of the chosen triggers applies to a source, the form warns that none of that source’s events can match. You can still save the alert. Select Trigger Conditions

​
Select Destinations

Choose where to send your alerts. Collate supports both internal and external channels. Internal Destinations:
  • Admins - Notify all platform administrators
  • Followers - Notify users following the asset
  • Owners - Alert the asset owners
  • Teams or Specific Users - Target specific teams or individuals
External Destinations:
  • Email
  • Chat: Slack, MS Teams, Google Chat
  • Automation: Generic Webhooks
Internal Destinations External Destinations

​
Native Pipeline Alert Boundaries

Native pipeline alerts react to status events reported to Collate. They do not evaluate whether an expected event is missing or whether a run took longer than a threshold. The same boundary applies to Automations jobs: their reported failure and partial-success states can trigger native alerts, but missed schedules and duration thresholds require an external check. For an external check on Collate ingestion pipelines and Automations jobs, query GET /api/v1/services/ingestionPipelines/{fqn}/pipelineStatus. Use startTs and endTs to select a time window. The response includes pipelineState, startDate, and endDate for each run. For an ingested pipeline asset, such as an Airflow, Dagster, or Fivetran pipeline, query GET /api/v1/pipelines/{fqn}/status with the same startTs and endTs parameters. The response includes executionStatus, timestamp, endTime, and taskStatus for each run. The timestamp field identifies the run and is not a reliable wall-clock time, so use endTime and the task start and end times to measure duration. A monitoring script can compare these values with the expected schedule or duration threshold before sending a notification. These pages cover alert behavior, webhook delivery, and the API.