We’re excited to share a significant update to all Rollbar plans in the next few weeks. We’ve redesigned our item detail page with a new mobile layout, prioritized important error context, display occurrence details more clearly, and put all actions at your fingertips. With our new UI, we are confident you will work more efficiently, so you can resolve errors quickly and get back to your essential work.
Debugging errors in your software often requires browsing stack traces (also called as backtraces or tracebacks). A stack trace is a sequence of stack frames which represents the chain of methods calling each other in your software. Rollbar collects your stack trace at the time a crash occurs – this way you will be able to know which pieces of code were active when an issue happened. You can find how to read stack traces in our previous blog post.
The database is one of the most critical components here at Rollbar and its performance ripples across most of our SLOs. One of our goals last months has been to remove unnecessary or repetitive load from it as much as possible. Caching queries is the 101 solution whenever you need to keep scaling up while maintaining, or even reducing, database costs (very relevant these days). Here’s an example of how just one query has been drastically reduced thanks to caching.
We are very lucky on the Rollbar Customer Engineering Team because we get to work with many many development teams. Each team develops, tests, and deploys their applications in their own way. They have chosen different languages and frameworks to solve their particular problem. We learn from each team that we work with, and share these learnings to our Product Design team.
One of the hardest tasks for software engineers is often having to stop what you are doing and look into a software bug (error), find the root cause and fix it quickly. This is hard because you may have never seen the affected code (someone else wrote it), it could be code you wrote a long time ago or just the context switching from what you are working on right now.
To enhance user experience, avoid data loss, and guard against security vulnerabilities, frontend errors must be handled properly. In this post, we'll cover the most common types of frontend errors and best practices for handling them. We'll also explore how to use the popular error monitoring platform Rollbar to track and manage errors.
What’s better than great support? Live in-app support with a real person when you need it During the last two months we have been rolling out our live chat capability for all Rollbar users regardless of the plan you are on. That's right; you can now speak to a real person from our customer engineering team to help answer your product related question from within the Rollbar application. Our goal is to provide more support channels when you need it without having to wait for an answer.
Rollbar was founded with the belief that done is better than perfect. Building software is complex and it's better to move quickly and manage risk intelligently rather than try to build perfect code. For the past decade, Rollbar has provided peace of mind to hundreds of thousands of developers by monitoring production environments for errors. The tool has been leveraged to find and fix bugs in a fraction of the time and is trusted by the individual developers to at-scale enterprises.
We are pleased to announce that an independent service auditor has certified that Rollbar meets SOC 2 Type II criteria and also SOC3 criteria. This extends our security, data privacy, and compliance certifications. Last year Rollbar was certified to meet SOC Type I to go with our existing ISO 27001 certification. The ISO 27001 standard promotes continuous improvement of security processes and demonstrates our commitment to customer support, customer excellence, and data privacy and security.
Rollbar is adopting the updated Oauth 2.0 flow created by Slack. Slack has revised their access tokens and now allows the Rollbar Slack bot to have its own credentials. This replaces the use of member’s credentials.
