SUMMARIZATION
Sentry Error-Budget Burn Brief Posted to GitLab MR
When a GitLab merge request is marked ready, compares Sentry release-health metrics between the current deploy and the previous release.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR marked readyGitLab
- ActionResolve candidate vs prior release tagsGitLab
- ActionFetch Sentry release-health for both releasesSentry
- ActionSummarize error-budget burn deltaOpenAI
- OutputPost regression brief as MR commentGitLab
What it does
Attaches a release-health verdict to every merge request before it lands. It pulls Sentry's crash-free session rate and unhandled error count for the candidate release and the release it would replace, computes how much of the error budget each one burns, and writes a short reviewer-facing brief directly on the GitLab MR.
When to use it
Use it when your team gates merges on stability and you want reviewers to see regression risk without opening Sentry. Ideal for services with defined crash-free SLOs where a noisy deploy should block the merge.
How it works
- 1A GitLab MR transitions to ready and fires a webhook.
- 2The flow resolves the candidate release tag and the prior production release from the MR metadata.
- 3Sentry release-health stats are fetched for both releases: crash-free sessions, crash-free users, and unhandled error volume.
- 4An LLM summarizes the delta into a budget-burn brief with a clear pass or regression verdict.
- 5The brief is posted as a comment on the originating GitLab merge request.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SentryErrors, performance, releases.
- 3Connect OpenAIModels, embeddings, files.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.