Rollbar

Vorteile

I’ve added rollbar to many projects and it was very simple and easy to integrate. Rollbar help and getting started was helpful. The tool is useful to understand what are the weakest parts of the applications and what are the most frequent source or errors.

Nachteile

The error grouping sometimes is not perfect and impacts in how much time I should dedicate to group errors properly in order to identify the real amount of errors and occurrences of the same problem in different parts of the application.

Vorteile

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

Nachteile

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.

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

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

Nachteile

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

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

The live view and simplistic, but informative, interface

Nachteile

Nothing comes to mind with the web interface, but the mobile app is very limited - I cannot even expand the view of the log

In Betracht gezogene Alternativen

Gründe für den Wechsel zu Rollbar

Vorteile

Integration with other tools
Detailed config

Nachteile

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

Vorteile

What I use Rollbar for is also what I like about it. I am able to use it for development (typically in PHP) to debug issues, as well as in Production to monitor any problems with the site.

Nachteile

The only con is that I always struggle to get it up and running on a project. I'm an old school developer and getting everything running using Composer takes so much time to figure out.

Vorteile

It helps narrow down where the issues are stemming from. I've had a client reach out in regards to an issue they were having and I could find out where I needed to look using rollbar.

Nachteile

I don't really have any downsides to using rollbar at this time

Vorteile

Simple to get started and setup with a really good UI.
Track down errors fast and solve them with the extended information Rollbar can provide

Nachteile

Can be expensive if you have a large volume of errors or large traffic site.

Vorteile

Rollbar's integration in our architecture is one of the easiest I have seen so far in terms of any small third-party service. A quick setup with token and environment, and you're done. I like how it can map the errors with timelines and usage. The most amazing thing is its seamless integration with Slack, to which we send all of our critical alerts.

Nachteile

I wrote a Go application for which Rollbar recently announced a client. The integration was easy as usual. However, I couldn't write unit tests around it. I wanted to mock the function calls using the widely accepted method of converting the function to a struct and call via an interface. However, neither the root `rollbar` nor the `rollbar.Client` could be restructured in that way. I finally had to remove the token from the testing environment to control the flow of error messages.
Secondly, in our organisation people routinely shift from tribe to tribe to work on different features. And in some scenarios, certain individuals require temporary access to Rollbar platform to review the magnitude of error messages. I'd like if Rollbar adds an X days pass like feature, where I don't have to revoke their access manually.

Vorteile

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

Nachteile

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

Vorteile

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.

Nachteile

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).

Vorteile

Saves time. Usability. Features.

Nachteile

One in half a year there's a lag between sending an error and seeing it analyzed. Not a big issue though.

Vorteile

I would not recommend rollbar at all given the way they have treated our issues and their lack of response.

Nachteile

They do not take major bugs seriously, and they will not fix them or even reply. Their error reporting does not point to the right file or line. They rely on an orig_trace to be accurate in order to trace issues back to the correct file and line, but that fundamental orig_trace is incorrect, causing all associated error reports to point to the incorrect file and incorrect line. I raised this bug with them 2 months ago.

Vorteile

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

Nachteile

The dashboard could be faster with some default dashboards.

Vorteile

Rollbar reached us out when they detected a problem on our production site and provided their help which was an awesome experience.

Installing Rollbar on our Rails app was very painless.

Love the email notication, as soon as someone sees the error Rollbar send email alert which helps to resolve issue faster.

Nachteile

We noticed that Rollbar also considers AJAX request in page load time, we need an option to disable this.

Vorteile

It's super easy to deploy. You can begin receiving your app's errors in minutes and without compromising a payment. You can pay only when you need to pay and have absolutely flexible plans.
Errors are presented as items, where you can immediately see frequency and a brief description. If you want, you can explore an item to know exactly where it happen (I mean, which line of code and entire stack trace), and even you can see each case to know the exact user operation that throws this error.
You can even search items using a SQL-like language.
Simply awesome.

Nachteile

Sometimes two different items are the same error (algorithm that put together occurrences divides the same error). Anyway, Rollbar allow to merge items with custom rules. Awesome.

Vorteile

I like the versatility of Rollbar as we are able to use it for error logging, system alerts and as a notification system whenever certain events happen.

Nachteile

It is sometimes hard to parse the information in a Rollbar error, specifically the parameters passed in through whatever means. This information does usually exist, but it could be pushed more to the forefront (or perhaps users could have more customization options so that they can configure Rollbar to expose this information).

Vorteile

