AI AGENTS
Sentry Spike to PagerDuty Escalation with AI Context
When a Sentry issue's event rate spikes abruptly, an agent assembles a root-cause brief and triggers a PagerDuty incident pre-loaded with the diagnosis so on-call responders skip…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry event-rate spike detectedSentry
- LogicConfirm spike exceeds baseline and isn't a known flake
- ActionFetch trace, release, and impact metrics from SentrySentry
- ActionWrite root-cause brief and suggested first stepOpenAI
- OutputOpen PagerDuty incident with embedded briefPagerDuty
What it does
Upgrades a raw Sentry spike into a context-rich PagerDuty page. On a sudden surge in event rate, the agent gathers the stack trace, recent release info, and affected user count, has an LLM write a one-paragraph root-cause brief, and opens a PagerDuty incident that carries the diagnosis in the description — so whoever gets paged starts mid-investigation, not from zero.
When to use it
Use it when alert fatigue means responders open a page and stare at a stack trace with no idea where to begin. Best for teams running PagerDuty rotations who want every escalation to arrive with a working hypothesis attached.
How it works
- 1Sentry fires on an abrupt event-rate spike for an issue.
- 2A filter confirms the spike exceeds the baseline multiplier and isn't a known flake.
- 3The agent fetches the trace, latest release, and impact metrics from Sentry.
- 4An OpenAI model writes a concise root-cause brief and suggested first step.
- 5A PagerDuty incident is opened with the brief embedded for the on-call responder.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.