--- title: "Trace how data flows through your project with lineage" description: "Lineage is recorded automatically for Load and Aggregate actions (Python and PySpark), and is opt-in for Custom actions and notebooks through the SDK" url: https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/lakehouse-manager-lineage lang: pl lastUpdated: 2026-09-14 --- > For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/pl/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/pl/llms-full.txt. # Trace how data flows through your project with lineage ## Objective **Lineage** gives you a built-in, visual map of how data flows through your project: which jobs feed each [table](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/lakehouse-manager-tables.md), which tables they produce in turn, and how everything connects from source to destination. The graph is built from the [OpenLineage](https://openlineage.io/) events your project records as jobs run, with nothing to install or configure. Lineage is recorded **automatically** for Load and Aggregate actions (Python and PySpark), and is **opt-in** for Custom actions and notebooks through the SDK. Lineage for Trino queries (Explorer, Analytics Manager) is coming soon. See [what generates lineage events](#what-generates-lineage-events) below. ![Lineage overview](/images/public-cloud/data-platform/product/lakehouse-manager/lineage/picts/lineage-overview.png) ## Open the lineage view There are two ways to reach the lineage of a table: - From the **Lineage** section of the Lakehouse Manager: the page opens on a **search bar** where every table of your project is searchable. Start typing the name of the table whose lineage you want to see and select it to display its graph. - From a **table's details view**: click the **Lineage** button to jump to the lineage page with that table already displayed. ![Open the lineage view — Lineage search](/images/public-cloud/data-platform/product/lakehouse-manager/lineage/picts/lineage-search.png) ## Explore the graph The graph starts out from the table you selected: your **central node**, marked with a blue outline so you never lose track of where the graph begins. Around it, the graph shows the tables and jobs it connects to: the jobs and tables your table is built from **upstream**, and everything built from it **downstream**. The graph is made of two kinds of nodes: **table nodes**, which list their columns, and **job nodes**, the runs that link tables together by reading and writing them. :::info The graph is never empty: a table without lineage yet is simply displayed on its own, without connections. Lineage appears as soon as a job run finishes, so a fresh run shows up immediately. ::: ![Explore the graph — Lineage overview](/images/public-cloud/data-platform/product/lakehouse-manager/lineage/picts/lineage-overview.png) ### Table nodes Click a table node to see the table's details: its **dataset**, its **columns**, the **producing job(s)** that write it, and the **consumer job(s)** that read it. Clicking another table node shows its details but does not re-center the graph: to start out from a different table, select it from the **Lineage** search bar instead. ![Table nodes — Lineage table node](/images/public-cloud/data-platform/product/lakehouse-manager/lineage/picts/lineage-table-node.png) ### Job nodes Click a job node to see the run behind the connection: | Detail | Meaning | | :------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------- | | **Job name** | The name of the job that produced the lineage event | | **Kind** | **DPE** (an action run), **Lakehouse** (the automatic load when a table is built), or **SDK** (custom tracking emitted from your own code) | | **Action type** | **Load**, **Aggregate**, or **Custom** | | **Last run** and **status** | When the job last ran and how it ended | | **Input tables** and **output tables** | What the job read and what it wrote | For **DPE** and **Lakehouse** jobs, a direct link at the bottom of the details opens the job itself. **SDK** jobs have no link, since they are lineage you emitted yourself through the [SDK helpers](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/developers-python-sdk-lineage.md). ![Job nodes — Lineage job node](/images/public-cloud/data-platform/product/lakehouse-manager/lineage/picts/lineage-job-node.png) ### Graph controls The controls at the top right adjust what the graph displays: - **Full graph** toggle: also shows the **sibling tables**, on top of the producers and consumers already displayed. - **Compact nodes** toggle: a minimal view of the nodes, without their columns. - **Zoom in**, **zoom out**, and **fit to screen**. - **Depth**: how many upstream and downstream levels the graph displays, from **1** to **10** (default: **2**); increase it to follow the flow further. ## Column-level lineage Beyond table-to-table flows, Lineage also tracks how **columns** connect across tables: for a given column, which upstream columns it is computed from, and which downstream columns are computed from it. Click a column on a table node in the graph, or a column in the table details, to switch to its column lineage. When lineage is available, the graph connects the columns across tables to show how they relate. A column with no lineage of its own is shown as independent, with a blue outline marking it as solo. ![Column-level lineage — Lineage columns](/images/public-cloud/data-platform/product/lakehouse-manager/lineage/picts/lineage-columns.png) :::info Column-level lineage is not available while **Compact nodes** is enabled: switch the toggle off to click through columns. ::: ## What generates lineage events | Source | Lineage | | :-------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Load** and **Aggregate** actions (Python and PySpark) | Automatic, with column-level detail | | **Custom** actions (Python and PySpark) | Opt-in: emit events from your code with the [SDK lineage helpers](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/developers-python-sdk-lineage.md) | | **Notebooks** (Python and PySpark) | Opt-in, using the same [SDK lineage helpers](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/developers-python-sdk-lineage.md) | | **Trino queries** (Explorer, [Analytics Manager](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/landing-page-analytics-manager.md)) | Coming soon | ## Use your own lineage tool The same OpenLineage events can be forwarded to an external lineage solution such as [Marquez](https://marquezproject.ai/). Configure the [OpenLineage consumer](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/connectors-consumers-openlineage.md) and schedule the [Send OpenLineage Events](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/dpe-actions-send-openlineage-events.md) action to stream them to your backend. ## Go further If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pl/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project. Ask questions, give your feedback and interact directly with the team building the Data Platform on the dedicated [Discord channel](https://discord.gg/ovhcloud). If you need support with your OVHcloud services, create a request in our [Help Centre](https://help.ovhcloud.com/csm?id=csm_get_help). Join our [community of users](https://community.ovhcloud.com/).