# dbt Core Metadata Extracted

## What does Secoda extract from dbt Core?

{% hint style="info" %}
dbt is a secondary integration that adds additional metadata on to your data warehouse or relational database tables. Before connecting dbt make sure to connect a data warehouse or relational database first. These include Snowflake, BigQuery, Postgres, Redshift, etc.
{% endhint %}

* Models:
  * Description
  * URL
  * Compiled SQL
* Columns:
  * Description
  * Tags
  * Updated Time
* Tests:
  * Name
  * Description
  * URL
  * Tags
  * Status
  * Error
  * Compiled code
* Metrics (Referred to as Dictionary terms in Secoda) on dbt v1.5 or less:
  * Name
  * Type
  * Dimensions
  * Time Grains
* Lineage:
  * dbt Jobs <-> external Tables
  * dbt Exposures <-> external Tables
* Groups (Groups are referred to as `USER_GROUPS` in Secoda)
* Contracts (dbt Contracts are referred to as `TEST` in Secoda)
* Exposures
  * name
  * description
  * tags
  * owners (from meta.owner)
  * url
  * type
    * The exposure type can be a dashboard, notebook, analysis, ml, or application
  * depends\_on
* Monitors
  * See [Monitors](/features/monitoring.md#monitors-as-code)on how to implement monitors in your model yml


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.secoda.co/integrations/data-transformation-tools/readme-1/dbt-core/metadata-extracted.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
