Rollbar offers an impressive array of error alerting and notification options for you to choose from, which is awesome! But sometimes we hear from our users that they aren't quite sure how to leverage their notifications to get the best results. What do notifications here at Rollbar do? How do they work? How should you interpret them? And perhaps most importantly, what are the best practices? Let's explore the answers to all these questions today.
When I first started full-time here at Rollbar, I was living in Malaysia for the month, starting a year-long journey around the world that I'm currently still on. While it was certainly fun and exciting to explore Kuala Lumpur, it was a bit more difficult to onboard in a new job when I was 15 hours ahead of the rest of the team. Luckily, everyone here at Rollbar is incredibly flexible and helpful, and we were able to get creative about the onboarding process. If you're considering onboarding a remote employee in a different time zone as the rest of your team, read on for some tips and tricks that should help speed up the process.
Our friends at Losant wanted to share how they built an actual 'error-alarm' using the Rollbar and Losant API's. Enjoy!
When I envision a tech company's smart office, I see tons of dashboards and indicator lights that monitor everything. Efficient monitoring is a critical piece of today's technology stack, and there are always ways to improve. Rollbar already does an impeccable job at alerting you when errors are thrown in your application. But, to increase awareness, accountability, and awesomeness in the office, we can connect Rollbar to our smart office. In this tutorial, we are going to build an office error alarm powered by Rollbar and Losant.
Happy International Women's Day from all of us at Rollbar! To commemorate the day, the women of Rollbar thought it would be great to discuss some of the experiences we have had as women in tech.
Resolving on-call errors can be faster and easier than ever before when you integrate VictorOps and Rollbar. VictorOps is a fantastic on-call management tool that provides incident notifications to engineers to help teams resolve incidents faster and minimize downtime. We're excited to announce that you can now automatically send your Rollbar items to VictorOps, and get alerted to new errors quickly - before your users notice.
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!