Operations | Monitoring | ITSM | DevOps | Cloud

You already have every error, trace, log, and replay in Sentry. Now let Seer, our agent debugger, do its thing: use that context to find what broke, why it broke, and how to fix it.

See what your users see. Don't try and guess what happened, watch it. Session Replay is a feature for Mobile and Web apps on Sentry to record user sessions as reproducible sessions. These are not videos. On web, a session replay contains the entire DOM reconstruction and DevTools. It's exactly like inspecting in Chrome DevTools locally on your machine, but in a real production session.

Andrea Griffiths is a Senior Developer Advocate at GitHub. She uses Sentry to monitor the Python scripts behind GitHub’s community streams, because when those pipelines fail, nobody knows until users start complaining. GitHub and Sentry built a loop that fixes that. Sentry catches the error, Seer diagnoses it, and Copilot drafts the fix. No one has to be in the middle of it. In this session, Paul Jaffre (Developer Experience at Sentry) breaks down what Seer is, then he and Andrea break a real script live and watch the loop catch it, diagnose it, and open the fix as a pull request.

We talk a lot about fixing bugs, but we never actually talked to one. Until now. Thank you, Judd, for your candor and bravery. Sentry will never be the same.

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.