DATA OPS
Honeycomb Cardinality Proposal with Linear Ticket and Slack Approval Loop
Detects a sustained high-cardinality spike, posts a consolidation proposal to Slack for human approval.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule triggers spike check
- ActionConfirm sustained spike in HoneycombHoneycomb
- ActionPost proposal to Slack with approve/dismissSlack
- LogicBranch on reviewer approval decision
- OutputCreate scoped Linear issue for owning team on approvalLinear
What it does
This workflow catches sustained high-cardinality spikes (not one-off blips), generates a derived-column consolidation proposal, and posts it to Slack with approve and dismiss actions. If a reviewer approves, it creates a Linear issue scoped to the offending dataset and routes it to the owning team; if dismissed, it records the decision and moves on. It puts a human gate between detection and ticket creation so the backlog stays clean.
When to use it
Use it when you want proposals reviewed before they become work — avoiding ticket spam from transient spikes while still capturing the ones that matter. Ideal for teams with dataset ownership mapped to Linear teams.
How it works
- 1A schedule triggers the spike check.
- 2Query Honeycomb and confirm the spike has persisted across multiple intervals.
- 3Draft a consolidation proposal and post it to Slack with approve/dismiss actions.
- 4Logic branches on the reviewer's response.
- 5On approval, create a scoped Linear issue assigned to the owning team.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.