Operations | Monitoring | ITSM | DevOps | Cloud

How to debug a Next.js production bug with Logs and Sentry

Stack traces tell you what broke. They rarely tell you why. In this video, Serge walks through a real Next.js production bug that only affected Firefox and Safari. The error showed up clearly in Sentry, but the stack trace alone wasn’t enough to explain what was going wrong. The missing piece turned out to be logs. You’ll see how adding logs to a Next.js API route exposed unexpected request data, how those logs connected back to traces, and how that context made the root cause obvious and easy to fix.

[Workshop] Building and Monitoring AI Agents and MCP servers

​See how Agent Monitoring gives you a better look at all things model usage, call duration, prompting, and more ​Go under the hood with MCP Monitoring - and learn how to debug client connection issues, tool call performance, transports, and all things MCP ​When things start breaking, use Seer, Sentry's AI Debugging Agent to troubleshoot those vague issues that are crashing and get help from a team of robots using Sentry’s AI PR Review.