Store Failures _or_ Continuous Data Quality Checks _or_ Running Data Quality Checks on Production Data

[ahelium]

What are we doing?

We at Materialize just enabled continuous testing in the dbt-materialize adapter. Run dbt-test once, and create materialized views that update in real time when test conditions fail. We piggy backed on dbt's awesome -store-failures functionally, and wrote about it here.

Questions for the dbt community!

This got me thinking about if/how other folks are using the tables that dbt automatically creates when tasked with storing failures in production. What are the most common alert mechanisms? Are folks using exposures? How might this change down the line if something like external-nodes exists?

cc: @morsapaes