A metric looks wrong. How do I find where it went bad?
Walk the column lineage upstream from the metric to inspect each transformation, narrowing down exactly where the value diverged. Bruin does this in one platform: ingestion, SQL and Python pipelines, quality checks, lineage, and an AI data analyst that answers in Slack, Microsoft Teams, and the browser.
Command
bruin lineageDefined in
SQL + YAML
Works with
Bruin CLI + your warehouse
What you get
How it works in code
$ bruin lineage ./pipeline --downstream --column orders.amountRun bruin lineage and you see the full downstream blast radius before you change anything.
Related use cases
See which columns feed a metric
How do I trace a metric back to its source columns?
Impact analysis and debuggingRun impact analysis before a schema change
What breaks if I drop or rename this column?
Impact analysis and debuggingFind unused columns in a model
Which columns in this table are never used downstream?
Know what breaks before you ship it
Open source. Column-level lineage parsed from your SQL, with no manual mapping.