Opiniones de Rollbar

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.

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.

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.

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.

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

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

It allows me to track some bugs and act quickly.

Lack of customer support and the bad user interface.

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!

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!

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.

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

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

We didn't experience any cons about Rollbar

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.

- 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

How easy has been to integrate it in our services and software.
The mail notifications that inform you of new errors.

Nothing. For now, It has proven to be a solution for our use case.

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.

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.

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

Log Grouping
Stacktrace with local variables
Enivronment Separation

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.

Saves time. Usability. Features.

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

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 setup and integration with popular frameworks such as Ruby on Rails was easy and we have used it for at least five years with no issues.

Rollbar does a good job trying to group similar errors but of course there is always room for improvement in this area since it requires advanced pattern matching, machine learning, etc.

Uptime, easy to use api, live feed, rql, people tracking, exceptional support

Unified dashboard between projects would be great, but can be implemented with their api

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.

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.

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

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

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.

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.

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