AI AGENTS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue marked resolvedSentry
- ActionFetch issue detail, resolving commit, and commentsSentry
- ActionSearch runbook repo for matching error coverageGitHub
- LogicSkip if runbook already documents this failure
- ActionAgent drafts missing remediation steps
- ActionOpen doc PR with new runbook sectionGitHub
- OutputPost PR link to Slack, tag the resolverSlack
What it does
Every time an on-call engineer resolves a Sentry issue, this agent inspects how it was fixed and checks whether your runbook already documents that failure mode. If the steps are missing or stale, it drafts the new section and opens a GitHub pull request against your docs repo, then pings the resolver in Slack to review.
When to use it
Use it when tribal knowledge keeps walking out the door — incidents get resolved in chat, but the runbook never catches up, so the same alert pages a fresh engineer at 3am. Best for teams running Sentry alerting against a Git-versioned docs repo.
How it works
- 1Sentry fires when an issue transitions to resolved.
- 2The agent pulls the issue: stack trace, breadcrumbs, resolving commit, and any comments explaining the fix.
- 3It searches the runbook in the GitHub repo for an existing section covering this error signature.
- 4If coverage exists and is accurate, it stops. Otherwise it drafts a remediation section grounded in the actual fix.
- 5It opens a PR with the new or updated runbook content.
- 6It posts the PR link to Slack, tagging the engineer who resolved the issue for review.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.
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.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
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.