DATA OPS
Auto-File GitHub Issue for Unexplained dbt Freshness Misses
On a dbt run-failure webhook, checks BigQuery freshness and Honeycomb for an upstream cause, and opens a labeled GitHub issue only when the miss is unexplained by upstream lag.
How it runs
The automated pipeline, trigger to output.
- Triggerdbt run-failure webhook receivedHTTP webhook
- ActionConfirm which failed models are over SLABigQuery
- ActionCheck Honeycomb upstream latency in windowHoneycomb
- LogicDrop upstream-explained, keep unexplained misses
- OutputOpen labeled, owner-assigned GitHub issueGitHub
What it does
Closes the loop between detection and tracking. When dbt Cloud (or your orchestrator) fires a run-failure webhook, the flow confirms which models actually went stale in BigQuery, checks Honeycomb to see if an upstream slowdown explains it, and — only for genuinely unexplained failures — files a pre-triaged GitHub issue so nothing falls through the cracks.
When to use it
Use this when you want every real, owner-actionable dbt freshness failure to become a tracked engineering ticket automatically, without manually opening issues or creating noise for transient upstream delays.
How it works
- 1A dbt run-failure webhook triggers the flow with the failed run's models.
- 2BigQuery confirms which of those models are now past their freshness SLA.
- 3Honeycomb is queried for upstream latency in the failure window.
- 4A logic step suppresses upstream-explained misses and keeps unexplained ones.
- 5For each unexplained breach it opens a labeled, owner-assigned GitHub issue with logs and links.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect HoneycombDistributed traces and queries.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.