How @JoshFerge, an engineer at Sentry, debugged 60,000 failed requests with Metrics and Requests Insights — silencing alerts and eliminating those 404s in less than an hour.

Join us for a discussion with contributors, founders and CEOs of organizations like Laravel, Node.js, Prisma, and Supabase. Join us as these experts chat through the latest trends, technologies, and what’s next for backend development. Hear how they navigate challenges, listen to their community, and leverage cutting-edge tools to innovate fast.

Join Sentry engineer Yagiz Nizipli as he shares how he uses Sentry to fix Sentry. In this session, he’ll demo how he identified and optimized critical pipeline tasks, saving $160,000 per year. The improvements he made, including caching, improving traffic distribution, and enabling background threads Throughout the workshop, Yagiz will also share tips and best practices for using Tracing to uncover performance bottlenecks and drive continuous improvement across our own services.

Introducing new Insights for Caches and Queues– so you can finally figure out if your app is using caching correctly, why those cache misses are killing your latency, and see how queues are impacting your app's performance (while ensuring your background jobs aren’t being sent to /dev/null).

See which APIs you’re making requests to, how often, and the various interesting ways those requests are probably breaking.

Learn more: https://docs.sentry.io/product/insights/
Try Sentry for free: https://sentry.io
Follow: https://twitter.com/getsentry

Tools like Page Speed Insights and Google Lighthouse are great for providing advice for front end performance issues. But what these tools can’t do, is evaluate performance across your entire stack of distributed services and applications. This is why you need tracing.

Frontend issues that affect your users are often triggered by backend problems. Join us in this workshop so you can learn how to identify the issues causing your poor Core Web Vitals. Then, discover how to trace issues to slow database queries or the dreaded server-side request waterfall. In this session you’ll learn how to: Discover common sources for poor web vitals Setup tracing with Sentry Trace issues through your stack to the code-level with Sentry.

React 19 isn’t GA yet, but Sentry already supports it. The Sentry React SDK now supports React 19 and it’s new error handling hooks. This means that Sentry will automatically attach your component stack to every new error, making it easy to know where to look in your component tree for debugging.

See your source code in your JavaScript project’s stack trace by uploading source maps to Sentry. Learn how to use the Sentry source map wizard to unminify the code displayed in a Sentry issue’s stack trace.