Impact Analysis

Impact analysis turns the lineage graph into a list. It answers two questions about a container without walking the canvas by hand: what does it feed, and what feeds it. It is the Impact analysis button on the toolbar of every lineage canvas, on a container's Lineage tab and on a datastore's.

What It Answers

If this container breaks, what is affected? Everything downstream of it, however many steps away.
Where does its data come from? Everything upstream of it, the same way.
Which of those already have problems or coverage? Each asset shows its active checks and active anomalies.

On a datastore's canvas with no card selected, it answers a third question: which of the datastore's containers have the most depending on them.

One Container

The panel opens on a container when one is selected on the canvas, or when you are on that container's own lineage. A header names the container, its type and its datastore.

Two tabs split the list: Downstream, what the container feeds, and Upstream, what feeds it. Each tab shows its count. The panel opens on Downstream, or on Upstream when nothing is downstream and something is upstream.

Three tiles sum up the side you are on:

Affected on Downstream, or Feeding it on Upstream: how many assets there are, and across how many datastores.
Assets with active anomalies: how many of them have active anomalies. Click the tile's filter to show only those assets, and again to show all.
Assets with active checks: how many have active checks, and how many have none.

Each row in the list shows:

Name, with the asset's datastore, or Not in Qualytics for an asset outside Qualytics. View table opens the container's page. The UI names it after the container's type, so it can read view or file instead of table.
Steps away: Direct when the container feeds the asset itself (or is fed by it, on Upstream), otherwise how many connections lie between them. On rows with assets in between, the route icon beside it, tooltip Show the route, lists a shortest route with every asset along the way.
Active checks and Active anomalies. An anomaly count opens the Anomalies side panel for that asset.

Search the list by name, and use Show more at the bottom to load further rows. Clicking a row opens the same analysis for that asset, and the back arrow in the header returns to the one before.

Limits

Very large results stop early and say so above the list:

Showing the nearest 1,000. There are more.
Showing assets up to 20 steps away. There are more.

The count on the tile then ends with a plus sign, meaning there are at least that many.

A Whole Datastore

On a datastore's canvas, either the lineage between two datastores or all of its lineage, open Impact analysis with no card selected and the panel ranks the datastore's containers by everything downstream of them.

The tiles count the datastore's containers with lineage, those with active anomalies (with the same filter to show only them), and those with active checks. Each row shows the container with its Downstream and Upstream counts, both counted directly or through others, plus Active checks and Active anomalies. Search by name to find one.

Clicking a row opens the one-container analysis for it. The back arrow returns to the ranking.

Exporting

Export at the bottom of the panel saves the list as a CSV file. The file follows what the panel shows: the side you are on, the active anomalies filter, and the search term. Its tooltip says what will be exported.

On a single asset, the arrow beside Export offers Both sides in one file, which saves upstream, then downstream, in one CSV.

Export is not available in deployments where downloads are turned off.