SUMMARIZATION

Sentry Budget-Burn Escalation Brief to PagerDuty

On a new Sentry release deploy, checks whether error-budget burn rate against the prior release crosses an alert threshold and, if so, pages on-call via PagerDuty with a concise…

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSentry release deployedSentrySentry
  • ActionFetch burn metrics for new vs prior releaseSentrySentry
  • LogicGate on budget-burn threshold breach
  • ActionSummarize regression briefOpenAI
  • OutputOpen PagerDuty incident with briefPagerDutyPagerDuty

What it does

Turns a post-deploy budget-burn spike into an actionable page. When a new release is deployed, it measures how fast the error budget is burning relative to the previous release and, only if the burn rate breaches your threshold, opens a PagerDuty incident with a short brief explaining which metric regressed and by how much.

When to use it

Use it when a bad deploy needs to wake someone, but you do not want to page on every release. The threshold gate keeps healthy deploys silent and reserves pages for real regressions.

How it works

  1. 1A Sentry release-deployed event triggers the flow.
  2. 2Release-health metrics are fetched for the new release and its predecessor.
  3. 3A logic gate evaluates whether the budget-burn rate exceeds the configured threshold; healthy deploys exit here.
  4. 4For breaches, an LLM writes a focused brief naming the regressed metric and magnitude.
  5. 5A PagerDuty incident is opened with the brief attached for on-call.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  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.