Skip to main content

Artifacts

When running dbt jobs, dbt Cloud generates and saves artifacts. You can use these artifacts, like manifest.json, catalog.json, and sources.json to power different aspects of dbt Cloud, namely: dbt Explorer, dbt Docs, and source freshness reporting.

Create dbt Cloud Artifacts

dbt Explorer uses the metadata provided by the Discovery API to display the details about the state of your project. It uses metadata from your staging and production deployment environments (development environment metadata is coming soon).

dbt Explorer automatically retrieves the metadata updates after each job run in the production or staging deployment environment so it always has the latest results for your project — meaning it's always automatically updated after each job run.

To view a resource, its metadata, and what commands are needed, refer to generate metadata for more details.

 For dbt Docs

Documentation

Navigate to dbt Explorer through the Explore link to view your project's resources and lineage to gain a better understanding of its latest production state.

To view a resource, its metadata, and what commands are needed, refer to generate metadata for more details.

Both the job's commands and the docs generate step (triggered by the Generate docs on run checkbox) must succeed during the job invocation to update the documentation.

 For dbt Docs

Source Freshness

To view the latest source freshness result, refer to generate metadata for more detail. Then navigate to dbt Explorer through the Explore link.

 For dbt Docs
0