> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/understand/assets/overview.md).

# Overview

The Assets overview shows how assets connect inside a Data Product. Use it to trace data from source inputs to curated outputs, semantic models, and metrics before you decide what to query or consume.

## Open the overview

From the Data Product page, open the **Assets** tab and stay on **Overview**. The graph renders assets as nodes and relationships as arrows, with the left panel listing the assets grouped by **Overview**, **Seeds**, **Inputs**, **Outputs**, **Semantics**, and **Metrics**.

<figure><img src="/files/SD8IUgdwTp7TsFPq5DsV" alt=""><figcaption></figcaption></figure>

## Show columns

To confirm where a specific field comes from, trace it column by column across the graph. Use the **Columns** toggle at the top right of the graph to show or hide the columns inside each node; with columns shown, you can follow how individual columns map from one asset to the next.

![Assets overview graph with columns shown inside each node](/files/K9tQc95ypM9CBZlJ861Y)

## Configure the graph

Large products can produce dense graphs. Use the **Chart Configuration** panel (the gear icon at the top right of the graph) to cut the view down to the assets and relationships you care about.

![Chart Configuration panel showing node and column controls](/files/zsjojMpOzwUfLGcqfMJ7)

* **Nodes**: toggle the node types shown in the graph: Hera Warehouse Lineage, External warehouse tables, Warehouse views, Seed models, Physical / dbt models, Semantic models, and Metrics.
* **Columns**: control column display with Expand all columns, Show column routes, Paginate columns, Columns per page, and Auto-sync column pages.
* **Graph**: set the line style to Curved or Orthogonal and toggle Show relationship labels.
* **Focus**: Isolate node on click to show only a node's direct links, or show Semantic relationships only.
* **Canvas**: toggle the Mini map and download the full graph as PNG or SVG.

## Search assets

When you already know the asset you need, jump straight to it instead of scanning the graph. Use the search box above the graph to focus on a specific asset name or keyword, and the filter icon in the left panel to narrow the listed assets.

## Read the graph

Use these cues to interpret the graph and follow data from its source to where it is consumed.

<table><thead><tr><th width="146.94891357421875">Graph element</th><th>What it tells you</th></tr></thead><tbody><tr><td>Node</td><td>An asset you can inspect or query, such as a seed, input, output, semantic model, or metric.</td></tr><tr><td>Edge</td><td>How data flows from one asset to another, so you can see what feeds what.</td></tr><tr><td>Direction</td><td>Follow the arrows from source assets to downstream assets or pipelines to see where data ends up.</td></tr><tr><td>Asset type</td><td>Icons and labels that let you tell datasets, models, and metrics apart at a glance.</td></tr></tbody></table>

## Open lineage

Select **View lineage** to open the full dependency graph for an asset. Lineage answers where a field comes from, where it is reused, and which downstream assets a change can affect.


---

# 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://v2.dataos.info/consume/understand/assets/overview.md?ask=<question>&goal=<endgoal>
```

`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.