Data Engineering Intern

Automate Sentry with AI agents (2026). By Loïc Jané · Founder, Fleece AI How to automate Sentry with AI agents. At a Glance: Fleece AI connects to Sentry and lets autonomous agents triage errors, create bug tickets, monitor release health, and orchestrate incident workflows across 3,000+ apps. Updated March 2026. Sentry is the leading application monitoring and error tracking platform, used by over 100,000 organizations including Disney, Cloudflare, and Dropbox. Sentry captures errors, performance issues, and session replays in real-time - but the operational workflow of triaging errors, filing bugs, notifying the right teams, and tracking fixes still relies heavily on manual processes. Engineering teams spend an estimated 20% of their time on unplanned work, including bug triage and incident response, according to Google's State of DevOps report. When a Sentry dashboard shows hundreds of new errors after a deployment, the triage process alone can consume hours of engineering time that should be spent building features. Fleece AI connects to Sentry (and 3,000+ other apps) to automate error management workflows with autonomous AI agents. Set up your error triage automations in natural language and let the agent handle the noise. What Sentry automation looks like with AI. Sentry's built-in alerts send notifications on error thresholds. AI-native automation handles the full error lifecycle: 1. Intelligent error triage. "Every 30 minutes, check Sentry for new unresolved issues with more than 50 events. For each, analyze the stack trace to determine the affected service. Create a Jira bug ticket with the error message, affected file, event count, and first/last seen timestamps. Assign the ticket based on the file path's code ownership rules." 2. Release health monitoring. "After every deployment (tracked via Sentry releases), monitor error rates for the next 2 hours. If the error rate for the new release exceeds the previous release by more than 20%, send a rollback alert to Slack #deployments with the top 5 new errors, affected users count, and a link to the Sentry release dashboard." 3. Weekly error digest. "Every Monday at 9 AM, pull Sentry stats for the past week: total errors, new issues, resolved issues, and top 10 noisiest issues by event count. Post a formatted digest to Slack #engineering. Export the full data to Google Sheets for trend tracking." 4. Customer-Impacting error escalation. "When a Sentry issue reaches 1,000 affected users, immediately notify the product team on Slack, create a Linear issue with P0 priority, and send a heads-up to the support team via Gmail so they can prepare for incoming tickets." How it works. * Connect Sentry - Fleece AI authenticates via Pipedream using your Sentry API token. * Describe your workflow - Write what you want in plain English. The agent maps it to Sentry API endpoints. * Set a schedule - Choose a cron frequency or event-based trigger. * Agent executes - The AI agent reads issues, analyzes error data, and coordinates across connected apps. * Review results - Check execution logs in your Fleece AI dashboard. Cross-App workflows with Sentry. | Workflow | Apps Involved | | Auto-create bug tickets | Sentry -> Jira | | Critical error alerts | Sentry -> Slack | | Release health monitoring | Sentry + GitHub | | Error trends to spreadsheet | Sentry -> Google Sheets | | Customer-impact escalation | Sentry -> Linear | | Incident coordination | Sentry -> PagerDuty | Popular Sentry automations. For Engineering Teams: * Automated bug filing from high-frequency errors to Jira or Linear * Post-deploy error rate monitoring with rollback alerts * Weekly error noise analysis and resolution tracking For SRE and DevOps: * Critical error escalation to PagerDuty * Release comparison dashboards in Google Sheets * Infrastructure error pattern detection For Product Teams: * Customer-impacting error visibility reports * Error correlation with feature flag rollouts * User experience impact assessments Sentry automation vs Manual Triage. | Capability | Manual Triage | Fleece AI + Sentry | | Error detection | Check Sentry dashboard | Agent monitors continuously | | Bug filing | Copy-paste to Jira | Auto-creates with full context | | Release monitoring | Watch dashboards post-deploy | Agent alerts on regression | | Trend analysis | Monthly manual review | Weekly automated digests | | Escalation | Depends on who sees it | Auto-escalation by impact | Automate your error ops. Start free on Fleece AI - connect Sentry in 60 seconds. Frequently asked questions. Can Fleece AI read Sentry issues and events? Yes. Fleece AI agents can list projects, read issues, query events, and access error details including stack traces, tags, user context, and breadcrumbs through the Sentry API. This enables intelligent triage workflows that go beyond simple threshold alerts. Can Fleece AI resolve or ignore Sentry issues? Yes. The agent can update issue status (resolve, ignore, mark as reviewed) and set assignees through the API. This enables automated cleanup workflows - for example, auto-resolving known flaky errors or auto-assigning issues based on file path ownership. Do I need a paid Sentry plan? Sentry offers a generous free tier (5K errors/month for developer accounts). The API is available on all plans. Fleece AI connects through the standard Sentry Web API, so any plan with API access works. Higher-volume teams benefit from Sentry's Team or Business plans. How is this different from Sentry's built-in integrations? Sentry's built-in integrations (Jira, Slack, GitHub) handle one-to-one alert forwarding. Fleece AI agents orchestrate multi-step workflows: reading error data, analyzing patterns with AI, creating tickets with enriched context, notifying the right people on Slack, and tracking resolution across Jira or Linear - all in a single automated flow. Can Fleece AI correlate Sentry errors with deployments? Yes. If you use Sentry releases (linked to GitHub commits or tags), the agent can correlate new errors with specific releases. This enables automated release health checks: deploy, monitor for regressions, and alert the team if the new version introduces more errors than the previous one. * Automate Jira with AI - issue tracking automation * Automate Linear with AI - engineering project automation * Automate GitHub with AI - developer workflow automation * Automate PagerDuty with AI - incident management automation * Automate Slack with AI - team communication automation * Automate Bitbucket with AI - DevOps automation Try Fleece AI free - deploy your first Sentry error automation in under 60 seconds. Ready to delegate your first task? Deploy your first AI agent in under 60 seconds. No credit card required.

