Why it matters
Governance only helps if it reaches where your team works: the catalog, the repository, the dashboards and the channels people read. LakeLogic has one place to set all of that up, so nobody has to hunt for where a connection lives.
What you can do
- Scan your data platform catalogs and read lineage.
- Run gates on pull requests in your repositories.
- Map BI reports and dashboards back to their tables.
- Send alerts to Slack or Teams, and ask Zeus from Slack.
- Have Zeus work Jira tickets.
How to do it in LakeLogic
- Open Integrations in the sidebar (
/integrations). Organisation admins can manage it. - Find the card and select Connect. The dialog lists the fields it needs and links to where to find each value.
- Save. Secrets are stored encrypted.
- Select See connection status in the header. It opens the Connections tab of the Estate page, which shows state but does not create connections.
- To change or remove a connection, select Manage on its card.
AI providers are set under AI → Models & routing. See Get answers about your estate in plain English.
What you get
Each card lists what works today and what is not built yet.
Data platforms (read-only metadata; see Estate and discovery)
| Integration | What LakeLogic does with it |
|---|---|
| Databricks | Scans Unity Catalog; reads table and column lineage |
| Microsoft Fabric | Scans lakehouse tables in a workspace; reads metadata |
| Snowflake | Scans INFORMATION_SCHEMA; lineage from view definitions |
| Google BigQuery | Scans datasets and tables; lineage from view definitions |
| AWS Glue Data Catalog | Scans databases, tables, columns and partitions; lineage from view definitions |
| Azure Synapse Analytics | Scans dedicated and serverless SQL pools; lineage from view definitions |
Cloud storage
| Integration | What LakeLogic does with it |
|---|---|
| AWS S3 | Checks the landing zone, lists objects, infers schema |
| Azure ADLS Gen2 | Checks the landing zone, lists paths, infers schema |
| Google Cloud Storage | Checks the landing zone, lists objects, infers schema |
Git providers (see Approve every contract change with evidence)
| Integration | What LakeLogic does with it |
|---|---|
| GitHub | Scans granted repositories for contract files; runs gates on pull requests; posts check runs and PR comments |
| Azure DevOps | Scans Azure Repos; rescans on push and pull-request service hooks; posts gate results on the PR |
| GitLab | Scans the repository, pushes a branch, rescans on push, posts an impact comment on a merge request |
| Bitbucket | Scans the repository, pushes a branch, rescans on push, posts an impact comment on a pull request |
BI and reporting (metadata only, no data rows or queries; see See what breaks downstream)
| Integration | What LakeLogic does with it |
|---|---|
| Power BI | Scans semantic models and reports; maps them to sources |
| Tableau | Scans workbooks and data sources; maps them to tables |
| Looker | Shown as Beta on the Integrations page. Not connectable yet: there is no Looker connector behind it. |
Notifications (see Know when data is late or missing)
| Integration | What LakeLogic does with it |
|---|---|
| Slack | Posts alerts set in Notification Routing (quarantine, schema drift, contract changes, pipeline failures, SLA breaches). With a bot token, answers @LakeLogic and /zeus. |
| Microsoft Teams | Posts the same alerts as Adaptive Cards through a webhook |
Ticketing (see Incidents and the Work Queue)
| Integration | What LakeLogic does with it |
|---|---|
| Jira Software | Zeus creates tickets, adds comments, moves status and searches issues in the projects the connection can see |
Good to know
- GitLab and Bitbucket do not yet open pull requests, set commit statuses or track merges.
- Teams does not answer Zeus questions. Neither Slack nor Teams sends lineage-change alerts yet.
- Hive Metastore is not offered. On EMR connect AWS Glue; on Databricks use the Databricks connector; on premises run LakeLogic Core inside your network.
- Confluence, SharePoint and Notion show Coming soon and cannot be connected.