Datastore-level Lineage

The datastore map is the view a datastore's Lineage tab opens on. The tab sits between Observability and Checks on the datastore page, and shows a Trial badge while the Lineage add-on is on trial. Where a container's graph starts from one container, the map starts from the whole datastore: which other datastores it exchanges data with, and every container in it that has lineage.

From the map you open two canvases: the lineage between this datastore and one other, and all of the datastore's lineage. Both are drawn with the cards and connections described in Reading the Graph. Each view has its own address, so a link to one opens it directly.

The Map

The tab opens on a map of datastores. This datastore sits in the middle. The datastores and assets outside Qualytics that feed it are on the left, and the ones it feeds are on the right.

Each card shows:

The datastore's logo and name, with Datastore under it. Assets outside Qualytics are drawn on a dashed, faded card captioned Not in Qualytics.
How many of that datastore's containers are linked to this one, in the footer. A card on the left reads, for example, 12 of 40 tables send data directly: 12 of that datastore's 40 containers feed this one. A card on the right reads 12 of 40 tables get data directly. When the same datastore appears on both sides, both of its cards show the count of its containers linked in either direction, not a separate total per side. The UI uses the datastore's own word for its containers, so a file store reads files instead of tables.
An anomaly badge: an alert icon when any of those containers has active anomalies, a check when none has. Hover it for the count. Assets outside Qualytics have no badge.
An arrow beside another datastore's name, which opens that datastore's page.

The center card counts this datastore's own containers that have lineage, and its footer reads View all N linked tables.

A datastore with no lineage yet shows an empty map that reads No lineage in this datastore, with a note that lineage appears once a Sync collects it, a data catalog imports it, or a computed table or file is created.

The Search assets box at the top left of the map searches this datastore's containers that have lineage, and picking one opens the all-containers canvas focused on it.

Following the Chain

A card that leads on to more datastores has chevrons on its outer side. Expand upstream (or Expand downstream) adds the next datastores along, and Expand all upstream opens everything behind that card. A datastore further along appears next to the one it comes through, and its footer names the route: 5 of 30 tables send data via Staging, or via 2 datastores when there are several, with their names on hover.

When a side has more partners than are drawn, a dashed + N more card ends that side. Clicking it shows the next batch. When the whole map does not fit in one go, a Show more bar appears on the toolbar with how many cards are shown.

A count followed by a plus sign, such as 40+, means counting stopped before the end. The real number is at least that.

Selecting a Card

Clicking a card highlights its connections to this datastore, including every route for a card further out, and dims the rest. A flow is highlighted in red only when at least one of its connections has active anomalies on both of its containers. An alert badge at just one end does not make the flow red. Clicking the canvas clears the selection.

Lineage Between Two Datastores

Clicking a card's footer, or its anomaly badge when it shows an alert, opens the lineage between that datastore and this one. It is a container-level canvas limited to the connections between the two ends, including any datastores in between.

The trail at the top left names the two ends, and any datastores in between, in the direction data moves. Because the view is limited to those connections:

Cards have no expand chevrons and no upstream and downstream count row.
A card's field count names the other end: 7 of 9 fields linked to Sales Warehouse. Opening the field list shows the fields with no connection to that end under a divider such as 2 fields (not linked).
Search and Pick from list stay within the connections between the two ends.

All of a Datastore's Lineage

View all N linked tables on the center card opens a canvas of every container in this datastore that has lineage, drawn in groups. A group is some of this datastore's assets and everything that feeds them or that they feed, directly or through others. Each group sits in its own box, labeled with how many assets it holds and how many of them are in this datastore. Drag a box by its handle to move the whole group.

A large datastore opens with part of its lineage drawn. The toolbar then shows how many assets are drawn out of the total, with Show more to draw the next part. A group that is only partly drawn says so on its box, as in 120 of 400 assets, and the arrows on the cards at its edge draw more of it.

Searching

The Search assets box at the top left finds containers already on screen, under On screen, and the other containers of this datastore that have lineage, under More in this datastore. Picking one on screen selects it. Picking one that is not drawn yet loads it with its group and focuses it. With nothing typed, the box lists Most links, the containers with the most connections.

Search covers only this datastore. A container of another datastore is found only when it is already on screen.

Where You Edit

The map, the lineage between two datastores and the all-containers canvas are read-only. They have no + buttons, no delete control on connections, and no add options on fields.

To add or delete a connection, open one container's lineage:

Open this table's lineage, the button beside a card's name, opens that container's lineage on top of the canvas. Its trail tooltip says what you can edit there.
The container's own Lineage tab offers the same editing.

Back, or Esc with nothing selected, returns from a container to the canvas, and from the canvas to the map, as you left them. If you added or deleted a connection in the meantime, the view reloads instead.