Watching everything is watching nothing: Sampling strategy for Sentry
TL;DR - Blanket sampling rates can be wasteful or inefficient. Capture 100% of the signal with less of the noise and fine-tune how you monitor your applications...
Less code, faster builds, same telemetry: Turbopack support for the Next.js SDK
TL;DR - Turbopack became the default in Next.js, so we reworked our SDK to stop depending on bundlers. The result is less code, faster builds, and the same tele...
Log Drains now available: Bringing your platform logs directly into Sentry
Sentry now supports log drains, making it easy to forward logs into Sentry without any application code changes or manual project-key lookups needed. If your lo...
When we launched Seer, our AI debugging agent, we built it on a core belief: production context is essential for understanding the complex failure modes of real...
Monitoring microservices and distributed systems with Sentry
If you’ve ever tried to debug a request that touched five services, a queue, and a database you don’t own, you already know why monitoring distributed systems i...
A VP of Engineering (from a company I’m not allowed to name) told me recently: "You helped us find and fix real user-facing issues. Now we need to convince our ...
Paginating large datasets in production: Why OFFSET fails and cursors win
The things that separate an MVP from a production-ready app are polish, final touches, and the Pareto ‘last 20%’ of work. Many of the bugs, edge cases, and perf...
Logs are often the first place dev teams look when they investigate an issue. But logs are often added as an afterthought, and developers struggle with the bala...
Not everything that breaks is an error: a Logs and Next.js story
Stack traces are great, but they only tell you what broke. They rarely tell you why. When an exception fires, you get a snapshot of the moment things went sidew...
At Sentry, interns aren’t just observers, they’re teammates who ship meaningful work. This fall, our software engineering interns across our San Francisco and T...
Unity SDK 4.0.0: Console support, logs, user feedback and more
We just released the Sentry SDK for Unity 4.0.0 , our biggest update yet. This major release brings comprehensive gaming console support, structured logging, us...
Trace-connected structured logging with LogTape and Sentry
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 ...
Another year, another $750,000 to Open Source maintainers
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 softw...
Building a Code Review system that uses prod data to predict bugs
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...
Here's a quick look at how Sentry handles your personal information (PII).
×
Who we collect PII from
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
