Dagster

Asset runs, materializations, and lineage from Dagster metadata.

The problem

Dagster assets fail quietly while downstream marts look fine until BI breaks.

The outcome

Connect Dagster GraphQL — runs and asset health join the pipeline NOC without reading result rows.

Ready

Connect UI

Assets

Materializations

Graph

Lineage stub

What you get

Job success, duration, and failure reason per asset.

Upstream/downstream in service map.

Dagster lane beside dbt and Fivetran.

Dagster Cloud / OSS GraphQL API key.

Integration · Warehouse

Google BigQuery

Freshness and cost from INFORMATION_SCHEMA and JOBS — never result rows.

Integration · Transform

dbt Core

Upload run_results.json or wire a webhook for calm failure triage.

Integration · Transform

dbt Cloud

Same triage path for Cloud runs — artifact-first, rows never exported.

Open workspace, or book a Data Stack Health Audit credited toward Managed.