Operations | Monitoring | ITSM | DevOps | Cloud

This video walks through connecting Sentry's MCP server to a Warp Agent, so instead of an agent starting from a raw error, it starts from Seer's actual root cause diagnosis: the error, the surrounding code, and recent commits. From there, the Warp Agent takes that diagnosis, implements the fix directly in the codebase, and opens a PR, all without leaving Warp.

Agents are pretty good at fixing your apps. We can make them even better. ​In this workshop we’re going to show you how to give your agents superpowers using Seer, the Sentry MCP server, and CLI tool. Join to learn how to: ​- Teach agents how to best implement and work with Sentry through agent skills and the CLI tool. ​- Set up Seer’s agent handoff feature for Claude, Cursor, or GitHub Copilot and have agents start automatically generating pull requests for fixes.

At any given moment, your AI systems can be down, slow, overloaded, or just returning bad results. Someone's gotta babysit the bots. Sentry traces across your AI pipeline, from user request to final response, so you can see exactly what's happening and fix it.

This workshop goes beyond the basics to show you how to monitor critical experiences in your application with workflows using dashboards, tracing, logs, and metrics.

Try Sentry for free: https://sentry.io/welcome
Docs: https://docs.sentry.io

Seer, Sentry's AI debugger, analyzes your issues and finds the root cause. Now you can pass that analysis directly to a GitHub Copilot agent which picks up the context, generates a fix, and opens a pull request. The agent session and PR both live on GitHub, with a link back in Sentry for easy access. This video walks through how the integration works and how to set it up in just a couple steps.

Join us for a conversational workshop with Simon Grimm, creator of Galaxies.dev and solo developer behind Tiny Harvest, as he shares how he monitors and debugs a real, live React Native app in production.

You set up Sentry. Errors are flowing in. You'd call it instrumented. We'd call it a start. When something breaks, you should know what failed, which commit caused it, who owns it, and what the user saw — without jumping between tools or getting surprised by your bill. Most teams are closer to that than they think. This is the 201 session for teams who got Sentry firing events and stopped there.

Your AI agent just did something unexpected. Was it a hallucination? A bad tool call? Or did it actually handle things correctly? Sentry Conversations lets you replay the full exchange and find out.

Next.js applications can be challenging to debug in production. It’s not always clear where an issue originated or how it impacts users. Hydration errors, server component failures, and performance bottlenecks don’t always come with clear answers.