DATA OPS

Honeycomb Cardinality Audit to Notion Runbook Tracker

Runs a weekly full-dataset cardinality audit and upserts each high-cardinality column as a tracked row in a Notion database.

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule starts audit
  • ActionPull cardinality and 4-week trend from HoneycombHoneycomb
  • LogicFilter to columns above threshold, compute trend
  • OutputUpsert offenders into Notion tracker databaseNotionNotion

What it does

Once a week this workflow audits every Honeycomb dataset for high-cardinality columns, then upserts each offender into a Notion database keyed by dataset and column name. Existing rows get their cardinality and volume trend updated; new offenders are created with a default status of `needs review`. The result is a durable, deduplicated backlog of cardinality debt instead of ephemeral alerts.

When to use it

Use it when you want cardinality reduction tracked like real work — owners, status, and trend over time — rather than alerts that scroll out of a Slack channel. Ideal for an observability guild driving a quarterly cost-reduction initiative.

How it works

  1. 1A weekly schedule starts the audit.
  2. 2Pull cardinality and 4-week volume trend for all columns from Honeycomb.
  3. 3Logic filters to columns above the cardinality threshold and computes their trend direction.
  4. 4Upsert each offender into the Notion tracker database, updating existing rows or creating new ones with `needs review` status.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HoneycombDistributed traces and queries.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.