Operations | Monitoring | ITSM | DevOps | Cloud

When we first built Rollbar, microservice architectures and continuous delivery practices weren't as common as they are today. Over time, we saw how our customers were setting up different projects for each code repository. As a complex distributed architecture becomes the norm, we want to make sure our core user experience reflects this new normal. Today, we’re introducing the new Rollbar user experience. We hope you like it as much as we have enjoyed building it for you!

We're very exited to bring all the error monitoring and debugging capabilities of Rollbar to Salesforce Apex applications. According to Salesforce, millions of developers and thousands of independent software vendors develop customized applications using Apex to extend the fuctionality of Salesforce. A few months ago, when some of our customers reached out and asked us for an error monitoring solution for their Salesforce Apex developers, our engineering team jumped on the task.

Traditionally, Quality Assurance (QA) has been a very manual process. Our QA teams do an amazing job running through test plans, finding critical bugs, and logging reports. But it can be a lot of work to run through the tests again and again, dig into the errors to provide the contextual information developers need to fix bugs quickly, and prepare the reports your developers need to find and fix errors in the codebase.

We sat down with Rollbar CTO, Cory Virok, for a Q&A on how his leadership role and industry expertise helped create an enterprise solution for today’s modern software company.

What’s better than an SDK that supports iOS? One that also supports macOS! With the latest version of rollbar-ios (v1.8.1), Rollbar now supports crash monitoring for macOS. You can use Rollbar to monitor, triage, and debug crashes and errors on both iOS and macOS. What else, you ask? We’re excited about some significant improvements for both iOS and macOS. Read on for the details. Real-time crash monitoring & debugging for macOS

In this tutorial, you will be introduced to errors tracking in Angular 7 using the errorHandler class and Rollbar. This is the last part of the Angular 7 error handling series, you can refer to the first part here, and the second part here. In this series, you have been introduced earlier to handling client side errors and then HTTP errors gracefully in Angular 7 with tools like errorHandlers, Interceptors and even RxJS operators.

Does your team use Azure DevOps for tracking work? You’re going to love our latest integration if that’s the case. You can now create and resolve Work Items in Azure DevOps directly from Rollbar, making error monitoring and debugging even faster. This is the latest addition to our toolkit for the Microsoft ecosystem (read about our Azure Active Directory integration). It reinforces our mission to help software developers build software quickly and painlessly.

Tools like Rollbar have changed the way development teams are recording and managing their exceptions. What used to be a very personal developer-by-developer activity can now be a team-wide tool for greater transparency, and increased application quality. But many still treat exception monitoring as a developer activity, and they are not leveraging its benefits across all environments, from development to stage and integration, to systems testing and production.

In production, the most important advantage of using a build tool like webpack is a smaller size and thus improved overall application performance. Although beneficial for our users, the bundled and minified code is harder to debug for developers as the code they have written doesn't map 1:1 to error stack traces. Multiple tools for minifying, bundling and transpiring JavaScript modules can generate source maps along with the resulting code.