Why it matters
Most teams cannot say with confidence what data their platform holds, which tables are covered by an agreement, and who is responsible for each one. Without that picture, every change and every audit starts with a manual inventory. LakeLogic builds the picture from the platform itself.
What you can do
- See your data assets, owners and coverage gaps in one place.
- Run a discovery against a connected platform and see what it read.
- See which tables have no contract, and which are ready to draft one.
- Organise assets into domains and assign owners.
- Get an assessment that ranks what needs attention, and export it as a report.
How to do it in LakeLogic
Everything here lives under Understand → Estate. The tab row reads Overview, Connections, Discovery, Assessment, Domains and Assets.
- Connect a platform. Connections are created in Integrations; the Connections tab shows what LakeLogic can reach and whether access is verified. See Connect your platform.
- Open Discovery. Under Discovery settings, choose the environment, one or more connections, and a scope for each: Tables, Landing files or Both. You can narrow the run to assets matching a name pattern.
- Select Run discovery. Progress shows the stages: Discover, Profile, Classify, Reconcile and Draft.
- Review the results. The results board counts what was Scanned, what is Draftable (landing drafts and uncontracted tables), Ready to draft, Needs review and Blocked on an unanswered question. Click a row to review it.
- Measure tables. The Profiling view on the Discovery page measures the tables you choose from what discovery found.
- Assign ownership. Use Domains to organise assets into domains and assign owners.
- Open Assessment. It has four views: Summary, Findings, Improvement plan and Scope & evidence. Select Update assessment to compose it again from the latest discovery, profile and gate results, or Export report to print it.
What you get
| Result | Where |
|---|---|
| An inventory of assets, owners and coverage gaps | Estate → Overview, Assets |
| A record of the last discovery run, its environment and time | Estate → Discovery |
| Draft candidates, with open questions marked | Estate → Discovery results |
| A ranked list of findings and an improvement plan | Estate → Assessment |
| A printable estate report | Assessment → Export report |
Good to know
- Discovery supports Databricks, Microsoft Fabric and Snowflake, and object storage on Azure (ADLS), AWS (S3) and Google Cloud (GCS).
- A scan reads metadata and samples. The run records its scope, so a tables-only scan is never presented as the whole estate.
- A targeted run does not refresh the estate. If you narrow a run to some assets, contracts outside that selection are not reported missing, and the estate map keeps its last full scan.
- A draft found by discovery cannot be saved as a contract from the review panel yet. The panel says so. To create a contract, use Contract Studio.
- Without environments defined, a run is labelled Development and uses your organisation-wide connection.
- Next: See what breaks downstream before you change a table.