2018

2017

Looking Back on 2016

David Cramer /

2016 was a big year for Sentry. It continued a test to see if we could turn a small idea into a big vision. Just a year prior there were only two of us with an overwhelming audience to support. We finally started to consider the potential and with that vision, began making our first hires. The last year was a continuation of that expedition. We built the team to an amazing 25 people while growing our footprint by an order of magnitude. Hundreds of thousands of developers have put their trust in Sentry to help them continuously ship software. The future is all about more of the past and executing on the trust you’ve given us.

Read more

2016

User Feedback in Laravel

David Cramer /

is a feature that allows you to interact with your customers when they hit an issue. While most of Sentry will justwork out of the box, Feedback requires a bit more work on your end. Today we're goingto try to help you get started so you can get back to shipping

Read more

Sentry + Linode <3 PyCon

David Cramer /

We’re teaming up with Linode to kick off PyCon in style! Join us for drinks and games at Ground Kontrol on Monday night, and come with your questions about how to debug Python and Django error tracking.

Read more

Breadcrumbs in Python

David Cramer /

A couple weeks back we announced Breadcrumbs, with full support in our JavaScript SDK, and the in-progress implementations for other platforms. Today we're going to focus on Breadcrumbs in our Python SDK, what they capture, and how you get started using them.

Read more

Debug Issues Faster with Breadcrumbs

Armin Ronacher /

If there’s one thing we’re particularly proud of Sentry for, it’s that not only does it notify you of new issues in your applications, but that it gives you a lot of helpful tools to help you quickly fix them – like augmented stack traces with surrounding source code, or our HTTP replay tool, or built-in user crash report dialogs (new), just to name a few.

Read more

Logging Laravel Errors with Sentry

David Cramer /

Today we’re announcing native integration with Laravel through our new sentry-laravel package. This is a drastic improvement over our previous support for Laravel error tracking (via Monolog) as it ensures proper stack traces, minimal configuration, and expanded error monitoring features (such as application detection).

Read more

Introducing User Feedback

David Cramer /

Years back it was common place to be using a desktop app, have it crash, and then be prompted for feedback. It’s not as prevalent as it used to be, but you’ll still find that the best desktop software still does this. Take for example Firefox:

Read more

Important change to our email delivery

Eric Feng /

Ensuring our users get email notifications of errors in real-time is a top priority for us. Last week, our email provider Mandrill announced significant changes to their service, prompting us to change outbound email providers. While we are doing everything possible to mitigate effects, for our customers, this means that starting Wednesday, there’s a higher chance your Sentry notifications end up in spam.

Read more

Looking Back on 2015

David Cramer /

In January of 2015, Chris and I sat down and decided it was time to commit to Sentry (no pun intended). We opened our first office here in San Francisco, hired the best people we knew, and set out to take Sentry to an entirely new level. Let’s take a look at what happened in 2015.

Read more

Buffering SQL Writes with Redis

David Cramer /

It’s no secret that one of Sentry’s core technologies is SQL, specifically PostgreSQL. We’re huge advocates of simplicity, and Postgres is one of those tools that’s not only quick to get started with, but can also grow with you. While at our scale very few things are simple, we’ve still managed to keep complexity to a minimum.

Read more

What is Crash Reporting?

David Cramer /

Crash reporting is a critical programming best practice. However, if you’ve never been exposed to the concept before, it can be tough to understand how it works and why it’s valuable. Here is how we look at crash reporting at Sentry.

Read more

Sentry's 2nd Happy Hour in San Francisco

Eric Feng /

We had an awesome turnout at last month’s Happy Hour, thanks to everyone who made it! Our next Happy Hour will be next Tuesday, so come grab a drink on us and meet everyone in the community. We’ll be ready to take on your hairiest JavaScript error questions and even introduce the basics of how to debug Python and handle a PHP exception.

Read more

Capturing Java Exceptions with Sentry

Ted Kaemming /

Getting started with Java exception handling can be an intimidating prospect. The large number of dependency managers, logging frameworks, configuration methods, and programming languages that run on the JVM can create a dizzying number of options for a programmer to choose between, so we’ve put this guide together to help you navigate the world of modern Java error tracking with Sentry.

Read more

Introducing Saved Searches

David Cramer /

If you’ve been staring at your stream this week you probably noticed something a little different. Our predefined filters have been replaced with a new dropdown. That dropdown represents our new Saved Searches feature. It’s been going on eight months since we built initial support the feature on our backend, and we figured it was probably time to expose them to the world.

Read more

Monitoring the Monitor

David Cramer /

At Sentry we aim to make crash reporting pleasant. For us, that means you don’t need to dig into sparse logs to determine what’s going on. The entire the reason the project exists is because that problem had gone unsolved, and we had experienced how painful it was. Unfortunately this leads us back into the hole ourselves, as the battle with recursion means we can’t always rely on Sentry to monitor Sentry. Our problems are also a bit more complex than most SaaS services since we ship an On-Premise solution as well. This means we need to support error monitoring in a way that carries over. So what do we do?

Read more

Happy Hour in San Francisco

David Cramer /

