dbt Core

Seemore supports dbt core by interpreting your projects manifest.json files

In order to integrate, please contact our support to get the details of our S3 bucket and your account specific credentials.

manifest.json is a JSON file generated by dbt build process. The file contains all metadata related to your dbt project.

Seemore supports extracting dbt core metadata from multiple dbt projects. You will need to use the following structure:

your-account-prefix:

• project1/manifest.json

• project2/manifest.json

• project3/manifest.json

• project4/manifest.json

• project5/manifest.json

The example above will be processed as five different dbt projects.

You can find the manifest.json file inside the target directory of each of your dbt projects, it can be generated by running the following command:

What dbt command should I use to generate manifest.json?

• If this is the first time running the project, and your dbt models have not been materialized, use dbt run or dbt build .

• If you have just made a change to your dbt project, use dbt run or dbt build .

• If you have run your dbt project, materialized dbt models and there is nothing you want to change, use dbt compile --full-refresh .

I have updated the dbt's metadata, will they automatically sync with Seemore?​

No. Currently, we don't support this yet.

If you have updated your dbt's metadata, you will need to re-push your latest manifest.json to Seemore. Once done, you can re-run your dbt core integration.

We recommend that you should set up a re-sync strategy from your side so the file manifest.json is automatically pushed to Seemore on a regular (or trigger) basis.