Welcome Brett Hoerner

Brett most recently worked at Spredfast, where he helped build out and scale a high throughput data processing pipeline and search cluster. He loves deep dives on databases, distributed systems, virtual machines, and programming languages. He will be working on the Java SDK and helping out with our event processing and storage growth. Brett resides in Austin, Texas and when he’s not working he is busy pacifying his newborn son using his pinky finger.

Welcome Bill Lapcevic

Bill joins Sentry as COO. He comes from New Relic, where he built the Business Development team and later headed up Customer Success, Support, Education, and Renewals. At Sentry, Bill will be helping set the direction of the business side of the company and driving it to new heights. Outside of the office, Bill spends time with his wife, 5 year old son, and 3 year old daughter. He’s also an aspiring catch and release fly fisherman, an a cappella singer, and a strong proponent of the Oxford comma (see what we did there).

Breadcrumbs Come to Node.js

Last year we announced a major new Sentry feature, breadcrumbs, supported by our biggest client libraries with one notable omission: Node.js.

This wasn’t an oversight. Node’s asynchronous nature and cooperative concurrency made breadcrumbs tricky to implement properly. To make it happen, we went back to the drawing board and reworked the Node client library’s internals and API, resulting in:

  • Proper asynchronous context tracking — think thread-local storage, but in a way that fits Node’s concurrency model
  • Callbacks better following Node’s “errback” convention and firing more intuitively
  • An API more closely resembling that of our browser JavaScript client; if you’ve used Raven-js before, Raven-node should feel familiar

But the most exciting part is that our Node client joins our browser JavaScript, Python, and PHP clients in having automatic breadcrumb support!

What are Breadcrumbs?

Breadcrumbs are a trail of events that occurred in your application leading up to a captured error. They can be as simple as generic logging messages, or they can contain rich metadata about the state of your application: network requests, database queries, UI events, navigation changes, or even earlier occurring errors.


Breadcrumbs can be incredibly helpful in reproducing the steps that led to the error you’re debugging. They add critical context to errors that a stack trace alone can’t provide. Once you use them, you won’t go back.

Getting Started

Get the latest version of Raven-node, 1.1.1:

$ npm install raven@1.1.1

Import and initialize the client library with automatic breadcrumbs enabled:

var Raven = require('raven');
Raven.config('your-dsn', {
  autoBreadcrumbs: true

Without any further setup, we’ll now automatically record a handful of useful breadcrumbs:

  • HTTP(S) requests via Node’s core modules
  • Log statements via console.log, console.warn, etc
  • PostgreSQL queries via the pg module

You can record your own custom breadcrumbs, too. In the example Express app below, a breadcrumb is captured to record the results of a cookie parsing step:


// custom Express middleware
app.use(function (req, res, next) {
  // grab cookie headers, do some parsing
    message: 'Parsed cookie',
    category: 'log',
    data: {
      cookie: parsedCookie

app.get('/', function (req, res, next) {
  // do some route handling, knowing that if an exception happens here,
  // your parsed cookie breadcrumb will be associated with it in Sentry


The Node client library’s Express middleware ensures that breadcrumbs captured in a route handler or middleware are associated with the correct request. You might use your own breadcrumbs to track major steps in your request handling pipeline, or to associate data that’s particularly useful for debugging.

For a more detailed summary of recent changes, take a look at the forum post announcement. Our Node client docs have also been updated to reflect the recent API changes and our new recommended usage patterns.

Looking Forward

Breadcrumbs for Node.js are still in the early phase, so we’re looking for feedback and suggestions on anything that we can make better or more useful. Our current plans are to tie automatic breadcrumbs into more database drivers and to eventually enable automatic breadcrumbs by default.

If you have feedback or run into trouble, let us know by posting on our forum or opening an issue on the raven-node GitHub repository.

Filtering Errors from Legacy Browsers

Older browser versions are well known for producing quirky errors that developers prefer to ignore. These errors are a distraction from the real bugs that need to be fixed, and can slowly eat away at your Sentry event quota if you don’t intend to fix them. Sentry provides controls that allow you to filter out these errors so you keep the noise down and don’t waste time and money tracking them.

Filter Legacy Browsers

Sentry previously let you toggle a single setting to filter out our recommended collection of legacy browser versions. Based on frequent requests, we’ve now added more granular customization so you can filter the specific browsers you do and do not want to pay attention to. When you use these filters, the discarded events will not count towards your event quota.

You can enable legacy browser filters in the inbound filters section of your project settings. We hope this feature helps you focus on the browser errors that are most important to you and your team!

Welcome Sam Warburg

We are excited to welcome Sam Warburg to our growth team.

Sam joins Sentry from Dropbox, where he was an early scaler on the enterprise sales team helping customers sync stuff to the cloud. At Sentry, Sam will help drive all things business and focus on delighting customers. When Sam’s not in the office, you can find him on a walk or at the park with his wife and one-year old daughter beat-bo’ing.