To celebrate the release of Sentry 8 we’re hosting a Happy Hour in San Francisco. Join us for some casual conversation and let us buy you a drink. Come ready with your questions on error monitoring and debugging workflows.

Read more

Internationalization and React

Armin Ronacher /

It’s always nice if a project outgrows your initial vision in a way. This happened for the first time in Sentry a long time ago when translations kept rolling in for languages none of us spoke. This was enabled by the excellent gettext-based internationalization support in Django, and the ability to collaborate on through Transifex which is an online tool where people can contribute translations and discuss the strings and raise issues on them.

Read more

Capture and report JavaScript errors with window.onerror

Ben Vinegar /

onerror is a special browser event that fires whenever an uncaught JavaScript error has been thrown. It’s one of the easiest ways to log client-side errors and report them to your servers. It’s also one of the major mechanisms by which Sentry’s client JavaScript integration (raven-js) works.

Read more

2015

Per-Project Rate Limits

David Cramer /

We’ve received a lot of requests for per-project quotas. Usually this comes up due to a specific project sending the majority of data, which then causes other lower-volume projects to lose events. To solve this we’ve added the ability to set an organization-wide project maximum.

Read more

Notification Digests For All

Ted Kaemming /

Several weeks ago we announced a preview release of notification digests, an error monitoring feature that we have been working on that focuses on reducing notification fatigue. Our goal was to address one of the more frequent pieces of feedback we receive: many users would like to reduce the number of notifications that they receive without resorting to disabling email notifications completely.

Read more

Marking Issues as Fixed in Sentry

David Cramer /

Since its inception Sentry has allowed you to resolve errors – that is, tell the system that the issue is fixed. This made sense if you resolved in Sentry after you deployed your fix live, and the error (hopefully) no longer occurred. While this behavior is simple and straightforward, it didn’t really fit with our workflow. It required our engineers to keep tabs on their fixes and wait until the deploy was finished before resolving the issue in Sentry, which we found distracting, time-consuming, and error-prone.

Read more

Notification Digests Preview

Ted Kaemming /

One of the more frequent pieces of feedback that we hear from users of Sentry is that they’d like to reduce the number of notifications that they receive without resorting to disabling email notifications completely. We’ve been working on and testing an error monitoring feature to address this issue on our own projects for the past several weeks, and we’re ready to open it up to other Sentry users for preliminary testing.

Read more

Welcome Eric Feng

David Cramer /

We’re excited to announce that Eric Feng is officially joining the engineering team, where he’ll be focusing on growth and customer happiness.

Read more

Sentry for HipChat Connect

Armin Ronacher /

Sentry is more useful when notifications arrive exactly where you want them. That’s why we’ve always put emphasis on supporting a wide range of notification systems for any error tracking workflow. Group chat plugins, especially, are among our most popular integrations.

Read more

Debuggable JavaScript in production with Source Maps

Ben Vinegar /

These days, the code you use to write your application isn’t usually the same code that’s deployed in production and interpreted by browsers. Perhaps you’re writing your source code in a language that “compiles” to JavaScript – like CoffeeScript, TypeScript, or the latest standards-body approved version of JavaScript, ECMAScript 2015 (ES6). Or perhaps more likely, you’re minifying your source code in order to reduce the filesize of your deployed scripts. Say, by using a tool like UglifyJS, or Google Closure Compiler.

Read more

Sentry emails get a facelift

Chris Jennings /

Last week we pushed an update to our notification emails. In addition to overhauling the visual design and addressing various legibility issues, we’ve restructured the emails by putting the most important error monitoring bits front and center. They also look much better on mobile.

Read more

Rethinking Roles

David Cramer /

Sentry has a long history of building features to add support to complex organizational security. It’s the reason we support things like multiple and revokable client keys, teams, and a variety of ways to limit the scoping of actions. Somewhere along the way, however, we feel we went a bit too far with our permission matrix. It became too complicated for the average user. Today that is changing with our new Roles.

Read more

Sentry 8 is here

Sentry /

After nearly 2 months of beta testing, bug fixing, and implementing feedback-driven improvements, we’re excited to announce that we have finally pushed the latest version of Sentry live for everybody.

Read more

Single Sign-On is now Open Source

David Cramer /

Sentry has always been a company built on open source fundamentals. In our past jobs we constantly pushed organizations to allow us to open source our work. At Sentry, nobody needs permission to open source code, and as part of that we’re going to keep doubling down on our commitment to providing high quality open source software. Today that includes the release of two of our SSO components, allowing you to use Single Sign-On in the On-Premise version of Sentry for both Google Apps and GitHub Orgs.

Read more

Austin Drinkup

David Cramer /

DjangoCon is in Austin this week and myself, Ted, and Armin will be kicking off Sentry’s first community drinkup. Whether you’re here for the conference or just a local, come have a drink and some conversation on us about Django error tracking.

Read more

rb: A Redis parallelization toolkit for Python

Armin Ronacher /

We love Redis at Sentry. Since the early days it has driven many parts of our system, allowing users to improve error monitoring with rate limiting and caching, as well as powering the entirety of our time series data storage. We have enough data in Redis that a single machine won’t cut it.

