Rollbar Connector

Its been a simple tool to setup. It didn't require a learning curve as with other tools

Sometimes the error on the title does not match the error in the description, so I need to manually check for the error.

We needed a way to get notified of the errors that get missed during testing and also before a customer encounters an error.

Rollbar integrates seamlessly with Ruby on Rails. I've used it in many projects over the years and it's never let me down. It's easy to use and great value for money.

Very little. It's simple and does what it says at a reasonable cost.

It reports errors when I need them in real-time.

The implementation and the integration are super easy, same for sending custom logs or custom info about the user. IMO it is super important for customer support, we have the tool connected to Slack so the first thing we do to start the day is check the channel and check all the errors our users have, you have a lot of information to be able to fix the bug you have in your application. For us it is an essential tool, we use every day.

You can check the API calls you are doing but you cannot have the response from the server, but, I think this is a matter of privacy.

We can know where the application is having bugs and solve them quickly. So, our customers have a fast response from us even before they contact us.

It's easier to use than looking at logs for debugging.

The error grouping. Errors with the same/similar names but different stack traces, e.g. a connection timeout create many Rollbar items. Errors grouped and displaying the different stack traces would help a lot.

Monitor for to many client errors. Debugging failed jobs by finding their stack trace. We retry the job and search for the recent errors to debug.

Definitely their support and communication. They help to solve different problems and help with approach for logging. Also they help to debug grouping issues and create custom rules. I like we can have custom grouping rules.

Default grouping algorithm is not best, but grouping is complex problem. Sometimes grouping does not work well as expected and issues are hidden. You have to make custom rules for custom logging. Some small annoying UI issues are not fixed. Not enough features: - it is hard to manage custom rules - It is hard to use RQL. There should be better way to search, group and do some analytics - RQL is limited. I cannot query on some things - RQL is slow and times out - I cannot build different graphqs and dashboards in UI

We log errors from different apps there. So we can catch errors. We have slack alerts and monitor rollbar daily. It helps to catch errors faster. But we have to use other tools to help debug errors.

It's extremely easy to integrate, but the real power is in the extended functionality. Rollbar telemetry can be a real time-saver, giving the context to user actions that preceded the actual issue. And for the actual deep-dive in errors, RQL (the query language) is invaluable. I'm also a big fan of the Slack notifications and the flexibility they offer.

The mobile view is a bit clunky / overcrowded, though it has been improved greatly in the last year or so.

Having all issues and warnings in the same place / grouped is important for us. Rollbar's Telemetry feature lets us review user's actions that preceed issues, making it easier to solve the more tricky bugs. Also, we're using the notifications system to alert us of unexpected increases of certain problems like timeouts, letting us catch system-wide issues earlier.

The freemium offering makes the solution a great fit for a startup to ensure that error monitoring is covered. The capability scales up with the organisation and event volumes; it's been useful to me and our org from 1 person to 600.

Lack of safeguards is a minor annoyance. In the event that our app, or Rollbar config, is misconfigured it's possible to blow through volume tier allocations for the month in a bad day.

Rollbar does one thing, and one thing well: error reporting. Rollbar gives us complete coverage of front and back end errors.

We started with Rollbar using their Ruby on Rails monitoring and have since expanded to using python, ios, android, javascript, and probably more. They are always responsive to support requests and keep adding extra features. Installation is also extremely straightforward: one of the few pieces of software that truly "Just Works."

Very occasionally Rollbar doesn't provide us enough information to fully debug and issue and we have to fall back to tried and true methods like reading logs, looking at the database, etc.

Rollbar gives us a great snapshot of not only errors but endpoint performance. We use it both reatively when support issues come in and proactively to prevent those issues in the first place.

Rollbar provides an array of features across multiple software languages that allow us to easily implement bug tracking across all our services. With up to the second bug tracking, we are able to quickly track any issues that might come up and keep our customers happy with our quick response. Our team relies on Rollbar to maintain a high level of customer support through their easy integrations to our entire platform. Rollbar also offers great integration with applications like Slack which makes it our primary tool for communicating issues with our team.

Rollbar lacks more in depth AWS integration which would be helpful for apps that also require tracking across AWS or cloud services.

Rollbar gives us the ability to quickly be alerted via Slack about issues that are coming up in our application. This has allowed us to have lightning fast responses to any issues a customer might be facing.

It's straight forward to integrate, the dashboard UX is pretty good and the way we can take actions on each exception is really well designed

It has been lacking out of the box support for a few of the new JS frameworks like NextJS and Remix (we've been talking about this issue tho, they are into it)

I mainly use Rollbar to help me deal with software exceptions and bugs.