Run history
Pass / fail / skip counts and timings you can scan in seconds.
Use case
Failed models and tests, grouped — not twenty Slack pings.
The problem
Overnight dbt fails. CI is red. Twelve models skip. Eight tests fail. Slack lights up. Everyone digs logs. Leadership still sees yesterday’s numbers.
The outcome
Upload a run artifact or connect a webhook. VectorData surfaces failed models, failed tests, diffs vs the last good run, and one alert for the blast radius.
run_results.json
In-browser analyzer — no warehouse rows
Diffs
What broke vs the last good run
Calm routing
One alert per upstream root cause
Pass / fail / skip counts and timings you can scan in seconds.
Names, statuses, and duration — the short list of what to fix first.
See where the failure sits in lineage so you don’t chase a child model.
Same view as freshness and cost — one place for the morning check.
Related use cases