Simplicity, Ability to integrate with tools and our application to track real-time issue.

Nachteile

None

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

Easy integration, slack notifications, level of details for each error

Nachteile

I would like to be able to see aggregate info from occurences of the same error, Airbrake offers something similar.

Vorteile

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.

Nachteile

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.

Vorteile

Detailed reporting of bugs, from the user who triggered it, to listing of occurrences of a bug, to the availability of a stacktrace.

Nachteile

Setting up filters and environment-specifc grouping can be confusing.

Vorteile

- Tracebacks
- Locals and args captured
- Request and user data
- RQL!

Nachteile

- Not everything can be exported as CSV (yet?)
- More out-of-the box integrations would be very useful (i.e. Celery)

Vorteile

I love how easy it is to drop Rollbar into an application. We deployed Rollbar in under an hour and the event lots started streaming in immediately. Within a day it had helped us solve several production issues.

Nachteile

If you have a larger project, or a particularly chatty application, Rollbar's event limits can quickly push you up into a higher pricing plan and if you don't pay up it will start swallowing errors silently until the quota renews at the end of the month.

Vorteile

It is incredibly useful and detailed with regards to notifying us about bugs, errors and issues within our code or that users are having. We can easily pinpoint the error and issue a fix right away. Rollbar have a great integration with Slack too.

Nachteile

Sometimes it can be a little difficult to identify the user that has had the error or bug.

Vorteile

Very powerful tracing at an individual level, easy to set up, very advanced querying capabilities, smart errors grouping, telemetry feature is quite powerful, the integration with slack is very good with a native experience. Github integration is also great.

Nachteile

Limited capabilities for filtering slack notifications. Suspect deploys produces a lot of fake positives. Automatic grouping doesn't work so well.
The frontend error tracking is too noisy as it detects also errors out of our scope as the errors provoked by browser extensions, bots, non-supported browsers, etc. This makes the frontend tracking useless as we can't trust the alerts as we do for the rest of the stacks.

Vorteile

So There is a lot to unpack here: As a software developer, having access to the WEB DASHBOARD is amazing We start our day and prioritize our work around what we see in this dashboard, the SLACK INTEGRATION makes this process even better, as we can see errors in real time before the end-user and proactively respond without having to call or confirm what the user does thanks to THE WONDERFUL TELEMETRY that we get. Also we build software with Rails, JS, Python, AWS Lambda, and all of your libraries work the same way as expected. Wonderful! You also sent my company a blue rollbar shirt a few years ago - IT WAS SO COMFORTABLE! also: YOUR UPTIME is better than just about anyone - Auth0, Gitlab, Dockerhub - have all had issues this year with uptime , and the most we've seen from you all has only been a small delay in processing. Nothing major.

ADDITIONALLY - I discovered a bug last month with rollbar and reported it to a community rep - AND YOU FIXED IT THIS RELEASE. FAST! As a fellow software developer I know how hard it is to get issues addressed, not to mention prioritized and deployed.

In short I love you, and love your company and I tell everyone that!

Nachteile

I wish I could come up with something, but you astound me. I'd complain about a bug I found in Rollbar Js, but you fixed it in 2.18!

Vorteile

I have enjoyed how easy Rollbar is to set up with Ruby, Javascript and Ruby on Rails. Their libraries made it painless to set up and already start reporting errors. I don't know that half of the errors caught by Rollbar would have been fixed in the short turn around time as if we didn't have Rollbar. Rollbar is also user friendly and they are constantly putting up more features. My favorite feature is with a given error they include the stack-trace in my code and who wrote the code that is erroring out. This is very useful for debugging.

Nachteile

In short the downtime. Albeit very minimal, there have been some days I can remember that Rollbar was down for more than an hour and if I recall correctly a whole work day. These times it made it hard not to worry if anything is breaking or throwing errors. For this reason I have enjoyed having another performance monitoring product.

Vorteile

Rollbar is the best error tracking tool out there. It is easy to set up and use and provides great insights into our application’s performance. The integration with other tools is top notch and the customer service is great. Highly recommended!

Nachteile

The only downside with Rollbar is the cost. It can be a bit expensive for smaller teams or for those just getting started. But the features you get for the cost makes it worth it.

Vorteile

Rollbar was easy to integrate and provides multiple libraries to integrate depending on what languages you're programming in. It reports errors well, it's reliable, the API and libraries are super flexible. I'm sure I only use about 20% of the overall functionality.

Nachteile

