ENGINEERING

Weekly Latency Envelope Recompute and PR

Each week, recompute per-query-shape p95 budgets from the latest Honeycomb data and open a GitHub pull request updating the budget config when production latency has drifted…

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionPull p95/p99 by query shape (30d)Honeycomb
  • LogicDiff observed vs committed budgets
  • ActionWrite updated budget config
  • OutputOpen PR with new budgetsGitHubGitHub

What it does

Latency budgets go stale as traffic and data grow. This workflow keeps them honest by recomputing every query shape's envelope from the trailing 30 days of Honeycomb data each week, then opening a pull request to update the committed budget file whenever the real p95 has drifted past a tolerance. The team reviews and merges, keeping the gate calibrated.

When to use it

Use it when your slow-query gate produces false positives or rubber-stamps because the budgets no longer reflect reality. It replaces manual budget tuning with a reviewable weekly proposal.

How it works

  1. 1A weekly schedule triggers the recompute.
  2. 2A Honeycomb action pulls p95 and p99 by query shape over the last 30 days.
  3. 3A logic step diffs the observed values against the committed budgets and keeps only shapes that drifted beyond tolerance.
  4. 4If nothing drifted, the run exits; otherwise it writes the updated budget config.
  5. 5A GitHub action opens a pull request with the new budgets and a per-shape changelog for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HoneycombDistributed traces and queries.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  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.