Data Observability platform Help

Lineage

Object and column level lineage can be managed by clicking on lineage icon lineageIcon, found after object/attribute name. The icon is highlighted when lineage relations have already been set; when there are none it only appears once the row is hovered. New relations can be added on both levels - see Adding new relations.

Object level lineage

Object level lineage opens on the Lineage tab of the object's detailed view - via the lineage icon in the Catalog objects list or the tab itself. The embedded graph can be expanded to full screen with the Maximize button.

object_lineage.png

The graph highlights the full relation path of a column or edge on hover; clicking a column name pins the highlight. Clicking another table's name loads that table's lineage in place - Back and Go to root in the actions bar return to where you started. The legend in the bottom left corner doubles as a filter: clicking a relation type (source, target, relation or foreign key, which the legend renders in lower case) hides or shows relations of that type.

Direct relations

  • By clicking on Columns chevron chevronIcon for any of the objects found on the lineage graph, a list of all active columns for selected object is displayed, with direct relations to any other columns.

  • By clicking on Columns detailed view icon lineageDetailed a detailed view of all columns for selected object is displayed.

    object_direct_relations.png

  • Clicking on a relation path between two objects expands the columns of both connected objects, showing the column-level relations behind the edge.

  • Every expanded column row has an actions menu with Add a relation (with edit privileges) and View attribute, which opens the attribute's detailed view.

dbt badge

Objects and columns matched to a dbt project display a small dbt badge in the corner of their node; clicking it opens the dbt Resources browser with the corresponding resource pre-selected.

Data quality

By clicking on data quality bar, a Data quality overview will be displayed

ObjectDataQuality

Clicking the ArrowUp open-in-new-tab icon will redirect to related test cases or profilings

Viewing origin queries

In case of automated lineage you can view the query where lineage originates from by pressing on the lineage_sql_button.png button on an object node or on an expanded column row. If several relations sit behind the button, a relation list opens first - click a row to see its queries.

Relations

From all relations you can view detailed information about queries the relation originates from

Relation reference queries

For each reference the modal shows Created by and Created at at the top of the relation summary, and each individual reference in the chain also shows its own Created at timestamp under the header. This makes it easy to tell when an automated lineage relation was first picked up and when individual contributing queries were last reimported.

Deleting a single query reference

When an automated relation has multiple contributing query references, you can remove just one of them without dropping the whole relation. Hover over a reference in the chain - a trash icon appears next to the header. Click it and confirm the prompt; the reference is removed and the relation stays in place as long as at least one other reference still backs it. If you remove the last remaining reference the relation itself is deleted.

Use this to clean up references from one-off ad-hoc queries while keeping the relation alive through your stable ETL queries.

Column level lineage

Column level lineage opens on the Lineage tab of the attribute's detailed view - via the lineage icon after the attribute's name or the tab itself. The tab is available once the attribute is part of at least one relation. From the object level graph, use a column row's actions menu (View attribute) to get to the attribute and its lineage.

column_lineage.png

Adding new relations

  • Open object level lineage to get options of adding new relations - the plus button in the Columns detailed view, or Add a relation in an expanded column row's actions menu

  • A modal lets you define the relation: select the Type (Source, Target or Related), then the target's Connection, Schema, Object and Column. The form remembers the last used target. Relations within the same object are not allowed.

    addRelation
  • Open column level lineage to get options of adding new relations

  • New relations can be added by hovering on any of the columns and clicking on the green Plus icon. The side of the node decides whether the new relation is a source or a target.

    columnsDetailed

Deleting a relation

deleteRelation

Open the Columns detailed view from the object node's list icon, then click the arrow-and-attribute link on the row whose relation you want to remove. A confirmation modal asks Delete relation between highlighted attributes? before anything is removed.

columnsDetailedDelete

To remove a relation between columns, hover on the column and click the red minus icon. Clicking on it will open a confirmation modal for deletion.

Lineage actions

lineage_actions
  • Navigate - Back and Forward through the graphs already visited, Go to root to return to the opened object, and Maximize to expand the embedded graph (which then offers Restore).

  • Open/close - Open all objects and Close all objects expand or collapse all column relations (object level only).

  • Export - Export PNG and Export Excel.

Mass actions

  • The Manage relations option is found in the "More" dropdown on the right of the toolbar on the Objects and Attributes tabs.

  • Manage relations view allows you to manage all lineage relations between catalog objects in a single view - with per-column filters, configurable columns, a Queries column opening the origin queries, and visibility into creator, creation date and origin. Relations can be selected and deleted in bulk.

    lineageMassActions

Relation origin tracking

The manage relations view includes two columns for tracking where relations originate from:

  • Origin Type - how the relation was created: Manual, Auto or Import

  • Origin - provides the specific source reference, such as the import file name or an UUID identifier for relation batch

For file-based imports, the origin is automatically set to the import file name. For automated lineage, the origin references the source query.

18 August 2026