DATA OPS
Axiom High-Cardinality Label Blowup Detector
Scans Axiom datasets for label fields whose distinct-value count is exploding (the classic cardinality bomb), pins the runaway label.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery-few-hours schedule
- ActionCount distinct values per label, two windowsAxiom
- LogicCardinality growth past multiplier?
- LogicBranch on severity (high vs minor)
- ActionOpen Linear ticket for flagged labelLinear
- OutputRaise PagerDuty incident if high severityPagerDuty
What it does
A cardinality bomb, like a label suddenly carrying per-request IDs, can balloon ingest cost without raising total event count much, so byte-volume alarms miss it. This workflow profiles each label's distinct-value growth, identifies the field whose cardinality jumped most, and escalates based on severity.
When to use it
Use it when a recent deploy can accidentally promote a unique value (user ID, trace ID, timestamp) into an indexed label, quietly inflating storage and query cost across a shared Axiom dataset.
How it works
- 1A schedule runs every few hours against the target datasets.
- 2Query Axiom to count distinct values per candidate label over the last window versus the prior window.
- 3A logic gate flags any label whose distinct-value count grew past the configured multiplier.
- 4A severity branch splits high-impact blowups from minor ones.
- 5For any flagged label, open a Linear ticket naming the dataset, label, and cardinality delta.
- 6For high-severity cases only, also raise a PagerDuty incident so on-call can throttle the emitter before billing compounds.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.