> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Lineage overview

Our lineage is built to be performant and work out of the box. This means you’ll automatically get column-level lineage from BigQuery, Snowflake, Redshift, and ClickHouse to Looker and Tableau with the ability to explore thousands of assets with sub-second latency. The lineage is helpful for core workflows such as

* Understand the downstream impact of an issue across your transformation layers (dbt, SQLMesh, Coalesce Transform) and BI tools to decide the urgency at which you resolve it.
* Understand the downstream implications of making a change to a column upstream.
* Debugging a data issue to find upstream dependencies.

The lineage is automatically extracted from your data warehouse and BI tool several times daily, ensuring you always have an up-to-date view.

### Understanding the downstream impact of an issue

1. Alerts show the number of impacted assets. Clicking on the impacted assets brings you to the lineage view with these assets pre-filtered

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage2.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=4b689bfc6704ef0a26962a40a1add566" alt="title" width="2000" height="1479" data-path="images/lineage/lineage2.png" />

2. Use the sidebar to quickly filter down to specific assets downstream, such as a Looker dashboard.

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage3.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=0af7296f5f70e23552259e490a34774a" alt="title" width="2000" height="1538" data-path="images/lineage/lineage3.png" />

### Assessing the impact of making a change

1. Navigate to the lineage for the table you’re about to change and click on the table name in the lineage to toggle `Filter by column`

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage4.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=c0061641fbb001dcbcc4ff62ae3cf59b" alt="title" width="2000" height="1740" data-path="images/lineage/lineage4.png" />

2. Filtering by a column lets you see all downstream assets where the column is being used. Click `X` to remove the column selection or `+` to expand the lineage.

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage5.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=6e5ecd58bd75c1b5695f0eb03fa98691" alt="title" width="2000" height="688" data-path="images/lineage/lineage5.png" />

3. Click on a column in one of the downstream assets to see how the column was derived in code

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage6.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=af5cad2e0ce4c6d8d658087d3d258fd0" alt="title" width="2000" height="1500" data-path="images/lineage/lineage6.png" />

### Upstream lineage to trace down the issue's root cause

1. Navigate to the most downstream asset, such as a Looker dashboard you’re debugging.

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage7.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=04eb6be49c69cc511d69aac5513c99da" alt="title" width="2000" height="663" data-path="images/lineage/lineage7.png" />

2. To trace upstream issues, use the left side menu bar to filter down on, e.g., sources or transformation models with status errors.

3. Click the data asset and select `Filter by column` to trace where a specific column is used upstream.

   <img src="https://mintcdn.com/synq-15/FoG6-YKTU-ydVrtS/images/lineage/lineage8.png?fit=max&auto=format&n=FoG6-YKTU-ydVrtS&q=85&s=e2d6ac51f58191cfa5f74277fa24ab58" alt="title" width="2000" height="960" data-path="images/lineage/lineage8.png" />
