React recently announced the release of version 16 with long standing feature requests including error boundaries, fragments, improved server-side rendering and more. Error boundaries are especially useful so that an error in one small part of the UI doesn’t break your entire application. Instead, it’s better to contain those errors to the affected components and recover gracefully.
Rollbar just added a new feature that allows you to quickly edit and merge hundreds or thousands of items at once. In the past, you could only edit or merge items on a single page, which is limited to 30 items at a time. We added a new link that allows you to apply the change to all items in your view or matching a search. This feature provides a similar user experience to how Gmail lets you select all conversions, and then update or delete them.
We’ve just updated our Rollbar.js and Python libraries, making it easy for you to monitor errors on AWS Lambda. If you’ve been considering building apps with serverless architectures on Lambda, we’ve got the exception tracking covered so you can rest easy.
Serverless architectures have taken resource abstraction to the next level.
We've now gone from having servers hosted and managed in the cloud, to having servers that require zero touch and are ephemeral in nature - they're spun up automatically only when certain events are triggered.
In the screenshot below, we see a timeline showing a complete story of how the user encountered an error. First they loaded the page, typed their email address into the sign up form, validated the email, navigated to an onboarding page, and then the error occurred. This gives clear context on what caused the error and which component needs to be fixed.
One of the more frequently asked questions we hear is: "Doesn't my existing Application Performance Management (APM) solution, such as New Relic, monitor and track errors in our application?"
The short answer is - it’s not enough. They are very complementary and most Rollbar users use both (we do) for various debugging scenarios. APM tools are great at telling you what's slow, when and where exceptions occur. Rollbar provides a lot more contextual information to help you determine what's broken, why they occur, who is affected, and how to fix them. It saves you a substantial amount of time dealing with errors and leaves more time for resolving issues and improving your product experiences.
Let’s see how New Relic and Rollbar compare when it comes to monitoring and managing application errors.
Are your services secure?
In today’s world, you can hardly go a week without reading in the news about security breaches, malware, and more. We’ve already had headline news this year for Wanna Cry, and now there are dozens of copycat malware programs taking advantage of out-of-date systems. Think of all the services that your company uses from error monitoring to logging and APM. Some of them may be delivered by vendors and others set up by internal teams. Did your IT team evaluate these services to determine how secure they are? If not, you might want to reconsider the services you use or who can best deliver them.
Before merging was an option, if the default fingerprinting algorithm didn’t combine occurrences the way you wanted, then you needed to define custom fingerprinting rules. Custom fingerprinting rules require you to learn our JSON-based rule syntax, and that could be a deterrent against setting them up.
Now that you can easily merge errors via the UI, is there still value in setting up custom fingerprinting rules? Absolutely, and this blog post will explain why!
Hopefully you've had the chance to try out our latest feature, error merging. We've heard a lot of positive feedback from our users. They're especially excited to be able to easily merge and un-merge related errors. We thought it would be useful to share how the Rollbar team made this happen from a technical standpoint. If you're interested in the nitty-gritty of how we implemented error merging, read on.
I interviewed Todd Dampier, one of the engineers here at Rollbar who was instrumental in making error merging possible, about what was involved in engineering this feature.