DEVOPS

Weekly error-budget review report from Honeycomb to Notion

Every Monday, gathers each service's week-over-week SLO compliance and budget consumed from Honeycomb, writes a structured review page in Notion.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionPull 7-day + prior-week SLO data from HoneycombHoneycomb
  • LogicCompute deltas, tag improving/regressing
  • ActionCreate review page in NotionNotionNotion
  • OutputPost Notion link to SlackSlack

What it does

Produces the artifact your weekly reliability review needs. It reads each tracked SLO's compliance and budget burned over the past seven days from Honeycomb, builds a Notion page with a per-service table and trend notes, and drops the link in Slack so the meeting starts with data already on the page.

When to use it

Use it when you hold a recurring SLO or error-budget review and someone currently assembles the numbers by hand. Turns a 30-minute prep chore into an automatic Monday-morning page.

How it works

  1. 1A weekly schedule fires Monday morning before the review.
  2. 2The flow queries Honeycomb for each SLO's seven-day compliance and budget consumed, plus the prior week for comparison.
  3. 3A logic step computes deltas and tags services as improving, flat, or regressing.
  4. 4It creates a Notion page from a template with the per-service table and headline summary.
  5. 5It posts the Notion link to the review Slack channel as the agenda anchor.

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
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.