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...
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...
How To Optimize ASP.NET Core Performance With Monitoring Tools
Slow requests are never subtle. They clog your logs, grumble in your profilers, and surface the moment your PM walks by. ASP.NET Core gives you the basics: buil...
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...
Using distributed tracing to debug timeout errors in Next.js
Next.js lets you write the UI, the API, and everything in between, so when a request stalls it can feel like you’re chasing a bug through a hall of mirrors. Wit...
How Sentry could stop npm from breaking the Internet
Caching is great! When it works… When it fails, it puts a big load on your backend, resulting in either a self-inflicted DoS, increased server bills, or both. T...
How to Configure Lightweight Browser Tracing for Debugging at Scale
Sentry’s auto-instrumentation, using BrowserTracing, is convenient. You can get interesting insights about your frontend application out-of-the-box, such as whe...
Introducing Sentry's Godot SDK 1.0 Alpha, with support for Godot 4.5 Beta
Debugging during development is easy. You've got a debugger, stack traces, and logs right in front of you. But once your Godot game is in the hands of players, ...
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...
Want to hear your users' complaints? There's a widget for that (now available on mobile)
A disappearing “Submit” button. A modal stuck half-offscreen. It's not a crash or a performance regression. Just broken UX. Frustrating enough to make users rag...
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.
