dbt™ assets

Your dbt™ project is the core of the catalog. Every resource type is indexed with metadata from your .yml files, your compiled SQL, and your warehouse information schema. Which tabs an asset shows depends on its type.

​

Overview

The Overview tab summarizes the asset: its description, ownership (Owner, Group, Tags), materialization, and last run. For models it also shows coverage as two progress bars, Tests and Docs, so you can see at a glance how well an asset is tested and documented. From a model you can also click Explore in Radar to monitor it over time.

​

Columns

The Columns tab lists every column, with a Search columns box for wide tables. Each column shows:

• its name and data type (for example NUMBER, TEXT, TIMESTAMP_TZ);
• its description, from your dbt™ docs;
• test badges for the data tests defined on it (for example not_null, unique), which link to the Quality tab;
• any classifications (meta key-value pairs). See Classifications.

Nested (STRUCT) columns expand to reveal their child fields and types.

​

Code

The Code tab shows the SQL behind a model, with a toggle between:

• Source: the raw model code, including Jinja such as {{ source(...) }} and {{ ref(...) }}.
• Compiled: the SQL after dbt™ resolves macros and references, which is what runs against your warehouse.

The code is syntax-highlighted, with copy and fullscreen controls. Macros also show an Arguments tab listing each argument’s name, type, and description.

​

Lineage

The Lineage tab shows the asset’s upstream and downstream dependencies. See the Lineage section for the full graph and list views, node-type filters, depth controls, and CSV export.

​

Quality

The Quality tab is the data-quality record for the asset: every test defined on it, and how each did on its last run. The header summarizes health (for example 4 passed), and a Search tests box filters the list. Each test shows:

• its status (pass, warn, fail, or not-run);
• the test name and the column it applies to;
• impacted rows flagged on the last run;
• the last run time.

For sources, the Quality tab also reflects dbt™ source freshness. Tests defined but not yet run appear as not-run. Test results come from your Bolt runs; to monitor quality trends and get alerted on failures, use Radar.