AI AGENTS
Sentry Error Cluster to Failing-Test GitLab MR
When a Sentry issue crosses an event threshold, an agent reproduces the crash, writes a failing test that captures it, and opens a draft GitLab merge request with the repro.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue crosses event-count thresholdSentry
- ActionFetch stack trace, breadcrumbs, and framesSentry
- ActionClone repo and reproduce in shell sandboxShell
- LogicContinue only if error signature matches
- ActionWrite failing test and commit to branchShell
- OutputOpen draft GitLab MR with repro + failing testGitLab
What it does
Watches Sentry for newly escalating error clusters and turns them into actionable engineering work. The agent reads the stack trace, reproduces the failure locally in a sandboxed shell, authors a failing test that pins the bug, and opens a draft GitLab merge request so a human can pick up a confirmed, test-backed defect instead of a raw alert.
When to use it
Use it when your team drowns in Sentry alerts and wants only reproducible, test-backed bugs to reach the MR queue. Ideal for backend services with a fast local test harness.
How it works
- 1A Sentry issue alert fires when an error cluster passes its event-count threshold.
- 2The agent pulls the full stack trace, breadcrumbs, and offending frame from the Sentry issue.
- 3It clones the repo and runs a shell sandbox to reproduce the exception from the captured inputs.
- 4Logic gate: only continue if the repro actually raises the same error signature.
- 5The agent writes a failing test asserting the buggy behavior and commits it to a branch.
- 6It opens a draft GitLab MR linking the Sentry issue, with the failing test and repro notes in the description.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.