​

Ingest Exposures from dbt

​

Requirements

​

Supported Exposure Types

​

Ingesting dbt Exposures

1. Add exposure information in your dbt project Define the exposure in your dbt project (for example in models/exposures.yml), and set meta.open_metadata_fqn to the Fully Qualified Name of the corresponding entity already ingested in OpenMetadata. For more information, see Add Exposures to your DAG.
   exposures:
     - name: orders_dashboard
       label: orders
       type: dashboard
       maturity: high
       url: http://localhost:8080/looker/dashboard/8/
       description: >
         Orders dashboard built on top of the orders model.
       depends_on:
         - ref('fact_sales')
       meta:
         open_metadata_fqn: sample_looker.orders  # OpenMetadata entity Fully Qualified Name
   
   After adding the exposure, run your dbt workflow (dbt compile or dbt run). The generated manifest.json will include the exposure under the exposures key, with upstream models listed under depends_on->nodes.
   "exposure.jaffle_shop.orders_dashboard": {
     "name": "orders_dashboard",
     "resource_type": "exposure",
     "type": "dashboard",
     "meta": {
       "open_metadata_fqn": "sample_looker.orders"
     },
     "depends_on": {
       "nodes": [
         "model.jaffle_shop.fact_sales"
       ]
     }
   }
   
2. Viewing the exposure lineage Once ingested, the linked dashboard, ML model, or API endpoint appears as a downstream node in the Lineage tab of the upstream dbt table(s) listed under depends_on.

​

Validation and Error Handling