You probably use many tools to get through the day. Do you ever wonder what tools get other people through their days? In our Tools This Engineer Uses series, we explore the routines, systems, and tools your peers rely on to solve problems and accomplish goals.
Errors are expensive; they steal resources allocated for other things and potentially negatively impact revenue and user sentiment. And, for teams comprised of volunteers working in their spare time, errors can take weeks to triage and resolve. So, despite what Google might tell you, Sentry for Good is not merely a solution to your pet’s pesky pheromone problems (although it is clearly also that, if PetSmart’s Google results are any indication).
Welcome to our series of blog posts about all the nitty-gritty details that go into building a great debug experience at scale. Today, we’re looking at Symbolicator, the service that processes all native crash reports and minidumps at Sentry.
There are a lot of things we, at Sentry, love about Rookout, a Sentry Integration Platform early adopter. First of all, Sentry loves purple, and Rookout loves purple. And, Rookout helps fix software in production, and Sentry helps fix software in production. Together, the two tools cut time from error to resolution. Honestly, Rookout and Sentry integrating is just kismet.
Whew. May is over, finally. It’s such a rude month, pretending like its summer when it actually is not summer. Get out of here, May. Anyway, hello, June! Here’s everything we shipped in May. Enjoy.
Whether a team is one person or one hundred, automated testing uncovers issues in an application before the code is deployed to production. The earlier a problem is diagnosed, the cheaper and less impact it has on you (the developer) and the organization.
Over a year ago, we first announced support for Minidumps in Sentry, which allows you to debug crashes from applications written in languages like C, C++, Objective-C and more — regardless of whether you’re targeting Windows, macOS, Linux, iOS, or Android.
Welcome to our series of blog posts about all the nitty-gritty details that go into building a great debug experience at scale. This time, we’re going to cover RAM bundles, which Sentry recently started to support to improve the debugging experience of React Native projects.
For most of 2018, we worked on an overhaul of our underlying event storage system. We’d like to introduce you to the result of this work — Snuba, the primary storage and query service for event data that powers Sentry in production. Backed by ClickHouse, an open source column-oriented database management system, Snuba is now used for search, graphs, issue detail pages, rule processing queries, and every feature mentioned in our push for greater visibility.
We recently tagged our final point release in the Sentry’s 9.x series. Just like old versions of Sentry, this includes a huge swath of bug fixes, improvements, and new features. If you’re on our cloud service, you’ve had access to these (and newer features) for quite a while due to the way we cycle features out. If you’re updating from a previous version of self-hosted Sentry and interested in the major highlights, take a look at our changelog.
