Need advice about which tool to choose?Ask the StackShare community!
Librato vs Sentry: What are the differences?
Librato: Real-Time Cloud Monitoring. Librato provides a complete solution for monitoring and understanding the metrics that impact your business at all levels of the stack. We provide everything you need to visualize, analyze, and actively alert on the metrics that matter to you; Sentry: Cut time to resolution for app errors from five hours to five minutes. Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time. 500K developers use Sentry to get the code-level context they need to resolve issues at every stage of the app lifecycle.
Librato can be classified as a tool in the "Performance Monitoring" category, while Sentry is grouped under "Exception Monitoring".
Some of the features offered by Librato are:
- REST API accepts any metrics you define
- Turnkey integration with AWS, Heroku, collectd, and more
- Integrates with more than 100 open-source agents, and language bindings
On the other hand, Sentry provides the following key features:
- Real-Time Updates: For the first time, developers can fix code-level issues anywhere in the stack well before users even encounter an error.
- Complete Context: Spend more time where it matters, rather than investing in low-impact issues.
- Integrate Everywhere: Drop-in integration for every major platform, framework, and language -- JavaScript, Python, PHP, Ruby, Node, Java, .NET, mobile.
"Easy setup" is the top reason why over 13 developers like Librato, while over 215 developers mention "Consolidates similar errors and makes resolution easy" as the leading cause for choosing Sentry.
Sentry is an open source tool with 21.4K GitHub stars and 2.45K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
Airbnb, Uber Technologies, and Instagram are some of the popular companies that use Sentry, whereas Librato is used by Heroku, Product Hunt, and Mapbox. Sentry has a broader approval, being mentioned in 1341 company stacks & 434 developers stacks; compared to Librato, which is listed in 61 company stacks and 5 developer stacks.
I essentially inherited a Shopify theme that was originally created by an agency. After discovering a number of errors being thrown in the Dev Console just by scrolling through the website, I needed more visibility over any errors happening in the field. Having used both Sentry and TrackJS, I always got lost in the TrackJS interface, so I felt more comfortable introducing Sentry. The Sentry free tier is also very generous, although it turns out the theme threw over 15k errors in less than a week.
I highly recommend setting up error tracking from day one. Theoretically, you should never need to upgrade from the free tier if you're keeping on top of the errors...
Pros of Librato
- Easy setup14
- Great visualization8
- Heroku integration4
- Free tier3
- Alerting2
Pros of Sentry
- Consolidates similar errors and makes resolution easy237
- 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
Sign up to add or upvote prosMake informed product decisions
Cons of Librato
Cons of Sentry
- Confusing UI12
- Bundle size4
Sign up to add or upvote consMake informed product decisions
What is Librato?
What is Sentry?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Librato?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Librato?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+8
+12+29
+42+31
+22
+39+43