At Rollbar, we care about reducing the time it takes developers to find and fix errors. This is why we’re making our integration with GitHub even stronger to provide more context around errors and reduce the mean time it takes to resolve them MTTR. Last year, we launched Code Context to show additional lines of code within each frame of the stack trace, reducing the back and forth between GitHub and Rollbar.
In the first post of this series, we looked at the state of your organization, how to tell if Microservices are right for you, and wrapped up with a few challenges this architecture brings to the table. In this article, we will look at organizational changes that will help you adopt a Microservice architecture. Additionally, we will touch on topics like how to bring change to your organization, how to embrace the primacy effect, and why you should embrace cross-functional teams.
It's Friday afternoon and you decide to check on your web logs one last time before you go out for the weekend. Since you've deployed recently, you want to make sure everything is going smoothly. You open your tool and suddenly you find your screen flooded with TypeErrors. Does this sound familiar? JavaScript TypeError is one of the most common browser errors because it wraps a number of different situations, each of which needs to be handled separately.
It's been a busy year at Rollbar! While many of the new features we built got all the needed attention (press, blog posts, conferences), the underlying work to transform and modernize our platform might have been less visible. With this blog post I'd like to share with you all the exciting initiatives we launched in this past year and recognize all the deserved credit for all the engineers that worked restlessly to get us where we proudly are today.
Handling errors properly is essential in building a robust application in Angular. Error handlers provide an opportunity to present friendly information to the user and collect important data for development. In today's age of advanced front-end websites, it's more important than ever to have an effective client-side solution for error handling.
Transitioning from a Monolith to a Microservices architecture can take years to complete. The internet is full of stories of companies famously making this transformation. But how do you know if it’s right for your organization? Is your organization ready? In this article, we will look at five questions you can ask to see if you’ll benefit from a Microservices architecture. We’ll also discuss five challenges you will face during this transformation.
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.
