DATA OPS
Stale Table Upstream Root-Cause Tracer
When a freshness alert fires, an agent walks the table's upstream lineage and recent job logs to pinpoint which dependency or load job actually broke.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: freshness breach receivedHTTP webhook
- ActionFetch upstream lineage + run historySnowflake
- ActionPull load-job logs and failuresAxiom
- LogicIdentify earliest broken hop and failure class
- OutputFile Linear issue with root-cause hypothesisLinear
What it does
Given a table that missed its load window, this agent traces the dependency chain backward through Snowflake lineage and the ingestion job logs in Axiom to find the earliest failing or stalled step. It distinguishes "upstream source never arrived" from "transform job errored" from "job ran but produced zero rows," then opens a Linear issue with the diagnosis and supporting evidence.
When to use it
Use it when freshness breaches are frequent enough that manually tracing each one through lineage and logs eats your on-call's morning. It does the first hour of investigation automatically.
How it works
- 1A freshness-breach webhook delivers the stale table name and its SLA lag.
- 2The agent pulls the upstream lineage and recent run history from Snowflake.
- 3It queries Axiom for the corresponding load-job logs and failure signatures.
- 4It reasons over the chain to identify the earliest broken hop and the failure class.
- 5It files a Linear issue with the root-cause hypothesis, evidence links, and severity.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect HTTP webhookTrigger any URL on agent 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
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.