DEVOPS
Sentry Error-Spike AI Triage and Dedup to Linear
On a Sentry error-spike alert, an agent reads the stack trace, checks for an existing duplicate issue.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry error-spike alert firesSentry
- ActionAgent fetches stack trace and breadcrumbsSentry
- ActionSearch Linear for duplicate by fingerprintLinear
- LogicBranch on existing vs new failure
- ActionComment on existing or file new Linear ticketLinear
- OutputPost one-line digest to SlackSlack
What it does
When Sentry detects a spike in a new error, this workflow uses an agent to read the stack trace and breadcrumbs, draft a plain-English summary of the likely cause, and decide whether the spike is a duplicate of an existing investigation. Duplicates get a comment; genuinely new failures get a fresh Linear ticket with severity and the Sentry link.
When to use it
Use it when error-spike alerts pile up faster than engineers can read them, and the same root cause keeps spawning redundant tickets. Best for teams using Sentry for error monitoring and Linear for engineering work tracking.
How it works
- 1Sentry fires an alert when an issue crosses its spike threshold.
- 2The agent fetches the full stack trace, tags, and recent breadcrumbs from Sentry.
- 3It searches Linear for an open ticket referencing the same fingerprint or file.
- 4A branch decides: existing ticket found vs. new failure.
- 5If found, it comments on the Linear ticket with the new occurrence count and timeframe.
- 6If new, it files a Linear ticket with an AI root-cause summary, severity, and Sentry link.
- 7The final step posts a one-line digest to the team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 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 DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.