> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What Prizm Collects from dbt

> Artifacts Prizm ingests from dbt and how dbt objects appear in the Prizm UI.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "What Prizm Collects from dbt",
            "description": "Artifacts Prizm ingests from dbt and how dbt objects appear in the Prizm UI.",
            "url": "https://docs.dqlabs.ai/sources/dbt/what-prizm-collects",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

Prizm runs two platform jobs against each dbt connector:

<Tabs>
  <Tab title="Technical">
    **Type:** CONTEXT — runs once after setup is complete.

    Parses `manifest.json` to build the full dbt catalog: models, sources, tests, exposures, columns, lineage, tags, and owners. All subsequent jobs and UI views depend on this completing successfully.

    | Object       | Fields Captured                                                                                |
    | :----------- | :--------------------------------------------------------------------------------------------- |
    | **Model**    | Name, database, schema, materialization, dependencies, tags, owner, description, compiled SQL  |
    | **Source**   | Name, database, schema, table, freshness thresholds, loaded-at field, tags, owner, description |
    | **Test**     | Name, type (generic / singular), severity, attached model/column, tags, description            |
    | **Exposure** | Name, type, upstream models, owner, maturity, tags, description                                |
    | **Column**   | Name, data type, description, parent model, associated tests, tags                             |

    <Note>
      `catalog.json` is optional and enriches column data types with warehouse-introspected values. `semantic_manifest.json` is ingested if present — full metric UI support coming soon.
    </Note>
  </Tab>

  <Tab title="Operational">
    **Type:** TRUST — re-runs on every artifact push (dbt Core) or webhook event (dbt Cloud).

    Ingests `run_results.json` and `sources.json` to power run history, test pass rates, model health trends, alerting, and freshness tracking.

    | Signal               | Source             | What It Powers                                         |
    | :------------------- | :----------------- | :----------------------------------------------------- |
    | **Job Run**          | `run_results.json` | Run history, job health cards                          |
    | **Model Run Result** | `run_results.json` | Execution time graphs, failure alerting, rows affected |
    | **Test Run Result**  | `run_results.json` | Test pass rate, failure issues                         |
    | **Source Freshness** | `sources.json`     | Freshness SLA tracking on source assets                |
  </Tab>
</Tabs>

***

## What You See in Prizm

### dbt Job Page

Access from **Home Page → View All → Jobs** **→ DBT**

<Tabs>
  <Tab title="Overview">
    Health snapshot of the dbt job powered by the last 30 days of run data.

    **Key Metric Cards:** Failure Rate (30D), Avg Duration (30D), P95 Duration (30D), Runs (Last 7D), Runs (Last 30D).

    Prizm also surfaces AI risk signals — duration regression, recurring failures, high-impact job, and test degradation.

    **Right Side Panel — More Info:** Qualified Name, Source Name, Type (JOB), Execution Mode, Job ID,  Last Run At, Modified At,

    DBT Cloud Specific Metadata: Environment, Job Schedule

    <Frame>
      <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_job.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=a0d6fb884803b55eacec64ebcd0dc75d" alt="Dbt Job" width="2828" height="3576" data-path="images/dbt_job.png" />
    </Frame>
  </Tab>

  <Tab title="Metric">
    | Metric            | Category     |
    | :---------------- | :----------- |
    | Execution Status  | Availability |
    | Job Run Freshness | Availability |
    | Job Duration      | Usage        |
    | Job Success Rate  | Queries      |
  </Tab>

  <Tab title="Run">
    Full run history. Columns: **Run ID**, **Status**, **Error**, **Duration**, **Trigger**, **Environment**, **Started At**.

    Click any row to open the **Run Detail Drawer** — Gantt-style timeline of the run plus a Run Result table with Model and Test sub-tabs. Each sub-tab shows: Name, Project Name, Job Name, Status, Execution Time.
  </Tab>

  <Tab title="Model">
    All models touched by this job.

    Columns: **Name**, **Materialization**, **Last Runs**, **Avg Duration (30D)**, **Failure Count (30D)**.
  </Tab>

  <Tab title="Test">
    All tests in scope for this job.

    Columns: **Test Name**, **Scope**, **Associated Model**, **Last Runs**, **Pass Rate 30D**, **Last Run At**.

    <Frame>
      <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_test_job_list.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=a93be264d29b65a2cf3103a63f87babf" alt="Dbt Test Job List" width="2828" height="1868" data-path="images/dbt_test_job_list.png" />
    </Frame>
  </Tab>
</Tabs>

***

### dbt Model Asset Page

<Frame>
  <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_mode.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=b7f6ff4746849e1448ff37f1ee9d8fad" alt="Dbt Mode" width="2828" height="2938" data-path="images/dbt_mode.png" />
