DEVOPS
Sentry Error Spike to Suspect-Deploy Correlation
When Sentry detects a new error spike, find the GitHub deploy that likely caused it, summarize the regression with an LLM, and post a candidate-cause report to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry error spike alertSentry
- ActionRead issue first-seen, stack trace, and releaseSentry
- ActionFetch GitHub deploys and PRs before the spikeGitHub
- LogicRank suspect commits and summarize regression with LLMOpenAI
- OutputPost suspect-cause report to SlackSlack
What it does
Correlates a fresh error spike in Sentry with the most recent code that shipped, so responders start triage with a prime suspect instead of a blank page. It pulls the failing issue's first-seen timestamp, finds the GitHub deployments and merged PRs just before it, asks an LLM to summarize the likely regression, and posts a ranked suspect-commit report to Slack.
When to use it
Use it when error spikes in production are hard to trace back to a release, and you want an automatic 'what changed right before this broke' brief on every new Sentry issue.
How it works
- 1Sentry fires an alert for a new or regressed issue crossing its event threshold.
- 2The flow reads the issue's first-seen time, stack trace, and affected release.
- 3GitHub is queried for deployments and PRs merged in the window just before first-seen.
- 4An LLM ranks the suspect commits by how well their changed files match the failing stack frames and writes a plain-English cause summary.
- 5A Slack message posts the suspect ranking, the regression summary, and direct links to the issue and each candidate PR.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.