Operations | Monitoring | ITSM | DevOps | Cloud

This post takes a closer look at how Sentry’s AI Code Review actually works. As part of Seer, Sentry’s AI debugger, it uses Sentry context to accurately predict bugs. It runs automatically or on-demand, pointing out issues and suggesting fixes before you ship. We know AI tools can be noisy, so this system focuses on finding real bugs in your actual changes—not spamming you with false positives and unhelpful style tips.

Note: This blog post was originally published for the Early Access of Size Analysis. if you're already familiar with Size Analysis in Sentry, go to the section titled What's new in the beta. If you're not familiar with Size Analysis, start at the section titled The curious case of man.jpg.

We launched agent monitoring earlier this year, allowing our users to instrument LLM usage and tool calls in their applications. However, we only had Agent Monitoring support for Python and JavaScript. We’ve been working on creating an Agent Monitoring SDK for.NET — specifically for Microsoft.Extensions.AI.Abstractions.

We’ve introduced a new type of Performance Issues, Web Vitals Performance Issues. These issues will be opened for the highest opportunity pages in your application if your Web Vitals metrics drop into our meh, or poor thresholds for performance. We’ve built these issues with Seer Issue Fix specifically in mind. Our goal is to not just alert you about low vitals scores, we want to give you actionable steps you can take to improve your scores and, when possible, fix the problem for you.

Instead of giving you yet another chatbot, we built AI straight into the parts of Sentry where teams lose time, turning your existing data into instant context — and it’s now available to all Sentry users.