DATA OPS
BigQuery Scheduled-Query Duration Regression Watcher
After each run, it pushes scheduled-query execution time and bytes-scanned as metrics to Datadog and raises an alert when a query's runtime regresses sharply versus its baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionRead run durations and bytesBigQuery
- ActionSubmit metrics to DatadogDatadog
- LogicFlag duration regressions vs baseline
- OutputNotify owning team in SlackSlack
What it does
It instruments scheduled queries as Datadog metrics and watches for performance regressions. A query that quietly creeps from two minutes to twenty isn't failing yet, but it's heading toward blowing its SLA window. This catches that drift early and feeds dashboards and monitors you already operate.
When to use it
Use it when you want scheduled-query performance to live in the same observability stack as the rest of your services, and when slow-burn degradation matters as much as hard failures. Best for teams standardized on Datadog for monitoring and on-call.
How it works
- 1A schedule fires every 15 minutes to sweep recently completed runs.
- 2A BigQuery action reads job durations and bytes scanned for scheduled queries from `INFORMATION_SCHEMA.JOBS`.
- 3A Datadog action submits per-query duration and bytes as tagged custom metrics.
- 4A logic step compares each run's duration to its recent baseline and flags significant regressions.
- 5A Datadog action posts an event annotation for flagged regressions; a Slack output notifies the owning team with the trend.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.