Sentry acquires XcodeBuildMCP. Today Sentry Inc. is announcing that Sentry has acquired XcodeBuildMCP, an open source MCP server that gives AI agents the ability to build, test, and debug native iOS and macOS apps. XcodeBuildMCP has become a go-to tool for agentic Apple-platform development, with more than 4,000 GitHub stars and an active community. It unlocks the full developer loop: build, run, debug, interact, and verify, allowing users to stay in their preferred agentic development environment. As part of this acquisition, the creator and maintainer Cameron Cooke will also join the Sentry team to help Sentry Inc. continue to improve Sentry's mobile tooling and the new agentic development landscape. Why this fits Sentry. Sentry is focused on making software more reliable and giving developers the fastest path from idea to production. For mobile teams, that path is still harder than it should be and was one of the reasons Sentry Inc. also acquired Emerge Tools in 2025. Apple platform tooling has again been slow to embrace agentic workflows, and developers are increasingly working in tools like Cursor, Claude Code, and Codex CLI rather than heavyweight IDEs. XcodeBuildMCP helps close that gap. It gives those agents the same real-world capabilities a developer has, which means they can iterate autonomously and verify changes instead of constantly handing control back to a human. What XcodeBuildMCP enables. Key capabilities include: * Build, run, and test apps on devices and simulators * Attach a debugger, inspect stack traces, and execute code * Capture simulator screenshots * Interact with running apps by tapping, swiping, and typing * Capture and stream runtime logs This is the closed loop developer workflow that makes agentic coding practical on Apple platforms. To get started, all you have to do is add this configuration to your MCP client of choice: { "mcpServers": {"XcodeBuildMCP": { "command": "npx", "args": ["-y", "xcodebuildmcp@latest", "mcp"]}}} Example workflow. XcodeBuildMCP turns high-level requests into working features. Here's what a typical interaction looks like when an agent has access to the full development loop: User: "Add dark mode support to my app." * Edited Theme.swift * Edited Settings.swift * XcodeBuildMCP: Found app project and build scheme * XcodeBuildMCP: Built and launched the app in the simulator * XcodeBuildMCP: Navigated to Settings * XcodeBuildMCP: Toggled the dark mode switch * XcodeBuildMCP: Captured screenshot * Verified dark mode is enabled Agent Response: "I've added dark mode support and verified it in the simulator." How this fits alongside Apple's MCP tooling. Apple has just started to support agentic development with Xcode's MCP tooling and agent integrations in the IDE. That's a positive move, but it still assumes a heavyweight IDE-first workflow. XcodeBuildMCP is IDE-agnostic. It supports developers who want the speed and flexibility of modern agentic tools while still building first-class Apple apps. In practice, XcodeBuildMCP also provides a broader and more complete capability set, especially for runtime debugging, simulator interaction, and automation, than Apple's current MCP tooling. Commitment to open source. Sentry is committed to open source and to the community that built XcodeBuildMCP. In 2024, Sentry Inc. helped launch the Open Source Pledge, a program that asks companies to contribute $2,000 per developer per year to the open source projects they depend on. Sentry Inc. created the pledge because the world runs on open source software, but the people maintaining it are often unpaid and burned out. The pledge is simple: pay the maintainers. Sentry Inc. don't think it's the only way to give back, but direct funding is a good way to recognize the work maintainers do and the value they create. Last year, Sentry gave $750,000 to open source maintainers, its fifth year in a row of direct funding. More than 25 companies have joined the pledge, collectively contributing over $6.8 million to open source since launch. The more who join, the more who will join, and the stronger the open source ecosystem will be. XcodeBuildMCP joins that ecosystem as a maintained, supported project that developers can rely on. Looking ahead. Sentry Inc. is continuing to invest in mobile and in the tooling that accelerates modern software teams. XcodeBuildMCP is now part of that mission, and Sentry Inc. is just getting started.