AI AGENTS

Slack ChatOps Sentry Cluster Investigator

An engineer pastes a Sentry issue link in Slack and the agent fetches the trace, cross-references GitHub, and replies in-thread with a root-cause analysis and an offer to file…

CategoryAI Agents
Enginepaperclip
Difficultyintermediate
Triggerchat
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack message with a Sentry issue linkSlack
  • ActionFetch event, stack trace, and tags from SentrySentrySentry
  • ActionCross-reference files and commits on GitHubGitHubGitHub
  • ActionProduce root-cause analysis and bug summaryOpenAI
  • OutputReply in-thread with analysis and confirm-to-file Linear optionSlack

What it does

Makes Sentry investigation a chat command. An engineer drops a Sentry issue URL into a Slack channel; the agent pulls the full event and stack trace, cross-references the implicated code on GitHub, and replies in the same thread with a root-cause analysis, suspected change, and a ready-to-confirm Linear bug draft — all without leaving Slack.

When to use it

Use it during live debugging or standup when someone shares an error and the team wants instant context. It fits teams who prefer pull-based, conversational triage over automated ticket creation, keeping a human in the loop on whether to escalate.

How it works

  1. 1A Slack message containing a Sentry issue link triggers the agent.
  2. 2The agent fetches the event, stack trace, and tags from Sentry.
  3. 3It cross-references the referenced files and recent commits on GitHub.
  4. 4An OpenAI model produces a root-cause analysis and a proposed bug summary.
  5. 5The agent replies in-thread on Slack with the analysis and a confirm-to-file Linear option.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect SentryErrors, performance, releases.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Connect LinearIssues, projects, cycles, triage.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.