• Per-Project Rate Limits

    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.

  • Notification Digests For All

    Several weeks ago we announced a preview release of notification digests, a 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.

  • Marking Issues as Fixed in Sentry

    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.

  • Notification Digests Preview

    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 a 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.

  • Welcome Eric Feng

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

  • Sentry for HipChat Connect

    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. Group chat plugins, especially, are among our most popular integrations.

  • Debuggable JavaScript in production with Source Maps

    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.

  • Sentry emails get a facelift

    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 bits front and center. They also look much better on mobile.

  • Rethinking Roles

    Sentry has a long history of building features to 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.

  • Sentry 8 is here

    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.

  • Single Sign-On is now Open Source

    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.

  • Austin Drinkup

    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.

  • rb: A Redis parallelization toolkit for Python

    We love Redis at Sentry. Since the early days it has driven many parts of our system, ranging from 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.

  • Take Part in the Sentry 8 Beta

    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.

  • Rethinking Sentry's Documentation

    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:

  • Transaction ID Wraparound in Postgres

    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.

  • Logging Go Errors to Sentry

    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 like Python or Ruby.

  • Free for Academia

    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.

  • Driven by Open Source

    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.

  • Single Sign-On via Google and New Pricing

    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 feature set (and limitations). One caveat to that is the restrictions limited and hobbyist plans (see below).

  • Better Team Managment in Sentry

    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. Here’s a quick look at what’s new:

  • Continuous Deployment with Freight

    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.

  • Welcome Armin Ronacher

    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.

  • Sentry + Facepunch Studios

    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.



  • Sentry at Disqus

    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.

  • Sentry lands a sweet new logo

    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.

  • We've redesigned Sentry!

    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 features.