> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/monitoring/job-status/stream-and-file-sources/lineage.md). # Lineage The **Lineage** tab provides an insight into your data's journey, visually displaying where datasets and jobs interact, enabling you to drill into each entity, and see how pipelines and datasets relate and connect. ## Viewing data lineage The lineage diagram for your job shows the related datasets for the current job, which is always highlighted in the diagram to show its position within the pipeline architecture:

The Lineage diagram displays the visual of the data processed by the job.

### Adjust the view You can use your mouse scroller to zoom in and out on the diagram to change the display size, or use the zoom control in the bottom left-hand corner of the screen to set the view. Click **fit view** to fill the screen with the diagram. If you need to move the image, use your mouse to grab and relocate the diagram on the screen. ### Data source Click on the **data source icon** to display a pop-up with the name of the topic or bucket location where the data is sourced, along with the connection used by the job to copy the data. ### Job Click the highlighted **job icon** to display information including the full name of the job, and whether it is a [sync or non-sync job](/content/articles-1/get-started/understanding-sync-and-non-sync-jobs.md). From here, click **Info** to display the **SQL** syntax that created the job, and optionally click **Copy** to paste the code into a worksheet:

View the job creation syntax, and the settings for job options and configurations.

### Data target The target includes additional information to provide a top-level view of the schema. Click the **dataset icon** to open the pop-up and view the table and schema names, and the connection used by the job to write the data.

Click on Info to display the schema or Entity Page to open the target in Datasets.

#### Schema Click **Info** to open the modal, which provides an overview into your data:

Click Info on the dataset icon to view the underlying schema and metadata.

From this modal, click **Entity Page** to navigate to [Datasets](/content/reference-1/monitoring/datasets.md) and view more detailed information about the data. Alternatively, click on the **Entity Page** link in the pop-up to open the entity in [Datasets](/content/reference-1/monitoring/datasets.md). #### SQL The SQL tab in the modal displays the syntax used to create the table, along with job options and configuration settings. Optionally, click **Copy** to paste the code into a worksheet. *** ## Extended lineage As well as viewing the immediate data sources that are processed by the job, you can click **Display Extended Lineage** to view where the job exists in relation to other entities in your ecosystem. Click the checkbox to extend the lineage diagram:

View where the job sits in relation to other pipelines within your organization.

In this example, the diagram extends to show that the current job - which is always highlighted - shares its data source with another job that writes to different location. Viewing a job in relation to other entities enables us to plan for changes that may have wider impact within our organization. As with the previous view, you can click on all related entities in the extended diagram to expose further information and drill into the details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://upsolver.gitbook.io/content/reference-1/monitoring/job-status/stream-and-file-sources/lineage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.