An important component of understanding the root cause of an error, and the importance of an error to the business is having additional contextual information about the error. The specific additional data that is important for your errors will be unique for your application and possibly the category of the error. Rollbar provides an easy way to tag your error data with additional custom tags. There are 2 main ways of doing this.
We have introduced a new design for the Item Detail page - as well as helping to investigate & resolve Items more quickly, the layout provides a framework for adding future improvements and also introduces a new style that will roll out across the Rollbar website in future.
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.
Software has changed the world we live and work in. The people behind the code are the real heros, but they require the technology to ship better software, faster. So how do they do this? They have to work smarter, be proactive and respond to problems quickly. Let's look at the top 10 error monitoring tools on the market to help you find the best solution for you and your team.
