DATA OPS
dbt Staleness RCA Agent: Investigate Stale Marts and Draft a Root Cause
When a stale-mart alert fires, an agent traces the dbt lineage, inspects recent run logs and source lag.
How it runs
The automated pipeline, trigger to output.
- TriggerStale-mart alert via webhook with incident idHTTP webhook
- ActionTrace upstream lineage and lags in SnowflakeSnowflake
- LogicFind earliest broken node from run logs
- LogicForm ranked root-cause hypothesis
- OutputPost RCA draft to the Linear incidentLinear
What it does
Takes a stale-table alert and does the first pass of investigation a human would. The agent walks the model's upstream lineage in Snowflake, reads the latest dbt run logs, checks whether the root cause is a stalled source, a failed model, or a slow run, and writes a plain-language root-cause hypothesis with the evidence it found. It posts the writeup as a comment on the related Linear incident.
When to use it
Use when freshness incidents land on-call without context and the engineer burns time reconstructing what broke. The agent hands them a head start: a likely cause and the lineage path to verify.
How it works
- 1A stale-mart alert arrives via HTTP webhook with the table and incident id.
- 2The agent queries Snowflake to trace the model's upstream lineage and load lags.
- 3It reviews recent dbt run logs to find the earliest broken node in the chain.
- 4It reasons over the evidence to form a ranked root-cause hypothesis.
- 5It posts the RCA draft with supporting evidence onto the Linear incident.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
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.
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.
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 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…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.