A question, not a map
0:07
A question, not a map. Downstream from each connector, broken ones first.
0:12
LineageMost lineage tools draw the whole warehouse as one graph, and nobody reads it twice. Antvia Data asks a narrower question: this connector stopped, so what is wrong now?
0:24
Nothing storedNothing on this page has its own copy of the facts. Each chain is built from the sources, the catalog, the models, the dashboards and the alerts, so it cannot disagree with any of them.
0:39
Sixteen thingsAt Acme Home Appliances, a demo company, two connectors are broken, and sixteen things sit below them.
0:47
Working perfectlyNone of those sixteen are failing. They are all working perfectly, on data that stopped arriving. That is the failure lineage exists to show.
0:57
Downstream of a breakSixteen downstream of a break, from two connectors.
1:02
Widest reachThe widest reach belongs to the ERP billing connector, fourteen things, and it is healthy.
1:09
No orphansEvery governed table has a connector behind it. None is maintained by hand without one.
1:17
All twelveAll twelve connectors are traced, broken ones first, then by how much rides on each.
Below the channel stock feed
1:24
Below the channel stock feed. Four stages, always in the same order.
1:28
Broken for nine daysThe channel stock feed opens by default. It has been broken for nine days, and nine things sit below it.
1:38
Lands inFirst, the tables it lands in: the staging table, the conformed fact, and the ageing mart.
1:46
StaleThe fact passes every check and is nine days stale.
1:52
FailingThe ageing mart has one check failing as well.
1:57
Modelled byThen the semantic model built on those tables. The channel inventory model is still a draft.
2:04
Shown onThen the dashboards that show it: Business pulse, Festive season readiness and Channel stock, with how many people read each.
2:13
Watched byAnd the alerts that watch it. The freshness rule is firing. The row-count rule is not, because no rows arrived to be counted.
2:23
Same shape every timeThe four stages are always drawn, even when one is empty, so two connectors can be compared at a glance.
Tracing a line
2:33
Tracing a line. Point at anything to see what it joins.
2:37
Trace a tablePoint at a table and everything joined to it stays lit while the rest recedes. The channel stock fact feeds the model and all three dashboards.
2:49
The staging tableThe staging table feeds the model and the Channel stock dashboard directly, and the freshness alert watches it.
2:58
Trace a dashboardPoint at a dashboard to see what it reads. Business pulse reads the fact table, so the leadership dashboard has been nine days behind on stock.
3:10
Trace a modelPoint at the model and its two source tables light up. The dashboards read the tables directly, so they stay dark.
3:20
Trace an alertAnd an alert shows the one table it watches.
3:25
Every node linksEvery node is a link to its own page: the catalog, the model, the dashboard, the alert.
Who was misled
3:33
Who was misled. Lineage ends at people, not at tables.
3:37
Seventy-eight peopleSeventy-eight people opened those three dashboards in the last thirty days. Every one of them saw stock figures up to nine days old.
3:47
The real costThat is the cost of the outage. Not a failed job, but decisions on festive stock made from numbers that had stopped moving.
4:01
The survey dropThe second broken connector, the customer feedback drop, has been down four days.
4:08
Failing, not staleIts two tables are old and failing checks, so every figure built on them is unverified.
4:16
Leadership reads itIt reaches four dashboards, including the leadership morning brief and the customer satisfaction tracker.
4:23
More peopleAnd a larger audience again: one hundred and nineteen people.
4:28
Same readershipBoth counts come from the dashboard register in Antvia Intelligence, so they are the same readership figures the Lens page shows.
Wide and healthy
4:38
Wide and healthy. The chains that matter even when nothing is wrong.
4:45
The widestERP billing is healthy and reaches fourteen things. If it stopped tomorrow, this is the list of what would go quietly wrong.
4:57
Most dashboardsIts billing tables feed half the dashboards in the company, from Business pulse to the compliance scan.
5:05
Worth knowing beforeThat is the list to review before an ERP upgrade, not after.
5:14
DegradedThe service CRM is degraded, not broken, so it sorts with the healthy ones. Its chain still shows three service tables a day and a half behind.
5:28
The plantsPlant systems reaches four things: the output table, the plant operations model, and the festive readiness and supply dashboards.
5:41
PausedAnd the paused price tracker lands one table that nothing reads. Switching it off cost nothing downstream.
Repair it from here
5:50
Repair it from here. The chain turns healthy while you watch.
5:57
Repair in placeThe bar at the top offers the repair on every page. With a fresh key from the portal, reconnect the feed without leaving lineage.
6:10
Six stagesConnect, extract, land, rebuild the models, run the quality gates, publish. About eight seconds.
6:19
One leftThe warning now counts only the survey drop: seven things downstream, not sixteen.
6:26
No longer brokenThe channel stock feed has lost its broken tag and moved down the list.
6:34
HealthyIts three tables are healthy.
6:38
Alert clearedAnd the freshness alert has gone from firing to active. Nobody touched the rule; the table it watches is simply current again.
6:48
Same worldNothing on this page was told about the repair. It read the same live world as every other surface, and the chain followed.
7:00
At the end of the chainAt the far end of the chain, in Antvia Intelligence, Business pulse shows channel stock as current again.
7:08
One leftIts warning now names only the satisfaction tile, which waits on the survey drop.