Alternatives to Rollbar logo

Alternatives to Rollbar

Sentry, Bugsnag, Airbrake, Crashlytics, and New Relic are the most popular alternatives and competitors to Rollbar.
1.4K
870
+ 1
510

What is Rollbar and what are its top alternatives?

Rollbar helps development teams find and fix errors faster. Quickly pinpoint what鈥檚 broken and why. View exceptions from all of your languages, frameworks, platforms & environments in one place. Get context & insights to defeat all errors.
Rollbar is a tool in the Exception Monitoring category of a tech stack.

Top Alternatives to Rollbar

Rollbar alternatives & related posts

related Sentry posts

Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare | 17 upvotes 404.6K views

For my portfolio websites and my personal OpenSource projects I had started exclusively using React and JavaScript so I needed a way to track any errors that we're happening for my users that I didn't uncover during my personal UAT.

I had narrowed it down to two tools LogRocket and Sentry (I also tried Bugsnag but it did not make the final two). Before I get into this I want to say that both of these tools are amazing and whichever you choose will suit your needs well.

I firstly decided to go with LogRocket the fact that they had a recorded screen capture of what the user was doing when the bug happened was amazing... I could go back and rewatch what the user did to replicate that error, this was fantastic. It was also very easy to setup and get going. They had options for React and Redux.js so you can track all your Redux.js actions. I had a fairly large Redux.js store, this was ended up being a issue, it killed the processing power on my machine, Chrome ended up using 2-4gb of ram, so I quickly disabled the Redux.js option.

After using LogRocket for a month or so I decided to switch to Sentry. I noticed that Sentry was openSorce and everyone was talking about Sentry so I thought I may as well give it a test drive. Setting it up was so easy, I had everything up and running within seconds. It also gives you the option to wrap an errorBoundry in React so get more specific errors. The simplicity of Sentry was a breath of fresh air, it allowed me find the bug that was shown to the user and fix that very simply. The UI for Sentry is beautiful and just really clean to look at, and their emails are also just perfect.

I have decided to stick with Sentry for the long run, I tested pretty much all the JS error loggers and I find Sentry the best.

See more
Bugsnag logo

Bugsnag

962
398
267
Bugsnag provides production error monitoring and management for front-end, mobile and back-end applications
962
398
+ 1
267

related Bugsnag posts

Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare | 17 upvotes 404.6K views

For my portfolio websites and my personal OpenSource projects I had started exclusively using React and JavaScript so I needed a way to track any errors that we're happening for my users that I didn't uncover during my personal UAT.

I had narrowed it down to two tools LogRocket and Sentry (I also tried Bugsnag but it did not make the final two). Before I get into this I want to say that both of these tools are amazing and whichever you choose will suit your needs well.

I firstly decided to go with LogRocket the fact that they had a recorded screen capture of what the user was doing when the bug happened was amazing... I could go back and rewatch what the user did to replicate that error, this was fantastic. It was also very easy to setup and get going. They had options for React and Redux.js so you can track all your Redux.js actions. I had a fairly large Redux.js store, this was ended up being a issue, it killed the processing power on my machine, Chrome ended up using 2-4gb of ram, so I quickly disabled the Redux.js option.

After using LogRocket for a month or so I decided to switch to Sentry. I noticed that Sentry was openSorce and everyone was talking about Sentry so I thought I may as well give it a test drive. Setting it up was so easy, I had everything up and running within seconds. It also gives you the option to wrap an errorBoundry in React so get more specific errors. The simplicity of Sentry was a breath of fresh air, it allowed me find the bug that was shown to the user and fix that very simply. The UI for Sentry is beautiful and just really clean to look at, and their emails are also just perfect.

I have decided to stick with Sentry for the long run, I tested pretty much all the JS error loggers and I find Sentry the best.

See more
James Smith
James Smith
Co-founder and CEO at James Smith | 1 upvotes 82.6K views
Shared insights
on
LeakCanaryLeakCanaryBugsnagBugsnag
at

There鈥檚 a tool called LeakCanary that was built by the team at Square. It detects memory allocations and can spot when this scenario is occurring. LeakCanary has been billed as a memory leak detection library for #Android (and you鈥檒l be happy to know there鈥檚 a Bugsnag integration for it as well!).

See more
New Relic logo

New Relic

16.4K
4.8K
1.9K
SaaS Application Performance Management for Ruby, PHP, .Net, Java, Python, and Node.js Apps.
16.4K
4.8K
+ 1
1.9K

related New Relic posts

Sebastian G臋bski
Sebastian G臋bski
CTO at Shedul/Fresha | 4 upvotes 486K views

Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).

See more
Jerome Dalbert
Jerome Dalbert
Senior Backend Engineer at StackShare | 4 upvotes 220.2K views

We currently monitor performance with the following tools:

  1. Heroku Metrics: our main app is Hosted on Heroku, so it is the best place to get quick server metrics like memory usage, load averages, or response times.
  2. Good old New Relic for detailed general metrics, including transaction times.
  3. Skylight for more specific Rails Controller#action transaction times. Navigating those timings is much better than with New Relic, as you get a clear full breakdown of everything that happens for a given request.

Skylight offers better Rails performance insights, so why use New Relic? Because it does frontend monitoring, while Skylight doesn't. Now that we have a separate frontend app though, our frontend engineers are looking into more specialized frontend monitoring solutions.

Finally, if one of our apps go down, Pingdom alerts us on Slack and texts some of us.

See more

related Datadog posts

Robert Zuber
Robert Zuber
CTO at CircleCI | 8 upvotes 525.3K views

Our primary source of monitoring and alerting is Datadog. We鈥檝e got prebuilt dashboards for every scenario and integration with PagerDuty to manage routing any alerts. We鈥檝e definitely scaled past the point where managing dashboards is easy, but we haven鈥檛 had time to invest in using features like Anomaly Detection. We鈥檝e started using Honeycomb for some targeted debugging of complex production issues and we are liking what we鈥檝e seen. We capture any unhandled exceptions with Rollbar and, if we realize one will keep happening, we quickly convert the metrics to point back to Datadog, to keep Rollbar as clean as possible.

We use Segment to consolidate all of our trackers, the most important of which goes to Amplitude to analyze user patterns. However, if we need a more consolidated view, we push all of our data to our own data warehouse running PostgreSQL; this is available for analytics and dashboard creation through Looker.

See more
Medeti Vamsi Krishna
Medeti Vamsi Krishna

We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

See more
Splunk logo

Splunk

285
379
0
Search, monitor, analyze and visualize machine data
285
379
+ 1
0
PROS OF SPLUNK
    Be the first to leave a pro
    CONS OF SPLUNK
      Be the first to leave a con

      related Splunk posts

      Shared insights
      on
      KibanaKibanaSplunkSplunkGrafanaGrafana

      I use Kibana because it ships with the ELK stack. I don't find it as powerful as Splunk however it is light years above grepping through log files. We previously used Grafana but found it to be annoying to maintain a separate tool outside of the ELK stack. We were able to get everything we needed from Kibana.

      See more