Operations | Monitoring | ITSM | DevOps | Cloud

As our applications grow from simple side projects into complex distributed systems with many users, the “old way” of console.log debugging isn’t going to hold up. To build truly observable systems, we have to transition from simple text logs to structured, queryable, trace-connected events.

Bored yet? 2025 was the fifth year in a row (2024, 2023, 2022, 2021) that Sentry gave a pretty hefty chunk of change to the maintainers of the Open Source software that we rely on and love. This is our first report since we launched the Open Source Pledge, which brings together companies that share our respect for the independent maintainers in the community. Pledge members have collectively paid $4.5M to Open Source maintainers and foundations since launch. No more excuses!

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.