SE: Sentry Triage — Autonomous Agents Agentic Workflow

schema_version: 1
id: agent_sentry_triage
title: "SE: Sentry Triage"
description: "Poll Sentry for new production errors, dedup against Jira, file Bug tickets with evidence and initial RCA"
overview: |
  A monitoring triage chain. The agent polls Sentry for fresh unresolved production errors across the account's projects, drops anything already tracked in Jira (matched by a sentry-<short-id> label), and files the most impactful remainder as Bug tickets — each with evidence, a stack-trace excerpt, and an initial root-cause hypothesis mapped to repo code. Tickets land in the backlog untouched; Jira webhook automations and playbooks drive the fix lifecycle from there.

  Run this on a schedule (cron automation) pinned to the one agent that holds a Sentry auth token and the Sentry MCP server. It is intentionally shallow on purpose: deep RCA, fixing, and regression testing belong to the downstream bug-fix playbook, so this workflow only watches, dedups, and reports.

category:
  level: pipeline
  domain: engineering

metadata:
  agent: true
  role: se

params:
  sentry_org:
    type: string
    default: "aictpo"
    description: "Sentry organization slug"
  sentry_projects:
    type: string
    default: "sidebutton-server, sidebutton-portal, sidebutton-extension, sidebutton-dashboard"
    description: "Comma-separated Sentry project slugs to check"
  jira_project:
    type: string
    default: "SCRUM"
    description: "Jira project key for new Bug tickets"
  max_tickets:
    type: string
    default: "3"
    description: "Max new tickets per run"
  hint:
    type: string
    default: ""
    description: "Optional extra instructions for the agent"
  entry_path:
    type: string
    default: "~/workspace"
    description: "Working directory for the agent"

steps:
  - type: terminal.open
    title: "Agent: Sentry Triage"
    cwd: "{{entry_path}}"
  - type: terminal.run
    cmd: |
      source ~/.agent-env && claude --dangerously-skip-permissions "$(cat <<'SB_PROMPT'
      use the sentry mcp tools, org {{sentry_org}}. if sentry tools are unavailable or auth fails, stop and report the error.
      search issues in each project separately - {{sentry_projects}} - with query "is:unresolved is:for_review" sorted by freq. org-wide search silently returns nothing, so always pass the project.
      for every candidate issue, check jira for an existing ticket: jql search {{jira_project}} for label sentry-<short-id, lowercased>. skip candidates that already have a ticket, regardless of its status.
      skip pure infrastructure noise (broken pipes, EPIPE spam, network blips) unless new or clearly escalating.
      pick at most {{max_tickets}} remaining issues, highest impact first (event count, users affected, recency).
      for each picked issue fetch full details - stack trace, event count, first/last seen, environment, server/release. locate the crashing frame in the repo code in your workspace and name the suspected cause (file:line). initial rca only - do not implement a fix.
      {{hint}}
      create one Bug in {{jira_project}} per picked issue and leave it in the backlog - no transitions, no assignee, no extra comments; downstream automations take it from there. labels: sentry plus sentry-<short-id, lowercased>. title: Sentry: <error title> (<SHORT-ID>). description: sentry issue link, evidence (event count, first/last seen, environment, server), short stack trace excerpt, suspected root cause with file:line refs, user impact, recommended priority. set the jira priority field to match.
      finish with one summary line: tickets created (keys), duplicates skipped (count), or no new issues.
      SB_PROMPT
      )"