Observability and Lineage

Observability monitors are attached to data assets — tables and columns in your warehouse. The catalog and lineage surfaces those same assets and their relationships. Together, observability and lineage help you find issues and understand impact.

Monitors and the Catalog

• When you Add Monitor, you select a data asset (table or column) from your warehouse. The monitor appears in the monitors table with a breadcrumb path (e.g. warehouse → database → schema → table → column).
• On a catalog asset details page (table or column), the right sidebar shows freshness, row count, custom monitors, and schema changes for that asset. You can add a custom monitor from the catalog using the + under monitors; the asset is pre-selected and you go straight to monitor type and configuration.

So monitors are discoverable both from Observability (by monitor) and from Catalog (by asset).

Lineage and Root Cause

When a monitor goes into alerting, you need to understand why. Lineage shows upstream sources and transformations. For a table with a freshness or row-count alert, open the table in the catalog and go to the Lineage tab. Trace upstream to see which ETL integrations, dbt models, or source tables feed it. An upstream failure or schema change often explains the alert. See View lineage and Lineage.

Lineage and Impact

Lineage also shows downstream dependencies. If you change or retire a table, you can see which dbt models, BI assets, or reverse ETL integrations use it. Observability issues on that table may affect those downstream consumers; use lineage to communicate impact and prioritize fixes.

Monitor Details and Integrations

On the monitor details page, the right sidebar lists Integrations — ETL and reverse ETL integrations that use the monitored asset. For each integration you see name, source and destination assets, last run time, and last sync result (successful, failed, completed with errors). This links observability back to pipelines so you can correlate monitor alerts with recent syncs.

For catalog and lineage concepts, see How catalog and lineage work. For monitor types and status, see Monitor types and Monitor status and lifecycle.