Opiniones de Rollbar

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.

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.

I've used a lot of error tracking tools in the past but I was really pleased with Rollbar.

For node applications it's very well laid out, keys are provided for you server and your client setup.

Errors are tracked and logged for your application, broken down by which side the error occured.

And if an error has been recurring you can track it and log it easily, plus the emails give a good breakdown of the error from the code side.

None at present, I may like the UI navigation to be improved so you can administer the setup quicker but once it's in place it kind of runs itself.

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

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.

The setup is very simple and the instant notifications for any unhandled issues make this product very attractive to use. It is very developer friendly.

I do not have anything to add which I find less useful.

- Price is really good
- It's realy easy to set up
- UI is intuitive and simple
- You can trace logs easily, once you setup 'People' tab
- Integration with slack and other notification tools
- Easy to integrate with Heroku's app

- UI could be somehow better, leaner like a sentry.io
- Features for breadcrumbs or tracing could be easier to implement
- Fingerprinting and error aggregation could be easier to setup, no complicated DSLs

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

- 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

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!

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.

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.

The features are generally fine, and similar to competitors

Their API has had a lot of serious incidents recently that takes hours to resolve

-Has a great integration with our software stack (python + django)so setup is easy and it captures a great amount of debugging information out of the box
-Groups errors nicely, but also moves them up when they occur again
-Good alerting rules

It can be spammy if you have a lot of errors, it's not really Rollbar's fault and there are many tools to ignore spammy errors.

The old version works, after I patched it so it would compile and also so it didn't crash.

I had to patch it so it would compile and and also so it didn't crash.

First time I upgraded the new version was missing crucial features.

The second time I updated, thinking it would be better, but it just crashed our app in a different way.

I've fallen back to the old version twice now.

Your iOS team is not good. Missing basic understanding of Objective-C, Objective-C libraries, and QA.

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.

Dashboard with items is extremely useful. It provides many options to filter & sort all captured errors/warnings/etc. It shows many pieces of information in a clear way.
I like recent updates with custom fingerprinting that allows easier grouping of items.

There are some places that require extra clicking after UI redesign, e.g. "Settings" for project.
I'd like to run RQL faster and have simple editor or code-completion aid to write RQL queries easier.

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

The pricing structure. I have a bunch of small projects with low numbers of users.Per project pricing gets too expensive fast.

Having to fill out multiple free text areas in their marketing survey.

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

Default email settings can be a bit verbose.