Data Catalog

Every lakehouse and warehouse table, what wrote it, what depends on it and who can read it — from the code and metadata already in your tenant.

Docs overview

The landing page summarises the estate: storage tables, how many have a known producer, how they are written (notebook, pipeline, dataflow), tables per workspace, and freshness from each table's Delta log.

Below it, the Catalog lists every workspace, item and table with the item that writes it, the write mode, the last write, the row count, what uses it and whether it is documented. Export CSV downloads exactly what the filters show.

Docs overview and the catalog.

Lineage graph

The graph lays the estate out from external sources through the lakehouse and warehouse layers to semantic models and reports. Click a table to light up everything upstream and downstream of it; drag tables to rearrange; drag the background to pan.

The Select box narrows the graph: +fact_sales+ shows what feeds a table and what it feeds, layer:warehouse one layer.

Tracing a table's lineage, down to the statement that writes it.

Table pages

Open a table from the graph, the sidebar or search. Its tabs:

Overview — what produces it (the item, and the notebook cell or pipeline activity), what orchestrates it, the last write, write mode, rows, size and Delta versions, plus what it depends on and what uses it.
Columns — each column's type and description, with likely personal data tagged.
Lineage — one hop up and down.
Code — the code that writes the table, with the writing lines highlighted.
Access — everyone who can read the data: workspace roles, OneLake data access roles, groups opened to their members, and people who reach it indirectly through a semantic model.

Items have pages too: a notebook lists what it reads and writes, a semantic model its tables and where each comes from, a report the model it is built on.

Search, then a table's overview, columns, lineage and access.

Search and filters

The sidebar search finds tables, items and columns by name. The filter bar narrows the overview, the catalog and the graph to the workspaces, items and tables you pick — several of each at once — and the choice follows you between pages.

Filtering to two lakehouses, on the overview and the graph.

Descriptions

Contributors and admins can write a description for any table or column, right on its page. Each description records who wrote it and when. Descriptions you write stay in Fabriscope; they are never written back to your tenant.

Documenting a column.

Findings and collection gaps

Each scan flags tables worth a look: stale (no write for a long time), undocumented, and possible personal data exposed to many people. A tag a person sets always wins over an automatic one.

Collection gaps, on the overview, list everything a scan could not reach — an item without the right role, a workspace outside the selection, code whose target is decided only at run time — with what to do about each. Fabriscope never fills a gap with a guess.