Operations | Monitoring | ITSM | DevOps | Cloud

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.

Aggregate and query logs on Sentry. Add logs to your errors, errors to not only make debugging easier, but also give valuable context to Seer AI. Logs help you and Seer better understand issues.

Get started with Sentry for Next.js in just one minute.

Learn about Sentry's Session Replay in 60 seconds.

You can use the Sentry MCP server to debug issues in applications that are built in v0. You can also use it to create projects, pull down configurations, or dig into performance issues in applications. Check it out.

We're looking at what building a standard set of tools to use in Claude Code looks like for Sentry - and Claude's plugin marketplace is a great way to distribute them. Take it for a spin - the plugin distributes the MCP server, a few skills for setting up core parts of Sentry, and a few commands to use.