Pipeline

When each source last loaded, how many rows each layer holds, and the current result of every data-quality test.

dbt tests

469

Failing

0

Rows landed

1,873,476

Rows modelled

3,675,689

Source freshness

No Results

What each layer holds

No Results

Test coverage

No Results
Loading...

Currently failing

Nothing is failing, which on a green build is the expected state. This section is not broken: every one of the tests above holds, so every dbt_test__audit table is empty. If one were failing, this table would name it and point at the audit table holding the offending rows.

What the build costs

The three sections above describe the warehouse. This one describes the build — one row per node per dbt build, appended rather than replaced, so it is the one table on this page that accumulates.

The most recent build ran 562 nodes.

No Results

The data-quality layer is the build: tests and unit tests cost several times what building every model costs.

Loading...

Written by transform/pipeline_status.py (just pipeline-status, part of just run and the Dagster asset analytics/pipeline_status). The first three sections are a snapshot taken at build time; What the build costs is a history, carried between releases like the two snapshots.