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.

So you want to A/B test your web app. The idea is simple, but the details can get messy, and you don’t want to re-invent the wheel. Services like Optimizely are pretty good, but they can be expensive and full of features you don’t need immediately. In this post, we’ll share how Sentry wrote an experimentation system with minimal work.

We’ve said it before, and we’ll say it again — teamwork makes the dream work. Nothing quite says teamwork like a software development project management tool that focuses heavily on enabling every person on every team to work collaboratively. In this case, that tool is Clubhouse, who also just happens to be an early adopter for the Sentry Integration Platform.

2019 has been a fun year for Sentry, and we’re only a third of the way through it. In four short months, we released a feature set focused on visibility as well as the new Sentry Integration Platform. In between the big stuff, we shipped the following changelog from the past month. Enjoy.

You probably use many tools to get you 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.

Since Sentry started, people have been asking us to build integrations for their favorite services. We get it — developer tools are always better when they work together. As Socrates said, teamwork makes the dream work. We like to help out, and that’s why today we’re launching the Sentry Integration Platform. Now you have the power to build the kind of integrations you want to see in Sentry. No need to wait around for us to do it.

Kubernetes, like a lot of other tools, can be noisy. Errors and warnings often go completely unnoticed in the event stream. Or sometimes they are noticed, but are hard to understand in the context of what else is happening in the cluster. Sentry, unlike a lot of other tools, works to eliminate that noise as much as possible, including Kubernetes-related noise.

Sentry helps developers monitor and fix crashes in real-time. Of course, finding and fixing bugs with Sentry is easier when Sentry itself is set up in a way that minimizes disruption. Our help center and documentation can help with that. We’ve also put together a list of the most common issues our Support team works on with Sentry customers that you’ll find useful (or, at least we hope you do).