> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/inventory/lineage.md).

# Lineage

The Dependency Lineage in [Inventory](/guides/inventory.md) shows how BI assets are connected.

It answers:

* What does this asset depend on? (upstream)
* What depends on this asset? (downstream)

This gives you a complete view of data flow, from source → model → report → dashboard.

{% hint style="info" %}
With Dependency Lineage, Datalogz has introduced the first steps towards operational lineage, which is a feature on the roadmap for later this year.
{% endhint %}

### Why Dependency Lineage Matters

Without lineage:

* You can’t see impact before making changes
* Broken reports are hard to trace
* Cleanup is risky

With lineage, you can:

* Understand BI dependencies instantly
* Identify high-impact assets
* Safely modify or delete content
* Detect redundant or unused chains

Lineage is foundational for governance and cleanup.

### Where to Find Lineage

1. Open **Inventory**
2. Select any asset (report, dashboard, semantic model)
3. Navigate to the **Lineage tab**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datalogz.io/guides/inventory/lineage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.