Operations | Monitoring | ITSM | DevOps | Cloud

Session Replay for Unreal Engine: see the crash before the crash

You know the drill: a crash report lands in your queue with a pristine stack trace pointing at some innocent-looking function and absolutely no clue about what the player was actually doing. Were they mid-boss-fight? Alt-tabbing during a loading screen? Standing perfectly still in the tutorial? QA can’t repro it, the player’s bug report says “game crashed lol,” and you’re left staring at a callstack playing twenty questions with a core dump.

From 57 bugs to 1, thanks to Seer

I was at the dentist the other day, getting ready for my appointment. The waiting room was pompously decorated. Each chair seemed to be from a different, expensive Danish designer. As I realize I’m about to get charged through the nose, I get a notification from my beloved Mail app. ** ding ** Screenshot of GitHub email notification It’s a new Pull Request on GitHub. This one is different though. I have no idea where it came from!

Sentry + GitHub Copilot Agents

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.

How to structure a log

You’ve decided to step up your logging game and start sending more valuable, structured logs that you can query, aggregate, and use for debugging in production. Go, you! Now, uh, how do you actually write them? We’re not going to spend much time on what you should log. We’ve covered that already, a few times before. What we will be covering is how to actually write those logs, answering questions like: What makes a log structured is not just pairing messages with arbitrary JSON objects.

MongoDB Query Tracing in .NET with Sentry + OTLP

If your.NET app talks to MongoDB, you almost certainly want to be able to measure DB performance so that you can effectively debug any performance issues you might run into. For that, you need to know which database command was running, how long it took, and whether this was a one-off blip or part of a broader pattern. Ideally, you also want to pivot from that trace to related errors and replays without stitching the story together by hand.

Session Replay: Reproducible User Sessions

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.

Sentry + GitHub Copilot: Let Agents Find and Fix Your Errors

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.