Operations | Monitoring | ITSM | DevOps | Cloud

Tracing does a lot more than help you monitor performance. It's what ties errors, logs, and session replay together in Sentry, so you, and your agents actually know what happened. It's included in every Sentry plan.

Sentry brings errors, logs, replays, spans, and metrics together to find and fix the worst issues in your application.

Join us for a hands-on workshop where we go deep on structured logging: what to capture, how to structure it, and how to stay informed so your next incident has a paper trail.

Learn how to user agents to turn Slack alerts into autonomous RCA sessions, build incident memory, and help on-call engineers move from signal to fix faster. ​Join us for the live stream demo of Incident Response. We will break things on stream and let agents fix them. We will watch Droid run a real incident from alert to fix, and we show exactly what it read to get there.

Seer, Sentry's agent 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.

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.

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.