Skip to main content
Lineage shows how a data asset connects to everything around it: what it depends on upstream and what depends on it downstream. It spans your dbt™ project and every connected BI and ingestion tool, so you can trace data all the way from an ingestion source through your models to a BI dashboard.
Lineage lives in the Data Catalog. Open any asset and select its Lineage tab to see its dependencies. This section explains how to read and work with that view.
The Lineage tab on a Catalog asset page showing 40 assets and 39 dependencies for int_f1__race_results_standings, with the lens strip, depth controls, Graph and Table toggle, Tour button, edge legend, and minimap

The lineage bar

The bar above the canvas carries everything that shapes the view:
  • A count of what is on screen, for example 40 assets · 39 dependencies.
  • Upstream and downstream depth, set independently and applied when you confirm. Lineage opens two levels upstream and two levels downstream.
  • Zoom in, zoom out, and fit view, plus a node-type filter. dbt™ tests are hidden by default: open the filter and tick Test to show them, or choose Reset to default to hide them again. The filter never hides the asset you are viewing.
  • Graph and Table, which swap between the canvas and the same dependencies as a list.
  • Tour, a guided walkthrough of the canvas and its controls.
The lens strip sits on the canvas itself, the edge legend along the bottom, and a minimap in the corner for graphs that run past the edge of the view.

Two ways to view lineage

Graph view

An interactive DAG of upstream and downstream nodes, with node-type filters, depth controls, and click-through navigation.

List view & export

The same dependencies as a sortable, filterable table you can download as CSV.

Follow a single column

Asset lineage tells you which models feed a model. To trace one value instead, click a column on any card in the Lineage tab, or click Lineage next to a column on an asset’s Columns tab. Either way, column-level lineage shows where that column’s value comes from, where it flows, and what happened to it at each hop. Column-level lineage covers your connected integrations too: Looker, Tableau, Power BI, Sigma, ThoughtSpot, Metabase, Omni, Lightdash, Hightouch, Fivetran, and custom integrations. Trace a dbt™ column forward to the dashboard fields that show it, or a dashboard field back to its source. See Lineage into BI and ingestion tools.

Integration assets

Assets from your connected BI, reverse ETL, and ingestion tools are part of the same graph. A Looker dashboard, Tableau workbook, or Power BI report shows the dbt™ models and warehouse tables it reads upstream. A Fivetran connector shows the dbt™ sources built on the tables it loads downstream. Lineage also follows links between assets of the same tool, such as a Looker dashboard and the Looks on it, or a Tableau dashboard and its worksheets. Paradime builds this lineage from the metadata each integration syncs, and links each warehouse table an asset reads to the dbt™ model that builds it. An integration asset’s lineage appears after its integration syncs.

Sources

At the top of the lineage view, the Sources chips show the source systems feeding the asset (for example a dbt™ source or a Fivetran connector), so you can see at a glance where its data originates.

dbt™ Mesh projects

If your workspaces are connected with cross-project dependencies, lineage crosses one workspace boundary in each direction:
  • In a consumer workspace, each producer model your project references appears as a node tagged with the workspace it comes from. Lineage stops at that model: the producer’s own upstream models, sources, and tests stay in the producer workspace. To trace further, open the model in the producer workspace, if you have access to it.
  • In a producer workspace, a model’s downstream lineage includes the models in other workspaces that reference it, tagged with their workspace.
Lineage doesn’t continue into a third workspace, such as the consumers of a consumer. Workspace connections come from each workspace’s production catalog, so a consumer appears once its production catalog builds with the cross-project setup working, and each workspace’s dbt™ project needs a unique name.
Lineage is built from your dbt™ project and connected integrations, and populates after your first Bolt production run. If an asset isn’t part of the graph yet, the view shows a note instead of a diagram.