</Frame>

<Tabs>
  <Tab title="Overview">
    **Key Metric Cards:** Volume, Schema, Freshness, Metrics, Total Runs, Failure Rate (%).

    **Right Side Panel:** Qualified Name, Source Name, Type, Materialization, Materializes To (linked warehouse table), Alias, dbt Owner, dbt Tags, Database, Schema, Execution Mode.
  </Tab>

  <Tab title="Attribute">
    Column-level metadata. Columns: **Name**, **Data Type**.

    <Frame>
      <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_attribute.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=fc48c69bbdb24d7c98e09aaf46576104" alt="Dbt Attribute" width="2828" height="2140" data-path="images/dbt_attribute.png" />
    </Frame>
  </Tab>

  <Tab title="Metric">
    | Metric           | Category     |
    | :--------------- | :----------- |
    | Run Success Rate | Queries      |
    | Execution Time   | Usage        |
    | Rows Affected    | Availability |
    | Freshness        | Availability |
  </Tab>

  <Tab title="Lineage">
    Directed lineage graph. Default view shows dbt models as transformation **edges** between warehouse tables. Toggle to dbt-only mode to see model-to-model dependencies as **nodes**. Column-level lineage is available.
  </Tab>

  <Tab title="Run">
    Execution history across all jobs. Columns: **Run ID**, **Status**, **Error**, **Duration**, **Trigger**, **Environment**, **Started At**.

    <Frame>
      <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_run.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=93c27790e5630801e73d436320c43da5" alt="Dbt Run" width="2828" height="2230" data-path="images/dbt_run.png" />
    </Frame>
  </Tab>

  <Tab title="Test">
    All configured tests. Columns: **Test Name**, **Column Name**, **Last Runs**, **Pass Rate 30D**, **Last Run At**.

    <Frame>
      <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_test_list.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=bfec2d4a3aefeca023747e31048d0fe7" alt="Dbt Test List" width="2828" height="1938" data-path="images/dbt_test_list.png" />
    </Frame>
  </Tab>

  <Tab title="Compiled Code">
    Final compiled SQL after Jinja and macro resolution. AI actions: **Explain** (plain-language summary) and **Improve Model** (dbt best-practice suggestions).

    <Frame>
      <img src="https://mintcdn.com/dqlabs/kl69flJoe09Gi0Ry/images/dbt_complied.png?fit=max&auto=format&n=kl69flJoe09Gi0Ry&q=85&s=0c466456bb87a6d6ae39dfc8904e6104" alt="Dbt Complied" width="2828" height="2590" data-path="images/dbt_complied.png" />
    </Frame>
  </Tab>
</Tabs>

***

### dbt Test Asset Page

Each dbt test is a standalone asset in Prizm.

<Tabs>
  <Tab title="Overview">
    **Key Metric Cards:** Total Executions, Failures, Failure Rate (%).

    Also shows Description, Semantic context, Owners, Audience, Who should use this, and inline Lineage showing the upstream model and column.
  </Tab>

  <Tab title="Metric">
    | Metric              | Category    |
    | :------------------ | :---------- |
    | Test Execution Time | Usage       |
    | Test Status         | Conditional |
  </Tab>

  <Tab title="Run">
    Execution history. Columns: **Run ID**, **Status**, **Error**, **Duration**, **Trigger**, **Environment**, **Started At**.
  </Tab>
</Tabs>

**Right Side Panel — More Info:** Qualified Name, Source Name, Type (TEST), Execution Mode, Severity (error / warn), Test Type (generic / singular), Created At, Modified At.

***

### dbt Exposure Asset Page

Each dbt exposure represents a downstream consumer (dashboard, notebook, application, ML pipeline).

**Tabs:** Overview, Lineage, Audit, Documentation, Conversation.

<Tabs>
  <Tab title="Overview">
    **Key Metric Cards:** Volume, Schema, Freshness, Metrics (inherited from upstream models).

    Also shows Description, Semantic context, Owners, Audience, Who should use this, and inline Lineage showing the upstream model chain.
  </Tab>

  <Tab title="Lineage">
    Full upstream graph tracing from raw warehouse sources through dbt models to the exposure endpoint.
  </Tab>
</Tabs>

<Note>
  Exposures have no Run, Test, Metric, or Compiled Code tabs — they are not executed by dbt. All quality and metric signals come from upstream models.
</Note>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Setup" icon="plug" href="/sources/dbt/setup">
    Connect Prizm to dbt Cloud or configure the dbt Core CLI plugin.
  </Card>

  <Card title="FAQ" icon="circle-question" href="/sources/dbt/faq">
    Common questions about artifacts, lineage, and troubleshooting.
  </Card>
</CardGroup>