AI AGENTS
Sentry Spike Triage with Slack Reproduce-or-Skip Gate
On a Sentry error spike, an agent attempts a quick repro and posts a Slack triage card; an engineer's approval there decides whether it proceeds to draft a failing test in GitLab.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry error-rate spike alertSentry
- ActionFetch grouping, frames, affected releasesSentry
- ActionRun lightweight shell repro attemptShell
- ActionPost Slack triage card with action buttonsSlack
- LogicContinue only on engineer approval
- OutputWrite failing test and open draft GitLab MRGitLab
What it does
Adds a human-in-the-loop gate to auto-reproduction. When Sentry detects an error-rate spike, the agent does a lightweight reproduction attempt and posts a Slack triage card summarizing the error, likelihood of a real bug, and repro result. An engineer clicks Reproduce or Skip; only an approval pushes the agent to write a full failing test and open a GitLab MR.
When to use it
Use it when fully automated MR creation is too noisy and you want a fast human decision before committing engineering artifacts to GitLab.
How it works
- 1A Sentry metric alert fires on an error-rate spike.
- 2The agent fetches the issue grouping, top frames, and affected releases.
- 3It runs a short shell repro attempt and classifies confidence.
- 4The agent posts a Slack triage card with the summary, repro result, and action buttons.
- 5Logic gate: continue only if an engineer approves on Slack.
- 6On approval, the agent writes the failing test and opens a draft GitLab MR; on skip, it closes the loop with a note.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect GitLabRepos, MRs, pipelines, registry.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.