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.
Some of the most common questions we get here at Rollbar deal with source maps:
- What are source maps and what do they do?
- How can you enable source mapping?
- Why aren't your source maps working properly?
We're excited to introduce Andrew Ledvina as the newest member of the Rollbar team and Lead SDK Engineer. The timing couldn't have been more perfect for Andrew to start during our quarterly all-hands last week! He was able to have 1:1 meetings with the team, meet our remote team members in person, join for company outings and happy hours, and get an overall feel for the team!
This week was our first quaterly all-hands of 2017 for the full Rollbar team. This is exciting, as Rollbar are a small and distributed team with members in Barcelona, Fort Worth, Las Vegas, Santa Monica and abroad. Most of us haven't all officially met aside from Slack, Google Hangouts or phone calls, so while we feel like we know one another from working together for some time, this has been long awaited!
Our friends at GorillaStack wanted to share how they set up Rollbar with the Serverless framework, and made a handy tool so you can do the same.
Here at GorillaStack, we are big lovers of the Serverless framework. By default, the Serverless framework uses CloudWatch logs to store any system log messages and output from your lambda code. Pretty quickly, we found ourselves needing to escalate log messages such that we could be notified of application errors and act on them more proactively.
Good news for GitLab users! You can now deep link error stack traces in Rollbar directly to the code in your GitLab repos. Rollbar now supports GitLab's native issue tracking features, allowing you to seemlessly debug and manage new issues as they happen in your existing workflow. We’ve rolled out support for source control for both GitLab.com and self-hosted. Issue tracking only supports Gitlab.com, self-hosted support is coming soon.
Linking source code in GitLab to Rollbar stack traces
Our friends at Cuttlesoft wanted to share how they use Rollbar to detect errors in Ionic built applications. Enjoy!
At Cuttlesoft, we use Rollbar's excellent full-stack error monitoring service for pinpointing and fixing tricky bugs. Our team loves Rollbar for its integrations with other popular services (we get our error notifications via Slack so we’re constantly in the know). For building hybrid mobile and progressive web apps, we generally rely on Ionic. Ionic is an open-source framework for hybrid mobile app development maintained by Drifty. Built with AngularJS and Cordova, Ionic is a popular tool for mobile developers everywhere. To combine these two, we've developed a method for integrating Rollbar error tracking with the Ionic stack.
Happy Holidays Rollbar users! 🎁 We're gifting you a handful of updates to a key feature in Rollbar, the Live Error Feed. We recently rolled out some improved fucntionality to the Live Error Feed, most notably the ability to quickly view and assign ownership of errors with your team. Instantly know who's working on what and ensure that urgent production issues don't get overlooked.
Here's an overview of how these updates will help you and your team members better manage errors in Rollbar: