Rollbar

Vorteile

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.

Nachteile

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.

Vorteile

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.

Nachteile

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.

Vorteile

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.

Nachteile

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.

Vorteile

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.

Nachteile

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.

Vorteile

I have been using Rollbar for more than 2 years now, it’s really easy to use. The best thing is that when you’re setting up a new service it very easy to setup with your standard logger like log4j. And then voila you have your errors in the rollbar dashboard. It is very handy when your releasing. On top of that you can set up slack integration that keeps you alerting when thing are broken. I’d definitely suggest this to my friends and ex-colleagues to use this.

Nachteile

I haven’t faced any cons yet. Only thing notice is if you do not configure your logger properly then it might spam with with errors you don’t care about, But that’s not the problem of the product itself.

Vorteile

The best part about Rollbar is the very even UI that permits you to see all mistakes followed for different situations including testing, arranging, and creation. I love the amazing way simple it is to coordinate with various dialects. Following customer side javascript is overly helpful with full stack follows to show you precisely what turned out badly. It's anything but difficult to see patterns in different bugs and imprint bugs as unraveled without any problem. The arrangement alternatives are generally great arrangements and it's anything but difficult to get ready for action, Rollbar is magnificent!

Nachteile

Here and there it's somewhat hard to tell where to discover a few alternatives on the grounds that they aren't generally similarly situated.
Missing disconnected assembling usefulness for JavaScript, however, I haven't discovered it in any item.

Vorteile

Monitors and alerts on new front-end errors. Easy to use it to investigate customer issues. Implementation is straightforward.

Nachteile

Default email settings can be a bit verbose.

Vorteile

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.

Nachteile

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.

Vorteile

A concise place to find all errors. Easy to hook up to the app.

Nachteile

Many times when I try to use the web app, UI will become buggy. Things will disappear when selected, grouping doesn't work etc. This is especially difficult when I am reacting to an incident.

Vorteile

The product is flexible and powerful. It's very easy to setup and has a lot of great integrations.

Nachteile

Their support responses are slow and they are very, very slow to fix serious bugs.

Vorteile

The ease of getting data into rollbar, and extracting meaningful information out of rollbar's dashboard.

Nachteile

The few times I've wanted to programmatically fetch information about all errors in a project it's not been trivial. It's possible with the API and the right queries via RQL, but it'd be nicer if there was a quicker way to export such data.

Vorteile

There are links that direct you to the line of code in Github.

Nachteile

Sometimes, the software incorrectly group occurrences together while delays proper diagnosis

Vorteile

It is very easy to use and compatible. And value for money.

Nachteile

Advertisement is required so that it get popular. Many people do not know about Capterra.

Vorteile

low latency, aggregates/groups similar errors, historical view

Nachteile

price is a bit high, high learning curve with ui

Vorteile

I like that its stays up to date and has simple yet strong monitoring and reports errors well.

Nachteile

It can be a little hard at first to get used to, but that may be because I'm not tech savvy. Also the graphs aren't that good.