New Sentry Pricing: Outcomes and Observability for Everyone
With outcomes-oriented pricing, improve observability and error monitoring without worrying about event caps. Focus on building awesome apps, not counting bugs.
With outcomes-oriented pricing, improve observability and error monitoring without worrying about event caps. Focus on building awesome apps, not counting bugs.
Elizabeth Campbell joins the Sentry team
Come hang out and join us for some food, drinks, games and fun with the community.
Introducing commit data with Heroku Releases
Sentry is nine years old!
Bring more people in the loop with mentions
Ryan Goldman joins the Sentry team
Have the tools you need to confidently guide deploys across the finish line.
Dena Metili Mwangi joins the Sentry team
Connect a repository to add commit data to Sentry
Erik Lee joins Sentry's business team
Jan Crisostomo joins Sentry's operations team
Some in depth information about how symbolication of crash reports on iOS works.
In March, Sentry hosted an open source sprint for the SF Python community.
Evan Ralston joins Sentry's operations team
Spare your inbox from noisy unwanted errors with these helpful tips.
Kelly Carino joins the Sentry team
Offical React Native Support
We improved our development experience for iOS.
How we took eggs out of the S3 basket.
Brett Hoerner joins the Sentry team
Bill Lapcevic joins as COO
Sentry's Node.js client now supports automatic breadcrumbs
We've added new filters to give you more granular control when you want to ignore errors from legacy browsers.
Sam Warburg joins business ops.
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.
We’re discarding our old, arbitrarily-capped plans and are moving to a single, usage-based plan.
Sentry is now certified under the EU-U.S. Privacy Shield.
Sentry Swift client launches for iOS, tvOS, macOS and watchOS
Daniel Griesser joins us in Vienna.
Create Asana tasks easily from your Sentry issues
Saloni Dudziak joins finance.
Sukhpreet Sembhi joins the growth team.
Jess Allen joins the customer success team.
The Sentry team is ending the year with a few more conferences up our sleeve and we’re super excited to be hitting the road once again.
What does Open Source mean at Sentry? We're refreshing our commitment to open source and how we build Sentry.
Why your JavaScript events are coming in quicker now.
Meredith Heller joins the engineering team.
Diagnose user issues faster with Sentry and JIRA Service Desk
Sentry issue tracking integrations now allow users to link to existing issues.
Max Bittker joins the engineering team.
Use inbound data filters to automatically reject unwanted issues.
Christina Nguyen joins us to help build the Sentry community and events programs.
Sentry.io has a new look!
We've migrated Sentry to a new domain.
We're excited to announce that Lewis Ellis is joining the engineering team.
Use redux-raven-middleware to attach Redux app state and logs to Sentry crash reports.
Sentry now supports Vue.js, including Vue 2
We hit 10,000 stars on GitHub this week.
We're excited to announce that Katie Lundsgaard is joining the engineering team.
Sentry now automatically expands minified errors from production React apps.
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
We've shipped a small update today to give you deeper insight into the impact of issues across releases and environments.
Sentry now fully supports Cocoa, with both Swift and Objective-C clients
We've shipped new notifications to make project management a little bit easier.
Fresh off our latest Sentry 8.6 release, we wanted to explain how we version Sentry and why it matters to you.
Sentry now supports Angular 2 with full TypeScript support
You can now use U2F devices (like yubikeys), Google Authenticator (or similar apps supporting TOTP), or SMS as second factor authentication.
Learn how Opera uses Sentry to monitor for errors in their backend services, including how they built an open source tool, sentrycli, to help triage Sentry errors.
On June 12th, we were alerted to a vulnerability in our backup infrastructure. After investigating the issue we have concluded that no data has been accessed.
If you’re sick of the mystery man avatar, we just made Sentry avatars a little bit better.
Continuing on our JavaScript and Python breadcrumb announcements we're happy announce native support in our PHP SDK.
We’re teaming up with Linode to kick off PyCon in style! Join us for drinks and games at Ground Kontrol on Monday night.
With the launch of Bitbucket’s continuous delivery service, Atlassian has been working with Sentry to create a Bitbucket Pipelines integration.
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.
If you’ve done any work with the JavaScript `onerror` event before, you’ve probably come across the following: "Script error."
Following up on our native Laravel integration, we’re happy to announce native integration with Symfony via the sentry-symfony package.
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.
Our design team has grown one person larger with the addition of Cameron McEfee.
Today we’re announcing native integration with Laravel through our new sentry-laravel package. This is a drastic improvement over our previous support (via Monolog) as it ensures proper stacktraces, minimal configuration, and expanded features (such as application detection).
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:
We’re excited to announce that James Cunningham is joining the engineering team.
We’re excited to announce that Jess MacQueen is joining the engineering team.
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.
Our next Happy Hour will be next Tuesday, so come grab a drink on us and meet everyone in the community.
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.
Sentry team members are packing their bags and heading out on the road! We’re sending representatives to conferences all around the world this year, and are super excited to announce our Spring lineup.
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.
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.
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.
In our client JavaScript SDK – Raven.js – we make use of a lot of function wrapping. We even provide a utility API method, Raven.wrap, that automatically wraps a function in try/catch and passes any caught errors to Raven.captureException, Raven’s primary error reporting function.
Getting started with exception reporting in Java 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 exception tracking with Sentry.
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.
We’re thrilled to have Theresa Vermeersch joining our team!
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 monitoring in a way that carries over. So what do we do?
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.
$ git diff --stat 7.7.4..8.0.0 [...] 1548 files changed, 196150 insertions(+), 132725 deletions(-)
It’s always nice if a project outgrows yourself 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.
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.
We’ve just released version 2.0.0 of our client JavaScript integration library, Raven.js. This version introduces some important major changes from 1.3.0. Let’s go over them.
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.
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.
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.
We pushed out a minor, but long overdue feature today: Snoozing.
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.
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 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.
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.
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.
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.
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.
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.
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.
We’re excited to announce that Ted Kaemming is joining the engineering team at Sentry.
We’re excited to announce that Matt Robenolt is officially joining the engineering team at Sentry.
Earlier this month we announced a brand new version of Sentry, “version 8”, which you can try today at beta.getsentry.com.
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.
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.
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:
We’re excited to announce that Ben Vinegar is joining the engineering team at Sentry.
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.
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.
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.
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.
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).
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:
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.
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.
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.
Today we’re excited to introduce the Sentry API, which will help ops teams and developers integrate Sentry deeper into their workflows.
Historically, managing org structure, membership, and billing in Sentry has been a pain. Today we’re announcing several giant steps towards making this better.
Watch our very own Matt Robenolt speak about the current state of javascript exceptions and stacktraces at this year’s JSConf.
You’ve likely already heard about the recent OpenSSL vulnerability. 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.
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.
We recently sat down with Yonas Beshawred, founder of Leanstack.io, and talked about how Sentry came to be.
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.
In perhaps our favorite interview of the day, Philip Forget, CTO of Readability, tells Dev Toolkit that Sentry is crucial to keeping their tech up and running:
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.
Today we’re launching the first draft of alerts in 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.
We’ve recently been working on improving our support in various clients, and in the latest round of changes that focus has been on PHP.