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...
React Native performance tactics: Modern strategies and tools
This is a guest post by Simon Grimm, founder of Galaxies.dev, a platform dedicated to helping developers master React Native through hands-on courses, expert gu...
You built the MCP server. Now track every client, tool, and request with Sentry.
TL;DR - Starting today, you can instrument most server-side JavaScript SDK based MCP servers with one line of instrumentation code within your MCP SDK implement...
Unity has a reputation for handing out surprises: the play-mode freeze just after a hot-reload, the sudden sea of pink materials, or the stack trace that polite...
Boosting Session Replay performance on iOS with View Renderer V2
After making Session Replay GA for Mobile, the adoption rose quickly and more feedback reached us. In less great news, our Apple SDK users reported that the per...
Debugging a production issue with Cursor? Your workflow probably looks like this: Alt-Tab to Sentry, copy error details, switch back to your IDE, paste into Cur...
Introducing new issue detectors: Spot latency, overfetching, and unsafe queries early
Not everything in production is on fire. Sometimes it’s just... a little warm. A page that loads a second too slow. An API that returns way more than anyone ask...
Evals are just tests, so why aren’t engineers writing them?
You’ve shipped an AI feature. Prompts are tuned, models wired up, everything looks solid in local testing. But in production, things fall apart—responses are in...
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.
