DATA OPS
Honeycomb Event-Volume Spike PagerDuty Cost Guardrail
Watches Honeycomb event ingest in near-real-time and pages on-call via PagerDuty when a single dataset's volume breaches a daily budget.
How it runs
The automated pipeline, trigger to output.
- TriggerShort-interval schedule triggers check
- ActionQuery Honeycomb ingest rate and per-column contributionHoneycomb
- LogicProject daily volume and compare to dataset budget
- LogicIdentify top contributing high-cardinality columns
- OutputOpen PagerDuty incident with overage and offendersPagerDuty
What it does
This workflow checks Honeycomb ingest volume on a tight interval, projects each dataset's daily event count against a per-dataset budget, and when a dataset is on pace to blow its budget it triggers a PagerDuty incident. The incident body names the specific high-cardinality columns contributing most to the spike so on-call can act immediately.
When to use it
Use it when an accidental log-level change or a chatty new field can quietly 10x your Honeycomb bill in hours. This is the real-time guardrail that catches cost runaways before they compound overnight.
How it works
- 1A short-interval schedule triggers the check.
- 2Query Honeycomb for current ingest rate and per-column contribution per dataset.
- 3Logic projects end-of-day volume and compares it to each dataset's budget.
- 4If a dataset is over pace, identify the top contributing high-cardinality columns.
- 5Open a PagerDuty incident with the dataset, projected overage, and offending columns.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.