Read more

Take Part in the Sentry 8 Beta

David Cramer /

Nearly 18 months ago we began exploring a brand new look for Sentry. Around the same time we also decided to modernize Sentry’s frontend. After many iterations on the technology and the design, we’re happy to finally be able to share it with you.

Read more

Rethinking Sentry's Documentation

Armin Ronacher /

If you have searched for the Sentry or integration docs lately you might have noticed that some things have changed. There are now consolidated docs for Sentry and the raven clients right at docs.sentry.io](https://docs.sentry.io/):

Read more

Transaction ID Wraparound in Postgres

David Cramer /

On Monday, July 20th, Sentry was down for most of the US working day. We deeply regret any issues this may have caused for your team and have taken measures to reduce the risk of this happening in the future. For transparency purposes, and the hope of helping others who may find themselves in this situation, we’ve described the event in detail below.

Read more

Logging Go Errors to Sentry

David Cramer /

So you’re picking up Go and wondering “where did all my exceptions go?” It takes a bit to wrap your head around using Go, especially if you’re coming from an interpreted language. Go error tracking is a lot different from Python error tracking or Ruby error tracking.

Read more

Free for Academia

David Cramer /

For a long time we’ve had an unwritten policy to support students and education. Over the years that has included various organizations, such as Scratch and The Harvard Crimson. In addition we’ve seen hundreds of students use us on their personal projects.

Read more

Driven by Open Source

David Cramer /

Seven years ago I would frequent an IRC channel setup for users of the Django web framework. Like an old-fashioned Stack Overflow, it was a mix of people asking questions and others answering. At some point, someone asked how to log exceptions to the database. While not understanding, it seemed not overly difficult and I helped come up with an example. Shortly afterwards I took that example, threw it into a repository, and committed the first lines of code to what would eventually become Sentry.

Read more

Single Sign-On via Google and New Pricing

David Cramer /

Today we’re launching updated pricing for our Small, Medium, and Large tiers. As we’ve done in the past, you’ll be grandfathered into your existing plan. Grandfathered plans remain the same price with the same error monitoring feature set (and limitations). One caveat to that is the restrictions limited and hobbyist plans (see below).

Read more

Better Team Managment in Sentry

Chris Jennings /

Today we’re rolling out several improvements to the way teams are managed in Sentry. We feel these changes will help your organization become more autonomous, as well as provide ways for its members to reduce any unnecessary noise and improve error monitoring. Here’s a quick look at what’s new:

Read more

Continuous Deployment with Freight

David Cramer /

Early on at Sentry we set up Jenkins to automatically deploy after a passing build. Eventually we wanted better control over where we were deploying, and when (i.e. branch FOO to staging). To solve this we started with simple parameterized builds, and effectively had something working. Unfortunately when it came down to adding external controls we hit the age-old API issues within Jenkins itself.

Read more

Welcome Armin Ronacher

David Cramer /

We’ve been building Sentry the product for a while now, but we’ve only recently begun building Sentry the business. With the overwhelming adoption of both our open source and paid products, it’s become clear that we no longer have a little side project — It’s time to up our game.

Read more

Sentry + Facepunch Studios

Sentry /

Culturally, the common thread at Sentry is gaming. More often than not we’ll close out a day by hopping on voice chat and firing up a game. Lately, that game has been Rust.

Read more

2014

Introducing Organizations

Chris Jennings /

Historically, managing org structure, membership, and billing in Sentry has been a pain. Today we’re announcing several giant steps towards making your error monitoring easier and better.

Read more

OpenSSL Vulnerability and SSL Certificate Changes

David Cramer /

You’ve likely already heard about the recent OpenSSL vulnerability called Heartbleed. We have no indication that any of our systems were compromised, and we’ve taken the best measures we can to ensure integrity throughout. As always, it’s worth noting that it’s never a bad idea to cycle your passwords.

Read more

CCP Games brings Sentry to the PlayStation

Chris Jennings /

CCP Games, the game development powerhouse behind Eve Online and Dust 514, has brought Sentry to the PS3. As they’re one of our largest and most unique customers, we decided to sit down with CCP Game’s Kristján Valur Jónsson to find out more about how his team utilizes Sentry.

Read more

2013

Sentry at Disqus

Sentry /

Since Sentry’s conception at Disqus in early 2010, its use inside has grown considerably. The entire Disqus engineering team (16 people and counting) use Sentry in one way or another, deploying 20 Sentry instances across a wide range of services.

Read more

Sentry lands a sweet new logo

Chris Jennings /

Three months ago David and I decided that it was time to ditch the Helvetica “S” and get ourselves a real logo. It was a difficult task — far more difficult than we anticipated. Over the course of several weeks we had looked at dozens of portfolios, trying our best to find a style we connected with. At the end of this stack of portfolios lived Mackey Saturday.

Read more

We've redesigned Sentry!

Chris Jennings /

Today we’re excited to announce that Sentry has an all new look. After listening to your feedback, we were able to package together a design that boasts a more consistent look, clearer navigation, snappier real-time, and much more. In addition to improving existing functionality, we’ve also introduced a couple of neat error monitoring features.

Read more