At Sentry, interns aren’t just along for the ride, they’re part of the team. This summer, our crew of software engineers, biz ops problem-solvers, and even an a...
Session Replay: Becoming your own digital secret shopper
Retail stores have long relied on a secret weapon to measure and improve the shopping experience: the secret shopper. Posing as ordinary customers, they evaluat...
Sentry AI code review, now in beta: break production less
This could’ve been prevented. This should have been prevented. This too. We all hate getting tagged in PRs. The time, the blame for when you inevitably miss som...
Inside Sentry’s Hackweek: An excuse to break things
During Sentry’s Hackweek, many ‘sentaurs’ used the opportunity to build useful additions to the Sentry service to help provide value for years to come. Not us t...
I turned error messages into a sales machine (by accident)
Dan Mindru is a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications includin...
Frontend JavaScript performance testing: A comprehensive guide
When a page pauses for even a quarter-second users feel it, and many will tab away before the spinner stops. Front-end performance testing lets us spot those de...
How we used Sentry’s User Feedback widget to shape Logs throughout beta
At Sentry, we build in public and we move fast. But moving fast means we don’t always get everything right on the first try. That’s where feedback comes in: it ...
Logic errors, failed HTTP requests, background jobs that ghost silently—software breaks in all kinds of fun ways. The difference between resilient systems and f...
Crash reporting for gaming consoles is now Generally Available
TL;DR: Error monitoring and crash reporting for all major gaming consoles is now generally available (plus, the v1.1 of our Unreal Engine SDK). Already convince...
SvelteKit observability just got 10x better, and we’re here for it
The Svelte Team recently announced full observability and tracing support for SvelteKit! This is great news for SvelteKit and Sentry users, since Sentry is alre...
Logs are Generally Available (Still logs, just finally useful)
When we started building Logs in Sentry we had one goal: make them useful for real debugging, not just another high-volume text storage. This meant making them ...
The core KPIs of LLM performance (and how to track them)
A few months ago, I built an MCP server for Toronto’s Open Data portal so an agent could fetch datasets relevant to a user’s question. I threw the first version...
How to measure and fix latency with edge deployments and Sentry
A 2017 study by Google, researchers found: As page load time goes from 1 to 3 seconds, the probability of bounce increases 32%. That was over 8 years ago. And l...
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.