Nothing that I *overly* dislike about Rollbar. I think that some of the UI could be improved a bit on the admin dashboard, some things are really nit-picky like I don't like the way that text or lines wrap in certain places. Any complaints I have would be bordering on trivial.

Vorteile

It allows me to track some bugs and act quickly.

Nachteile

Lack of customer support and the bad user interface.

Vorteile

It is easy to use, UI is great, easily integrated with my project. easy to send errors and logs.

Nachteile

UI for seeing the occurrences of an item needs some work, sometimes there are a lot of fields in an occurrence and the horizontal slider was given all the way to the end which is inconvenient.

Vorteile

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.

Nachteile

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.

In Betracht gezogene Alternativen

Gründe für den Wechsel zu Rollbar

Vorteile

The deduplication works well for the most part, and the ability to capture lots of additional information (both automatically and manually) is great. Makes identifying what an issue could be really easy.

Nachteile

Doing custom searches look like they could be really useful but are is really slow compared with more general purpose logging tools like ELK/CloudWatch/Splunk and I wish it was possible to expand and change the time periods of the graphs.

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

Log Grouping
Stacktrace with local variables
Enivronment Separation

Nachteile

Something the grouping can work too well, and errors that are different actually get grouped together. The standards can be a little hard to figure out, and there are multiple ways to do everything.

Vorteile

It's great that it logs errors. And the grouping of errors is sometimes helpful.

Nachteile

That searching for anything other than the unique identifier is almost impossible. Found a work-around using RQL, but that is sometimes hours later by the time the RQL database is populated with recent errors... so basically, we have to reproduce and error and then hurry and click the errors at the top and hope we can maybe find it. It's worse than logging errors to a text file honestly... cause at least I could search that in a reasonable amount of time.

Vorteile

Easy integration with readily available SDKs and code snippets
Grouping of errors
Easy to use webhooks
Value for money
Access Management
Our dev loves rollbar because of the easy integration
Our oncal loves rollbar because of the easy error tracking

Nachteile

Rollbar Query Language (RQL) can be made easy as well as search functionality can be improved
Reporting can also be improved

Vorteile

Love the minimalistic UI, which keeps everything clear and understandable.
Developers constantly add new features, like automatic events grouping, etc.
Love to have all platforms on one Dashboard to look at reported error from different platforms point of view.

Nachteile

The quality of Android SDK isn't the top tier with not enough options for event reporting. Also had to so some adjustments for test suits, since in some cases the SDK wouldn't initialize correctly.

Vorteile

It is simple to customize grouping rules, you can easily propagate notifications settings to all projects so they are matching, easy to customize, easy to integrate.

Nachteile

We have to pay much more to have a simple feature like viewing all projects' errors in a single view.

Vorteile

I like that it sends notifications if something goes wrong and your team can stay alert about it. It's pretty nice to know if something is down or something isn't working. We also use it to track custom events when some logic isn't behaving as expected. For example when server returns a new Key value that is not handled on client side.

Nachteile

The notifications customization is pretty hard and not clear. I tried to turn off some part but I couldn't do it only to myself. You (seems) can only turn it off for the "team". So I end up creating a filter in Gmail.

Vorteile

- 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

Nachteile

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

Vorteile

Rollbar is very easy to configure and use in our stack (Ruby + .NET + React). Rollbar gather error information with many details about situations it occurs.
Interface is very intuitive and have option to set up many notification destinations (we use Slack + daily reports on mail).

Nachteile

We didn't experience any cons about Rollbar

Vorteile

Rollbar was very easy to learn and to navigate, which was a massive plus. Having our own website programmed from the ground-up, it was crucial we had a software that detected and located any errors and/or bugs within our website so they could be fixed/eliminated. Rollbar provides real-time bug tracking, which saved us and our programmer LOADS of time as we located any issues quickly and prevented any possible website crashes/any unnecessary downtime.

Nachteile

I don't have any cons; Rollbar has helped us to the fullest extent.

Vorteile

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.

Nachteile

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.

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

I love the immediate notifications for errors as users see them. Shooting for "Rollbar Zero" on a team can be the best way to reap value from the product. It gives immense visibility into what's failing.

Nachteile

Why it's failing is not often immediately obvious looking at the rollbar; we have to use multiple observability tools to figure that out. I also am not a huge fan of the UI, it's slow and cluttered and deters me from using it all the time.

- Grouping is not great
- If Rollbar goes down or stops sending messages, a lot of visibility is taken away -- it's reliability could be a reason why we don't continue using it in the future.