DATA OPS
BigQuery metric anomaly opens a Slack investigation thread with context
Runs a scheduled BigQuery query that scores a key metric for anomalies, and when one trips threshold it opens a Slack thread pre-loaded with the metric trend, recent deploys…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionScore watched metric against rolling baseline in BigQueryBigQuery
- LogicExit unless z-score exceeds threshold
- ActionPull top contributing dimension breakdowns from BigQueryBigQuery
- OutputOpen Slack investigation thread with full contextSlack
What it does
Every hour it queries BigQuery for a watched metric (signups, revenue, error rate), compares the latest value against a rolling baseline, and if the deviation exceeds your z-score threshold it opens a dedicated Slack investigation thread. The thread arrives with the trend chart description, the top contributing dimensions, and a link back to the query so the responder never starts from a blank page.
When to use it
Use it when a metric matters enough to page a human but you don't want false-alarm fatigue from naive threshold alerts. Good for revenue dips, conversion drops, or ingestion-volume cliffs where the first ten minutes of context-gathering are the painful part.
How it works
- 1A schedule fires hourly.
- 2BigQuery runs the anomaly-scoring query (latest vs. rolling mean and stddev).
- 3A logic step checks whether the z-score crosses the configured threshold; if not, it exits quietly.
- 4A second BigQuery call pulls the top dimension breakdowns driving the move.
- 5Slack posts a parent message and opens a threaded reply with the baseline, current value, deltas, and a deep link to the query.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.