What is Crashlytics and what are its top alternatives?
Top Alternatives to Crashlytics
- Sentry
Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. ...
- TestFairy
When testing apps in the crowd, you never know what exactly was done, and what went wrong on the client side. TestFairy shows you a video of the exact test that was done, including CPU, memory, GPS, network and a lot more. ...
- Bugsnag
Bugsnag captures errors from your web, mobile and back-end applications, providing instant visibility into user impact. Diagnostic data and tools are included to help your team prioritize, debug and fix exceptions fast. ...
- Google Analytics
Google Analytics lets you measure your advertising ROI as well as track your Flash, video, and social networking sites and applications. ...
- Rollbar
Rollbar is the leading continuous code improvement platform that proactively discovers, predicts, and remediates errors with real-time AI-assisted workflows. With Rollbar, developers continually improve their code and constantly innovate ra ...
- TestFlight
With TestFlight, developers simply upload a build, and the testers can install it directly from their device, over the air. ...
- New Relic
The world’s best software and DevOps teams rely on New Relic to move faster, make better decisions and create best-in-class digital experiences. If you run software, you need to run New Relic. More than 50% of the Fortune 100 do too. ...
- Fabric
Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution. ...
Crashlytics alternatives & related posts
- Consolidates similar errors and makes resolution easy238
- Email Notifications121
- Open source108
- Slack integration84
- Github integration71
- Easy49
- User-friendly interface44
- The most important tool we use in production28
- Hipchat integration18
- Heroku Integration17
- Good documentation15
- Free tier14
- Self-hosted11
- Easy setup9
- Realiable7
- Provides context, and great stack trace6
- Feedback form on error pages4
- Love it baby4
- Gitlab integration3
- Filter by custom tags3
- Super user friendly3
- Captures local variables at each frame in backtraces3
- Easy Integration3
- Performance measurements1
- Confusing UI12
- Bundle size4
related Sentry posts
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.
This is my stack in Application & Data
JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
Slack
- Get video rec of the user on your app8
- Landing Page4
- Better design4
- JIRA Integration3
- Cross-platform2
- Supports Enterprise IPA's (TestFlight doesn't/didn't)2
- GitHub Integration2
- Application full Log information1
- App Distribution1
- Single Sign-On1
- In-App Feedback1
related TestFairy posts
Bugsnag
- Lots of 3rd party integrations45
- Really reliable42
- Includes a free plan37
- No usage or rate limits25
- Design23
- Slack integration21
- Responsive support21
- Free tier19
- Unlimited11
- No Rate6
- Email notifications5
- Great customer support3
- React Native3
- Integrates well with Laravel3
- Reliable, great UI and insights, used for all our apps3
- Error grouping doesn't always work2
- Bad billing model2
related Bugsnag posts
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.
There’s 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’ll be happy to know there’s a Bugsnag integration for it as well!).
- Free1.5K
- Easy setup927
- Data visualization891
- Real-time stats698
- Comprehensive feature set406
- Goals tracking182
- Powerful funnel conversion reporting155
- Customizable reports139
- Custom events try83
- Elastic api53
- Updated regulary15
- Interactive Documentation8
- Google play4
- Walkman music video playlist3
- Industry Standard3
- Advanced ecommerce3
- Irina2
- Easy to integrate2
- Financial Management Challenges -2015h2
- Medium / Channel data split2
- Lifesaver2
- Confusing UX/UI11
- Super complex8
- Very hard to build out funnels6
- Poor web performance metrics4
- Very easy to confuse the user of the analytics3
- Time spent on page isn't accurate out of the box2
related Google Analytics posts
This is my stack in Application & Data
JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
Slack
Functionally, Amplitude and Mixpanel are incredibly similar. They both offer almost all the same functionality around tracking and visualizing user actions for analytics. You can track A/B test results in both. We ended up going with Amplitude at BaseDash because it has a more generous free tier for our uses (10 million actions per month, versus Mixpanel's 1000 monthly tracked users).
Segment isn't meant to compete with these tools, but instead acts as an API to send actions to them, and other analytics tools. If you're just sending event data to one of these tools, you probably don't need Segment. If you're using other analytics tools like Google Analytics and FullStory, Segment makes it easy to send events to all your tools at once.
- Consolidates similar errors by impact74
- Centralize error management64
- Slack integration63
- Github integration58
- Usage based pricing47
- Insane customer support32
- Instant search23
- Heroku integration21
- Consolidate errors by OS18
- Great Free Plan15
- Trello integration15
- Flexible logging (not just exceptions)13
- Simple yet powerful error tracking tool11
- Multiple Language Support9
- Consolidate errors by browser7
- Easy setup6
- Query errors with RQL6
- Best rails exception handler5
- Deployment tracking is a nice free bonus5
- Awesome service5
- Simple and fast integration5
- Easy setup, friendly ui, demo, lots of integrations4
- Beat your users to the error report3
- Server-side + client-side3
- Errors Analysis3
- Clear and concise information.3
- Powerful3
- Mailgun integration2
- Easy integration with sails.js2
- Bitbucket integration2
- Clear errors on deploy or push1
- Easy Set up familiar UI that doesn't make you look dumb1
- Teams1
- Gitlab integration1
related Rollbar posts
Our primary source of monitoring and alerting is Datadog. We’ve got prebuilt dashboards for every scenario and integration with PagerDuty to manage routing any alerts. We’ve definitely scaled past the point where managing dashboards is easy, but we haven’t had time to invest in using features like Anomaly Detection. We’ve started using Honeycomb for some targeted debugging of complex production issues and we are liking what we’ve 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.
- Must have for ios development62
- Beta testing49
- Easy setup20
- Easy way to push out updates for internal testers10
- In-App Updates7
- Crash Logging5
- Checkpoints4
- Multiple platforms3
- Remote Logging2
- Sessions1
related TestFlight posts
I created microservices with Kafka for message queue, Meteor for app development with JavaScript & TestFlight for iOS app development, Elasticsearch for logging SendGrid for automated mails. Git & GitHub for SCM.
New Relic
- Easy setup415
- Really powerful344
- Awesome visualization245
- Ease of use194
- Great ui151
- Free tier106
- Great tool for insights80
- Heroku Integration66
- Market leader55
- Peace of mind49
- Push notifications21
- Email notifications20
- Heroku Add-on17
- Error Detection and Alerting16
- Multiple language support13
- SQL Analysis11
- Server Resources Monitoring11
- Transaction Tracing9
- Apdex Scores8
- Azure Add-on8
- Analysis of CPU, Disk, Memory, and Network7
- Detailed reports7
- Performance of External Services6
- Error Analysis6
- Application Availability Monitoring and Alerting6
- Application Response Times6
- Most Time Consuming Transactions5
- JVM Performance Analyzer (Java)5
- Browser Transaction Tracing4
- Top Database Operations4
- Easy to use4
- Application Map3
- Weekly Performance Email3
- Pagoda Box integration3
- Custom Dashboards3
- Easy to setup2
- Background Jobs Transaction Analysis2
- App Speed Index2
- Super Expensive1
- Team Collaboration Tools1
- Metric Data Retention1
- Metric Data Resolution1
- Worst Transactions by User Dissatisfaction1
- Real User Monitoring Overview1
- Real User Monitoring Analysis and Breakdown1
- Time Comparisons1
- Access to Performance Data API1
- Incident Detection and Alerting1
- Best of the best, what more can you ask for1
- Best monitoring on the market1
- Rails integration1
- Free1
- Proce0
- Price0
- Exceptions0
- Cost0
- Pricing model doesn't suit microservices20
- UI isn't great10
- Expensive7
- Visualizations aren't very helpful7
- Hard to understand why things in your app are breaking5
related New Relic posts
Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.
Current Environment: .NET Core Web app hosted on Microsoft IIS
Future Environment: Web app will be hosted on Microsoft Azure
Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server
Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.
Please advise on the above. Thanks!
I need to choose a monitoring tool for my project, but currently, my application doesn't have much load or many users. My application is not generating GBs of data. We don't want to send the user information to New Relic because it's a 3rd party tool. And we can deploy Kibana locally on our server. What should I use, Kibana or New Relic?
- Python23
- Simple21
- Low learning curve, from bash script to Python power5
- Installation feedback for Twitter App Cards5
- Easy on maintainance3
- Single config file3
- Installation? pip install fabric... Boom3
- Easy to add any type of job3
- Agentless3
- Easily automate any set system automation2
- Flexible1
- Crash Analytics1
- Backward compatibility1
- Remote sudo execution1