Skip to content

dbt

The dbt connector uses the dbt manifest.json file as input. The connector can either retrieve the manifest.json file by providing a URL to a published file, like a dbt Docs URL (recommended), or by uploading a manifest.json file manually (use for testing or if the manifest.json file is not available through a URL).

The dbt connector is a secondary connector (see above) and can therefore be combined with other connectors to blend metadata from multiple sources, or used stand-alone.

The dbt connector currently support import of the following metadata:

  • schema (such as tables, columns, datatypes etc)
  • descriptions
  • lineage
  • code / technical definition (both raw and compiled)

It does (not yet) support import of this metadata:

  • tags
  • meta
  • owner
  • relationships
  • exposures

The default manifest.json filename can be configured in the Settings -> Connectors -> dbt section. The filename specified there is the filename the connector looks for when a URL without specified filename is provided, like “www.url.to/dbt_docs”.