Sentry

San Francisco, CA, USA
2011
  |  By Will McMullen
Mobile devs know the struggle. Small regressions can cause big issues in production, and fixing them isn't as easy as pushing a quick patch. Unlike a web app, shipping fixes for apps means navigating app store approvals, and often hopping on meetings with customers to debug because mobile issues can be so challenging to recreate. Catching these issues before the 1-star reviews roll in is crucial. Luckily, Sentry just made it easier than ever.
  |  By Armin Ulrich
Which JS framework is the most performant? React, Vue, Svelte, Angular,…? When trying to answer this question, we often get lost in comparing benchmarks for reactivity, bundle size, memory usage and other factors. Of course we want to choose the best framework to create performant apps! But your app will only benefit from framework performance if you also follow best practices for performance optimization of web apps in general, and React apps in particular. So, where to start?
  |  By Sasha Blumenfeld
Bugs don’t announce themselves politely. They crash your checkout flow, break authentication, or slow your API to a crawl—usually right before your CEO asks how things are going. And when the error inbox is flooded with a hundred variations of TypeError: cannot read property of undefined, figuring out what actually matters can feel impossible.
  |  By Sasha Blumenfeld
Even at Sentry, we're not immune to downtime. In a moment of "oh-the-irony," we once took down our own application with a bad migration. We were adding a field to a critical database table, and the migration locked it completely. Since this table was essential to Sentry’s operation, the entire app went down. The website wouldn’t load, ingestion paused—everything ground to a halt.
  |  By Richard C.
This guide explains how errors work in PHP and how to debug them efficiently using logging functions and Sentry. The information in this guide is correct for PHP 8 and perhaps above, depending on how much future PHP versions change.
  |  By Tillman Elser
Sentry uses Issue Grouping to aggregate identical errors and prevent duplicate issues from being created, and duplicate alerts being sent. One of the chief complaints we’ve heard from our users is that in some cases the existing algorithm did not sufficiently group similar errors together, and Sentry would create separate issues and alerts, causing unnecessary disruption–or at least annoyance–to developers.
  |  By Will McMullen
We’ve all worked on that app that hangs just a little too long in weird places, or had that query we could never get to perform just right. The network waterfall in Chrome DevTools can’t quite show us what’s going on behind the scenes, and tracing with OTel (and honestly, tracing in Sentry) was just… hard. Today that changes.
  |  By Bruno Garcia
Sentry integrates directly with the tools you already use, giving you real-time crash and performance insights for Unity, Unreal Engine, and Godot. No matter what engine you use, Sentry helps you find and fix issues before they impact your players.
  |  By Abdul D
During the development of your program, you might rely on simple println() statements to trace program execution flows and identify issues in your code. But as projects grow in size and complexity, print statements quickly become messy. A better approach to tracing program execution is logging, an approach that provides a consistent and organized way to track your application’s behavior, allowing you to systematically identify and resolve issues.
  |  By Steven Eubank
When debugging issues in production, context is everything. While Sentry already provides rich error data like stack traces, breadcrumbs, and user information, understanding the application state at the time of an error can still help reproduce, fix and ship quickly. Sentry’s Pinia integration solves this by automatically capturing Pinia state wherever errors occur. Now you get the complete picture of your Vue or Nuxt application's state at the moment things went wrong.
  |  By Sentry
Autofix from Sentry takes all the context Sentry captures around errors and crashes in your code, and uses AI to determine root causes, propose solutions, and even pull a PR to fix it. Autofix allows you to add additional context as needed, and help influence the solution. Code breaks, it happens. Autofix helps you fix it and get back up and running.
  |  By Sentry
First episode of Breakpoint with Sentry is here! We're talking all things Robots and Autofix, A brand new Issues refresh, Uptime watching for your downtime, and Dev Toolbars with red flags and feature flags galore. This is Breakpoint!
  |  By Sentry
In this video, we walk through how to debug faster with the new Sentry Dev Toolbar, specifically when you're also monitoring errors behind Feature Flags. See how you can track feature rollouts, catch errors tied to specific flags, and get real-time insights without leaving your app.
  |  By Sentry
Uptime Monitoring in Sentry has arrived! Cody from Sentry's developer experience team takes you through how to configure uptime monitors to monitor not just website status, but also how it uses tracing to help troubleshoot and debug issues.
  |  By Sentry
Join Sentry Solutions Engineer Simon Zhong for an introductory demo on accelerating Android debugging with Sentry.
  |  By Sentry
Join Sentry Solutions Engineer Karan Pujji for an introductory demo on accelerating iOS debugging with Sentry. Watch the demo to see Sentry in action.
  |  By Sentry
Debugging is like solving a puzzle. Sentry's new issue view is designed to give you more clues when solving your puzzles, so you can debug faster, and get back to building.
  |  By Sentry
We've been messing with AI, and we came up with a feature that automatically fixes your bugs for you!
  |  By Sentry
The Trace Explorer is a new way to query and visualize the application metrics from the traces and spans within your applications. In this video, Cody from the Sentry Developer Experience team shows you how you can get started using it. Want to dive in and find your slow database queries, or what pages or components are loading the slowest? Trace Explorer is the best way to do it - and gives you an easy path to jumping into the spans that make up all actions within your application.
  |  By Sentry
You get a crash report: “App crashed on checkout page.” But you can’t reproduce it on your Pixel. Maybe it’s only happening on a Samsung device? Maybe it’s a memory issue? Or maybe the user was on a bad network? Now you’re stuck digging through logs, guessing at settings, and running the same scenario over and over in your emulator.

Open-source error tracking that helps developers monitor and fix crashes in real time. Iterate continuously. Boost efficiency. Improve user experience.

Sentry provides open source error tracking that gives you insight into every crash in your stack as it happens, with the details needed to prioritize, identify, reproduce, and fix each issue. Sentry supports all popular languages and platforms, and offers a perspective that enables you to see which errors are doing the most harm to your business and help you understand how issues affect your bottom line.

Find out about exceptions right away. Set up Sentry in minutes with just a few lines of code. Get notifications via email, SMS, or chat as part of an existing workflow when errors occur or resurface.

Quickly find and fix production errors. Triage, reproduce, and resolve errors with max efficiency and visibility. Exception handling with Sentry helps developers build better apps and iterate faster.

See the impact of each release. Integrate error tracking with your commit and deploy workflows. Aggregate events to see where bugs happen, how often, and who's affected before users even notice.

Error tracking built for community. Sentry started as and remains a 100% open-source project, now delivered as a hosted service. Development aligns to security, observability, and production at scale.

Users and logs provide clues. Sentry provides answers.