Skip to main content
The /armor:lineage skill helps you understand how data flows through your systems by showing upstream sources and downstream consumers.

Usage

Or ask naturally:
  • “What depends on this table?”
  • “Where does this data come from?”
  • “Show me the impact of changing the customers table”

Concepts

Upstream

Tables that feed data into the target table (data sources).

Downstream

Tables that consume data from the target table (data consumers).

Depth

How many levels of dependencies to traverse:
  • depth=1: Direct dependencies only
  • depth=2: Two levels
  • depth=3+: Extended chain (max 5)

Example Usage

Find Downstream Consumers

Find Upstream Sources

Impact Analysis

Common Questions

Where does lineage come from, query logs or dbt manifests?

AnomalyArmor parses query history from your warehouse to build table-level lineage automatically. If you use dbt, manifest-based lineage can be ingested on top for more complete column-level detail. See lineage.

How deep can I trace dependencies in one query?

Up to 5 levels. Ask for depth=3 or “show me 5 levels deep” to extend traversal. Deeper queries take longer to return, so start with depth 2 unless you’re doing full impact analysis.

Investigate

Root cause analysis

Status

Health overview