New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
The pipeline finished green again this morning, exactly like every other morning, and yet the number sitting on the executive dashboard is still wrong.
What you'll have at the end
A running check on one business metric that computes its own expected range from recent history and fires the day the real number steps outside it, before a stakeholder notices
You need
A business metric already computed once per period by an existing pipeline, sitting in a queryable table with at least three to four months of its own history, and a place in that same pipeline to add a new scheduled check.
Not covered
Diagnosing why a number that's already been flagged went wrong, or retuning an alert that's already live and being ignored.
Your loudest data quality alert stopped meaning anything
once this check is live and starts firing on days that turn out fine, or the team starts muting it
Trace a wrong dashboard number back to its real cause
once this check fires for real and you need the exact upstream break that caused it, rather than only a confirmation that the number is off
Checked 26 Aug 2026
Part of the Data Observability cookbook