Rollbar Reviews

I get the notifications that matter to me about broken stuff in production, saving precious time and allowing me to be ahead of users complaints.

Rollbar has much more than what I actually use at this point, but I'd be using even more if I found the setup process to be smoother.

Ability to view in memory data snapshot and current variable values when exception occurred.

The dashboard could be faster with some default dashboards.

I like to see my errors/warnings and have it work with PagerDuty. Serves an essential purpose, I couldn't go without. The query language is pretty powerful. It is also easy to integrate into my services.

The UI is absolutely the worst. Extremely slow and the toggles/selects are a huge pain. The graphs are near useless. Even the deep linking is bad with the new UI that was recently released. Can't see trends or changes over time.

The query language is good but you can't save them or plot them. Kinda bare bones.

It is my debugging tool of last resort because the UI is so frustrating.

What I like the most about Rollbar is how easy it is to integrate within your code. Providing you with a powerful tool that will help you debugging possible exception that might occur in production, alerting you right away when some errors are happening very often and pointing your right at the line where the error was triggered.

As long as I have been using it I don't have something I dislike about Rollbar. A feature that could improve it significantly could be request tracing, that way you could have all the data in one place to understand quicker what went wrong.

Rollbar is great for logging client-side javascript errors (although they can also log errors from a bunch of other sources), and we use their source-map feature to have useful error reports on our minified code. Rollbar also has useful alerting for when a new issue crops up, or an issue crosses a threshold for number of times seen. When we've gone to them for support we've found it to be great.

Rollbar is reasonably good at de-duping the same errors and grouping them into a single item, although that's not yet flawless. They've also got a query language that we've used a little but, although in our experience it is pretty slow to return results (which could totally be on us).

- Easy integrations make setup a breeze
- Ability to filter errors by environment and assigned level make management great
- Deployment tracking, view errors by user, search errors using SQL-like syntax, deobfuscation of stack traces - more features than you can shake a stick at

- Automatic grouping of errors leaves something to be desired, but this is can be worked around by marking these errors manually

Free package comes with high limits, Github integration is satisfying, easy to setup and manage.

Honestly, nothing so far. Rollbar is the best option when compared to other alternatives, in terms of price/value rate. Most projects can use free version of the Rollbar without any hassle.

The dashboard, filtering features, aggregation capabilities and integration with other tools are the one of the best things of Rollbar.

Deleting the occurrences could be made easier. Had to use API and Python to do the job efficiently.

Rollbar was decently easy to implement into our code and we started collecting info immediately. It's wonderful that it aggregates the errors and warnings together based on the type and gives enough info to start tracking down the issues. The interface is pretty easy to understand as well. The RQL was nice to be able to query against the list of errors for more details or specific traits.

Working with large amounts of instances of the same error or warning can get very frustrating because of the limitations of RQL. Queries would time out. The solution was to either constrain the data by timestamps (guess and check if it times out) or to implement their API and have some scheduled jobs to break the data into more manageable chunks via the same method.

Integration with other tools
Detailed config

Can generate alot of emails at times
Very sensitive, raises errors at the smallest issue which is both good and bad in a way

The ability to aggregate your bug/debug information into a single platform, with the ability to prioritize based on the severity and frequency. Sure beats our shared email inbox "solution". Integration into things like Slack are amazingly useful for highlighting Nth errors.

Inability to setup fine-tuned VCS integration, we have a multi-branch environment and only being able to set 1 git branch for all the environments basically nullifies any use it has outside of the production environment. We have setup all the environments in rollbar but there is no ability to map each to its own git branch.

It's really easy to use, there's a ton of wrappers available for any programming language / framework, and they have an 'always free' formula, which I use for my personal projects

As with any online product, I don't like to pay :) But other than that, I can't say anything bad about it. And as I said, they have a free formula, which is great if you're just working on a small personal project

Setup is relatively easy
Easy to see all the issues
Integrations with jira & slack

The RQL feature is quite difficult to use, most times it times out. I think this will be fixed with further updates.

easy integration, wide support, good error insights

sometimes our issues are spread across staging, production, separate server containers and environments - not sure how to display all of them at once

having troubles tracking errors in Embedded JS (EJS) templates

Good language support. Good both for frontend and backend error tracking. Quick to set up notification (e.g. slack messages) for multiple projects thanks to "copy notification settings from existing project" feature. Very easy to comprehend pricing and packaging.

Grouping of errors could be better out of the box. But it's not like Rollbar is worse than any of the competition in this regards and they do offer manual configuration to solve common grouping mistakes.

We have a rails application with.a large amount of javascript involved. Rollbar does an excellent job capturing rails exceptions. These errors are clear and understandable. The javascript errors are based on the minified version of the code. Javascript errors are not easily actionable. I will need to learn how to use a sourcemap so that I can zero in on the exact cause of the exception.

Needing to use a sourcemap on my javascript files. I could use a good tutorial on how to do this! I have not had any time to do thorough research on creating a sourcemap. Until that is done, though, I'm afraid the javascript exceptions( There are a lot of errors!) are not actionable.

other than recent problems, handles notifications well. Handles overages in a fair way. Allows a lot to be collected.

Search is terrible. It’s very slow and often not found. If I have a problem from a customer it is nearly impossible to find that item (even if they gave us the unique ID we generated).

Rollbar makes it very easy to see where and how frequently bugs in your programs crop up. Rollbar can also be early warnings for other monitoring platforms like Datadog, and indicate something is wrong before your other alarms start going off. The tracebacks on the errors are super helpful and since you can add whatever metadata you want pinpointing problems is made a lot easier.

The error grouping is not also on point, and it's *so easy* to use Rollbar that you will end up spending a lot of time trying to determine which errors actually merit throwing a Rollbar error, and your Rollbar slack channel will definitely get noisy if you don't stay on top of it.

I love the fact that I get very quick notices about an issue with one of our software programs and at the same time it doesn't nag with by sending me a hundred emails.

We still have some Perl scripts (one of our vendor's systems still uses it) and it would be nice to have a Rollbar API for those scripts to prevent getting angry phone calls if the system is having issues.

Rollbar is super easy to use and a breeze to integrate. It has a ton of features like sourcemaps and fingerprinting that work smoothly for thousands of errors a day.

Whenever there's a timeout on rollbar it shows a message that the site is undergoing maintenance. This happens to me at least once a day which is frustrating. The couple of times using Rollbar where the service is down they haven't updated their status page until hours into the incident.

It is easy to set-up, and starting to use it is really easy.

The control panel is pretty good but some times is a little bit confuse.
The reports (PHP) some times are very useless, due to lack of information or too much unnecessary information.
The custom properties are difficult to read (plain structures is not the best way to display JSON information)

The configuration options allowing me to customize the management of multiple projects. And as an addition I really like the diverse tech stack integrations for Rollbar when using diverse programming languages.

The amount of Rollbar API updates, too many to stay up to date reasonably without investing too much time in the maintance of the integration.

Rollbar helps us catch issues in production, and respond to them as quickly as possible. Without Rollbar, we would miss hundreds of issues. Seriously, it's extremely helpful.

The UI makes it a bit difficult to navigate. For example, some hyperlinks navigate to a Rollbar page, while others navigate to the hyperlink's actual URL.

The slack integration so we can very easily alerted about issues that arise in our apps!

Having multiple environments, sometimes a bit hard to get to the correct environment!

It's easy to use and has helped us keep up with anything that goes wrong much faster than if we weren't using it.

The UI can be pretty slow, and I wish there were a dark mode so I can put it on tvs above the developers without being super bright. I also work a lot at night and a dark mode would be great.